Installing Sp1 On Cloned DB Server To VM Server

Feb 6, 2007

We have a HP server with windows 2003. MS sql 2005 was installed on it. The third party databases were installed. SP1 was never installed. This server (paahouentsqlp) PROD was cloned and placed on a vm server.

When server came up on vm enviornment the server name was changed to (paahouentsqlt) TEST. Nothing was done to the SQL environment. No registery entries were altered. No sp_dropserver or sp_addserver were ran. TEST server seems to be running ok.

I have attempted to install sp1 on TEST server (paahouentsqlt). The enumeration process takes about 1-2 hrs. When I finally get a screen all product selections are grey out except for SQL Server Native Client, Setup Support File, MSXML 6.0 Parser, SQLXML4, Backward Compatibility, and MS SQL Server VSS Writer. Than I'm prompted with a couple of NEXT screens, than Finish.

When I look at the product version it still shows it as the original 9.0.1399

Any ideas? Log included.

02/03/2007 11:27:23.786 ================================================================================
02/03/2007 11:27:23.801 Hotfix package launched
02/03/2007 11:27:23.801 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:23.801 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 11:27:23.817 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:23.817 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 11:27:24.239 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:24.239 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 11:27:24.239 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:24.239 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 11:27:24.239 Local Computer:
02/03/2007 11:27:24.255 Target Details: PAAHOUENTSQLT
02/03/2007 11:27:24.255 commonfilesdir = C:Program FilesCommon Files
02/03/2007 11:27:24.255 lcidsupportdir = e:50b73396ce0726e1761033
02/03/2007 11:27:24.255 programfilesdir = C:Program Files
02/03/2007 11:27:24.255 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 11:27:24.255 supportdirlocal = e:50b73396ce0726e176
02/03/2007 11:27:24.255 windir = C:WINDOWS
02/03/2007 11:27:24.255 winsysdir = C:WINDOWSsystem32
02/03/2007 11:27:24.255
02/03/2007 11:27:24.270 Enumerating applicable products for this patch
02/03/2007 11:27:24.395 Found Redist 2005 product definition
02/03/2007 11:27:24.755 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:24.755 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 11:27:24.755 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:24.755 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 11:27:26.411 Attempting to check IA 64 platform
02/03/2007 11:27:26.411 Result of IA64 check: 0
02/03/2007 11:27:26.411 Last error: 0
02/03/2007 11:27:26.426 Found Redist 2005 product definition
02/03/2007 11:27:26.583 Found Redist 2005 product definition
02/03/2007 11:27:26.833 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:26.833 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 11:27:26.833 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 11:27:26.833 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 11:27:28.567 Attempting to check IA 64 platform
02/03/2007 11:27:28.567 Result of IA64 check: 0
02/03/2007 11:27:28.567 Last error: 0
02/03/2007 11:27:28.583 Found SQL 2005 product definition
02/03/2007 11:39:12.833 Found OLAP Server 2005 product definition
02/03/2007 11:50:56.333 Found Notification Services 2005 product definition
02/03/2007 12:02:39.786 Found Report Server 2005 product definition
02/03/2007 12:14:23.051 Found DTS 2005 product definition
02/03/2007 12:26:06.801 Found SQL 2005 Tools product definition
02/03/2007 12:37:50.208 Found Redist 2005 product definition
02/03/2007 12:37:50.848 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:50.848 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 12:37:50.848 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:50.848 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 12:37:51.255 Attempting to check IA 64 platform
02/03/2007 12:37:51.255 Result of IA64 check: 0
02/03/2007 12:37:51.255 Last error: 0
02/03/2007 12:37:51.270 Found Redist 2005 product definition
02/03/2007 12:37:51.426 Found Redist 2005 product definition
02/03/2007 12:37:51.661 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:51.676 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 12:37:51.676 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:51.676 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 12:37:52.083 Attempting to check IA 64 platform
02/03/2007 12:37:52.083 Result of IA64 check: 0
02/03/2007 12:37:52.098 Last error: 0
02/03/2007 12:37:52.114 Found Redist 2005 product definition
02/03/2007 12:37:52.333 Found Redist 2005 product definition
02/03/2007 12:37:52.551 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:52.551 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 12:37:52.551 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:52.551 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 12:37:52.911 Attempting to check IA 64 platform
02/03/2007 12:37:52.926 Result of IA64 check: 0
02/03/2007 12:37:52.926 Last error: 0
02/03/2007 12:37:52.942 Found Redist 2005 product definition
02/03/2007 12:37:53.098 Found Redist 2005 product definition
02/03/2007 12:37:53.364 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:53.364 Successfully read registry key: CommonFilesDir, string value = C:Program FilesCommon Files
02/03/2007 12:37:53.364 Successfully opened registry key: SOFTWAREMicrosoftWindowsCurrentVersion
02/03/2007 12:37:53.364 Successfully read registry key: ProgramFilesDir, string value = C:Program Files
02/03/2007 12:37:53.676 Attempting to check IA 64 platform
02/03/2007 12:37:53.676 Result of IA64 check: 0
02/03/2007 12:37:53.676 Last error: 0
02/03/2007 12:37:53.692 Found Redist 2005 product definition
02/03/2007 12:37:53.864 Product Details:
02/03/2007 12:37:53.880 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlncli.inf
02/03/2007 12:37:53.880 alwaysinstall = 1
02/03/2007 12:37:53.880 baselinebuild = 1399
02/03/2007 12:37:53.880 build = 2047
02/03/2007 12:37:53.880 description = SQL Server Native Client
02/03/2007 12:37:53.880 details = Service Pack for Microsoft SQL Server Native Client.
02/03/2007 12:37:53.880 kbarticle = KB913090
02/03/2007 12:37:53.880 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:53.880 lcid = 1033
02/03/2007 12:37:53.880 legalproductname = Microsoft SQL Native Client
02/03/2007 12:37:53.880 machinetype = x86
02/03/2007 12:37:53.880 package = HotFixSqlncli
02/03/2007 12:37:53.880 packagetype = Hotfix
02/03/2007 12:37:53.880 productcode = {50A0893D-47D8-48E0-A7E8-44BCD7E4422E}
02/03/2007 12:37:53.880 productname = Redist9
02/03/2007 12:37:53.895 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:53.895 splevel = 0,1
02/03/2007 12:37:53.895 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:53.895 upgradecode = {A6B19337-7392-4765-8675-5C25B758BA37}
02/03/2007 12:37:53.895 version = 9
02/03/2007 12:37:53.895
02/03/2007 12:37:53.895 File Group Details: MSI
02/03/2007 12:37:53.895 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:53.895 File Details: sqlncli.msi
02/03/2007 12:37:53.895
02/03/2007 12:37:53.895 Instance Details: SQL Server Native Client
02/03/2007 12:37:53.895 productcode = {50A0893D-47D8-48E0-A7E8-44BCD7E4422E}
02/03/2007 12:37:53.895
02/03/2007 12:37:53.895 Product Details:
02/03/2007 12:37:53.895 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlncli_x64.inf
02/03/2007 12:37:53.895 alwaysinstall = 1
02/03/2007 12:37:53.895 baselinebuild = 1399
02/03/2007 12:37:53.926 build = 2047
02/03/2007 12:37:53.926 description = SQL Server Native Client (64-bit)
02/03/2007 12:37:53.926 details = Service Pack for Microsoft SQL Server Native Client.
02/03/2007 12:37:53.926 kbarticle = KB913090
02/03/2007 12:37:53.926 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:53.926 lcid = 1033
02/03/2007 12:37:53.926 legalproductname = Microsoft SQL Native Client (64-bit)
02/03/2007 12:37:53.926 machinetype = x64
02/03/2007 12:37:53.926 package = HotFixSqlncli_x64
02/03/2007 12:37:53.926 packagetype = Hotfix
02/03/2007 12:37:53.942 productname = Redist9
02/03/2007 12:37:53.942 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:53.942 splevel = 0,1
02/03/2007 12:37:53.942 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:53.942 upgradecode = {6EC3319D-84BE-4C32-AA91-7D6057CF05A5}
02/03/2007 12:37:53.942 version = 9
02/03/2007 12:37:53.942
02/03/2007 12:37:53.942 File Group Details: MSI
02/03/2007 12:37:53.942 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:53.942 File Details: sqlncli_x64.msi
02/03/2007 12:37:53.942
02/03/2007 12:37:53.942 Product Details:
02/03/2007 12:37:53.942 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlSupport.inf
02/03/2007 12:37:53.942 alwaysinstall = 1
02/03/2007 12:37:53.942 baselinebuild = 1399
02/03/2007 12:37:53.958 build = 2047
02/03/2007 12:37:53.958 description = Setup Support Files
02/03/2007 12:37:53.958 details = Service Pack for the SQL Server support files.
02/03/2007 12:37:53.958 kbarticle = KB913090
02/03/2007 12:37:53.958 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:53.958 keyqualifier = 1
02/03/2007 12:37:53.958 lcid = 1033
02/03/2007 12:37:53.958 legalproductname = SQL Server 2005 Setup Support Files
02/03/2007 12:37:53.958 machinetype = x86
02/03/2007 12:37:53.958 package = HotFixSqlSupport
02/03/2007 12:37:53.958 packagetype = Hotfix
02/03/2007 12:37:53.958 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
02/03/2007 12:37:53.958 productname = Redist9
02/03/2007 12:37:53.958 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:53.973 splevel = 0,1
02/03/2007 12:37:53.973 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:53.973 upgradecode = {3A91FA19-A197-467C-850F-0AFE90899371}
02/03/2007 12:37:53.973 version = 9
02/03/2007 12:37:53.973
02/03/2007 12:37:53.973 File Group Details: MSP
02/03/2007 12:37:53.973 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:53.973 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:53.989 File Details: SqlSupport.msp
02/03/2007 12:37:53.989
02/03/2007 12:37:53.989 Instance Details: Setup Support Files
02/03/2007 12:37:53.989 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
02/03/2007 12:37:53.989
02/03/2007 12:37:53.989 Product Details:
02/03/2007 12:37:53.989 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSQL.inf
02/03/2007 12:37:53.989 baselinebuild = 1399
02/03/2007 12:37:53.989 baselinebuildmax = 2047
02/03/2007 12:37:53.989 build = 2047
02/03/2007 12:37:53.989 description = Database Services
02/03/2007 12:37:53.989 details = Service Pack for the SQL Server database engine, and the tools for managing relational and XML data, Replication, and Full-Text Search.
02/03/2007 12:37:53.989 kbarticle = KB913090
02/03/2007 12:37:54.005 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.005 lcid = 1033
02/03/2007 12:37:54.005 legalproductname = SQL Server Database Services 2005
02/03/2007 12:37:54.005 machinetype = x86
02/03/2007 12:37:54.005 package = HotFixSQL
02/03/2007 12:37:54.005 packagetype = Hotfix
02/03/2007 12:37:54.005 productname = SQL9
02/03/2007 12:37:54.005 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.005 splevel = 0,1
02/03/2007 12:37:54.005 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.005 validateauthentication = true
02/03/2007 12:37:54.005 version = 9
02/03/2007 12:37:54.005
02/03/2007 12:37:54.005 File Group Details: MSP
02/03/2007 12:37:54.020 lockedfilecheck = 1
02/03/2007 12:37:54.020 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:54.020 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.020 File Details: sqlrun_sql.msp
02/03/2007 12:37:54.020
02/03/2007 12:37:54.020 Product Details:
02/03/2007 12:37:54.020 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixAS.inf
02/03/2007 12:37:54.020 baselinebuild = 1399
02/03/2007 12:37:54.020 baselinebuildmax = 2047
02/03/2007 12:37:54.020 build = 2047
02/03/2007 12:37:54.020 description = Analysis Services
02/03/2007 12:37:54.020 details = Service Pack for Analysis Services, and the tools used to support online analytical processing (OLAP) and data mining.
02/03/2007 12:37:54.020 kbarticle = KB913090
02/03/2007 12:37:54.020 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.036 lcid = 1033
02/03/2007 12:37:54.036 legalproductname = SQL Server Analysis Services 2005
02/03/2007 12:37:54.036 machinetype = x86
02/03/2007 12:37:54.036 package = HotFixAS
02/03/2007 12:37:54.036 packagetype = Hotfix
02/03/2007 12:37:54.036 productname = OLAP9
02/03/2007 12:37:54.036 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.036 splevel = 0,1
02/03/2007 12:37:54.036 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.036 version = 9
02/03/2007 12:37:54.036
02/03/2007 12:37:54.036 File Group Details: MSP
02/03/2007 12:37:54.036 lockedfilecheck = 1
02/03/2007 12:37:54.036 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:54.051 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.051 File Details: sqlrun_as.msp
02/03/2007 12:37:54.051
02/03/2007 12:37:54.051 Product Details:
02/03/2007 12:37:54.051 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixNS.inf
02/03/2007 12:37:54.051 baselinebuild = 1399
02/03/2007 12:37:54.051 baselinebuildmax = 2047
02/03/2007 12:37:54.051 build = 2047
02/03/2007 12:37:54.051 description = Notification Services
02/03/2007 12:37:54.051 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.
02/03/2007 12:37:54.051 kbarticle = KB913090
02/03/2007 12:37:54.051 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.051 lcid = 1033
02/03/2007 12:37:54.051 legalproductname = SQL Server Notification Services 2005 instances
02/03/2007 12:37:54.051 machinetype = x86
02/03/2007 12:37:54.067 package = HotFixNS
02/03/2007 12:37:54.067 packagetype = Hotfix
02/03/2007 12:37:54.067 productname = NS9
02/03/2007 12:37:54.067 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.067 splevel = 0,1
02/03/2007 12:37:54.067 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.067 version = 9
02/03/2007 12:37:54.067
02/03/2007 12:37:54.067 File Group Details: MSP
02/03/2007 12:37:54.067 lockedfilecheck = 1
02/03/2007 12:37:54.067 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:54.067 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.067 File Details: sqlrun_ns.msp
02/03/2007 12:37:54.067
02/03/2007 12:37:54.067 Product Details:
02/03/2007 12:37:54.067 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixRS.inf
02/03/2007 12:37:54.083 baselinebuild = 1399
02/03/2007 12:37:54.083 baselinebuildmax = 2047
02/03/2007 12:37:54.083 build = 2047
02/03/2007 12:37:54.083 description = Reporting Services
02/03/2007 12:37:54.083 details = Service Pack for the Report Server and Report Builder, which manages, executes, renders, and distributes reports.
02/03/2007 12:37:54.083 kbarticle = KB913090
02/03/2007 12:37:54.083 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.098 lcid = 1033
02/03/2007 12:37:54.098 legalproductname = SQL Server Reporting Services 2005
02/03/2007 12:37:54.098 machinetype = x86
02/03/2007 12:37:54.098 package = HotFixRS
02/03/2007 12:37:54.098 packagetype = Hotfix
02/03/2007 12:37:54.098 productname = RS9
02/03/2007 12:37:54.098 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.098 splevel = 0,1
02/03/2007 12:37:54.098 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.098 validateauthentication = 1
02/03/2007 12:37:54.098 version = 9
02/03/2007 12:37:54.098
02/03/2007 12:37:54.098 File Group Details: MSP
02/03/2007 12:37:54.098 lockedfilecheck = 1
02/03/2007 12:37:54.114 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:54.114 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.114 File Details: sqlrun_rs.msp
02/03/2007 12:37:54.114
02/03/2007 12:37:54.114 Product Details:
02/03/2007 12:37:54.114 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixDTS.inf
02/03/2007 12:37:54.114 baselinebuild = 1399
02/03/2007 12:37:54.114 baselinebuildmax = 2047
02/03/2007 12:37:54.114 build = 2047
02/03/2007 12:37:54.114 description = Integration Services
02/03/2007 12:37:54.114 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.
02/03/2007 12:37:54.114 kbarticle = KB913090
02/03/2007 12:37:54.114 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.114 lcid = 1033
02/03/2007 12:37:54.114 legalproductname = SQL Server Integration Services 2005
02/03/2007 12:37:54.114 machinetype = x86
02/03/2007 12:37:54.114 package = HotFixDTS
02/03/2007 12:37:54.130 packagetype = Hotfix
02/03/2007 12:37:54.130 productname = DTS9
02/03/2007 12:37:54.130 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.130 splevel = 0,1
02/03/2007 12:37:54.130 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.130 version = 9
02/03/2007 12:37:54.130
02/03/2007 12:37:54.130 File Group Details: MSP
02/03/2007 12:37:54.130 lockedfilecheck = 1
02/03/2007 12:37:54.130 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:54.130 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.130 File Details: sqlrun_dts.msp
02/03/2007 12:37:54.130
02/03/2007 12:37:54.130 Product Details:
02/03/2007 12:37:54.130 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixTools.inf
02/03/2007 12:37:54.130 baselinebuild = 1399
02/03/2007 12:37:54.130 baselinebuildmax = 2047
02/03/2007 12:37:54.145 build = 2047
02/03/2007 12:37:54.145 description = Client Components
02/03/2007 12:37:54.145 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.
02/03/2007 12:37:54.145 kbarticle = KB913090
02/03/2007 12:37:54.145 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.145 lcid = 1033
02/03/2007 12:37:54.145 legalproductname = SQL Server Tools and Workstation Components 2005
02/03/2007 12:37:54.145 machinetype = x86
02/03/2007 12:37:54.145 package = HotFixTools
02/03/2007 12:37:54.145 packagetype = Hotfix
02/03/2007 12:37:54.145 productname = SQLTools9
02/03/2007 12:37:54.145 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.145 splevel = 0,1
02/03/2007 12:37:54.145 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.145 version = 9
02/03/2007 12:37:54.145
02/03/2007 12:37:54.161 File Group Details: MSP
02/03/2007 12:37:54.161 lockedfilecheck = 1
02/03/2007 12:37:54.161 parameters = SQLBUILD=2047 KBNUMBER=KB913090 REBOOT=ReallySuppress
02/03/2007 12:37:54.161 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.161 File Details: sqlrun_tools.msp
02/03/2007 12:37:54.161
02/03/2007 12:37:54.161 Product Details:
02/03/2007 12:37:54.161 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixMsxml6.inf
02/03/2007 12:37:54.161 baselinebuild = 1399
02/03/2007 12:37:54.161 build = 2047
02/03/2007 12:37:54.161 description = MSXML 6.0 Parser
02/03/2007 12:37:54.161 details = Service Pack for Microsoft XML 6.0 Parser.
02/03/2007 12:37:54.161 kbarticle = KB913090
02/03/2007 12:37:54.161 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.161 lcid = 1033
02/03/2007 12:37:54.161 legalproductname = MSXML 6.0 Parser
02/03/2007 12:37:54.161 machinetype = x86
02/03/2007 12:37:54.176 package = HotFixMsxml6
02/03/2007 12:37:54.176 packagetype = Hotfix
02/03/2007 12:37:54.176 productcode = {AEB9948B-4FF2-47C9-990E-47014492A0FE}
02/03/2007 12:37:54.176 productname = Redist9
02/03/2007 12:37:54.176 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.176 splevel = 0,1
02/03/2007 12:37:54.176 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.176 upgradecode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
02/03/2007 12:37:54.176 version = 9
02/03/2007 12:37:54.176
02/03/2007 12:37:54.176 File Group Details: MSI
02/03/2007 12:37:54.176 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.176 File Details: msxml6.msi
02/03/2007 12:37:54.176
02/03/2007 12:37:54.176 Instance Details: MSXML 6.0 Parser
02/03/2007 12:37:54.176 productcode = {AEB9948B-4FF2-47C9-990E-47014492A0FE}
02/03/2007 12:37:54.176
02/03/2007 12:37:54.192 Product Details:
02/03/2007 12:37:54.192 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixMsxml6_x64.inf
02/03/2007 12:37:54.192 baselinebuild = 1399
02/03/2007 12:37:54.192 build = 2047
02/03/2007 12:37:54.192 description = MSXML 6.0 Parser (64-bit)
02/03/2007 12:37:54.192 details = Service Pack for Microsoft XML 6.0 Parser.
02/03/2007 12:37:54.192 kbarticle = KB913090
02/03/2007 12:37:54.192 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.192 lcid = 1033
02/03/2007 12:37:54.192 legalproductname = MSXML 6.0 Parser (64-bit)
02/03/2007 12:37:54.192 machinetype = x64
02/03/2007 12:37:54.192 package = HotFixMsxml6_x64
02/03/2007 12:37:54.192 packagetype = Hotfix
02/03/2007 12:37:54.192 productname = Redist9
02/03/2007 12:37:54.208 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.208 splevel = 0,1
02/03/2007 12:37:54.208 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.208 upgradecode = {5BBED1F8-E6F3-4A02-BC97-26D35BE200CA}
02/03/2007 12:37:54.208 version = 9
02/03/2007 12:37:54.208
02/03/2007 12:37:54.208 File Group Details: MSI
02/03/2007 12:37:54.208 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.208 File Details: msxml6_x64.msi
02/03/2007 12:37:54.208
02/03/2007 12:37:54.208 Product Details:
02/03/2007 12:37:54.208 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlxml4.inf
02/03/2007 12:37:54.208 baselinebuild = 1399
02/03/2007 12:37:54.208 build = 2047
02/03/2007 12:37:54.208 description = SQLXML4
02/03/2007 12:37:54.208 details = Service Pack for Microsoft SQLXML 4.0.
02/03/2007 12:37:54.223 kbarticle = KB913090
02/03/2007 12:37:54.223 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.223 lcid = 1033
02/03/2007 12:37:54.223 legalproductname = SQLXML4
02/03/2007 12:37:54.223 machinetype = x86
02/03/2007 12:37:54.223 package = HotFixSqlxml4
02/03/2007 12:37:54.223 packagetype = Hotfix
02/03/2007 12:37:54.223 productcode = {A188FCCF-E929-494D-B1F1-4313E02ACD52}
02/03/2007 12:37:54.223 productname = Redist9
02/03/2007 12:37:54.223 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.223 splevel = 0,1
02/03/2007 12:37:54.223 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.223 upgradecode = {D9CA3D82-6F1B-41A7-8141-B90ACA8F865B}
02/03/2007 12:37:54.223 version = 9
02/03/2007 12:37:54.223
02/03/2007 12:37:54.223 File Group Details: MSI
02/03/2007 12:37:54.239 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.239 File Details: sqlxml4.msi
02/03/2007 12:37:54.239
02/03/2007 12:37:54.239 Instance Details: SQLXML4
02/03/2007 12:37:54.239 productcode = {A188FCCF-E929-494D-B1F1-4313E02ACD52}
02/03/2007 12:37:54.239
02/03/2007 12:37:54.239 Product Details:
02/03/2007 12:37:54.239 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlxml4_x64.inf
02/03/2007 12:37:54.239 baselinebuild = 1399
02/03/2007 12:37:54.239 build = 2047
02/03/2007 12:37:54.239 description = SQLXML4 (64-bit)
02/03/2007 12:37:54.239 details = Service Pack for Microsoft SQLXML 4.0.
02/03/2007 12:37:54.239 kbarticle = KB913090
02/03/2007 12:37:54.239 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.239 lcid = 1033
02/03/2007 12:37:54.255 legalproductname = SQLXML4 (64-bit)
02/03/2007 12:37:54.255 machinetype = x64
02/03/2007 12:37:54.255 package = HotFixSqlxml4_x64
02/03/2007 12:37:54.255 packagetype = Hotfix
02/03/2007 12:37:54.255 productname = Redist9
02/03/2007 12:37:54.255 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.255 splevel = 0,1
02/03/2007 12:37:54.255 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.255 upgradecode = {F457D8E6-7686-437D-9B17-E21D45CCABD8}
02/03/2007 12:37:54.255 version = 9
02/03/2007 12:37:54.255
02/03/2007 12:37:54.255 File Group Details: MSI
02/03/2007 12:37:54.255 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.255 File Details: sqlxml4_x64.msi
02/03/2007 12:37:54.270
02/03/2007 12:37:54.270 Product Details:
02/03/2007 12:37:54.270 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSQLServer2005_BC.inf
02/03/2007 12:37:54.270 baselinebuild = 1399
02/03/2007 12:37:54.270 build = 2047
02/03/2007 12:37:54.270 description = Backward Compatibility
02/03/2007 12:37:54.270 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
02/03/2007 12:37:54.270 kbarticle = KB913090
02/03/2007 12:37:54.270 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.270 lcid = 1033
02/03/2007 12:37:54.270 legalproductname = Microsoft SQL Server 2005 Backward Compatibility
02/03/2007 12:37:54.270 machinetype = x86
02/03/2007 12:37:54.270 package = HotFixSQLServer2005_BC
02/03/2007 12:37:54.270 packagetype = Hotfix
02/03/2007 12:37:54.270 productcode = {2243F21A-E132-44F7-BA13-024D0845C815}
02/03/2007 12:37:54.286 productname = Redist9
02/03/2007 12:37:54.286 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.286 splevel = 0,1
02/03/2007 12:37:54.286 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.286 upgradecode = {1E70C6C9-E1B7-4A74-BC8C-8EB5D010CEC9}
02/03/2007 12:37:54.286 version = 9
02/03/2007 12:37:54.286
02/03/2007 12:37:54.286 File Group Details: MSI
02/03/2007 12:37:54.286 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.286 File Details: SQLServer2005_BC.msi
02/03/2007 12:37:54.286
02/03/2007 12:37:54.286 Instance Details: Backward Compatibility
02/03/2007 12:37:54.286 productcode = {2243F21A-E132-44F7-BA13-024D0845C815}
02/03/2007 12:37:54.301
02/03/2007 12:37:54.301 Product Details:
02/03/2007 12:37:54.301 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSQLServer2005_BC_x64.inf
02/03/2007 12:37:54.301 baselinebuild = 1399
02/03/2007 12:37:54.301 build = 2047
02/03/2007 12:37:54.301 description = Backward Compatibility (64-bit)
02/03/2007 12:37:54.301 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
02/03/2007 12:37:54.301 kbarticle = KB913090
02/03/2007 12:37:54.301 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.301 lcid = 1033
02/03/2007 12:37:54.301 legalproductname = Microsoft SQL Server 2005 Backward Compatibility (64-bit)
02/03/2007 12:37:54.301 machinetype = x64
02/03/2007 12:37:54.301 package = HotFixSQLServer2005_BC_x64
02/03/2007 12:37:54.301 packagetype = Hotfix
02/03/2007 12:37:54.301 productname = Redist9
02/03/2007 12:37:54.317 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.317 splevel = 0,1
02/03/2007 12:37:54.317 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.317 upgradecode = {7B6BF434-3C72-4DB3-8049-FEF31AEAFF9A}
02/03/2007 12:37:54.317 version = 9
02/03/2007 12:37:54.317
02/03/2007 12:37:54.317 File Group Details: MSI
02/03/2007 12:37:54.317 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.317 File Details: SQLServer2005_BC_x64.msi
02/03/2007 12:37:54.317
02/03/2007 12:37:54.317 Product Details:
02/03/2007 12:37:54.317 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlWriter.inf
02/03/2007 12:37:54.317 baselinebuild = 1399
02/03/2007 12:37:54.317 build = 2047
02/03/2007 12:37:54.333 description = Microsoft SQL Server VSS Writer
02/03/2007 12:37:54.333 details = Service Pack for Microsoft SQL Server VSS Writer.
02/03/2007 12:37:54.333 kbarticle = KB913090
02/03/2007 12:37:54.333 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.333 lcid = 1033
02/03/2007 12:37:54.333 legalproductname = Microsoft SQL Server VSS Writer
02/03/2007 12:37:54.333 machinetype = x86
02/03/2007 12:37:54.333 package = HotFixSqlWriter
02/03/2007 12:37:54.333 packagetype = Hotfix
02/03/2007 12:37:54.333 productcode = {C0D2F614-5CE5-4DCB-8678-E5C9AF7044F8}
02/03/2007 12:37:54.333 productname = Redist9
02/03/2007 12:37:54.333 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.333 splevel = 0,1
02/03/2007 12:37:54.333 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.333 upgradecode = {65D8E1DF-6201-4B53-A0F9-E654F8E80F97}
02/03/2007 12:37:54.333 version = 9
02/03/2007 12:37:54.348
02/03/2007 12:37:54.348 File Group Details: MSI
02/03/2007 12:37:54.348 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.348 File Details: SqlWriter.msi
02/03/2007 12:37:54.348
02/03/2007 12:37:54.348 Instance Details: Microsoft SQL Server VSS Writer
02/03/2007 12:37:54.348 productcode = {C0D2F614-5CE5-4DCB-8678-E5C9AF7044F8}
02/03/2007 12:37:54.348
02/03/2007 12:37:54.348 Product Details:
02/03/2007 12:37:54.348 INF File Name: \PAAHOUENTSQLTe$50b73396ce0726e176HotFixSqlWriter_x64.inf
02/03/2007 12:37:54.348 baselinebuild = 1399
02/03/2007 12:37:54.348 build = 2047
02/03/2007 12:37:54.348 description = Microsoft SQL Server VSS Writer (64-bit)
02/03/2007 12:37:54.348 details = Service Pack for Microsoft SQL Server VSS Writer.
02/03/2007 12:37:54.348 kbarticle = KB913090
02/03/2007 12:37:54.348 kbarticlehyperlink = http://support.microsoft.com/?kbid=913090
02/03/2007 12:37:54.348 lcid = 1033
02/03/2007 12:37:54.348 legalproductname = Microsoft SQL Server VSS Writer (64-bit)
02/03/2007 12:37:54.364 machinetype = x64
02/03/2007 12:37:54.364 package = HotFixSqlWriter_x64
02/03/2007 12:37:54.364 packagetype = Hotfix
02/03/2007 12:37:54.364 productname = Redist9
02/03/2007 12:37:54.364 servicepackname = Microsoft SQL Server 2005 Service Pack 1 Setup
02/03/2007 12:37:54.364 splevel = 0,1
02/03/2007 12:37:54.364 supportdir = \PAAHOUENTSQLTe$50b73396ce0726e176
02/03/2007 12:37:54.364 upgradecode = {E9031696-DD39-4C25-BAEB-425FF28279EA}
02/03/2007 12:37:54.364 version = 9
02/03/2007 12:37:54.364
02/03/2007 12:37:54.364 File Group Details: MSI
02/03/2007 12:37:54.364 sourcepath = <SUPPORTDIR><PACKAGE>Files
02/03/2007 12:37:54.364 File Details: SqlWriter_x64.msi
02/03/2007 12:37:54.364
02/03/2007 15:33:40.192 Attempting to install product: Redist9
02/03/2007 15:33:45.817 Successfully installed product: Redist9
02/03/2007 15:33:45.817 Attempting to install product: Redist9
02/03/2007 15:33:58.051 Successfully installed product: Redist9
02/03/2007 15:33:58.083 Attempting to install product: Redist9
02/03/2007 15:34:00.020 Successfully installed product: Redist9
02/03/2007 15:34:00.051 Attempting to install product: Redist9
02/03/2007 15:34:03.130 Successfully installed product: Redist9
02/03/2007 15:34:03.192 Attempting to install product: Redist9
02/03/2007 15:34:05.770 Successfully installed product: Redist9
02/03/2007 15:34:05.801 Attempting to install product: Redist9
02/03/2007 15:34:08.489 Successfully installed product: Redist9
02/03/2007 15:34:08.520
02/03/2007 15:34:08.520 Product Status Summary:
02/03/2007 15:34:08.520 Product: SQL Server Native Client
02/03/2007 15:34:08.520 SQL Server Native Client (RTM ) - Success
02/03/2007 15:34:08.520
02/03/2007 15:34:08.520 Product: Setup Support Files
02/03/2007 15:34:08.520 Setup Support Files (RTM ) - Success
02/03/2007 15:34:08.536
02/03/2007 15:34:08.536 Product: MSXML 6.0 Parser
02/03/2007 15:34:08.536 MSXML 6.0 Parser (RTM ) - Success
02/03/2007 15:34:08.536
02/03/2007 15:34:08.536 Product: SQLXML4
02/03/2007 15:34:08.536 SQLXML4 (RTM ) - Success
02/03/2007 15:34:08.536
02/03/2007 15:34:08.536 Product: Backward Compatibility
02/03/2007 15:34:08.536 Backward Compatibility (RTM ) - Success
02/03/2007 15:34:08.536
02/03/2007 15:34:08.536 Product: Microsoft SQL Server VSS Writer
02/03/2007 15:34:08.536 Microsoft SQL Server VSS Writer (RTM ) - Success
02/03/2007 15:34:08.536
02/03/2007 15:34:08.551 Hotfix package completed
02/03/2007 16:08:49.614 Hotfix package closed

View 2 Replies


ADVERTISEMENT

Installing MSDTC Resource After Installing SQL Server 2000 Cluster

Oct 19, 2006

Is it possible to install and configure the MSDTC resource in a SQL Server 2000 cluster after SQL is installed and running?

When I recently went through a rebuild of my cluster, I forgot to install the resource before installing SQL Server. Now, if I install and bring online the MSDTC resource the SQL disk groups will not fail over correctly. The SQL Server resource will not come online.

Thanks in advance for any help. I would really like to avoid rebuilding again.



Andy

View 1 Replies View Related

Installing SQL Server Standard Edition 2005 After Installing SQL Server Express 2005

Feb 14, 2007

Hi

I have installed SQL Server Express 2005 on my machine.

I want to install SQL Server Standard Edition 2005 on my machine to check new services it has.

Can these 2 Editions coexist with each other, or any troubles you think might encounter?

Thanks

View 5 Replies View Related

Cloned SQL 2005 Install

May 11, 2007

I need a little help with a cloned SQL 2005 install. We have a couple of Virtual Machines that SQL 2005 was installed on. The install was orginally completed on <pc1> and then duped over to <pc2>. The problem now is that <pc2> is showing information from <pc1> everywhere. I have reviewd this document: http://msdn2.microsoft.com/en-us/library/ms143799.aspx, and it doesn't seem to help any. I have used the sp_dropserver command with 'droplogins' to try to recreate the logins for <pc2> but it's still showing the logins from <pc1>. Can someone please help me out, I'm not sure what I'm doing wrong here. Thanks!

View 2 Replies View Related

Changes To Cloned Database Are Affecting The Original

Oct 20, 2006

I am trying to use SQL Express to support unit testing of functionality which requires database access.

I created an express database (.mdf) which contains a database snapshot which is the database environment that each test expects to see when it starts. Through the execution of the test the database will be modified arbitrarily and I need to reset the database to the original state before the next test executes.

Here's what I do today:

Before Test:

The original database is copied to a unique location in the temp directory
A unique database name is generated (GUID-based)
I connect to the new database file with:

Server=.SQLEXPRESS;AttachDbFilename="PathToTempFile";Database="GuidDBName";Initial Catalog="GuidDBName";Trusted_Connection=Yes;User Instance=true

During the test all database access is routed to the temporary database GuidDBName

After Test:

Close all active database connections and clear the connection pool
Connect to the master database and detach the database:

Server=.SQLEXPRESS;Database=master;Initial Catalog=master;Trusted_Connection=Yes;User Instance=true - sp_detach_db 'GuidDBName'


Delete the temporary file

When I do this, everything seems to work correctly but when I re-open the original database it has changed unexpectedly and includes the modifications that were made by the test as it ran.

Can anyone explain why this is happening and/or provide a solution?

View 1 Replies View Related

Problem Installing SQL Server 2005 Enterprise Edition On Windows Server 2003 Box

Sep 20, 2007

While attempting to install SQL Server 2005 Enterprise Edition on a Windows Server 2003 box, it is failing as follows...

Microsoft SQL Server 2005 Setup beginning at Thu Sep 20 11:11:35 2007
Process ID : 5440
E:setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/8/20 11:11:35
Complete: LoadResourcesAction at: 2007/8/20 11:11:35, returned true
Running: ParseBootstrapOptionsAction at: 2007/8/20 11:11:35
Loaded DLL:E:xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/8/20 11:11:35, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run:
Could not parse command line due to datastore exception.
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 124
----------------------------------------------------------
writeEncryptedString() failed
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Fri Jul 29 01:13:55 2005
Function Name: writeEncryptedString
Source Line Number: 123
----------------------------------------------------------
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: cryptohelpercryptsameusersamemachine.cpp
Compiler Timestamp: Mon Jun 13 14:30:00 2005
Function Name: sqls::CryptSameUserSameMachine:rotectData
Source Line Number: 50
2
Could not skip Component update due to datastore exception.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "5440"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Running: ValidateWinNTAction at: 2007/8/20 11:11:35
Complete: ValidateWinNTAction at: 2007/8/20 11:11:35, returned true
Running: ValidateMinOSAction at: 2007/8/20 11:11:35
Complete: ValidateMinOSAction at: 2007/8/20 11:11:35, returned true
Running: PerformSCCAction at: 2007/8/20 11:11:35
Complete: PerformSCCAction at: 2007/8/20 11:11:35, returned true
Running: ActivateLoggingAction at: 2007/8/20 11:11:35
Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run:
Datastore exception while trying to write logging properties.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
00CFCFC8Unable to proceed with setup, there was a command line parsing error. : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
Failed to create CAB file due to datastore exception
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "5440"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name: SetupBootstrapOptionsScope.HostSetup
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Message pump returning: 2

Any ideas?

Thanks in advance.

View 1 Replies View Related

Setup Error Installing SQL Server 2005 Eval On Windows Server 2008 Beta

Apr 21, 2008

Hi,


Is it possible to install SQL Server 2005 Eval on a Virtual PC 2007
client running Server 2008 Beta? Nothing says it isn't possible, it
says I need to service pack it right away, but before it gets started
it comes up with the error 'sqlcu.dll failed to load'. Anyone know
what this is all about?





Any ideas?


Any help would be appreciated.
Thanks!

View 1 Replies View Related

COM Plus Catalog Requirement (Warning) When Installing MS SQL SERVER 2005 ENTERPRISE ON WINDOWS SERVER 2003

Sep 21, 2006

COM Plus Catalog Requirement (Warning)



Messages

COM Plus Catalog Requirement


If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.

View 6 Replies View Related

A Transport-level Error Has Occurred When Receiving Results From The Server. - After Installing New Instance Of SQL Server 2005 W/NO App Changes

Sep 27, 2006

We've devoted a resource to this today, but I have to believe it's something easy that we're overlooking.  The scneario is that we have a production Web application that until last weekend had a SQL 2000 back end.  This weekend we installed a new instance of SQL 2005 and everything works (we tested in a sandbox environment, but someone must not have load tested enough) and never saw these exceptions.   So, after the upgrade we now receive 100's of thexe SQL excptions per day:A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)Does anyone know what we've overlooked that's causing this issue?Thanks for any help! 

View 2 Replies View Related

Access Violation Error On Setup.exe When Installing SQl Server 6.5 On NT 4.0 Server

Feb 18, 1999

I have tried several times to install SQL server onto an NT4.0 server which is more than capable of having more than one application to cope with, however, when going through the install procedure the programm stops with the following message


DR.Watson
Access Violation
Setup.exe
In address :

Any hints as to where the problems lies or point me inthe right direction would be appreciated.

View 1 Replies View Related

Installing SQL Server 2005 Reporting Services On Server 2000

Feb 25, 2008

I'm trying to install SQL Server 2005 on a server 2000 machine, everything is working with the exception of the Web Service Identity. It is putting machinenameASPNET, and I don't know where to go to make it use something else. I've look around but I have really seen any answers that have worked for me.

Thanks in advance

Will

View 3 Replies View Related

Problems Installing SQL Server 2005 On Windows Server 2008

Feb 25, 2008

Hello:

I just installed Windows Server 2008. The installation also included Web Server.

When I tried to install SQL Server, I got the following warning:


IIS Feature Requirement (Warning)



Messag

IIS Feature Requirement


Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.

Can somebody advise me on how I can resolve this warning? Would running SP2 take care of this?

Venki

View 18 Replies View Related

Cannot Select Server Database Engine When Installing SQL Server Sep 2005 CTP

Sep 30, 2005

I am trying to install SQL Server Sep 2005 CTP - ENTERPRISE, there are 

View 1 Replies View Related

Uninstalling SQL Server Comapct Edition And Installing Sql Server 2005

May 16, 2008



Hi,

Recently I have installed Visual Studion Team System 2008 Development Edition in my sytem. Along with this, MS-SQL Server aand MSSQL Server Compact Edition is also installed. I need to install the SQL Server 2005 in my system.

In such a scenario, does the Compact Edition is required? Can I uninstall them and install Sql Server 2005 only? If I uninstall anything, would it cause any problems for the .Net programs to work?

Please respond asap.

Thanks for any help.
meeram.

View 1 Replies View Related

Installing IIS After Installing SQL Server 2005 And Visual Studio 2005 Help Requested!

Aug 31, 2007

Hi all, Im new here so il start with a little introduction of myself, My name is Arjan im 19 years old from Holland, and i work for a company to compleet my ICT Education.

My situation:

My boss gave me a server with server 2003 standard and Sql server 2005 and visual studio 2005 installed already, he asked me if i could figure out how the 'new' reporting services work, Im pretty new to SQL and the reporting service but i figured out i had to install asp.net / frameworks and IIS.

So right now i wanna start the Reporting Services Configuration Manager and i get an error that says 'Invalid namespace' and when im trying to approach by using my browser i get 'page not found' so obviously their is Alot wrong. I asked my boss if i could not reinstall everything and do it in the correct order (IIS / ASP.net / Frameworks before installing SQL server 2k5 but that was not an option because we dont seem to have the cd's anymore.

The server is not connected to any network or the internet.

My Question:

Is their any way to fix this? and if yes could anyone tell me where to start


Thanks in Advance!

ps if their is information or logs that u need in order to help me just say so :-)


-Arjan

View 1 Replies View Related

Installing SQL Server 2005 To Windows Server 2003

Apr 2, 2007

when trying to install SQL Sever 2005 to windows server 2003 its display the message Windows Installer 3.1 is required. But when tring to install windows installer 3.1 is displays the message Service Pack version of newer than the update that you are applying, Ther is no need to install the update. Why?

View 1 Replies View Related

Installing Sql Server 2005 On Windows Server 2000

Jun 8, 2006

Is there a problem doing this or will it run fine.

View 1 Replies View Related

Installing MS Sql Server 2000 On Win 2003 Server

Jul 20, 2005

How do I do this when my instalation cd is an old veriosn with no SPīs? Win2003 requires MS SQL 2000 SP3 sp what do I do???RegardsAnders

View 2 Replies View Related

When Installing SQL Server 7, What Domain Is Server In?

Oct 2, 2000

When installing SQL Server 7.0, how do you tell what domain the server is in?

Thanks.

View 1 Replies View Related

No Server Found After Installing Sql Server

Mar 22, 2006

sadegh writes "hello
i installed sql server 2005 on my windows xp sp2 os for the first time. but it doesent recegnize any servers and also,no server is listed in registered servers and object explorer.
and also in connect to server dialog box,when i click on browse for more... , it cannot find any local o network servers. ( this is my personal pc and not connected to any networks.)
how can i define a server for the first time?
thank you"

View 2 Replies View Related

Installing SQL Server 05 On Same Machine As SQL Server 2K ?

Dec 19, 2006

Can this be done safely ??
If so is there any speacil tricks i should know about ?

Thanks !
Gene

View 1 Replies View Related

Installing SQL Server On XP Pro

Oct 26, 2005

I thought SQL Server allowed installation on XP Pro? For some reason I am getting an error. SQL Server Ent. 2000 is telling me that it does not support XP Pro. Is there a work around for this? I don't want to have to rebuild by box just to isntall SQL server!

View 1 Replies View Related

Installing SQL 7 And SMS On The Same Server??

Mar 20, 2000

My question is:

Is it better to have SMS reside on a different sever than a server that is using SQL or is more effecient to have SMS and SQL residing on the same server being that SMS backend is SQL Server? What factors do I need to consider in trying to make this decision? Thanks to whoever can help with this.

View 2 Replies View Related

Installing Sql Server 6.5

Aug 30, 1999

hi I just installed sql server 6.5 to a workstating of window NT 4.0. then tried to connect to the database... I could not connect, an error message said the server name does not exist and could not connect.... then I move to the control panel and added in the Network icon/ Adapters tap a Network adaptor called MS Loopback Adapter... then restart the workstation and run sql server... guess what happened.... I was able to connect.... great..I am curious to know why I could not connect in the first place and what is the relation between sql server and the adaptor named "Loop back Adaptor"... any ideas...

thanks

Ali

View 1 Replies View Related

Installing NT4 & SQL Server 6.5 SPs

Jan 26, 1999

Hi,

I'm going to set up my SQL Server database on a new server. Can someone recommend what service packs I should install (NT 4.0 and SQL Server 6.5)? My old platform is NT 3.51 and SQL Server 6.5 without service packs.

Are the latest packs - SP4 for NT and SP5 for SQL Server - a reasonable choice?

Thanks, Al

View 1 Replies View Related

Installing SQL Server

Nov 7, 2001

We are writing a server application that will require SQL server for the database server. Is it possible (or desirable) to install SQL server as part of our installation process, of course paying Microsoft some lisencing fee? Or, do we have to make our customers install it for themselves?

View 4 Replies View Related

Installing SQL Server

Feb 15, 2005

I am about to install SQL server 2000, but it just occured to me that I might have to install IIS first, is this correct?

grissom

View 2 Replies View Related

Installing Sql Server

Oct 30, 2007

I installed microsoft Visual Studio 2005.
and after that, I installed Sql Server.
All the installations finished in succsess.

But I can't start Sql Server, because there is not Shortcut in the START menu.

How do I execute Sql Server?

Thank's

View 1 Replies View Related

Installing Sql Server

Oct 30, 2007

I installed microsoft Visual Studio 2005.
and after that, I installed Sql Server.
All the installations finished in succsess.

But I can't start Sql Server, because there is not Shortcut in the START menu.

How do I execute Sql Server?

Thank's

View 2 Replies View Related

Installing Sql Server

Jun 8, 2006

Hi,

I downloaded the Sql server 2005 express advanced and installed it in my computer. Everything went well except for a warning message that said "minimum hardware requirements not met". I have dual core pentium 4 computer with 250 G hard disk and 1gb ram.

Anyways, after installing I cannot find the real application anywhere. When I goto start, programs, sql server it only shows sql server configuration tools. I have never used sql server before and how do I start the app?

Any help will be much appreciated. Please note I already installed net framework 2 and also visual studio 2005 professional.

View 4 Replies View Related

HELP! Installing SQL Server

Dec 11, 2005

Help!

View 1 Replies View Related

Installing SQL Server On XP SP2

Mar 31, 2008

Hi,

I am trying to install MS SQL Server 2005 on Windows XP SP2. When I reach to the screen which asks for component selection, I am unable to select any of the options as they are greyed out. Only documentation/books online option is available for me to select.

Please let me know how I can install it on XP. Thanks

View 4 Replies View Related

Installing SQL Server 2005 Standard Edition When Express 2005 Is Already On Server

Sep 30, 2007

I need to install SQL Server 2005 Standard Edition on a new Windows Server 2003 machine that has SQL Server 2005 Express Edition installed by a backup application (Backup Exec). Will I need to uninstall the express edition in order to install the standard edition? Can the two coexist as separate instances or will the standard edition installation simply upgrade the express installation?

Thanks

View 3 Replies View Related







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