 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / General / Security / July 2008Trying to patch SQL 2005 Developer SP2 Build 3033 - failing
db2040 @ 2005 SP2 CTP (December) - Fix List 9.00.3033 I am an administrator on the box. I ran the installation packages as follows: SQLServer2005-KB934458-x86-ENU.exe 2005 SP2+Q934458 9.00.3054 hotfix_3.log The product instance MSSQLSERVER has had update 3033 applied. You cannot install GDR update 3054 overtop update 3033. An update of build equal to or greater than 3159 should be downloaded. --tried going for cumualtive SQLServer2005-KB948109-x86-ENU.exe 9.00.3068.00 hotfix_4.log The product instance SQL Tools has had update 3033 applied. You cannot install GDR update 3068 overtop update 3033. An update of build equal to or greater than 3229 should be downloaded. SQLServer2005-KB934459-x86-ENU.exe 2005 SP2+Q934459 9.00.3159 hotfix_5.log The product instance MSSQLSERVER does not have prerequisite update 3042 installed. Update 3159 is dependent on prerequisite update 3042. Exit setup and refer to the Knowledge Base article to find the prerequisite patch. Install the prerequisite and rerun the installation. SQLServer2005-KB921896-x86-ENU.exe [9.00.3042] hotfix_6.log • Installed on db2040 with database errors, DID NOT CHANGE THE DATABASE - required re-start of the computer Instance Details: MSSQLSERVER 07/11/2008 07:25:16.324 agentservicename = SQLSERVERAGENT 07/11/2008 07:25:16.324 associatedhotfixbuild = 1520 07/11/2008 07:25:16.324 clustername = 07/11/2008 07:25:16.324 default = TRUE 07/11/2008 07:25:16.340 ftsservicename = MSFTESQL 07/11/2008 07:25:16.340 fullversion = 2005.090.3033.00 07/11/2008 07:25:16.340 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.1 07/11/2008 07:25:16.340 id = MSSQL.1 07/11/2008 07:25:16.340 installsqldatadir = D:\MSSQL2K\MSSQL 07/11/2008 07:25:16.340 installsqldir = d:\MSSQL2K\MSSQL.1\MSSQL 07/11/2008 07:25:16.340 lcid = 1033 07/11/2008 07:25:16.356 name = MSSQLSERVER 07/11/2008 07:25:16.356 productcode = {2373A92B-1C1C-4E71-B494-5CA97F96AA19} 07/11/2008 07:25:16.356 qfelevel = 3033 07/11/2008 07:25:16.356 servicename = MSSQLServer 07/11/2008 07:25:16.356 sku = DEVELOPER 07/11/2008 07:25:16.356 sp = 2 07/11/2008 07:25:16.356 type = SQL Server Standalone Product 07/11/2008 07:25:16.356 vermajbld = 3033 07/11/2008 07:25:16.371 version = 9 07/11/2008 07:26:19.699 Installing file: sqlrun_sql.msp 07/11/2008 07:26:20.090 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log 07/11/2008 07:26:20.090 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer" 07/11/2008 07:26:20.090 Registry: Cannot read registry key value "Debug" 07/11/2008 07:29:09.621 MSP Error: 1920 Service 'SQL Server VSS Writer' (SQLWriter) failed to start. Verify that you have sufficient privileges to start system services. 07/11/2008 07:30:00.856 MSP returned 1603: A fatal error occurred during installation. 07/11/2008 07:30:00.902 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer" 07/11/2008 07:30:00.902 Registry: Cannot read registry key value "Debug" 07/11/2008 07:30:01.871 Copy Engine: Error, unable to install MSP file: d:\dbb25850ee8c9ead410d7aa6\HotFixSQL\Files\sqlrun_sql.msp 07/11/2008 07:30:01.918 The following exception occurred: Unable to install Windows Installer MSP file Date: 07/11/2008 07:30:01.918 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 800 07/11/2008 07:30:03.371 Watson: Param1 = Unknown 07/11/2008 07:30:03.387 Watson: Param2 = 0x780 07/11/2008 07:30:03.402 Watson: Param3 = Unknown 07/11/2008 07:30:03.418 Watson: Param4 = 0x780 07/11/2008 07:30:03.418 Watson: Param5 = copyengine.cpp@800 07/11/2008 07:30:03.418 Watson: Param6 = Unknown 07/11/2008 07:30:03.418 Watson: Param7 = SQL9 07/11/2008 07:30:03.418 Watson: Param8 = Hotfix@ 07/11/2008 07:30:03.434 Watson: Param9 = x86 07/11/2008 07:30:03.434 Watson: Param10 = 3042 07/11/2008 07:30:03.434 Installed product: SQL9 07/11/2008 07:30:03.449 Installing product: OLAP9 07/11/2008 07:30:03.449 Installing instance: MSSQLSERVER 07/11/2008 07:30:03.465 Installing target: db2040 Demi, Not sure if you tried this but did you try installing SP2 build 3042? The post SP2 builds need SP2 to be installed first. Chris > db2040 @ 2005 SP2 CTP (December) - Fix List 9.00.3033 > [quoted text clipped - 87 lines] > 07/11/2008 07:30:03.449 Installing instance: MSSQLSERVER > 07/11/2008 07:30:03.465 Installing target: db2040 Yes it's the last thing in the list of builds I tried and the one that I pasted the error log from. > Demi, > > Not sure if you tried this but did you try installing SP2 build 3042? The > post SP2 builds need SP2 to be installed first. > > Chris MS changed build 3042 from its original release so you will probably have to talk to them. Never good to use 'beta' versions because they don't always patch properly. Good luck. Chris > Yes it's the last thing in the list of builds I tried and the one that I > pasted the error log from. [quoted text clipped - 5 lines] >> >> Chris That was tried first and the phone person at wanted a $250 support call to investigate the issue so here I am... > MS changed build 3042 from its original release so you will probably have to > talk to them. Never good to use 'beta' versions because they don't always [quoted text clipped - 3 lines] > > Chris Hello Demi, I suggest you to take a look at the following blog: http://sqlblogcasts.com/blogs/blakmk/archive/2008/06/26/ctp-nightmares.aspx  SignatureEkrem Önsoy > db2040 @ 2005 SP2 CTP (December) - Fix List 9.00.3033 > [quoted text clipped - 87 lines] > 07/11/2008 07:30:03.449 Installing instance: MSSQLSERVER > 07/11/2008 07:30:03.465 Installing target: db2040 I was prepared to do that but I tried one more time to install 3042 this time using the "sa" account instead of windows auth and that worked and then I was able to install the security patch afterwards. So problem solved. Thanks. > Hello Demi, > [quoted text clipped - 92 lines] > > 07/11/2008 07:30:03.449 Installing instance: MSSQLSERVER > > 07/11/2008 07:30:03.465 Installing target: db2040 Oh OK. It's good to hear that. SignatureEkrem Önsoy > I was prepared to do that but I tried one more time to install 3042 this > time using the "sa" account instead of windows auth and that worked and [quoted text clipped - 106 lines] >> > 07/11/2008 07:30:03.449 Installing instance: MSSQLSERVER >> > 07/11/2008 07:30:03.465 Installing target: db2040 Hi All, This SP2 reinstall appears to work - great answer! I wonder how we managed to get stuck with a CTP build of SP2? I think the MS Article for the 3033 is sorely lacking in information. I receive this message when I try to run the update "This fix updates the SQL Server Integration Services 2005 (SSIS) scripting environment to work with a newly-released patch for a security vulnerability in the .Net Framework 2.0. Without this fix, any VB.Net scripts (Script Task or Script Component) in your SSIS packages may not execute, or work at design-time as expected. More information for this update can be found at http://support.microsoft.com/kb/932557" The link takes me to a bunch of hotfixes for 64 bit machines (which I have). Did Microsoft slip me a mickey on the SP2? I don't search for them, I let Windows Update handle it. I suspect it may be a problem on our server as well. Thanks for the info DEMI, it is a big help! SignatureRegards, Jamie > I was prepared to do that but I tried one more time to install 3042 this > time using the "sa" account instead of windows auth and that worked and then [quoted text clipped - 97 lines] > > > 07/11/2008 07:30:03.449 Installing instance: MSSQLSERVER > > > 07/11/2008 07:30:03.465 Installing target: db2040 > SQLServer2005-KB921896-x86-ENU.exe [9.00.3042] hotfix_6.log > • Installed on db2040 with database errors, DID NOT CHANGE THE [quoted text clipped - 10 lines] > (SQLWriter) failed to start. Verify that you have sufficient > privileges to start system services. This seems to be the crux of the matter. Why SQL Server VSS Writer fails to start, I don't know, but you could check the event log for clues. The fastest route may be to uninstall SQL 2005, and start over. SignatureErland Sommarskog, SQL Server MVP, esquel@sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.