Re: Trying to patch SQL 2005 Developer SP2 Build 3033 - failing



Oh OK. It's good to hear that.

--
Ekrem Önsoy



"Demi" <Demi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:A2A26E84-2ECF-409A-9E4A-F03899566BD5@xxxxxxxxxxxxxxxx

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.

"Ekrem Önsoy" wrote:

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

--
Ekrem Önsoy



"Demi" <Demi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8D73E50D-C13E-44C1-9704-733353CAA58E@xxxxxxxxxxxxxxxx
> 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


.



Relevant Pages

  • Re: Error installing (KB 921896)
    ... But when I clicked on the setup file itself as Administrator, I was able to install. ... 03/20/2008 03:01:49.925 Enumeration: Found following QFE level for product instance MSSMLBIZ: 2047 ... 03/20/2008 03:01:50.204 Enumeration: Found following QFE level for product instance SQLEXPRESS: 2047 ... 03/20/2008 03:01:50.555 Product discovery completed during the install process for MSSMLBIZ ...
    (microsoft.public.windowsupdate)
  • Re: Trying to patch SQL 2005 Developer SP2 Build 3033 - failing
    ... This SP2 reinstall appears to work - great answer! ... I was able to install the security patch afterwards. ... The product instance MSSQLSERVER has had update 3033 applied. ... Update 3159 is dependent on prerequisite update 3042. ...
    (microsoft.public.sqlserver.security)
  • Re: Trying to patch SQL 2005 Developer SP2 Build 3033 - failing
    ... Not sure if you tried this but did you try installing SP2 build 3042? ... The product instance MSSQLSERVER has had update 3033 applied. ... install GDR update 3054 overtop update 3033. ... Update 3159 is dependent on prerequisite update 3042. ...
    (microsoft.public.sqlserver.security)
  • Re: Trying to patch SQL 2005 Developer SP2 Build 3033 - failing
    ... The product instance MSSQLSERVER has had update 3033 applied. ... install GDR update 3054 overtop update 3033. ... Update 3159 is dependent on prerequisite update 3042. ...
    (microsoft.public.sqlserver.security)
  • Re: Trying to patch SQL 2005 Developer SP2 Build 3033 - failing
    ... I was able to install the security patch afterwards. ... The product instance MSSQLSERVER has had update 3033 applied. ... Update 3159 is dependent on prerequisite update 3042. ...
    (microsoft.public.sqlserver.security)