Reporting Services :: Connection Failure / Timeout Or Low Disk Condition Within Database

Dec 3, 2010

I have started getting this error since a week now when I try to schedule a report or change a schedule of a report. An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError) Get Online support For more information about this error navigate to the report server on the local server machine, or enable remote errors..

We have SQL Server 2008 installed along with SSRS running on the server. I have never seen this happening before for almost a year now but suddenly it appeared.  Along with this, report subscription is also messed up and some report are not been emailed as they have a error like..Failure sending mail: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.Mail will not be resent. 

View 19 Replies


ADVERTISEMENT

Connection Timeout In Visual Studio 2005(Reporting Services)

Oct 26, 2007

Hello.



I am having problems with a couple of queries in the Development Studio (Reporting Services 205). I am working on a report that runs a lot of functions so I expect it to be slow. But it times out in 30 seconds.



Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.




The report finishes when clicking on the preview tab but not when on the data tab. If finishes fine when deployed as well. Is there a way to increase the amount of time the query designer in Visual Studio takes to time out on a query?



I have tried setting the Connect Timeout=60 on the Data Source but it seems to be overridden by a setting in Visual Studio 2005.



Thanks much for any help.



Leo

View 3 Replies View Related

Reporting Services :: SSRS IIF One Condition Or IIF Another Condition

Jun 22, 2015

I  am trying to write an visibility function to have message shown based on two different IIF  conditions:

If behavior is to Add a customer ( if message =NAME ALREADY EXISTS, return " NAME ALREADY EXISTS",    otherwize return " NAME CREATED")If behavior is to  Delete a customer (( if message =NAME DOES NOT EXIST, return "NAME DOES NOT EXIST",    otherwize return "NAME SUCCESSFULLY DELETED")
I tried the following which doesn't work:
=IIF((UCase(First(Fields!Message.Value, "DataSetName")) = "NAME ALREADY EXISTS"), "WARNING: NAME ALREADY EXIST", "NAME  CREATED"),
IIF((UCase(First(Fields!Message.Value,  "DataSetName")) = " NAME DOES NOT EXIST"), "WARNING: NAME DOES NOT EXIST", " NAME DELETED")

View 6 Replies View Related

Integration Services :: Shared Memory Provider - Timeout Error 258 / Communication Link Failure

Apr 1, 2014

When running the etl I'm getting the error: <SSIS Task>: Shared Memory Provider: Timeout error [258] ; followed by the message "Communication link failure".

What is special about this message that it happens on a SQL Execute task (random task) and the Timeout is after 2 minutes.

When executing the packages separatly it is working fine. The SQL Tasks that are failing are also quit heavy, but reasonable and takes between >2min and 10 - 15 min. Statements are stored procedures that puts an index on 3 mil. records or update statements,...

I had a look to all my (SSIS-etl) timeouts and they have the default value 0, the "remote query timeout" of the server is set to 10 minutes. According to me, these are the only one that exists?

There are 2instances on the server each instance has 24GB allocated, the server has 64 in total. Also when the etl runs (that results in an error) no other etl is running on the 2 instances. I'm working with the oledb sql server native client11.0 provider : SQLNCLI11.1.

View 7 Replies View Related

Reporting Services Configuration (Database Connection)

Nov 9, 2006

Hi,

I want to configure my Reporting Service.

And if I want to configure the Database Connection I the action

"Create a Grants Rights Script" fails.

I tried all credential types by it doesn't work.



Does anybody have an idea? Thanks for your help!



Jo-Jo

View 3 Replies View Related

Reporting Services :: Sum Values Based On IIF Condition

Oct 9, 2015

I am using SQL server 2012 and Report builder 3.0 to build my report. I have build a  report which product the following table

What I try to achieve is to add 2 calculated field at the bottom of the table which will represent 2 Total value based on a condition

OutTotal field should show the SUM of the Quantity only for ItemStatus=0
InTotal field should show the SUM of the Quantity only for ItemStatus=1

IMPORTANT : I cannot group my data because I need to shown them in a time Wise flow

I have try to insert the first field and define an expression but it gives an #Error. The expression I used is as below

=SUM(IIF(Fields!ItemStatus.Value = 0, Fields!ItemQuantity.Value*Fields!ItemUnitWeight.Value,0))
 
The Quantity filed in my table is calculated from expression Fields!ItemQuantity.Value*Fields!ItemUnitWeight.Value

View 2 Replies View Related

Reporting Services :: Daily Report For Disk Space

Aug 17, 2015

I want to send a status report for disk space such as :

Server Name 
Drive | Total disk space | free space | used in %  

I want do this for multiple server in one SSRS report or HTML format 

View 7 Replies View Related

Reporting Services :: Use IIF IsNothing Expression And Check Another Condition?

Jul 29, 2015

Is it possible to use a IIF IsNothing expression and check another condition? For all the values that are blank, I want it to check another column if  "Disposition" = 2 then I want to show "Inactive"

=iif(isnothing(Fields!Value)," ","MS " & Fields!Value)

View 3 Replies View Related

Reporting Services :: Find Items With Type Name Search Condition

May 17, 2012

The following 

SearchCondition[] sc = {new SearchCondition() {                                               
Name = "TypeName"
,Values = new string[] {"Report"}         
,Condition = ConditionEnum.Equals
,ConditionSpecified = true
}};
catalogItems = ReportService2010.FindItems("/"
,BooleanOperatorEnum.And
,new Property[] {new Property(){Name = "Recursive",Value="True"}}
,sc
);

Returns the following error

System.Web.Services.Protocols.SoapException: The TypeName field has a value that is not valid. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidElementException: The TypeName field has a value that is not valid.
at Microsoft.ReportingServices.WebServer.ReportingService2010Impl.FindItems(String Folder, BooleanOperatorEnum BooleanOperator, Property[] SearchOptions, SearchCondition[] SearchConditions, CatalogItem[]& Items)
   at Microsoft.ReportingServices.WebServer.ReportingService2010.FindItems(String Folder, BooleanOperatorEnum BooleanOperator, Property[] SearchOptions, SearchCondition[] SearchConditions, CatalogItem[]& Items)

The type appears to be correct. I've tried type of "Folder" and receive the same error.

View 5 Replies View Related

Reporting Services :: In SSRS Report IIF Condition With Value 0 Was Displaying As Error

Sep 22, 2015

I am having 3 columns like A,B,C. In the C column I am having calculations like 

=CInt(IIf(B=0,100,((A-B)/B)*100))

After this calculation if the column B is 0(zero) corresponding C column get display as "#Error",  if B is not having 0 every thing is working fine.

In the calculation if I remove the " /B" it is working fine. So, how to display the value 100 in C if B=0.

View 5 Replies View Related

Reporting Services: Timeout Issue

Jan 9, 2006

Hi there,

I've just developed this big report in RS SQL 2000 that includes 6 subreports (repeated for each item in the database) and that should print some 800 pages. A light version of the report that only queries part of the data (about 10%, for testing purposes) run with success, including all subreports in about 15 minutes. Once I try to test the report with all the data (all subreports and the main report query directly from the cube in AS), it fails under three different scenarios:

1st: The timeout setting is left as the default 1800 seconds. After half an hour the report gets partially displayed and the subreports that were not processed within the 30 minutes period display only "The subreport data could not be displayed".

2nd: The timeout value is set not to time out. After about 2 hours, the report fails ("The page cannot be displayed"). I checked all log files and the only one I could identify as related to this was the following:

SQL Server Scheduled Job 'ReportScheduler_CreateJobs' (0x4A64EE6822172C478B4DBF1E385699D6) - Status: Failed - Invoked on: 2006-01-09 13:00:00 - Message: The job failed. The Job was invoked by Schedule 1 (DailyRun). The last step to run was step 1 (spc_sched_CreateJobs).

3rd: Tried to export the file to PDF instead of rendering as HTML. I got the message on the page "Action Cancelled" and an IE message box displaying a "Permission Denied" error.

I've tried many things and ran out of ideas. If anyone could give me any suggestions, I'd greatly appreciate it.

Thanks,

Érico Maia

 

 

 

 

 

View 6 Replies View Related

Reporting Services Timeout Problem

Feb 8, 2008



Hi,

We just started to use Reporting Services in integrated mode (SQL Server 2005, MOSS 2007). The huge problem is we unable to build models of big databases:

"Server was unable to process request. ---> The operation has timed out "

The process teminates correctly if database is small enouth to finish model building under appoximatly 100 sec. Curently I increased timeout values in site and RS service config files:

rsreportserver.config:
<Add Key="SQLCommandTimeoutSeconds" Value="2400"/>
<Add Key="DatabaseQueryTimeout" Value="9000"/>


site web.config :
<httpRuntime maxRequestLength="51200" executionTimeout="9000" />


Still having same problem. Any suggestions where I can find that 100 sec value? Please help.

View 2 Replies View Related

Reporting Services :: How To Create Multi-valued Parameter For Only One Specific Condition

Jul 21, 2015

I have report where i should create a report which is multivalued parametr report,but here my condition is i want to see only one county name  in my output that is Ex: Asia Specific (CountryName),I dnt want to see the other Country names,So how should we create for this condition .

View 5 Replies View Related

Reporting Services Timeout But Query Keep Running?

Apr 2, 2008

The Gobal value for the reporting timeout is 10 minutes (600).

I Have a report which takes around (1hr to run).. The report correctly timesout (page cannot be display)
but the query kept on running..until it completed.

Is there any way to stop this from happening (Report and Query timeout after 10 minutes)

I have look on the internet and in my rsreportserver.config ..
<Add Key="SQLCommandTimeoutSeconds" Value="60"/>
<Add Key="MaxActiveReqForOneUser" Value="20"/>
<Add Key="DatabaseQueryTimeout" Value="120"/>

.. This information seems to be ingnored

View 2 Replies View Related

Reporting Services :: Using Exists Condition In WHERE Clause While Passing Values From SSRS Parameter

Sep 10, 2015

Table : incident
----------------
incident_id usr_id item_id Inc_Date
10059926 191 61006 8-22-2015
10054444 222 3232 6-7-2015

Table: act_reg
--------------
act_reg_id act_type_id incident_id usr_id act_type_sc
454244 1 10059926 191 ASSIGN
471938 115 10059926 191 TRAVEL TIME
473379 40 10059926 191 FOLLOW UP
477652 115 10059926 191 TRAVEL TIME
489091 504 10059926 191 ADD_ATTCHMNTS
477653 504 10054444 222 ADD_ATTCHMNTSParameter: @attach (value=1, Label=Yes & Value=0, Label=No)

Result (While I am selecting 'Yes' in dropdown)
----------------------------------------------
incident_id usr_id item_id
10059926 191 61006
10054444 222 3232

SELECT incident.incident_id,incident.usr_id,incident.item_id
FROM incident
where exists (How i can write query here to check the act_type_sc=ADD_ATTCHMNTS is exists)

View 7 Replies View Related

SP1 Installation Failure For Reporting Services Instances

Apr 21, 2006

The upgrade was alright for my first/default instance of reporting services but failed for the other 3 non-default instances.

I was running SP1 using remote desktop connection.

I got the following error at the report manager and the reporting services configuration's initialization. Is there any way to get around this?













The version of the report server
database is either in a format that is not valid, or it cannot be read. The
found version is 'C.0.8.40'. The expected version is 'C.0.8.43'. To continue,
update the version of the report server database and verify access rights.
(rsInvalidReportServerDatabase)

Extract from RS9_Hotfix_KB913090.log:
....
04/21/2006 13:20:34.652 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller04/21/2006 13:20:34.668 Failed to read registry key: Debug04/21/2006 13:20:34.761 Unable to install MSP file: \D11-OEMP4-16c$481974575b35c5d8b2HotFixRSFilessqlrun_rs.msp04/21/2006 13:20:34.808 The following exception occurred: Unable to install Windows Installer MSP file Date: 04/21/2006 13:20:34.808 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 856
04/21/2006 13:20:34.871
04/21/2006 13:20:34.933 Product Status Summary:
04/21/2006 13:20:34.980 Product: SQL Server Native Client
04/21/2006 13:20:35.027 SQL Server Native Client (RTM ) - Reboot Required
04/21/2006 13:20:35.090
04/21/2006 13:20:35.168 Product: Setup Support Files
04/21/2006 13:20:35.230 Setup Support Files (RTM ) - Success
04/21/2006 13:20:35.277
04/21/2006 13:20:35.340 Product: Database Services
04/21/2006 13:20:35.402 Database Services (RTM 1399 ENU) - Reboot Required
04/21/2006 13:20:35.465 Analysis Services (RTM 1399 ENU) - Success
04/21/2006 13:20:35.511 Reporting Services (RTM 1399 ENU) - Success
04/21/2006 13:20:35.574
04/21/2006 13:20:35.636 Product: Notification Services
04/21/2006 13:20:35.699 Notification Services (RTM 1399 ENU) - Success
04/21/2006 13:20:35.746
04/21/2006 13:20:35.808 Product: Reporting Services
04/21/2006 13:20:35.871 Reporting Services (RTM 1399 ENU) - Failure04/21/2006 13:20:35.933 Details: Unable to install Windows Installer MSP file04/21/2006 13:20:35.980 04/21/2006 13:20:36.043 Product: Reporting Services04/21/2006 13:20:36.105 Reporting Services (RTM 1399 ENU) - Failure04/21/2006 13:20:36.152 Details: Unable to install Windows Installer MSP file04/21/2006 13:20:36.215 04/21/2006 13:20:36.277 Product: Reporting Services04/21/2006 13:20:36.340 Reporting Services (RTM 1399 ENU) - Failure04/21/2006 13:20:36.402 Details: Unable to install Windows Installer MSP file
04/21/2006 13:20:36.480
04/21/2006 13:20:36.543 Product: Integration Services
04/21/2006 13:20:36.605 Integration Services (RTM 1399 ENU) - Not Applied
04/21/2006 13:20:36.683
04/21/2006 13:20:36.746 Product: Client Components
04/21/2006 13:20:36.808 Client Components (RTM 1399 ENU) - Not Applied
04/21/2006 13:20:36.871
04/21/2006 13:20:36.918 Product: MSXML 6.0 Parser
04/21/2006 13:20:36.996 MSXML 6.0 Parser (RTM ) - Not Applied
04/21/2006 13:20:37.043
04/21/2006 13:20:37.074 Product: SQLXML4
04/21/2006 13:20:37.105 SQLXML4 (RTM ) - Not Applied
04/21/2006 13:20:37.183
04/21/2006 13:20:37.246 Product: Backward Compatibility
04/21/2006 13:20:37.308 Backward Compatibility (RTM ) - Not Applied
04/21/2006 13:20:37.371
04/21/2006 13:20:37.433 Product: Microsoft SQL Server VSS Writer
04/21/2006 13:20:37.496 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
04/21/2006 13:20:37.543
04/21/2006 13:37:53.718 Hotfix package closed

View 17 Replies View Related

Reporting Services 2000 W/ Forms Auth - Rs.Timeout Not Getting Set

Feb 23, 2007

I have implemented the Forms Authentication in Reporting Services 2000. In addition, we have a reports web application that uses the authentication to access the reports in the Reports Server. I have implemented a similar code that is posted in http://msdn2.microsoft.com/en-us/library/aa902691(SQL.80).aspxhttp://msdn2.microsoft.com/en-us/library/aa902691(SQL.80).aspx for the Reports Server and Reports Manager. For the web application, I added reference to the custom security assembly, created a new ReportsServerProxy, and then called the LogonUser().

Now, one of the functionality we have in the applicaiton is to set the reporting services Timeout for reports that take too long to run. The weird thing is the Timeout (in milliseconds) is getting ignored by the ReportServerProxy using the custom security assembly. I verified that without the custom secuirty assembly, the Timeout property is getting set.

I did find the code for ReportServerProxy's GetWebRequest(Uri uri) is setting the request.Timeout to -1. I thought this was interfering with the rs.Timeout, but removing the code did not make any difference.

How do I set the Timeout property correctly? Do you know of any issues with setting the Timeout property for Reporting Services with Forms Authentication?

Can anybody help PLEASE? I need an answer ASAP. Thanks in advance for your help.

/**partial UILogon.aspx code for ReportServerProxy below**/

public class ReportServerProxy : ReportingService

{

protected override WebRequest GetWebRequest(Uri uri)

{

HttpWebRequest request;

request = (HttpWebRequest)HttpWebRequest.Create(uri);

// Create a cookie jar to hold the request cookie

CookieContainer cookieJar = new CookieContainer();

request.CookieContainer = cookieJar;

Cookie authCookie = AuthCookie;

// if the client already has an auth cookie

// place it in the request's cookie container

if (authCookie != null)

request.CookieContainer.Add(authCookie);

request.Timeout = -1;

request.Headers.Add("Accept-Language",

HttpContext.Current.Request.Headers["Accept-Language"]);

return request;

} ...}

/** Below is the Reports Web applicaiton code that calls the ReportsServerProxy LogonUser **/

Public Function GetReportServerProxy() As ReportServerProxy

Dim rsProx As New ReportServerProxy

rsProx.Url = ConfigurationSettings.AppSettings("REPORT_SERVER_URL") + "/ReportService.asmx"

Try

rsProx.LogonUser("SYSADMIN", "password", Nothing)

Return rsProx

Catch ex As Exception

Throw New Exception("GetReportServerProxy Failed.", ex)

End Try

End Function



Private Function CreateSnapShot() As String

...

Dim rs As RSCustomSecurity.ReportServerProxy

Try



rs = GetReportServerProxy()

' First set the parameters' default values

parameters = setParamters()

rs.SetReportParameters(reportPath, parameters)

If errorsList.Count > 0 Then Throw New Exception

'Server.ScriptTimeout = 10

rs.Timeout = Integer.Parse(ConfigurationSettings.AppSettings.Get("REPORT_PROCESS_TIMEOUT"))

lsHistoryID = rs.CreateReportHistorySnapshot(reportPath, warnings)

'lblStatus.NavigateUrl = "ViewSnapShot.aspx?History_ID=" & lsHistoryID

lblStatus.Text = "Your request has been processed. View report as"

....

Catch ex As Exception

....

Finally

Debug.Write("End : " & Now.ToLongTimeString)

rs = Nothing

End Try

End Function

View 1 Replies View Related

Reporting Services :: Getting Execution And Session Timeout Params

May 12, 2015

We run std 2008 r2.  I've never been able to get to my ssrs server thru ssms as u can see as part of the question at 

[URL] ..... but I've found workarounds to this point by knowing how to look at the rs db itself and by having access to the server itself thru rdp with an admin acct.

I'm looking at an error from a user that reminds me of what we used to call session timeouts.  They would occur when the user has walked away from his desk long enough for ssrs to delete refs to the report he just ran.

I logged into the server itself hoping to find both exec and session timeout params via the rs config tool but did not see them there. What the config file is called and where i'd likely find it?  Or perhaps a query I could use to see what the current values are?

View 8 Replies View Related

Reporting Services :: SSRS 2008 Report Timeout For User Not For Admin?

Sep 17, 2015

When a user runs the report after a minute or 3 the user gets a timeout message, if an administrator runs te same report he will get the results. No errors in log. report timeout on 1800 seconds

View 2 Replies View Related

Reporting Services :: Query Timeout In Report Builder Design Mode

May 18, 2012

I have a very frustrating problem.  But given that this is a development forum, I'll keep that for my 'Envelope Lickers Rehab' and instead talk about an issue I'm having.

I have a very large query (line-wise) that executes in less than a minute when run from the SQL Management Studio as well as via Excel Services. 

It is a stored procedure with one parameter. When I try to prime the designer with this query it gives me the following message:

"Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
The statement has been terminated."

I've considered cracking open the xml source and manually creating the fields, but I'd rather not go there.

View 8 Replies View Related

Reporting Services :: SSRS Error - Failure Sending Mail

Jun 4, 2015

I am Getting this error in SSRS Report Subscription. I went to Subscription table Checked the Laststatus. The LastStatus is :Failure sending mail: The specified string is not in the form required for an e-mail address.Mail will not be resent.

View 3 Replies View Related

SQL Server 2005 SP1 Problem: Reporting Services (RTM 1399 ENU)- Failure

Jun 30, 2006

Hello,

we have problem installing SP1, Reporting Services is not updated correctly.

what schould we do? below our log file:

Thank You for answer

Wojtek


06/29/2006 18:59:39.579 ================================================================================
06/29/2006 18:59:39.611 Hotfix package launched
06/29/2006 18:59:39.626 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:39.642 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:40.548 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:40.564 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:42.376 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:42.392 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:42.423 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:42.439 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:42.454 Local Computer:
06/29/2006 18:59:42.470 Target Details: xxxxxxxxxxx
06/29/2006 18:59:42.486 commonfilesdir = C:Program FilesCommon Files
06/29/2006 18:59:42.501 lcidsupportdir = d:8eab555422b5e3d6e18cd38a7afa281033
06/29/2006 18:59:42.517 programfilesdir = C:Program Files
06/29/2006 18:59:42.548 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 18:59:42.564 supportdirlocal = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 18:59:42.579 windir = C:WINDOWS
06/29/2006 18:59:42.595 winsysdir = C:WINDOWSsystem32
06/29/2006 18:59:42.611
06/29/2006 18:59:42.626 Enumerating applicable products for this patch
06/29/2006 18:59:42.673 Found Redist 2005 product definition
06/29/2006 18:59:42.907 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:42.923 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:42.939 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:42.970 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:43.564 Attempting to check IA 64 platform
06/29/2006 18:59:43.595 Result of IA64 check: 0
06/29/2006 18:59:43.626 Last error: 0
06/29/2006 18:59:43.657 Found Redist 2005 product definition
06/29/2006 18:59:43.704 Found Redist 2005 product definition
06/29/2006 18:59:43.751 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:43.767 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:43.798 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:43.814 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:44.142 Attempting to check IA 64 platform
06/29/2006 18:59:44.157 Result of IA64 check: 0
06/29/2006 18:59:44.189 Last error: 0
06/29/2006 18:59:44.220 Found SQL 2005 product definition
06/29/2006 18:59:46.189 Determining QFE level for product instance MSSQLSERVER
06/29/2006 18:59:46.282 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.2MSSQLBinnSQLServr.exe
06/29/2006 18:59:46.314 Found following QFE level for product instance MSSQLSERVER: 2047
06/29/2006 18:59:46.345 Determining GDR branching Hotfix for product instance MSSQLSERVER
06/29/2006 18:59:46.361 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.2MSSQLBinnSQLServr.exe
06/29/2006 18:59:46.376 No GDR branch Hotfix found for product instance MSSQLSERVER
06/29/2006 18:59:46.423 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:46.454 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:46.470 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:46.486 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:46.673 Attempting to check IA 64 platform
06/29/2006 18:59:46.689 Result of IA64 check: 0
06/29/2006 18:59:46.704 Last error: 0
06/29/2006 18:59:46.736 Found OLAP Server 2005 product definition
06/29/2006 18:59:47.532 Determining QFE level for product instance MSSQLSERVER
06/29/2006 18:59:47.564 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1OLAP\Binmsmdsrv.exe
06/29/2006 18:59:47.595 Found following QFE level for product instance MSSQLSERVER: 2047
06/29/2006 18:59:47.611 Determining GDR branching Hotfix for product instance MSSQLSERVER
06/29/2006 18:59:47.626 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1OLAP\Binmsmdsrv.exe
06/29/2006 18:59:47.642 No GDR branch Hotfix found for product instance MSSQLSERVER
06/29/2006 18:59:47.673 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:47.704 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:47.720 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:47.736 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:47.861 Attempting to check IA 64 platform
06/29/2006 18:59:47.876 Result of IA64 check: 0
06/29/2006 18:59:47.907 Last error: 0
06/29/2006 18:59:47.939 Found Notification Services 2005 product definition
06/29/2006 18:59:48.689 Determining QFE level for product instance
06/29/2006 18:59:48.736 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242\Binsservice.exe
06/29/2006 18:59:48.751 Found following QFE level for product instance : 2047
06/29/2006 18:59:48.767 Determining GDR branching Hotfix for product instance
06/29/2006 18:59:48.782 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242\Binsservice.exe
06/29/2006 18:59:48.814 No GDR branch Hotfix found for product instance
06/29/2006 18:59:48.845 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:48.861 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:48.876 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:48.892 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:49.017 Attempting to check IA 64 platform
06/29/2006 18:59:49.032 Result of IA64 check: 0
06/29/2006 18:59:49.064 Last error: 0
06/29/2006 18:59:49.079 Found Report Server 2005 product definition
06/29/2006 18:59:49.829 Determining QFE level for product instance MSSQLSERVER
06/29/2006 18:59:49.923 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.3Reporting Services\ReportServerinReportingServicesService.exe
06/29/2006 18:59:49.986 Found following QFE level for product instance MSSQLSERVER: 1399
06/29/2006 18:59:50.048 Determining GDR branching Hotfix for product instance MSSQLSERVER
06/29/2006 18:59:50.111 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.3Reporting Services\ReportServerinReportingServicesService.exe
06/29/2006 18:59:50.157 No GDR branch Hotfix found for product instance MSSQLSERVER
06/29/2006 18:59:50.220 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:50.251 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:50.282 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:50.314 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:50.470 Attempting to check IA 64 platform
06/29/2006 18:59:50.501 Result of IA64 check: 0
06/29/2006 18:59:50.517 Last error: 0
06/29/2006 18:59:50.548 Found DTS 2005 product definition
06/29/2006 18:59:51.361 Determining QFE level for product instance
06/29/2006 18:59:51.439 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90DTS\BinnDTSPipeline.dll
06/29/2006 18:59:51.454 Found following QFE level for product instance : 2047
06/29/2006 18:59:51.470 Determining GDR branching Hotfix for product instance
06/29/2006 18:59:51.501 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90DTS\BinnDTSPipeline.dll
06/29/2006 18:59:51.532 No GDR branch Hotfix found for product instance
06/29/2006 18:59:51.564 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:51.579 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:51.595 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:51.626 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:51.767 Attempting to check IA 64 platform
06/29/2006 18:59:51.798 Result of IA64 check: 0
06/29/2006 18:59:51.814 Last error: 0
06/29/2006 18:59:51.845 Found SQL 2005 Tools product definition
06/29/2006 18:59:52.657 Determining GDR branching Hotfix for product instance
06/29/2006 18:59:52.704 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Tools\BinnVSShellCommon7IDESQLWB.EXE
06/29/2006 18:59:52.736 No GDR branch Hotfix found for product instance
06/29/2006 18:59:52.767 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:52.798 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:52.814 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:52.845 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:52.986 Attempting to check IA 64 platform
06/29/2006 18:59:53.017 Result of IA64 check: 0
06/29/2006 18:59:53.048 Last error: 0
06/29/2006 18:59:53.079 Found Redist 2005 product definition
06/29/2006 18:59:53.126 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:53.142 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:53.157 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:53.189 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:53.282 Attempting to check IA 64 platform
06/29/2006 18:59:53.298 Result of IA64 check: 0
06/29/2006 18:59:53.314 Last error: 0
06/29/2006 18:59:53.329 Found Redist 2005 product definition
06/29/2006 18:59:53.376 Found Redist 2005 product definition
06/29/2006 18:59:53.423 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:53.454 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:53.470 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:53.486 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:53.579 Attempting to check IA 64 platform
06/29/2006 18:59:53.595 Result of IA64 check: 0
06/29/2006 18:59:53.611 Last error: 0
06/29/2006 18:59:53.642 Found Redist 2005 product definition
06/29/2006 18:59:53.689 Found Redist 2005 product definition
06/29/2006 18:59:53.720 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:53.751 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:53.767 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:53.782 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:53.892 Attempting to check IA 64 platform
06/29/2006 18:59:53.907 Result of IA64 check: 0
06/29/2006 18:59:53.923 Last error: 0
06/29/2006 18:59:53.939 Found Redist 2005 product definition
06/29/2006 18:59:53.970 Found Redist 2005 product definition
06/29/2006 18:59:54.001 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:54.032 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
06/29/2006 18:59:54.048 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
06/29/2006 18:59:54.079 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
06/29/2006 18:59:54.142 Attempting to check IA 64 platform
06/29/2006 18:59:54.173 Result of IA64 check: 0
06/29/2006 18:59:54.189 Last error: 0
06/29/2006 18:59:54.220 Found Redist 2005 product definition
06/29/2006 18:59:54.251 Product Details:
06/29/2006 18:59:54.267 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixSqlncli.inf
06/29/2006 18:59:54.282 alwaysinstall = 1
06/29/2006 18:59:54.314 baselinebuild = 1399
06/29/2006 18:59:54.329 build = 2047
06/29/2006 18:59:54.345 description = SQL Server Native Client
06/29/2006 18:59:54.361 details = Service Pack for Microsoft SQL Server Native Client.
06/29/2006 18:59:54.376 kbarticle = KB913090
06/29/2006 18:59:54.392 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 18:59:54.407 lcid = 1033
06/29/2006 18:59:54.439 legalproductname = Microsoft SQL Native Client
06/29/2006 18:59:54.470 machinetype = x86
06/29/2006 18:59:54.486 package = HotFixSqlncli
06/29/2006 18:59:54.501 packagetype = Hotfix
06/29/2006 18:59:54.517 productcode = {50A0893D-47D8-48E0-A7E8-44BCD7E4422E}
06/29/2006 18:59:54.532 productname = Redist9
06/29/2006 18:59:54.548 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 18:59:54.564 splevel = 0,1
06/29/2006 18:59:54.595 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 18:59:54.611 upgradecode = {A6B19337-7392-4765-8675-5C25B758BA37}
06/29/2006 18:59:54.626 version = 9
06/29/2006 18:59:54.642
06/29/2006 18:59:54.657 File Group Details: MSI
06/29/2006 18:59:54.689 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 18:59:54.704 File Details: sqlncli.msi
06/29/2006 18:59:54.720
06/29/2006 18:59:54.736 Instance Details: SQL Server Native Client
06/29/2006 18:59:54.751 productcode = {50A0893D-47D8-48E0-A7E8-44BCD7E4422E}
06/29/2006 18:59:54.767
06/29/2006 18:59:54.798 Product Details:
06/29/2006 18:59:54.814 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixSqlncli_x64.inf
06/29/2006 18:59:54.829 alwaysinstall = 1
06/29/2006 18:59:54.845 baselinebuild = 1399
06/29/2006 18:59:54.861 build = 2047
06/29/2006 18:59:54.876 description = SQL Server Native Client (64-bit)
06/29/2006 18:59:54.907 details = Service Pack for Microsoft SQL Server Native Client.
06/29/2006 18:59:54.923 kbarticle = KB913090
06/29/2006 18:59:54.939 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 18:59:54.954 lcid = 1033
06/29/2006 18:59:54.970 legalproductname = Microsoft SQL Native Client (64-bit)
06/29/2006 18:59:55.001 machinetype = x64
06/29/2006 18:59:55.017 package = HotFixSqlncli_x64
06/29/2006 18:59:55.032 packagetype = Hotfix
06/29/2006 18:59:55.048 productname = Redist9
06/29/2006 18:59:55.064 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 18:59:55.079 splevel = 0,1
06/29/2006 18:59:55.111 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 18:59:55.126 upgradecode = {6EC3319D-84BE-4C32-AA91-7D6057CF05A5}
06/29/2006 18:59:55.142 version = 9
06/29/2006 18:59:55.157
06/29/2006 18:59:55.173 File Group Details: MSI
06/29/2006 18:59:55.204 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 18:59:55.220 File Details: sqlncli_x64.msi
06/29/2006 18:59:55.236
06/29/2006 18:59:55.251 Product Details:
06/29/2006 18:59:55.282 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixSqlSupport.inf
06/29/2006 18:59:55.314 alwaysinstall = 1
06/29/2006 18:59:55.345 baselinebuild = 1399
06/29/2006 18:59:55.361 build = 2047
06/29/2006 18:59:55.392 description = Setup Support Files
06/29/2006 18:59:55.407 details = Service Pack for the SQL Server support files.
06/29/2006 18:59:55.439 kbarticle = KB913090
06/29/2006 18:59:55.470 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 18:59:55.501 keyqualifier = 1
06/29/2006 18:59:55.517 lcid = 1033
06/29/2006 18:59:55.548 legalproductname = SQL Server 2005 Setup Support Files
06/29/2006 18:59:55.579 machinetype = x86
06/29/2006 18:59:55.611 package = HotFixSqlSupport
06/29/2006 18:59:55.626 packagetype = Hotfix
06/29/2006 18:59:55.642 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
06/29/2006 18:59:55.673 productname = Redist9
06/29/2006 18:59:55.689 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 18:59:55.720 splevel = 0,1
06/29/2006 18:59:55.751 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 18:59:55.767 upgradecode = {3A91FA19-A197-467C-850F-0AFE90899371}
06/29/2006 18:59:55.782 version = 9
06/29/2006 18:59:55.814
06/29/2006 18:59:55.829 File Group Details: MSP
06/29/2006 18:59:55.861 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
06/29/2006 18:59:55.892 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 18:59:55.907 File Details: SqlSupport.msp
06/29/2006 18:59:55.939
06/29/2006 18:59:55.954 Instance Details: Setup Support Files
06/29/2006 18:59:55.986 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
06/29/2006 18:59:56.017
06/29/2006 18:59:56.032 Product Details:
06/29/2006 18:59:56.048 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixSQL.inf
06/29/2006 18:59:56.079 baselinebuild = 1399
06/29/2006 18:59:56.095 baselinebuildmax = 2047
06/29/2006 18:59:56.111 build = 2047
06/29/2006 18:59:56.142 description = Database Services
06/29/2006 18:59:56.157 details = Service Pack for the SQL Server database engine, and the tools for managing relational and XML data, Replication, and Full-Text Search.
06/29/2006 18:59:56.189 kbarticle = KB913090
06/29/2006 18:59:56.204 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 18:59:56.236 lcid = 1033
06/29/2006 18:59:56.267 legalproductname = SQL Server Database Services 2005
06/29/2006 18:59:56.282 machinetype = x86
06/29/2006 18:59:56.298 package = HotFixSQL
06/29/2006 18:59:56.329 packagetype = Hotfix
06/29/2006 18:59:56.345 productname = SQL9
06/29/2006 18:59:56.361 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 18:59:56.392 splevel = 0,1
06/29/2006 18:59:56.423 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 18:59:56.439 validateauthentication = true
06/29/2006 18:59:56.454 version = 9
06/29/2006 18:59:56.486
06/29/2006 18:59:56.517 File Group Details: MSP
06/29/2006 18:59:56.532 lockedfilecheck = 1
06/29/2006 18:59:56.548 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
06/29/2006 18:59:56.579 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 18:59:56.611 File Details: sqlrun_sql.msp
06/29/2006 18:59:56.626
06/29/2006 18:59:56.657 Instance Details: MSSQLSERVER
06/29/2006 18:59:56.673 agentservicename = SQLSERVERAGENT
06/29/2006 18:59:56.704 associatedhotfixbuild = 0
06/29/2006 18:59:56.720 clustername =
06/29/2006 18:59:56.751 default = TRUE
06/29/2006 18:59:56.782 ftsservicename = MSFTESQL
06/29/2006 18:59:56.798 hiveregpath = SoftwareMicrosoftMicrosoft SQL ServerMSSQL.2
06/29/2006 18:59:56.814 id = MSSQL.2
06/29/2006 18:59:56.845 installsqldatadir = C:Program FilesMicrosoft SQL ServerMSSQL.2MSSQL
06/29/2006 18:59:56.861 installsqldir = C:Program FilesMicrosoft SQL ServerMSSQL.2MSSQL
06/29/2006 18:59:56.876 lcid = 1033
06/29/2006 18:59:56.907 name = MSSQLSERVER
06/29/2006 18:59:56.939 productcode = {EB76B218-8FC5-41DF-9F1F-7FF3E0448383}
06/29/2006 18:59:56.954 qfelevel = 2047
06/29/2006 18:59:56.970 servicename = MSSQLServer
06/29/2006 18:59:57.001 sku = ENTERPRISE
06/29/2006 18:59:57.032 sp = 1
06/29/2006 18:59:57.048 type = SQL Server Standalone Product
06/29/2006 18:59:57.079 vermajbld = 2047
06/29/2006 18:59:57.095 version = 9
06/29/2006 18:59:57.110
06/29/2006 18:59:57.142 Product Details:
06/29/2006 18:59:57.173 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixAS.inf
06/29/2006 18:59:57.189 baselinebuild = 1399
06/29/2006 18:59:57.220 baselinebuildmax = 2047
06/29/2006 18:59:57.235 build = 2047
06/29/2006 18:59:57.267 description = Analysis Services
06/29/2006 18:59:57.298 details = Service Pack for Analysis Services, and the tools used to support online analytical processing (OLAP) and data mining.
06/29/2006 18:59:57.314 kbarticle = KB913090
06/29/2006 18:59:57.345 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 18:59:57.392 lcid = 1033
06/29/2006 18:59:57.423 legalproductname = SQL Server Analysis Services 2005
06/29/2006 18:59:57.439 machinetype = x86
06/29/2006 18:59:57.470 package = HotFixAS
06/29/2006 18:59:57.501 packagetype = Hotfix
06/29/2006 18:59:57.517 productname = OLAP9
06/29/2006 18:59:57.532 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 18:59:57.564 splevel = 0,1
06/29/2006 18:59:57.595 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 18:59:57.610 version = 9
06/29/2006 18:59:57.642
06/29/2006 18:59:57.657 File Group Details: MSP
06/29/2006 18:59:57.673 lockedfilecheck = 1
06/29/2006 18:59:57.704 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
06/29/2006 18:59:57.735 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 18:59:57.751 File Details: sqlrun_as.msp
06/29/2006 18:59:57.782
06/29/2006 18:59:57.798 Instance Details: MSSQLSERVER
06/29/2006 18:59:57.814 associatedhotfixbuild = 0
06/29/2006 18:59:57.845 clustername =
06/29/2006 18:59:57.860 default = TRUE
06/29/2006 18:59:57.876 hiveregpath = SoftwareMicrosoftMicrosoft SQL ServerMSSQL.1
06/29/2006 18:59:57.907 id = MSSQL.1
06/29/2006 18:59:57.923 installsqldatadir = C:Program FilesMicrosoft SQL Server
06/29/2006 18:59:57.954 installsqldir = C:Program FilesMicrosoft SQL ServerMSSQL.1OLAP
06/29/2006 18:59:57.970 lcid = 1033
06/29/2006 18:59:58.001 name = MSSQLSERVER
06/29/2006 18:59:58.017 olapservicename = MSSQLServerOLAPService
06/29/2006 18:59:58.032 productcode = {52B0D62A-860D-4136-9A8A-9FD877E8EE89}
06/29/2006 18:59:58.064 qfelevel = 2047
06/29/2006 18:59:58.079 servicename = MSSQLServerOLAPService
06/29/2006 18:59:58.110 sku = ENTERPRISE
06/29/2006 18:59:58.126 sp = 1
06/29/2006 18:59:58.157 type = Olap Standalone Product
06/29/2006 18:59:58.173 vermajbld = 2047
06/29/2006 18:59:58.204 version = 9
06/29/2006 18:59:58.220
06/29/2006 18:59:58.251 Product Details:
06/29/2006 18:59:58.267 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixNS.inf
06/29/2006 18:59:58.282 baselinebuild = 1399
06/29/2006 18:59:58.314 baselinebuildmax = 2047
06/29/2006 18:59:58.329 build = 2047
06/29/2006 18:59:58.360 description = Notification Services
06/29/2006 18:59:58.376 details = Service Pack for Notification Services, a platform for developing and deploying applications that send personalized, timely notifications to a variety of devices or applications.
06/29/2006 18:59:58.392 kbarticle = KB913090
06/29/2006 18:59:58.423 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 18:59:58.439 lcid = 1033
06/29/2006 18:59:58.470 legalproductname = SQL Server Notification Services 2005 instances
06/29/2006 18:59:58.501 machinetype = x86
06/29/2006 18:59:58.517 package = HotFixNS
06/29/2006 18:59:58.548 packagetype = Hotfix
06/29/2006 18:59:58.595 productname = NS9
06/29/2006 18:59:58.642 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 18:59:58.720 splevel = 0,1
06/29/2006 18:59:58.767 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 18:59:58.814 version = 9
06/29/2006 18:59:58.829
06/29/2006 18:59:58.860 File Group Details: MSP
06/29/2006 18:59:58.876 lockedfilecheck = 1
06/29/2006 18:59:58.907 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
06/29/2006 18:59:58.923 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 18:59:58.954 File Details: sqlrun_ns.msp
06/29/2006 18:59:58.970
06/29/2006 18:59:58.985 Instance Details: NS
06/29/2006 18:59:59.157 associatedhotfixbuild = 0
06/29/2006 18:59:59.235 clustername =
06/29/2006 18:59:59.282 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90NS
06/29/2006 18:59:59.329 id =
06/29/2006 18:59:59.392 installsqldatadir =
06/29/2006 18:59:59.423 installsqldir = C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242
06/29/2006 18:59:59.501 lcid = 1033
06/29/2006 18:59:59.517 name =
06/29/2006 18:59:59.532 productcode = {C0B81E26-F7D0-4E84-941A-21C438BC586D}
06/29/2006 18:59:59.548 qfelevel = 2047
06/29/2006 18:59:59.564 sku = ENTERPRISE
06/29/2006 18:59:59.595 sp = 1
06/29/2006 18:59:59.610 type = Tools Only
06/29/2006 18:59:59.626 vermajbld = 2047
06/29/2006 18:59:59.642 version = 9
06/29/2006 18:59:59.657
06/29/2006 18:59:59.673 Product Details:
06/29/2006 18:59:59.720 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixRS.inf
06/29/2006 18:59:59.735 baselinebuild = 1399
06/29/2006 18:59:59.751 baselinebuildmax = 2047
06/29/2006 18:59:59.767 build = 2047
06/29/2006 18:59:59.782 description = Reporting Services
06/29/2006 18:59:59.814 details = Service Pack for the Report Server and Report Builder, which manages, executes, renders, and distributes reports.
06/29/2006 18:59:59.829 kbarticle = KB913090
06/29/2006 18:59:59.845 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 18:59:59.860 lcid = 1033
06/29/2006 18:59:59.876 legalproductname = SQL Server Reporting Services 2005
06/29/2006 18:59:59.892 machinetype = x86
06/29/2006 18:59:59.923 package = HotFixRS
06/29/2006 18:59:59.954 packagetype = Hotfix
06/29/2006 18:59:59.970 productname = RS9
06/29/2006 18:59:59.985 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 19:00:00.001 splevel = 0,1
06/29/2006 19:00:00.079 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 19:00:00.110 validateauthentication = 1
06/29/2006 19:00:00.126 version = 9
06/29/2006 19:00:00.142
06/29/2006 19:00:00.157 File Group Details: MSP
06/29/2006 19:00:00.173 lockedfilecheck = 1
06/29/2006 19:00:00.204 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
06/29/2006 19:00:00.220 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 19:00:00.235 File Details: sqlrun_rs.msp
06/29/2006 19:00:00.251
06/29/2006 19:00:00.267 Instance Details: MSSQLSERVER
06/29/2006 19:00:00.282 clustername =
06/29/2006 19:00:00.298 default = TRUE
06/29/2006 19:00:00.329 hiveregpath = SoftwareMicrosoftMicrosoft SQL ServerMSSQL.3
06/29/2006 19:00:00.345 id = MSSQL.3
06/29/2006 19:00:00.360 installsqldatadir =
06/29/2006 19:00:00.376 installsqldir = C:Program FilesMicrosoft SQL ServerMSSQL.3Reporting Services
06/29/2006 19:00:00.407 lcid = 1033
06/29/2006 19:00:00.423 name = MSSQLSERVER
06/29/2006 19:00:00.439 productcode = {7D7E6D55-E338-4B4C-AD91-E750BFD2BA4C}
06/29/2006 19:00:00.454 qfelevel = 1399
06/29/2006 19:00:00.470 rsservicename = ReportServer
06/29/2006 19:00:00.501 servicename =
06/29/2006 19:00:00.517 sku = ENTERPRISE
06/29/2006 19:00:00.532 sp = 0
06/29/2006 19:00:00.548 type = Report Server Standalone Product
06/29/2006 19:00:00.579 vermajbld = 1399
06/29/2006 19:00:00.595 version = 9
06/29/2006 19:00:00.626
06/29/2006 19:00:00.642 Product Details:
06/29/2006 19:00:00.657 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixDTS.inf
06/29/2006 19:00:00.673 baselinebuild = 1399
06/29/2006 19:00:00.704 baselinebuildmax = 2047
06/29/2006 19:00:00.735 build = 2047
06/29/2006 19:00:00.767 description = Integration Services
06/29/2006 19:00:00.782 details = Service Pack for Integration Services, a set of tools and programmable objects used to create and manage packages that extract, transform, and load data, as well as perform tasks.
06/29/2006 19:00:00.798 kbarticle = KB913090
06/29/2006 19:00:00.829 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 19:00:00.860 lcid = 1033
06/29/2006 19:00:00.892 legalproductname = SQL Server Integration Services 2005
06/29/2006 19:00:00.907 machinetype = x86
06/29/2006 19:00:00.939 package = HotFixDTS
06/29/2006 19:00:00.970 packagetype = Hotfix
06/29/2006 19:00:00.985 productname = DTS9
06/29/2006 19:00:01.064 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 19:00:01.110 splevel = 0,1
06/29/2006 19:00:01.157 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 19:00:01.204 version = 9
06/29/2006 19:00:01.251
06/29/2006 19:00:01.282 File Group Details: MSP
06/29/2006 19:00:01.360 lockedfilecheck = 1
06/29/2006 19:00:01.392 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
06/29/2006 19:00:01.407 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 19:00:01.423 File Details: sqlrun_dts.msp
06/29/2006 19:00:01.454
06/29/2006 19:00:01.485 Instance Details: DTS
06/29/2006 19:00:01.517 associatedhotfixbuild = 0
06/29/2006 19:00:01.532 clustername =
06/29/2006 19:00:01.548 dtsservicename = MsDtsServer
06/29/2006 19:00:01.579 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90DTS
06/29/2006 19:00:01.595 id =
06/29/2006 19:00:01.626 installsqldatadir =
06/29/2006 19:00:01.642 installsqldir = C:Program FilesMicrosoft SQL Server90DTS
06/29/2006 19:00:01.657 lcid = 1033
06/29/2006 19:00:01.689 name =
06/29/2006 19:00:01.704 productcode = {8E408A85-E0E5-4094-903F-8675707AC313}
06/29/2006 19:00:01.735 qfelevel = 2047
06/29/2006 19:00:01.767 servicename = MsDtsServer
06/29/2006 19:00:01.782 sku = ENTERPRISE
06/29/2006 19:00:01.798 sp = 1
06/29/2006 19:00:01.829 type = Tools Only
06/29/2006 19:00:01.845 vermajbld = 2047
06/29/2006 19:00:01.876 version = 9
06/29/2006 19:00:01.892
06/29/2006 19:00:01.907 Product Details:
06/29/2006 19:00:01.939 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixTools.inf
06/29/2006 19:00:01.954 baselinebuild = 1399
06/29/2006 19:00:01.970 baselinebuildmax = 2047
06/29/2006 19:00:02.017 build = 2047
06/29/2006 19:00:02.064 description = Client Components
06/29/2006 19:00:02.110 details = Service Pack for the interactive management tools for running SQL Server, including SQL Server Configuration Manager, SQL Server Management Studio, SQL Profiler, and Replication Monitor.
06/29/2006 19:00:02.157 kbarticle = KB913090
06/29/2006 19:00:02.204 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 19:00:02.235 lcid = 1033
06/29/2006 19:00:02.251 legalproductname = SQL Server Tools and Workstation Components 2005
06/29/2006 19:00:02.282 machinetype = x86
06/29/2006 19:00:02.298 package = HotFixTools
06/29/2006 19:00:02.314 packagetype = Hotfix
06/29/2006 19:00:02.345 productname = SQLTools9
06/29/2006 19:00:02.376 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 19:00:02.407 splevel = 0,1
06/29/2006 19:00:02.423 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 19:00:02.454 version = 9
06/29/2006 19:00:02.470
06/29/2006 19:00:02.517 File Group Details: MSP
06/29/2006 19:00:02.532 lockedfilecheck = 1
06/29/2006 19:00:02.564 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
06/29/2006 19:00:02.579 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 19:00:02.610 File Details: sqlrun_tools.msp
06/29/2006 19:00:02.642
06/29/2006 19:00:02.673 Instance Details: SQL Tools
06/29/2006 19:00:02.689 associatedhotfixbuild = 0
06/29/2006 19:00:02.720 clustername =
06/29/2006 19:00:02.735 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90Tools
06/29/2006 19:00:02.767 id =
06/29/2006 19:00:02.798 installsqldatadir =
06/29/2006 19:00:02.814 installsqldir = C:Program FilesMicrosoft SQL Server90Tools
06/29/2006 19:00:02.845 lcid = 1033
06/29/2006 19:00:02.860 name =
06/29/2006 19:00:02.892 productcode = {4D2DFB70-AECB-47BF-A895-3B3AA544934F}
06/29/2006 19:00:02.923 qfelevel = 2047
06/29/2006 19:00:02.954 sku = ENTERPRISE
06/29/2006 19:00:02.970 sp = 1
06/29/2006 19:00:03.017 type = Tools Only
06/29/2006 19:00:03.064 vermajbld = 2047
06/29/2006 19:00:03.095 version = 9
06/29/2006 19:00:03.157
06/29/2006 19:00:03.189 Product Details:
06/29/2006 19:00:03.220 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixMsxml6.inf
06/29/2006 19:00:03.235 baselinebuild = 1399
06/29/2006 19:00:03.267 build = 2047
06/29/2006 19:00:03.298 description = MSXML 6.0 Parser
06/29/2006 19:00:03.329 details = Service Pack for Microsoft XML 6.0 Parser.
06/29/2006 19:00:03.345 kbarticle = KB913090
06/29/2006 19:00:03.376 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 19:00:03.407 lcid = 1033
06/29/2006 19:00:03.423 legalproductname = MSXML 6.0 Parser
06/29/2006 19:00:03.454 machinetype = x86
06/29/2006 19:00:03.485 package = HotFixMsxml6
06/29/2006 19:00:03.501 packagetype = Hotfix
06/29/2006 19:00:03.532 productcode = {AEB9948B-4FF2-47C9-990E-47014492A0FE}
06/29/2006 19:00:03.564 productname = Redist9
06/29/2006 19:00:03.595 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 19:00:03.610 splevel = 0,1
06/29/2006 19:00:03.642 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 19:00:03.673 upgradecode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
06/29/2006 19:00:03.689 version = 9
06/29/2006 19:00:03.720
06/29/2006 19:00:03.751 File Group Details: MSI
06/29/2006 19:00:03.767 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 19:00:03.798 File Details: msxml6.msi
06/29/2006 19:00:03.829
06/29/2006 19:00:03.845 Instance Details: MSXML 6.0 Parser
06/29/2006 19:00:03.876 productcode = {AEB9948B-4FF2-47C9-990E-47014492A0FE}
06/29/2006 19:00:03.907
06/29/2006 19:00:03.939 Product Details:
06/29/2006 19:00:03.954 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixMsxml6_x64.inf
06/29/2006 19:00:03.985 baselinebuild = 1399
06/29/2006 19:00:04.017 build = 2047
06/29/2006 19:00:04.079 description = MSXML 6.0 Parser (64-bit)
06/29/2006 19:00:04.126 details = Service Pack for Microsoft XML 6.0 Parser.
06/29/2006 19:00:04.173 kbarticle = KB913090
06/29/2006 19:00:04.189 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 19:00:04.220 lcid = 1033
06/29/2006 19:00:04.235 legalproductname = MSXML 6.0 Parser (64-bit)
06/29/2006 19:00:04.251 machinetype = x64
06/29/2006 19:00:04.282 package = HotFixMsxml6_x64
06/29/2006 19:00:04.314 packagetype = Hotfix
06/29/2006 19:00:04.329 productname = Redist9
06/29/2006 19:00:04.360 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 19:00:04.376 splevel = 0,1
06/29/2006 19:00:04.407 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 19:00:04.439 upgradecode = {5BBED1F8-E6F3-4A02-BC97-26D35BE200CA}
06/29/2006 19:00:04.454 version = 9
06/29/2006 19:00:04.485
06/29/2006 19:00:04.517 File Group Details: MSI
06/29/2006 19:00:04.532 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 19:00:04.564 File Details: msxml6_x64.msi
06/29/2006 19:00:04.595
06/29/2006 19:00:04.610 Product Details:
06/29/2006 19:00:04.642 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixSqlxml4.inf
06/29/2006 19:00:04.657 baselinebuild = 1399
06/29/2006 19:00:04.689 build = 2047
06/29/2006 19:00:04.720 description = SQLXML4
06/29/2006 19:00:04.735 details = Service Pack for Microsoft SQLXML 4.0.
06/29/2006 19:00:04.767 kbarticle = KB913090
06/29/2006 19:00:04.782 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 19:00:04.814 lcid = 1033
06/29/2006 19:00:04.845 legalproductname = SQLXML4
06/29/2006 19:00:04.860 machinetype = x86
06/29/2006 19:00:04.892 package = HotFixSqlxml4
06/29/2006 19:00:04.907 packagetype = Hotfix
06/29/2006 19:00:04.954 productcode = {A188FCCF-E929-494D-B1F1-4313E02ACD52}
06/29/2006 19:00:04.970 productname = Redist9
06/29/2006 19:00:05.001 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 19:00:05.048 splevel = 0,1
06/29/2006 19:00:05.079 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 19:00:05.110 upgradecode = {D9CA3D82-6F1B-41A7-8141-B90ACA8F865B}
06/29/2006 19:00:05.173 version = 9
06/29/2006 19:00:05.189
06/29/2006 19:00:05.220 File Group Details: MSI
06/29/2006 19:00:05.235 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 19:00:05.267 File Details: sqlxml4.msi
06/29/2006 19:00:05.282
06/29/2006 19:00:05.314 Instance Details: SQLXML4
06/29/2006 19:00:05.345 productcode = {A188FCCF-E929-494D-B1F1-4313E02ACD52}
06/29/2006 19:00:05.360
06/29/2006 19:00:05.392 Product Details:
06/29/2006 19:00:05.407 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixSqlxml4_x64.inf
06/29/2006 19:00:05.439 baselinebuild = 1399
06/29/2006 19:00:05.470 build = 2047
06/29/2006 19:00:05.485 description = SQLXML4 (64-bit)
06/29/2006 19:00:05.517 details = Service Pack for Microsoft SQLXML 4.0.
06/29/2006 19:00:05.532 kbarticle = KB913090
06/29/2006 19:00:05.564 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 19:00:05.595 lcid = 1033
06/29/2006 19:00:05.610 legalproductname = SQLXML4 (64-bit)
06/29/2006 19:00:05.642 machinetype = x64
06/29/2006 19:00:05.657 package = HotFixSqlxml4_x64
06/29/2006 19:00:05.689 packagetype = Hotfix
06/29/2006 19:00:05.720 productname = Redist9
06/29/2006 19:00:05.735 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 19:00:05.767 splevel = 0,1
06/29/2006 19:00:05.782 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 19:00:05.814 upgradecode = {F457D8E6-7686-437D-9B17-E21D45CCABD8}
06/29/2006 19:00:05.845 version = 9
06/29/2006 19:00:05.860
06/29/2006 19:00:05.892 File Group Details: MSI
06/29/2006 19:00:05.907 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 19:00:05.939 File Details: sqlxml4_x64.msi
06/29/2006 19:00:05.970
06/29/2006 19:00:05.985 Product Details:
06/29/2006 19:00:06.017 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixSQLServer2005_BC.inf
06/29/2006 19:00:06.064 baselinebuild = 1399
06/29/2006 19:00:06.095 build = 2047
06/29/2006 19:00:06.110 description = Backward Compatibility
06/29/2006 19:00:06.142 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
06/29/2006 19:00:06.157 kbarticle = KB913090
06/29/2006 19:00:06.189 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 19:00:06.220 lcid = 1033
06/29/2006 19:00:06.235 legalproductname = Microsoft SQL Server 2005 Backward Compatibility
06/29/2006 19:00:06.267 machinetype = x86
06/29/2006 19:00:06.282 package = HotFixSQLServer2005_BC
06/29/2006 19:00:06.314 packagetype = Hotfix
06/29/2006 19:00:06.345 productcode = {2243F21A-E132-44F7-BA13-024D0845C815}
06/29/2006 19:00:06.360 productname = Redist9
06/29/2006 19:00:06.392 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 19:00:06.407 splevel = 0,1
06/29/2006 19:00:06.439 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 19:00:06.454 upgradecode = {1E70C6C9-E1B7-4A74-BC8C-8EB5D010CEC9}
06/29/2006 19:00:06.485 version = 9
06/29/2006 19:00:06.517
06/29/2006 19:00:06.532 File Group Details: MSI
06/29/2006 19:00:06.564 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 19:00:06.579 File Details: SQLServer2005_BC.msi
06/29/2006 19:00:06.610
06/29/2006 19:00:06.642 Instance Details: Backward Compatibility
06/29/2006 19:00:06.657 productcode = {2243F21A-E132-44F7-BA13-024D0845C815}
06/29/2006 19:00:06.689
06/29/2006 19:00:06.704 Product Details:
06/29/2006 19:00:06.735 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixSQLServer2005_BC_x64.inf
06/29/2006 19:00:06.751 baselinebuild = 1399
06/29/2006 19:00:06.782 build = 2047
06/29/2006 19:00:06.798 description = Backward Compatibility (64-bit)
06/29/2006 19:00:06.829 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
06/29/2006 19:00:06.860 kbarticle = KB913090
06/29/2006 19:00:06.876 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 19:00:06.907 lcid = 1033
06/29/2006 19:00:06.923 legalproductname = Microsoft SQL Server 2005 Backward Compatibility (64-bit)
06/29/2006 19:00:06.954 machinetype = x64
06/29/2006 19:00:06.985 package = HotFixSQLServer2005_BC_x64
06/29/2006 19:00:07.017 packagetype = Hotfix
06/29/2006 19:00:07.064 productname = Redist9
06/29/2006 19:00:07.095 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 19:00:07.126 splevel = 0,1
06/29/2006 19:00:07.142 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 19:00:07.173 upgradecode = {7B6BF434-3C72-4DB3-8049-FEF31AEAFF9A}
06/29/2006 19:00:07.189 version = 9
06/29/2006 19:00:07.220
06/29/2006 19:00:07.251 File Group Details: MSI
06/29/2006 19:00:07.267 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 19:00:07.298 File Details: SQLServer2005_BC_x64.msi
06/29/2006 19:00:07.329
06/29/2006 19:00:07.360 Product Details:
06/29/2006 19:00:07.439 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixSqlWriter.inf
06/29/2006 19:00:07.470 baselinebuild = 1399
06/29/2006 19:00:07.501 build = 2047
06/29/2006 19:00:07.517 description = Microsoft SQL Server VSS Writer
06/29/2006 19:00:07.548 details = Service Pack for Microsoft SQL Server VSS Writer.
06/29/2006 19:00:07.579 kbarticle = KB913090
06/29/2006 19:00:07.595 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 19:00:07.626 lcid = 1033
06/29/2006 19:00:07.657 legalproductname = Microsoft SQL Server VSS Writer
06/29/2006 19:00:07.673 machinetype = x86
06/29/2006 19:00:07.704 package = HotFixSqlWriter
06/29/2006 19:00:07.735 packagetype = Hotfix
06/29/2006 19:00:07.767 productcode = {C0D2F614-5CE5-4DCB-8678-E5C9AF7044F8}
06/29/2006 19:00:07.782 productname = Redist9
06/29/2006 19:00:07.814 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 19:00:07.829 splevel = 0,1
06/29/2006 19:00:07.860 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 19:00:07.892 upgradecode = {65D8E1DF-6201-4B53-A0F9-E654F8E80F97}
06/29/2006 19:00:07.923 version = 9
06/29/2006 19:00:07.939
06/29/2006 19:00:07.970 File Group Details: MSI
06/29/2006 19:00:08.017 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 19:00:08.064 File Details: SqlWriter.msi
06/29/2006 19:00:08.110
06/29/2006 19:00:08.142 Instance Details: Microsoft SQL Server VSS Writer
06/29/2006 19:00:08.173 productcode = {C0D2F614-5CE5-4DCB-8678-E5C9AF7044F8}
06/29/2006 19:00:08.189
06/29/2006 19:00:08.220 Product Details:
06/29/2006 19:00:08.251 INF File Name: d:8eab555422b5e3d6e18cd38a7afa28HotFixSqlWriter_x64.inf
06/29/2006 19:00:08.282 baselinebuild = 1399
06/29/2006 19:00:08.298 build = 2047
06/29/2006 19:00:08.329 description = Microsoft SQL Server VSS Writer (64-bit)
06/29/2006 19:00:08.360 details = Service Pack for Microsoft SQL Server VSS Writer.
06/29/2006 19:00:08.392 kbarticle = KB913090
06/29/2006 19:00:08.407 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
06/29/2006 19:00:08.439 lcid = 1033
06/29/2006 19:00:08.454 legalproductname = Microsoft SQL Server VSS Writer (64-bit)
06/29/2006 19:00:08.485 machinetype = x64
06/29/2006 19:00:08.517 package = HotFixSqlWriter_x64
06/29/2006 19:00:08.548 packagetype = Hotfix
06/29/2006 19:00:08.564 productname = Redist9
06/29/2006 19:00:08.595 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
06/29/2006 19:00:08.610 splevel = 0,1
06/29/2006 19:00:08.642 supportdir = d:8eab555422b5e3d6e18cd38a7afa28
06/29/2006 19:00:08.673 upgradecode = {E9031696-DD39-4C25-BAEB-425FF28279EA}
06/29/2006 19:00:08.689 version = 9
06/29/2006 19:00:08.720
06/29/2006 19:00:08.735 File Group Details: MSI
06/29/2006 19:00:08.767 sourcepath = <SUPPORTDIR><PACKAGE>Files
06/29/2006 19:00:08.798 File Details: SqlWriter_x64.msi
06/29/2006 19:00:08.814
06/29/2006 19:00:08.845 Authenticating user using Windows Authentication
06/29/2006 19:00:08.876 SQL Service MSSQLServer was previously running, ready for authentication
06/29/2006 19:00:08.907 SQL Agent Service SQLSERVERAGENT was previously running
06/29/2006 19:00:09.423 User authentication was successful
06/29/2006 19:00:09.439 Attempting to install product: Redist9
06/29/2006 19:00:13.235 Successfully installed product: Redist9
06/29/2006 19:00:13.251 Attempting to install product: Redist9
06/29/2006 19:00:18.079 Successfully installed product: Redist9
06/29/2006 19:00:18.142 Attempting to install product: SQL9
06/29/2006 19:03:29.328 Successfully installed product: SQL9
06/29/2006 19:03:29.375 Attempting to install product: OLAP9
06/29/2006 19:04:45.906 Successfully installed product: OLAP9
06/29/2006 19:04:45.921 Attempting to install product: RS9
06/29/2006 19:05:13.952 Successfully installed product: RS9
06/29/2006 19:05:13.983 Attempting to install product: NS9
06/29/2006 19:06:11.999 Successfully installed product: NS9
06/29/2006 19:06:12.030 Attempting to install product: DTS9
06/29/2006 19:08:03.842 Successfully installed product: DTS9
06/29/2006 19:08:03.857 Attempting to install product: SQLTools9
06/29/2006 19:12:20.746 Successfully installed product: SQLTools9
06/29/2006 19:12:20.778 Attempting to install product: Redist9
06/29/2006 19:12:24.637 Successfully installed product: Redist9
06/29/2006 19:12:24.762 Attempting to install product: Redist9
06/29/2006 19:12:27.309 Successfully installed product: Redist9
06/29/2006 19:12:27.543 Attempting to install product: Redist9
06/29/2006 19:12:31.059 Successfully installed product: Redist9
06/29/2006 19:12:31.246 Attempting to install product: Redist9
06/29/2006 19:12:34.512 Successfully installed product: Redist9
06/29/2006 19:12:34.621
06/29/2006 19:12:34.653 Product Status Summary:
06/29/2006 19:12:34.684 Product: SQL Server Native Client
06/29/2006 19:12:34.731 SQL Server Native Client (RTM ) - Success
06/29/2006 19:12:34.762
06/29/2006 19:12:34.793 Product: Setup Support Files
06/29/2006 19:12:34.824 Setup Support Files (RTM ) - Success
06/29/2006 19:12:34.856
06/29/2006 19:12:34.887 Product: Database Services
06/29/2006 19:12:34.918 Database Services (SP1 2047 ENU) - Success
06/29/2006 19:12:34.949 Analysis Services (SP1 2047 ENU) - Success
06/29/2006 19:12:34.981 Reporting Services (RTM 1399 ENU) - Failure
06/29/2006 19:12:35.028
06/29/2006 19:12:35.059 Product: Notification Services
06/29/2006 19:12:35.090 Notification Services (SP1 2047 ENU) - Success
06/29/2006 19:12:35.184
06/29/2006 19:12:35.246 Product: Integration Services
06/29/2006 19:12:35.293 Integration Services (SP1 2047 ENU) - Success
06/29/2006 19:12:35.324
06/29/2006 19:12:35.356 Product: Client Components
06/29/2006 19:12:35.387 Client Components (SP1 2047 ENU) - Success
06/29/2006 19:12:35.434
06/29/2006 19:12:35.465 Product: MSXML 6.0 Parser
06/29/2006 19:12:35.496 MSXML 6.0 Parser (RTM ) - Success
06/29/2006 19:12:35.528
06/29/2006 19:12:35.543 Product: SQLXML4
06/29/2006 19:12:35.574 SQLXML4 (RTM ) - Success
06/29/2006 19:12:35.621
06/29/2006 19:12:35.637 Product: Backward Compatibility
06/29/2006 19:12:35.668 Backward Compatibility (RTM ) - Success
06/29/2006 19:12:35.699
06/29/2006 19:12:35.731 Product: Microsoft SQL Server VSS Writer
06/29/2006 19:12:35.762 Microsoft SQL Server VSS Writer (RTM ) - Success
06/29/2006 19:12:35.824
06/29/2006 19:12:35.856 Hotfix package completed
06/29/2006 19:12:36.246 Hotfix package closed

View 5 Replies View Related

Is It Possible To Move My Sql 2000 Database (in C Disk) To Another Disk (Disk) ?

Dec 28, 2006

hello,all
          I am new to Sql 2000,I installed sql 2000 database in C disk,but Now I found my C disk space is smaller than before,So I want to move my databse(include data and structure)   from C Disk to D Disk(its space is very large) .
         is it possible to do it ? 
         if its can be done ,do I need to change my asp.net program source code (exp: chaneg my crystal  report connectstring ) ?
        thanks in advanced!
 
 
 
      

View 1 Replies View Related

How To Increase A Session Timeout For Report Creation Uing SQL Server 2005 Reporting Services.

Dec 31, 2007



Hi,
Does any know how to increase a session timeout for Report Creation uing SQL Server 2005 Reporting Services. Iam trying to export a report (to a .pdf) using SQL 05 reporting services. However, it seems that the the query is timing out coz of session-time out. Can anyone tell me how to increase this value ?


Thanks
Nik

View 11 Replies View Related

Reporting Services :: Failure Sending Mail - The Transport Failed To Connect To The Server

Jun 25, 2015

I am trying to create subscription on report manager.

Getting this error: "Failure sending mail: The transport failed to connect to the server. ".

how to resolve this..

View 8 Replies View Related

Database Connection Timeout / Dropped

Jan 25, 2013

My sql server is setup to use windows authentication. From time to time one of the applications on that server would have issues connecting to that server. I changed it to use sql authentication and all of a sudden all the problems went away.

View 8 Replies View Related

A Connection Cannot Be Made To The Database. Timeout Expired.

Feb 19, 2008

Looks like I'm up to no good as usual.

Basically due to a client spec, I had to create 115 datasets (one for each of my 115 tables).

After I created the 111th, I am getting the following error:

A connection cannot be made to the database. Timeout Expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.


How do I clear the pooled connections or increase the max pool size?

I suppose what happened is each time I create a dataset it opens a connection to the database and these connections aren't being terminated...

View 3 Replies View Related

Connection Failure To SQL When Database Updated

Jan 23, 2008

Hi,

I have very little, to zero, IT configuration knowledge and I am hoping that someone is able to help me out.

I am currently writing the SQL scripts and developing the reports in the SQL Server Business Intelligence Development Studio, and then deploying the reports to the server for managers to eventually view.

Recently the IT section updated the test database (temp) that is connected to SQL Server 2005, with the live database (production), so that the data and database structure were up to date for me to create the reports.

When the update was done, the connection to SQL Server failed, and the newly appointed IT person responsible for SQL does not know how to resolve the problem. Up until yesterday I was getting a message that said that the connection has failed and then today I have the following message (she has been trying very hard to get it working):

An error occurred during local report processing.
An error has occurred during report processing.
Query execution failed for dataset 'Division'.
The SELECT permission was denied on the object 'Dim1', database 'payglobal', schema 'dbo'.

The reports that were deployed to the server prior to the update are still accessible however I am unable to review any reports I edit within the Development Studio. It has been out of action now for nearly two weeks.

Could someone please give me very detailed instructions on where the IT person should look, and what she should do to fix the problem. I will then pass these onto her.

Thanks.

View 3 Replies View Related

Recovery From LOG Disk Failure

Dec 30, 2004

I am writing up a general purpose document regarding Disaster Recovery and Backup and Restore, etc. I have a question that I've been unable to find any definitive answer on, and I was hoping that someone might have an answer.

Here is the scenario and what I have so far, and my question:

Scenario - A simple database, with one MDF and one LDF, each on it's own disk, with no mirroring or filegroups etc.

Disaster - the LOG disk fails.

To simulate the disaster, I shut down SQL Server, and delete the LDF manually.

When I restart SQL Server, the database is marked as suspect. As expected :)

So, now the recovery begins..... I've read that in this case there is no data loss, but I find that hard to believe. Can anyone confirm?

Anyway, how to restore the database to usable status? Here is what I've come up with so far:

1) Do a backup of "the tail of the log." This works even though there is no log. I have no idea why really, but I can't proceed otherwise.

2) Detach the database.

3) Reattach the database. This auto-creates a new log file (albeit not in the location I want, which makes for more work after).

At this point the database appears to be fine. I have not seen any lost data or problems, but of course I'm working on a test database, not with live users hitting it constantly. If the database were under heavy use, I expect that there might indeed be data lost?

Is this the recommended way to recover from a disaster of this type? Or, would it be better to just go back to your last good backups and forget about "up to the minute" recovery in this case? Or is there yet another means?

Thanks,
Travis

View 3 Replies View Related

Integration Services :: Failure Sending Mail / Connection Attempt Failed Because Connected Party Did Not Properly Respond

Jul 7, 2015

I recently started working on SSIS packages and I have a package which will Validate a table records and prepare a txt file with all details and sends the email to approriate email ids. The problem i'm facing is I'm getting System.Net.Mail.SmtpException  with inner exception as A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xx.xx.xx.xx:25. I'm using SMTPConnection and Windows Authentication as credentials.I also add the ISServerExec.exe to the firewall exclusion list still it throws the same error.

View 3 Replies View Related

Timeout Expired. The Timeout Period Elapsed Prior To Obtaining A Connection From The Pool

Jan 13, 2008

 
Server Error in '/' Application.


Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.InvalidOperationException: Timeout expired.  The timeout period elapsed prior to obtaining a connection from the pool.  This may have occurred because all pooled connections were in use and max pool size was reached.Source Error:



An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:



[InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.]
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +1188873
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +413
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
LogDo.Log_Db_Save(String sjm, String k_sql, String bz) +438
LogDo.Log_Save(Exception e, String sql) +124
DataCaoZuo.Manage_ResultTB_Caozuo(String comstr) +145
Cls_UserManage.GetAllUserList() +18
Index.Page_Load(Object sender, EventArgs e) +83
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +34
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061


Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832

View 1 Replies View Related

Timeout Expired. The Timeout Period Elapsed Prior To Obtaining A Connection From The Pool.

Feb 5, 2004

Ok bear with me here :). I have a server that is getting about 1000000 hits per day with about 10,000 unique vistors. For the past 2 months I have been revamping my code trying to deal with the increase in traffic. I have 2 boxes, one for the website, and one for the SQL. They are connected through a secure backlink so that I dont have to worry about encrypting the data. So the problem started when I updated the MDAC components a few weeks ago. I started getting these freaking timeout errors, they are up to about 1000 errors per hour. I have been monitoring the connection pooling using the system monitor for about a week and have noticed that I am not maxing out the pooling but I am still dropping connections. I went into the web.config and turned my max connections to 1000. Unfortunately this didn't even put a dent in the problem. It doesn't matter if I have 12 or 212 open connections it still drops them. I am at my wits end with trying to debug this problem. I am wondering if anyone else has had similiar problems recently. Also on a side note I have checked all my connections to make sure that I am closing them. Not only do I close my datareaders but I also set them to nothing. In addition to closing and reseting my datareaders I am also disposing and reseting my connection objects as well as closing them. Any help would be greatly appreciated.

Thanks,
Daniel Christoffersen

View 3 Replies View Related

SSIS Connection Manager General TimeOut Vs Command Timeout

Oct 15, 2007



Hi All,

This is first time I am trying to ste timeout on SSIS package ,Can some one let me know which is the best way to set timeout for connection?
And what is the difference between General TimeOut and Command TimeOut?

Thanks,
Shilpa

View 4 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved