SQL 2005 Sp2 Works But SQL Maint Studio And The Instance Still Report As 9.0.1399
Jan 25, 2008
SQL 2005 SP2 install succeeds but in SQL Maintenance Studio the instance is still 9.0.1399. Also when I interogate using TSQL it is reported as 9.0.1399
Here's the log (I did try it a couple of times)
Time: 01/25/2008 13:25:05.338
KB Number: KB921896
Machine: ------------- (I took this out)
OS Version: Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
Cluster Installation: No
**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed
**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Setup Support Files ENU 9.2.3042 x86
Reporting Services (MSSQLSERVER) ENU SP2 9.00.3042.00 x86 STANDARD
SQL Server Native Client ENU 9.00.3042.00 x86
Client Components ENU SP2 9.2.3042 x86 STANDARD
MSXML 6.0 Parser ENU 6.10.1200.0 x86
SQLXML4 ENU 9.00.3042.00 x86
Backward Compatibility ENU 8.05.2004 x86
Microsoft SQL Server VSS Writer ENU 9.00.3042.00 x86
**********************************************************************************
Products Disqualified & Reason
Product Reason
**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID
**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 3042
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Reporting Services (MSSQLSERVER)
Product Version (Previous): 3042
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRS9_Hotfix_KB921896_sqlrun_rs.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : SQL Server Native Client
Product Version (Previous): 3042
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlncli.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Client Components
Product Version (Previous): 3042
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : MSXML 6.0 Parser
Product Version (Previous): 1200
Product Version (Final) : 6.10.1129.0
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_msxml6.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : SQLXML4
Product Version (Previous): 3042
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_sqlxml4.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Backward Compatibility
Product Version (Previous): 2004
Product Version (Final) : 2004
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SQLServer2005_BC.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 3042
Product Version (Final) : 3042
Status : Success
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlWriter.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
**********************************************************************************
Summary
Success
Exit Code Returned: 0
View 4 Replies
ADVERTISEMENT
Jun 20, 2007
I'm having a strange problem with this but I know (and admit) that the problem is on my PC and nowhere else. My firewall was causing a problem because I was unable to PING the database server, switching this off gets a successful PING immediately. The most useful utility to date is running netstat -an in the command window. This illustrates all the connections that are live and ports that are being listed to. I can establish a connection both by running
telnet sql5.hostinguk.net 1433 and
sqlcmd -S sql5.hostinguk.net -U username -P password
See below:
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
TCP 81.105.102.47:1134 217.194.210.169:1433 ESTABLISHED
TCP 81.105.102.47:1135 217.194.210.169:1433 ESTABLISHED
TCP 127.0.0.1:1031 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5354 0.0.0.0:0 LISTENING
TCP 127.0.0.1:51114 0.0.0.0:0 LISTENING
TCP 127.0.0.1:51201 0.0.0.0:0 LISTENING
TCP 127.0.0.1:51202 0.0.0.0:0 LISTENING
TCP 127.0.0.1:51203 0.0.0.0:0 LISTENING
TCP 127.0.0.1:51204 0.0.0.0:0 LISTENING
TCP 127.0.0.1:51206 0.0.0.0:0 LISTENING
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1025 *:*
UDP 0.0.0.0:1030 *:*
UDP 0.0.0.0:3456 *:*
UDP 0.0.0.0:4500 *:*
UDP 81.105.102.47:123 *:*
UDP 81.105.102.47:1900 *:*
UDP 81.105.102.47:5353 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1086 *:*
UDP 127.0.0.1:1900 *:*
Both these utilities show as establishing a connection in netstat so I am able to connect the database server every time, this worked throughout yesterday and has continued this morning.
The problem is when I attempt to use SQL Server Management Studio. When I attempt to connect to tcp:sql5.hostinguk.net, 1433 nothing shows in netstat at all. There is an option to encrypt the connection in the connection properties tab in management studio, when I enable this I do get an entry in netstat -an, see below:
TCP 81.105.102.47:1138 217.194.210.169:1433 TIME_WAIT
TCP 81.105.102.47:1139 217.194.210.169:1433 TIME_WAIT
TCP 81.105.102.47:1140 217.194.210.169:1433 TIME_WAIT
Amost as if it's trying the different ports but you get this time_wait thing. The error message is more meaningful and hopefull because I get:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) (.Net SqlClient Data Provider)
I would expect this as the DNS has not been advised to encrypt the conection.
This is much better than the : Login failed for user 'COX10289'. (.Net SqlClient Data Provider) that I get, irrespective of whether I enter a password or not.
This is on a XP machine trying to connect to the remote webhosting company via the internet.
I can ping the server
I have enabled shared memory and tcp/ip in protocols, named pipes and via are disabled
I do not have any aliases set up
No I do not force encryption
I wonder if you have any further suggestions to this problem?
View 7 Replies
View Related
Jan 24, 2006
It works fine and I see the system tables and can make my own tables.
But how do I open a standalone MDF file with it? Or maybe it is a restriction ?
I am trying to get to the database for my personal start kit.
View 2 Replies
View Related
Jul 8, 2007
Hi all,I'm having a big problem here. I can't seem to connect to a database of MSSQL Server 2005... Here is what I've did:1. Under the Server Explorer>Data Connections. Right click and choose "Add Connection..."2. Data Source was "Microsoft SQL Server Database File". Click OK.3. I browse to the database in the MSSQL.2/MSSQL/Data folder.4. Click on the "Advanced" button, and change the default DataSource from .SQLEXPRESS to .MSSQLSERVER. Click OK5. Received this error:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default setting SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 25 - Connection string is not valid) Only .SQEXPRESS that I was able to connect to... i've tried the solution from Microsoft, opened SQL Server 2005 Surface Area Configuration and enabled "Local and remote connections", checked the option "Using both TCP/IP and named pipes" but it didn't help. This is frustrating because I can't get the Membership provider, login to work on my host. Please help. Thank you very much,Kenny.
View 2 Replies
View Related
Sep 12, 2006
Hi all,
i have installed SQL client instance on my Desktop "Machine-A", and i used to connect to SQLServer2000 running on another "Machine-B" by using valid username and password.
i created a DTS package and i used to run it. im very confused how the communication happens between the two machines and which process run where and which initiates which and which machine allocates waht resources. im really interested to know all these things. if any one know plz help me out.
Thanks in advance.
View 1 Replies
View Related
Jun 13, 2006
Hi,
What are the step to upgrade
SQl 2005 Beta version {9.00.0852} to SQl 2005 ver {9.00.1399.06}
also let me know where I can download .it
Thanks in advance
View 4 Replies
View Related
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
Apr 10, 2008
Hi,
I've created an SSRS report in Visual Studio 2005 which runs fine in the preview. I have a list of server names which when clicked on expands to a list of databases on the chosen server. When I click on a database it then queries a table of information and displays information on that database. The query is something like:
SELECT * FROM MyDB.dbo.DB_info
WHERE ServerName = @ServerName and DBname = @DBname
This works fine in preview mode. When I run it in SQL Management Studio via the Custom Reports menu it only works when the chosen server is the one that contains MyDB. I've run a trace and can see the query being issued when I use preview mode. However, when I run it from SSMS I don't see any query being issued to the database. This seems strange as it does return data in the instance described above and if I put MyDB into single-user mode it then complains that it can't access it so it is obviously trying to communicate with the database but not showing up on the trace. I've selected all events and only put a filter on the database name.
Seeing as all of the information is in the same table it seems odd that they query only works when the server name is the one where the database is held and that the query is not shown up in a trace. I'm running the report under the same credentials too.
I'm completely baffled by this so I'd be very grateful if someone could explain what might be happening here.
Thanks.
View 4 Replies
View Related
Feb 29, 2008
I have SSRS in Visual Studio. I created a query that works fine in SQL Server Management Studio, but when pasted into Visual Studio I get the error "An expression of non-boolean type specified in a context where a condition is expected, near '('.
Here is the query. Can anyone help on why this isn't working? Thanks.
SELECT CASE WHEN MONTH(dbo.MAS_CCS_ARN_InvHistoryHeader.SOTransDate) = MONTH(GETDATE()) AND YEAR(dbo.MAS_CCS_ARN_InvHistoryHeader.SOTransDate) = YEAR(GETDATE())
THEN dbo.MAS_CCS_ARO_InvHistoryDetail.SOExtChargeAmount ELSE 0 END AS CurrentMonth,
CASE WHEN SubString(dbo.MAS_CCS_GL_Account.Account,1,3) = '400' THEN 'ALEDO' ELSE ' ' END AS Location,
dbo.MAS_CCS_ARN_InvHistoryHeader.SOTransDate, dbo.MAS_CCS_ARN_InvHistoryHeader.InvoiceNumber,
dbo.MAS_CCS_AR1_CustomerMaster.CustomerName, dbo.MAS_CCS_ARO_InvHistoryDetail.DetailSeqNumber,
dbo.MAS_CCS_ARO_InvHistoryDetail.LineType, dbo.MAS_CCS_GL_Account.Account, dbo.MAS_CCS_ARO_InvHistoryDetail.SOExtChargeAmount
FROM dbo.MAS_CCS_AR1_CustomerMaster, dbo.MAS_CCS_ARN_InvHistoryHeader, dbo.MAS_CCS_ARO_InvHistoryDetail,
dbo.MAS_CCS_GL_Account
WHERE dbo.MAS_CCS_AR1_CustomerMaster.CustomerNumber = dbo.MAS_CCS_ARN_InvHistoryHeader.CustomerNumber AND
dbo.MAS_CCS_ARN_InvHistoryHeader.InvoiceNumber = dbo.MAS_CCS_ARO_InvHistoryDetail.InvoiceNumber AND
dbo.MAS_CCS_ARO_InvHistoryDetail.SOGLSalesAcct = dbo.MAS_CCS_GL_Account.AccountKey
View 1 Replies
View Related
Feb 25, 2006
I have encountered an error (as shown below) when attempting to install the SQL Server 2005 Express Edition 9.00.1399.06 on on my XP SP2 pc.
the file: "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSummary.txt"
show the following messages:
Machine : DUMBO
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
and ...
Machine : DUMBO
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Install : Failed
Log File : C:ProgrammiMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0015_DELL8400_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (17058) .
Error Number : 29503
Also, the file: "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_CBXP_Core.log"
show this message:
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"c:ProgrammiMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 17058
Aborting queue processing as nested installer has completed
Message pump returning: 17058
Maybe that's not a fatal error, but the SQLExpress service does not get installed.
Someone can help me?
Thanks!
View 9 Replies
View Related
Jun 29, 2007
Hello,
I have scalar valued function that simply convert a date from UTC to LET by using the .NET functions..
The code is very simple:
Partial Public Class UserFunction
<Microsoft.SqlServer.Server.SqlFunction(isDeterministic:=True, Name:="ConvertLETDatetoUTC")> _
Public Shared Function ConvertLETDatetoUTC(ByVal DateLETFormat As SqlDateTime) As DateTime
' Add your code here
Dim DateLETFormatToConvert As Date
DateLETFormatToConvert = DateLETFormat.Value
Return DateLETFormatToConvert.ToUniversalTime
End Function
End Class
select ConvertLETDatetoUTC('2007-06-25 10:00:00')
Now the problem is that the function works properly on my sql server instanc but in the moment I deploy the same code on the sql server instance on a remote machine the conversion doesn't work that means that date I pass is not converted.
On the SQl server machine there the .net framework 1.1 and 2.0 ...
I really don't know what to check to solve the problem .. some idea?
Thank you
View 7 Replies
View Related
Apr 17, 2007
Dear All,
I am basically new as far as SQl server 2005 concern.
I want to try out reporting services provided by sql server 2005.
That is make report using sql server 2005 and call that report from web or window application.
Please guide me in doing so or give me some useful link.
Thanks
View 1 Replies
View Related
Dec 8, 2007
I am creating a sql 2005 maintenance plan backup job. How can i specify 'write log files to some particular drive'. I am new to sql server 2005
Please advice
View 3 Replies
View Related
Dec 25, 2007
I need to create a maintplan for user databses,scheduled everyday 8pm
includes
Reoraganize index
fullbackup
Histoty clean up
What should be tasks order? is it okay reorganize index before full backup?
Please advice
View 1 Replies
View Related
Dec 26, 2007
I need to create a maintplan for user databses,scheduled everyday 8pm
includes
Reoraganize index
fullbackup
Histoty clean up
What should be tasks order? is it okay reorganize index before full backup?
Please advice
View 8 Replies
View Related
Apr 30, 2007
We have an application that uses MS SQL 2005 to stored information related to user internet usage. It is storing a large amout of data on a daily bases. The application is set to create a new logging database, when the current database reaches 10GB, then it will start logging to the new database.
A new database is getting created at the rate of about 1 new db every 48hrs and the backup maintenance plan for the user databases, is not picking up the new database. I have to remember to refresh the maintenance job so, the new database gets picked up and is included in the daily backup.
Is there a way to have the backup maintenance job refesh itself? Or possibly a stored procedure or some sort of scripting option to do this?
Please provide information if you have a way of doing this. Thanks.
View 7 Replies
View Related
Mar 5, 2008
Hi all,
For the first time, I want to set up the configuration of my SQL Server Management Studio Express (SSMSE) to allow me in doing the non-User-Instance/ADO.NET 2.0 programming from my VB 2005 Express. The SSMSE and VB 2005 Express are in my Windows XP Pro PC that is part of our NT 4 LAN System in our office. I read the article "How to configure SQL Server 2005 to allow remotre connections" in http://support.microsoft.com/kb/914277/ about (i) "Enable remote connections for SQL Server 2005 Express", (ii) Enable the SQL Server Browser service", (iii) Create exception in Windows Firewall, and (iv) Create an exception for the SQL Server Browser service in Windows Firewall. I entered the SQL Server Surface Area Configuration and I could not decide what options I should take for doing the non-User-Instance/ADO.NET 2.0 programming from my VB 2005 Express. I have the following questions on the page of "Minimize SQL Server 2005 Surface Area":
(1) I saw "Configure Surface Area for localhost [change computer]". I clicked on [change computer] and I saw the
following: Select Computer
The Surface Area Configuration of this surface area of this computer or a remote computer.
Specify a computer to configure: O Local computer
O Remote computer
Should I choose the "Local computer" or the "Remote computer" option?
(2) Below the "Configure Surface Area for localhost [change computer]",
I clicked on "Surface Area Configuration for Service and Connections", Select a component and then configure its services and connections: |-| SQLEXPRESS
|-| Database Engine
Service
I picked => Remote Connection
On the right-hand side, there are: O Local connections only
O Local and remorte connections
O Using TCP/IP
O Using named pipes only
O Using both TCP/IP and named pipes
Should I choose O Local and remorte connections and O Using named pipes only?
Please help and tell me what options I should choose in (1) and (2).
Thanks in advance,
Scott Chang
View 10 Replies
View Related
Aug 8, 2007
Hello,
I just installed SQL Server 2005 Enterprise edition from my company's DVD. It was installed with the setting of using both Integrated windows authenitication as well as basic named authenication. I installed all the options too: Database Engine, Analysis Services, Reporting Services, SQL Server compact edition, and Integration Services. When I look at services there are: SQL Server Integration Services, SQL Server Analysis Services, SQL Server Reporting Services, and SQL Server Browser. All of which are running. Something that took me offguard was the installation did not ask me to provide an SA password. Other than that, the install looked like it went good.
I was able to connect to the local instance of the SQL Server 2005 using the SQL Server Management Studio. I could connect with SA, or connect with Integrated Windows Authenication. Whoohoo. Off and running! As a matter of fact, for the SA account I could use any password and it would still log me in.
First thing I did was I went in to the copy wizard to attempt to copy a database from a server on our network to my local box. First it asked me for the remote server. Then when I specified my local instance in the wizard, the wizard complained that my local instance was NOT SQL Server 2005. Doh! This I didn't understand. I figured maybe I need to check for MS updates. Sure enough, I found that ther was a SP2 and then a hot-fix for that SP2. I applied both. Now I cannot connect from SQL Server Management studio to my local instance of SQL Server 2005 database server. I get the following error:
"An error occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)"
However, I went in to see what other services I could connect to, and here's the results:
Analysis Services : OK!
Reporting Services (Windows Auth/Basic/Forms) : NG "The reporting Services Instance could not be found (Microsoft.SqlServer.Management.UI.RSClient)"
SQL Server Compact Edition : NG "The database cannot be found. Check the path to the database. [ File Name = CCG092 ] (SQL Server Compact Edition ADO.NET Data Provider)
Integration Services : OK!
I can connect to other SQL Server databases on our network. However, just not my local one. No one on the network can connect to me either.
I even turned off my windows firewall and still no luck connecting to my own.
So something really went wrong when I applied SP2, however, admittedly from the error message when I tried to use the copy wizard, something was probably already wrong.
Any ideas?
Thanks!
View 4 Replies
View Related
Aug 16, 2007
I am running 2005 SP2 (It is the SP2 refresh as I downloaded the SP2 on 3/15/07) and I can't get the .txt maint plans to delete. The job completes successfully; however, the old .txt files are still there. I found this technote: http://support.microsoft.com/kb/938085
although I don't receive the error message in the KB. The report does have "New Component Output" as the 1st line in the report. I still don't see how deleting the 1st line of an already run job (the report) will affect a new run of the job.
Also, I checked the version of the Microsoft.SqlServer.MaintenancePlanTasks.dll and it is at 9.00.3043.00 (which is the SP2 Refresh) in KB 933508 ( http://support.microsoft.com/kb/933508 ).
I have several SQL/2005 servers and they all have this problem. Any help would be appreicated...
Thanks,
DeWayne
View 3 Replies
View Related
Apr 4, 2007
When I launch Visual Studio 2005 and choose to start a new project...I expect to see "Report Model" as an available template (at least that is what my book says).
How can I install this?
Why is it missing? Is it due to the order of my installations? I installed RS first then Visual Studio.
Any help is appreciated.
Thanks
View 1 Replies
View Related
Jan 25, 2007
Has anybody ever had VS2005 sometimes crash when deploying reports? It only happens once and awhile, but it is annoying. I was hoping this would go away with service pack 1, but it didn't.
Another problem that I thought would be fixed is when you try to close VS2005 after working on reports and it states "Cannot close because an active modal is active" occasionally.
BJ
View 3 Replies
View Related
Sep 27, 2007
I have a new named instance (SQL Server 2005 x64 SP2 (Build 3159) Developer edition) setup with dynamic port selection. A default instance was also running on the server prior to the named instance setup.
SQL Server Browser service is running. Remote connections are configured on the named instance. But still remote clients can only connect when the port number is specified after the instance name (servernameinstancename,9999). Without the port number, "error 26 - Error locating Server/instance specified" is thrown.
Doesn't the SQL Server Browser service eliminate the need for clients to specify the port number? What am I missing?
Thanks.
View 1 Replies
View Related
Nov 17, 2006
i ran my project on the visual studio 2005. but when i posted the same folder in teh wwwroot folder, it gave me the following error:
An attempt to attach an auto-named database for file C:PreranaOnCitoRunningFoldercitoason1606App_DataDatabase.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.
Can anybody help me show the way to get through it??
Any relevant comment/ suggestion is appreciated!!
View 1 Replies
View Related
Jul 3, 2007
I have an ASP.NET/ADO.NET page i wrote. It was based off of the development database during most development, and it switched over seamlessly to the production database.
Except for yesterday, when i went back to edit the page. It simply stopped returning results on my queries. To see if it was caused by bad values being passed to the sqldatasource, i tried it in the "Configure Data Source..." window, and it returns zero rows. When passing all of the exact same parameters to the same procedure in the same DB engine, even using the same login information, it works.
Just not in my ADO.NET app anymore...
Can anyone tell me what the hell could be going on here, please? I already rebuilt the page from an older version this morning, being very minimal on changes, and the last thing i changed before it stopped working was the connection string... *BUT* I have triple-checked that against the canon string we have always used in every working copy.
I'm losing a lot of hair over this . Any help would be greatly appreciated.
Thanks in advance
stoland
View 2 Replies
View Related
Jul 17, 2007
Hi,
I am unable to launch report builder from the report manager from a client machine. But I am able to launch from the localhost.
Even I am able to launch report builder by clicking reportbuilder.exe on the local machine.
Please help !!
OS - Windows XP professional
SQL Reporting Services 2005.
View 1 Replies
View Related
Apr 7, 2008
Hi everyone!
I'm using Microsoft Visual Studio 2005 to design reports. Is there any way to use one single image as background for a whole report-page? I only managed to set seperate background images for page header, body and footer, so the only 2 possibilities to solve this problem would be to either
* divide the image into 3 parts so that they fit exactly to the page parts or
* not use any page header and footer.
Is there another possibility that I've missed?
Any help is highly appreciated!
Thanks in advance,
Calad
View 1 Replies
View Related
Jul 6, 2015
I've gotten to the point of publishing the new reports on the SSRS server and have run into the following problem.
I use a field in the primary report with the "Go to report" action to open up another report (also published) for more details. It works properly from within ReportBuilder (2.0) using the report server and I can go to and from the secondary report as I expect. Its passing the correct parameters to the second report and its runs.
But when I use the reports from the SSRS web, the Go To link no longer works. Mouse hover shows its still a link but clicking goes no where. I can run both reports independently from SSRS and they still work.
I've tried this in IE and Chrome with no luck in either. I also poked around at Compatability view and popup blocker but nothing made any difference.
View 2 Replies
View Related
Mar 17, 2008
I have a bit of an odd problem in an sql statement where it works in management studio but not in c# when setting up a table adapter the sql is:
DECLARE @week char(2)
SET @Week = 7
SELECT student_id, acad_period, register_id, register_group, week_no, absence_code, attendance_type
FROM dbo.sttdstud
WHERE (student_id LIKE '%') AND (register_id LIKE '%') AND (register_group LIKE '%') AND
week_no = Case @Week when null Then '#' Else @Week End
the idea is if they don't enter a number it would bring up all records. This works in mangaement studio but c# brings up the error sql server doesn't support udt on excecution of the sql. This is sql server 2000. Any ideas why this doesn't work and how to fix it.
View 3 Replies
View Related
Jul 4, 2007
I have an SQL statement that, when run through SQL Server management studio works fine. However, when I run it on my ASP page, it doesn’t update the data! I have tried both as a stored procedure and as a simple commandText update statement.
All I do is simly update the value of a column based on another column – nothing particularly complex: update customer set dateChanged = System.DateTime.Now.ToString("dd-MMM-yyyy"), CURRSTAT = 'Active',custType = case WHEN cust_Changing_To IS NOT NULL THEN cust_Changing_To ELSE custType END,cust_Changing_To = NULLFROM customers_v WHERE CURRSTAT = 'Changing'
As you can see, nothing that complex. The line that is causing the problem is the case:
custType = case WHEN cust_Changing_To IS NOT NULL THEN cust_Changing_To ELSE custType END
all it does is if another nullable integer column is not null, sets it to the value of that column, else it retains its existing value.
Like I say, this works in Management studio, but I cannot get it to execute programatticaly from an asp page.
No exceptions are being thrown, it just doesn’t update the data.
Any ideas?
Thanks
View 1 Replies
View Related
Apr 4, 2008
I have a stored procedure which is run through MS Access (yuck). It does not appear to fail, but it does not populate certain tables, and is also rather complex. I did not write it, and am trying my best to fix it. However, when I run the same procedure with the same parameters from within Management Studio (database state is the same, I restore from backup before trying out each execution) it populates the tables correctly. I have profiled both executions (from MS and from Access) and it is running with the same NTUsername, and thus the same permissions. The process used to work and then some changes were made to the DB which seem to have broken it from Access. As far as I know, the Access code has not changed, although it may have done so. The proc call from Access uses the same parameters, and does not throw an error, although it does not appear to close the connection to the DB (I'm looking into this). Access uses an ODBC connection to connect to SQL Server.
Any ideas?
View 3 Replies
View Related
Oct 26, 2006
Hi,I have an interesting scenario. I have a SQL Server 2000 Standard Edition instance running on Computer A. I'm trying to access it through computers B and C.Computer B has Sql Server 2005 Express Edition installed and I was able to use its Management Studio and connect to instance on Computer A.Computer C has SQL Server 2000 Standard Edition installed. When I try to connect to the instance on Computer A, I get connection failed message.I checked some settings. Both TCP/IP and Named pipes are enabled on the instance in A. The TCP/IP port is set to 1433 for both client and server.Please give me some ideas as to how I can solve this problem. -Thanks
View 5 Replies
View Related
Feb 21, 2008
SELECT favorites.FID, favorites.filename, favorites.username, files.status, files.private, files.views, files.title FROM favorites INNER JOIN files ON favorites.filename = files.filename WHERE (favorites.username = @username) AND (files.status IS NULL) AND (files.private = @private)@private is manually set to 'no'@username is set to profile.usernamewhen I run the above query in microsoft sql server mgmt studio express on the database, it presents all the information i'm asking for very easily. however when i try to implement this query on a aspx .net2.0 page with teh sqldatasource and a gridview, no data is displayed.anyone know what my problem is?
View 1 Replies
View Related
