SQLServerWiki

“The Only Thing That Is Constant Is Change”

Installation of SP3 fails.

Posted by database-wiki on March 6, 2011

How to Reverse GUID:

REVERSED GUID:

STEPS to un-reverse it:

1. Take first 3 sets reverse it as below.

2. Take next two sets and reverse as below.

3. Adding all together we get

ISSUE:

=====

SP3 failed for the services and components.

Products Detected                         Language  Level      Patch Level  Platform  Edition

Database Services (MSSQLSERVER)           ENU       SP2    2005.090.3282.00  x86       STANDARD

Notification Services                     ENU       SP2        9.00.3282.00  x86       STANDARD

Integration Services                      ENU       SP2        9.00.3282.00  x86       STANDARD

Client Components                         ENU       SP2            9.2.3282  x86       STANDARD

Analyzing the Database Services (MSSQLSERVER)  logs:

————————————————————————————————————————————————————————————

Product                   : Database Services (MSSQLSERVER)

Product Version (Previous): 3282

Product Version (Final)   :

Status                    : Failure

Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB955706_sqlrun_sql.msp.log

Error Number              : 1635

Error Description         : Unable to install Windows Installer MSP file

————————————————————————————————————————————————————————————

Find the product GUID of SQL Servers:

From SQL9_Hotfix_KB955706_sqlrun_sql.msp.log

=== Verbose logging started: 06/16/2009  13:11:25  Build type: SHIP UNICODE 3.01.4000.4042  Calling process: d:\ffde4c4f88f82f4986beaea67b81f965\hotfix.exe ===

MSI (c) (FC:B4) [13:11:25:808]: Resetting cached policy values

MSI (c) (FC:B4) [13:11:25:808]: Machine policy value ‘Debug’ is 0

MSI (c) (FC:B4) [13:11:25:808]: ******* RunEngine:

           ******* Product: {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}

           ******* Action:

           ******* CommandLine: **********

PRODUCT GUID: 130A3BE1-85CC-4135-8EA7-5A724EE6CE2C => We need to reverse it.

 Look at “How to Reverse GUID:”

 OUTPUT: 1EB3A031CC585314E87AA527E46EECC2

Take this value go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products and search:

Then expand the GUID to find the patches applied to it.

In our case three patch were applied to SQL Server 2005:

05CCC6FF17E99624A8558E75D7650B18 — Hotfix 3024

A4FE53A4868D51B48AD4E39852AA5985 — Hotfix (KB921896) 3042   issue is cause by SP2 see the GUID below.

93567640A626AFF4485EFDF85A4CE21B — Hotfix (KB953752) 3282

From SQL9_Hotfix_KB955706_sqlrun_sql.msp.log

MSI (s) (28:F8) [13:11:33:308]: Opening existing patch ‘C:\WINDOWS\Installer\2b117.msp’.

MSI (s) (28:F8) [13:11:33:308]: Note: 1: 2203 2: C:\WINDOWS\Installer\2b117.msp 3: -2147287038

MSI (s) (28:F8) [13:11:33:308]: Couldn’t find local patch ‘C:\WINDOWS\Installer\2b117.msp’. Looking for it at its source.

MSI (s) (28:F8) [13:11:33:308]: Resolving Patch source.

MSI (s) (28:F8) [13:11:33:308]: User policy value ‘SearchOrder’ is ‘nmu’

MSI (s) (28:F8) [13:11:33:308]: SOURCEMGMT: Media enabled only if package is safe.

MSI (s) (28:F8) [13:11:33:308]: SOURCEMGMT: Looking for sourcelist for product {4A35EF4A-D868-4B15-A84D-3E8925AA9558} — by reversing the 4A35EF4A-D868-4B15-A84D-3E8925AA9558 to get  A4FE53A4868D51B4D48A85559AA5298E3 ( eg: 4A35EF4A -> A4FE53A4 + D868 -> 868D + …..) This is called the product code. This will give the info of the patch that has been applied previously from the registry.

MSI (s) (28:F8) [13:11:33:308]: SOURCEMGMT: Adding {4A35EF4A-D868-4B15-A84D-3E8925AA9558}; to potential sourcelist list (pcode;disk;relpath).

MSI (s) (28:F8) [13:11:33:308]: SOURCEMGMT: Now checking product {4A35EF4A-D868-4B15-A84D-3E8925AA9558}

MSI (s) (28:F8) [13:11:33:308]: SOURCEMGMT: Media is enabled for product.

MSI (s) (28:F8) [13:11:33:308]: SOURCEMGMT: Attempting to use LastUsedSource from source list.

MSI (s) (28:F8) [13:11:33:308]: SOURCEMGMT: Trying source f:57548568fb180a49c2352350840\HotFixSQL\Files\.

MSI (s) (28:F8) [13:11:33:308]: Note: 1: 2203 2: f:57548568fb180a49c2352350840\HotFixSQL\Files\sqlrun_sql.msp 3: -2147287037

MSI (s) (28:F8) [13:11:33:308]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.

MSI (s) (28:F8) [13:11:33:308]: Note: 1: 1706 2: -2147483647 3: sqlrun_sql.msp

MSI (s) (28:F8) [13:11:33:308]: SOURCEMGMT: Processing net source list.

MSI (s) (28:F8) [13:11:33:308]: Note: 1: 1706 2: -2147483647 3: sqlrun_sql.msp

MSI (s) (28:F8) [13:11:33:308]: SOURCEMGMT: Processing media source list.

MSI (s) (28:F8) [13:11:33:324]: SOURCEMGMT: Resolved source to: ‘sqlrun_sql.msp’

MSI (s) (28:F8) [13:12:03:433]: Note: 1: 1314 2: sqlrun_sql.msp

MSI (s) (28:F8) [13:12:03:433]: Unable to create a temp copy of patch ‘sqlrun_sql.msp’.

MSI (s) (28:F8) [13:12:03:433]: Note: 1: 1708

MSI (s) (28:F8) [13:12:03:433]: Note: 1: 2729

MSI (s) (28:F8) [13:12:03:433]: Note: 1: 2729

MSI (s) (28:F8) [13:12:03:433]: Product: Microsoft SQL Server 2005 — Installation failed.

———–

Solution:

=======

Let’s go to this location in the registry and

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Patches\A4FE53A4868D51B4D48A85559AA5298E3

Your local package details should be “LocalPackage”=” C:\WINDOWS\Installer\2b117.msp

So the missing file in the error log and the registry is same.

STEP 1:

-from the logs we find that it was looking for f:57548568fb180a49c2352350840\HotFixSQL\Files\sqlrun_sql.msp

-so go to d drive and created f:57548568fb180a49c2352350840

-downloaded the SP2 pack and extracted it with /X option to c:\SP2   (start>run>cmd ? SP2.exe /X and select a location to extract.)

-copied HotFixSQL, HotFixRS, HotFixAS, HotFixIS, HotFixNS and HotFixTools into  f:57548568fb180a49c2352350840

STEP 2:

-copy f:57548568fb180a49c2352350840\HotFixSQL\Files\sqlrun_sql.msp and pasted it in C:\WINDOWS\Installer\. Then renamed it to 2b117.msp (setup extracts the files in one folder in our case f:57548568fb180a49c2352350840 then copies the file sqlrun_sql.msp from f:57548568fb180a49c2352350840\HotFixSQL\Files and puts it in C:\WINDOWS\Installer\ with a random number 2b117.msp (Available in the product code from registry)  – We are manually doing what setup used to do)

-This should resolve the issue with database services.

 Analyzing the Analysis Services (MSSQLSERVER)  log:

————————————————————————————————————————————————————————————

Product                   : Integration Services

Product Version (Previous): 3282

Product Version (Final)   :

Status                    : Failure

Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB955706_sqlrun_dts.msp.log

Error Number              : 1635

Error Description         : Unable to install Windows Installer MSP file

————————————————————————————————————————————————————————————

=== Verbose logging started: 06/16/2009  13:12:36  Build type: SHIP UNICODE 3.01.4000.4042  Calling process: d:\ffde4c4f88f82f4986beaea67b81f965\hotfix.exe ===

MSI (c) (FC:48) [13:12:36:057]: Resetting cached policy values

MSI (c) (FC:48) [13:12:36:057]: Machine policy value ‘Debug’ is 0

MSI (c) (FC:48) [13:12:36:057]: ******* RunEngine:

           ******* Product: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}

           ******* Action:

           ******* CommandLine: **********

PRODUCT GUID: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}

Reverse Value 9DFFC8EE92E63CD49A7637845D4FF144

0CA47FB2DDDF29E43B06B9B293D76447 Hotfix 3282 for SQL Server Integration Services 2005 ENU (KB953752)

2835661AF203F674993BB116841BBA61 Service Pack 2 for SQL Server Integration Services 2005 ENU (KB921896) issue is cause by SP2 see the GUID below.

MSI (s) (28:D8) [13:12:40:104]: Opening existing patch ‘C:\WINDOWS\Installer\34bc9.msp’.

MSI (s) (28:D8) [13:12:40:104]: Note: 1: 2203 2: C:\WINDOWS\Installer\34bc9.msp 3: -2147287038

MSI (s) (28:D8) [13:12:40:104]: Couldn’t find local patch ‘C:\WINDOWS\Installer\34bc9.msp’. Looking for it at its source.

MSI (s) (28:D8) [13:12:40:104]: Resolving Patch source.

MSI (s) (28:D8) [13:12:40:104]: User policy value ‘SearchOrder’ is ‘nmu’

MSI (s) (28:D8) [13:12:40:104]: SOURCEMGMT: Media enabled only if package is safe.

MSI (s) (28:D8) [13:12:40:104]: SOURCEMGMT: Looking for sourcelist for product {A1665382-302F-476F-99B3-1B6148B1AB16}

MSI (s) (28:D8) [13:12:40:104]: SOURCEMGMT: Adding {A1665382-302F-476F-99B3-1B6148B1AB16}; to potential sourcelist list (pcode;disk;relpath).

MSI (s) (28:D8) [13:12:40:104]: SOURCEMGMT: Now checking product {A1665382-302F-476F-99B3-1B6148B1AB16}

MSI (s) (28:D8) [13:12:40:104]: SOURCEMGMT: Media is enabled for product.

MSI (s) (28:D8) [13:12:40:104]: SOURCEMGMT: Attempting to use LastUsedSource from source list.

MSI (s) (28:D8) [13:12:40:104]: SOURCEMGMT: Trying source f:\d3063d72f178de7c17131261\HotFixDTS\Files\.

MSI (s) (28:D8) [13:12:40:104]: Note: 1: 2203 2: f:\d3063d72f178de7c17131261\HotFixDTS\Files\sqlrun_dts.msp 3: -2147287037

MSI (s) (28:D8) [13:12:40:104]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.

MSI (s) (28:D8) [13:12:40:104]: Note: 1: 1706 2: -2147483647 3: sqlrun_dts.msp

MSI (s) (28:D8) [13:12:40:104]: SOURCEMGMT: Processing net source list.

MSI (s) (28:D8) [13:12:40:104]: Note: 1: 1706 2: -2147483647 3: sqlrun_dts.msp

MSI (s) (28:D8) [13:12:40:104]: SOURCEMGMT: Processing media source list.

MSI (s) (28:D8) [13:12:40:120]: SOURCEMGMT: Resolved source to: ‘sqlrun_dts.msp’

MSI (s) (28:D8) [13:13:10:245]: Note: 1: 1314 2: sqlrun_dts.msp

MSI (s) (28:D8) [13:13:10:245]: Unable to create a temp copy of patch ‘sqlrun_dts.msp’.

MSI (s) (28:D8) [13:13:10:245]: Note: 1: 1708

MSI (s) (28:D8) [13:13:10:245]: Note: 1: 2729

MSI (s) (28:D8) [13:13:10:245]: Note: 1: 2729

MSI (s) (28:D8) [13:13:10:245]: Product: Microsoft SQL Server 2005 Integration Services — Installation failed.

Reverse the Patch GUID {A1665382-302F-476F-99B3-1B6148B1AB16} = 2835661AF203F674993BB116841BBA61

Same issue as that as database services so following the same action plan.

STEP 1: Already done for database services.

STEP 2:

-copy f:\d3063d72f178de7c17131261\HotFixAS\Files\sqlrun_as.msp and pasted it in C:\WINDOWS\Installer\. Then renamed it to 34bc9.msp (setup extracts the files in one folder in our case f:\d3063d72f178de7c17131261 then copies the file sqlrun_as.msp from f:\d3063d72f178de7c17131261\HotFixSQL\Files and puts it in C:\WINDOWS\Installer\ with a random number 34bc9.msp (Available in the product code from registry)  – We are manually doing what setup used to do)

-This should resolve the issue with analysis services.

For Notification Services:

————————————————————————————————————————————————————————————

Product                   : Notification Services

Product Version (Previous): 3282

Product Version (Final)   :

Status                    : Failure

Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\NS9_Hotfix_KB955706_sqlrun_ns.msp.log

Error Number              : 1635

Error Description         : Unable to install Windows Installer MSP file

————————————————————————————————————————————————————————————

=== Verbose logging started: 06/16/2009  13:12:04  Build type: SHIP UNICODE 3.01.4000.4042  Calling process: d:\ffde4c4f88f82f4986beaea67b81f965\hotfix.exe ===

MSI (c) (FC:0C) [13:12:04:026]: Resetting cached policy values

MSI (c) (FC:0C) [13:12:04:026]: Machine policy value ‘Debug’ is 0

MSI (c) (FC:0C) [13:12:04:026]: ******* RunEngine:

           ******* Product: {37E9AD9F-3217-4229-B5A5-7A0C82364C6C}

Product GUID: {37E9AD9F-3217-4229-B5A5-7A0C82364C6C}

Reversed GUID: F9DA9E73712392245B5AA7C02863C4C6

MSI (s) (28:74) [13:12:05:355]: Opening existing patch ‘C:\WINDOWS\Installer\34b36.msp’.

MSI (s) (28:74) [13:12:05:355]: Note: 1: 2203 2: C:\WINDOWS\Installer\34b36.msp 3: -2147287038

MSI (s) (28:74) [13:12:05:355]: Couldn’t find local patch ‘C:\WINDOWS\Installer\34b36.msp’. Looking for it at its source.

MSI (s) (28:74) [13:12:05:355]: Resolving Patch source.

MSI (s) (28:74) [13:12:05:355]: User policy value ‘SearchOrder’ is ‘nmu’

MSI (s) (28:74) [13:12:05:355]: SOURCEMGMT: Media enabled only if package is safe.

MSI (s) (28:74) [13:12:05:355]: SOURCEMGMT: Looking for sourcelist for product {40466B79-713C-42D1-913E-245BEA11A825}

MSI (s) (28:74) [13:12:05:355]: SOURCEMGMT: Adding {40466B79-713C-42D1-913E-245BEA11A825}; to potential sourcelist list (pcode;disk;relpath).

MSI (s) (28:74) [13:12:05:355]: SOURCEMGMT: Now checking product {40466B79-713C-42D1-913E-245BEA11A825}

MSI (s) (28:74) [13:12:05:355]: SOURCEMGMT: Media is enabled for product.

MSI (s) (28:74) [13:12:05:355]: SOURCEMGMT: Attempting to use LastUsedSource from source list.

MSI (s) (28:74) [13:12:05:355]: SOURCEMGMT: Trying source f:\d3063d72f178de7c17131261\HotFixNS\Files\.

MSI (s) (28:74) [13:12:05:355]: Note: 1: 2203 2: f:\d3063d72f178de7c17131261\HotFixNS\Files\sqlrun_ns.msp 3: -2147287037

MSI (s) (28:74) [13:12:05:355]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.

MSI (s) (28:74) [13:12:05:355]: Note: 1: 1706 2: -2147483647 3: sqlrun_ns.msp

MSI (s) (28:74) [13:12:05:355]: SOURCEMGMT: Processing net source list.

MSI (s) (28:74) [13:12:05:355]: Note: 1: 1706 2: -2147483647 3: sqlrun_ns.msp

MSI (s) (28:74) [13:12:05:355]: SOURCEMGMT: Processing media source list.

MSI (s) (28:74) [13:12:05:370]: SOURCEMGMT: Resolved source to: ‘sqlrun_ns.msp’

MSI (s) (28:74) [13:12:35:495]: Note: 1: 1314 2: sqlrun_ns.msp

MSI (s) (28:74) [13:12:35:495]: Unable to create a temp copy of patch ‘sqlrun_ns.msp’.

MSI (s) (28:74) [13:12:35:495]: Note: 1: 1708

MSI (s) (28:74) [13:12:35:495]: Note: 1: 2729

MSI (s) (28:74) [13:12:35:495]: Note: 1: 2729

MSI (s) (28:74) [13:12:35:495]: Product: Microsoft SQL Server 2005 Notification Services — Installation failed.

STEP 1:  Already done for database services.

STEP 2:

copy f:\d3063d72f178de7c17131261\HotFixNS\Files\sqlrun_ns.msp and pasted it in C:\WINDOWS\Installer\. Then renamed it to 34b36.msp (setup extracts the files in one folder in our case f:\d3063d72f178de7c17131261 then copies the file sqlrun_ns.msp from f:\d3063d72f178de7c17131261\HotFixNS\Files and puts it in C:\WINDOWS\Installer\ with a random number 34b36.msp (Available in the product code from registry)  – We are manually doing what setup used to do)

-This should resolve the issue with Notification services.

For Client Components

————————————————————————————————————————————————————————————

Product                   : Client Components

Product Version (Previous): 3282

Product Version (Final)   :

Status                    : Failure

Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB955706_sqlrun_tools.msp.log

Error Number              : 1635

Error Description         : Unable to install Windows Installer MSP file

————————————————————————————————————————————————————————————

=== Verbose logging started: 06/16/2009  13:15:52  Build type: SHIP UNICODE 3.01.4000.4042  Calling process: d:\ffde4c4f88f82f4986beaea67b81f965\hotfix.exe ===

MSI (c) (FC:24) [13:15:52:558]: Resetting cached policy values

MSI (c) (FC:24) [13:15:52:558]: Machine policy value ‘Debug’ is 0

MSI (c) (FC:24) [13:15:52:558]: ******* RunEngine:

           ******* Product: {1DD463C0-A50A-4394-B7E4-5895C02F9E0D}

Reversed Product code: 0C364DD1A05A49347B4E85590CF2E9D0

MSI (s) (28:14) [13:16:24:324]: Opening existing patch ‘C:\WINDOWS\Installer\34cf9.msp’.

MSI (s) (28:14) [13:16:24:324]: Note: 1: 2203 2: C:\WINDOWS\Installer\34cf9.msp 3: -2147287038

MSI (s) (28:14) [13:16:24:324]: Couldn’t find local patch ‘C:\WINDOWS\Installer\34cf9.msp’. Looking for it at its source.

MSI (s) (28:14) [13:16:24:324]: Resolving Patch source.

MSI (s) (28:14) [13:16:24:324]: User policy value ‘SearchOrder’ is ‘nmu’

MSI (s) (28:14) [13:16:24:324]: SOURCEMGMT: Media enabled only if package is safe.

MSI (s) (28:14) [13:16:24:324]: SOURCEMGMT: Looking for sourcelist for product {88591C3A-E392-4B2C-98B7-F123862FD540}

MSI (s) (28:14) [13:16:24:324]: SOURCEMGMT: Adding {88591C3A-E392-4B2C-98B7-F123862FD540}; to potential sourcelist list (pcode;disk;relpath).

MSI (s) (28:14) [13:16:24:324]: SOURCEMGMT: Now checking product {88591C3A-E392-4B2C-98B7-F123862FD540}

MSI (s) (28:14) [13:16:24:324]: SOURCEMGMT: Media is enabled for product.

MSI (s) (28:14) [13:16:24:324]: SOURCEMGMT: Attempting to use LastUsedSource from source list.

MSI (s) (28:14) [13:16:24:324]: SOURCEMGMT: Trying source f:\d3063d72f178de7c17131261\HotFixTools\Files\.

MSI (s) (28:14) [13:16:24:324]: Note: 1: 2203 2: f:\d3063d72f178de7c17131261\HotFixTools\Files\sqlrun_tools.msp 3: -2147287037

MSI (s) (28:14) [13:16:24:324]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.

MSI (s) (28:14) [13:16:24:324]: Note: 1: 1706 2: -2147483647 3: sqlrun_tools.msp

MSI (s) (28:14) [13:16:24:324]: SOURCEMGMT: Processing net source list.

MSI (s) (28:14) [13:16:24:324]: Note: 1: 1706 2: -2147483647 3: sqlrun_tools.msp

MSI (s) (28:14) [13:16:24:324]: SOURCEMGMT: Processing media source list.

MSI (s) (28:14) [13:16:24:340]: SOURCEMGMT: Resolved source to: ‘sqlrun_tools.msp’

MSI (s) (28:14) [13:16:24:340]: Note: 1: 1314 2: sqlrun_tools.msp

MSI (s) (28:14) [13:16:24:340]: Unable to create a temp copy of patch ‘sqlrun_tools.msp’.

MSI (s) (28:14) [13:16:24:340]: Note: 1: 1708

MSI (s) (28:14) [13:16:24:340]: Note: 1: 2729

MSI (s) (28:14) [13:16:24:340]: Note: 1: 2729

MSI (s) (28:14) [13:16:24:340]: Product: Microsoft SQL Server 2005 Tools — Installation failed.

88591C3A-E392-4B2C-98B7-F123862FD540 reverse it to A3C19588293EC2B4897B1F3268F25D04

STEP 1 Already done for database services.

STEP 2:

copy f:\d3063d72f178de7c17131261\HotFixTools\Files\sqlrun_tools.msp and pasted it in C:\WINDOWS\Installer\. Then renamed it to 34CF9.msp (setup extracts the files in one folder in our case f:\d3063d72f178de7c17131261 then copies the file sqlrun_tools.msp from f:\d3063d72f178de7c17131261\HotFixTools\Files\and puts it in C:\WINDOWS\Installer\ with a random number 34CF9.msp (Available in the product code from registry)  – We are manually doing what setup used to do)

-This should resolve the issue with Client components.

Another simple method to resolved the above issue.

Problem Description:

===============================================================================================================================================================================

Trying to install SP3 on SQL Server 2005 SP2.It fails for database Services and all other client components.

SP2 failed with “1635” “unable to install Windows Installer MSI file”

Error Message:

===============================================================================================================================================================================

=== Verbose logging started: 3/20/2011  3:48:28  Build type: SHIP UNICODE 3.01.4000.4042  Calling process: e:\104f77f7a119ac45ff\hotfix.exe ===

MSI (c) (B0:C0) [03:48:28:905]: Resetting cached policy values

MSI (c) (B0:C0) [03:48:28:905]: Machine policy value ‘Debug’ is 0

MSI (c) (B0:C0) [03:48:28:905]: ******* RunEngine:

           ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi

           ******* Action:

           ******* CommandLine: **********

MSI (c) (B0:C0) [03:48:28:905]: Client-side and UI is none or basic: Running entire install on the server.

MSI (c) (B0:C0) [03:48:28:905]: Grabbed execution mutex.

MSI (c) (B0:C0) [03:48:28:921]: Cloaking enabled.

MSI (c) (B0:C0) [03:48:28:921]: Attempting to enable all disabled priveleges before calling Install on Server

MSI (c) (B0:C0) [03:48:28:921]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (74:C8) [03:48:29:030]: Grabbed execution mutex.

MSI (s) (74:F8) [03:48:29:046]: Resetting cached policy values

MSI (s) (74:F8) [03:48:29:046]: Machine policy value ‘Debug’ is 0

MSI (s) (74:F8) [03:48:29:046]: ******* RunEngine:

           ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi

           ******* Action:

           ******* CommandLine: **********

MSI (s) (74:F8) [03:48:29:046]: Machine policy value ‘DisableUserInstalls’ is 0

MSI (s) (74:F8) [03:48:30:769]: File will have security applied from OpCode.

MSI (s) (74:F8) [03:48:31:207]: SOFTWARE RESTRICTION POLICY: Verifying package –> ‘C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi’ against software restriction policy

MSI (s) (74:F8) [03:48:31:207]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi has a digital signature

MSI (s) (74:F8) [03:48:47:496]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi is permitted to run at the ‘unrestricted’ authorization level.

MSI (s) (74:F8) [03:48:47:496]: End dialog not enabled

MSI (s) (74:F8) [03:48:47:512]: Original package ==> C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi

MSI (s) (74:F8) [03:48:47:512]: Package we’re running from ==> C:\WINDOWS\Installer\905d5600.msi

MSI (s) (74:F8) [03:48:47:512]: APPCOMPAT: looking for appcompat database entry with ProductCode ‘{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}’.

MSI (s) (74:F8) [03:48:47:512]: APPCOMPAT: no matching ProductCode found in database.

MSI (s) (74:F8) [03:48:47:512]: MSCOREE not loaded loading copy from system32

MSI (s) (74:F8) [03:48:47:543]: Opening existing patch ‘C:\WINDOWS\Installer\1b70e.msp’.

MSI (s) (74:F8) [03:48:47:543]: Note: 1: 2203 2: C:\WINDOWS\Installer\1b70e.msp 3: -2147287038

MSI (s) (74:F8) [03:48:47:543]: Couldn’t find local patch ‘C:\WINDOWS\Installer\1b70e.msp’. Looking for it at its source.

MSI (s) (74:F8) [03:48:47:543]: Resolving Patch source.

MSI (s) (74:F8) [03:48:47:543]: User policy value ‘SearchOrder’ is ‘nmu’

MSI (s) (74:F8) [03:48:47:543]: User policy value ‘DisableMedia’ is 0

MSI (s) (74:F8) [03:48:47:543]: Machine policy value ‘AllowLockdownMedia’ is 0

MSI (s) (74:F8) [03:48:47:543]: SOURCEMGMT: Media enabled only if package is safe.

MSI (s) (74:F8) [03:48:47:543]: SOURCEMGMT: Looking for sourcelist for product {EE92F683-5F5C-4970-BB0B-9AC591B60268}

MSI (s) (74:F8) [03:48:47:543]: SOURCEMGMT: Adding {EE92F683-5F5C-4970-BB0B-9AC591B60268}; to potential sourcelist list (pcode;disk;relpath).

MSI (s) (74:F8) [03:48:47:668]: SOURCEMGMT: Now checking product {EE92F683-5F5C-4970-BB0B-9AC591B60268}

MSI (s) (74:F8) [03:48:47:668]: SOURCEMGMT: Media is enabled for product.

MSI (s) (74:F8) [03:48:47:668]: SOURCEMGMT: Attempting to use LastUsedSource from source list.

MSI (s) (74:F8) [03:48:47:668]: SOURCEMGMT: Trying source \\COLO\e$\dd0d298ee7de04edd3459f7396e3\HotFixSqlSupport\Files\.

MSI (s) (74:F8) [03:49:05:789]: Note: 1: 1314 2: \\COLO\e$\dd0d298ee7de04edd3459f7396e3\HotFixSqlSupport\Files\

MSI (s) (74:F8) [03:49:05:789]: ConnectToSource: CreatePath/CreateFilePath failed with: -2147483648 1314 -2147483648

MSI (s) (74:F8) [03:49:05:789]: ConnectToSource (con’t): CreatePath/CreateFilePath failed with: -2147483648 -2147483648

MSI (s) (74:F8) [03:49:05:789]: SOURCEMGMT: net source ‘\\COLO\e$\dd0d298ee7de04edd3459f7396e3\HotFixSqlSupport\Files\’ is invalid.

MSI (s) (74:F8) [03:49:05:789]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp

MSI (s) (74:F8) [03:49:05:789]: SOURCEMGMT: Processing net source list.

MSI (s) (74:F8) [03:49:05:789]: SOURCEMGMT: Trying source \\COLO\e$\3cd98dcc1d89d2f23c83d7f540\HotFixSqlSupport\Files\.

MSI (s) (74:F8) [03:49:05:805]: Note: 1: 1314 2: \\COLO\e$\3cd98dcc1d89d2f23c83d7f540\HotFixSqlSupport\Files\

MSI (s) (74:F8) [03:49:05:805]: ConnectToSource: CreatePath/CreateFilePath failed with: -2147483648 1314 -2147483648

MSI (s) (74:F8) [03:49:05:805]: ConnectToSource (con’t): CreatePath/CreateFilePath failed with: -2147483648 -2147483648

MSI (s) (74:F8) [03:49:05:805]: SOURCEMGMT: net source ‘\\COLO\e$\3cd98dcc1d89d2f23c83d7f540\HotFixSqlSupport\Files\’ is invalid.

MSI (s) (74:F8) [03:49:05:805]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp

MSI (s) (74:F8) [03:49:05:805]: SOURCEMGMT: Processing media source list.

MSI (s) (74:F8) [03:49:06:839]: SOURCEMGMT: Resolved source to: ‘SqlSupport.msp’

MSI (s) (74:F8) [03:50:44:335]: Note: 1: 1314 2: SqlSupport.msp

MSI (s) (74:F8) [03:50:44:335]: Unable to create a temp copy of patch ‘SqlSupport.msp’.

MSI (s) (74:F8) [03:50:44:351]: Note: 1: 1708

MSI (s) (74:F8) [03:50:44:351]: Note: 1: 2729

MSI (s) (74:F8) [03:50:44:351]: Note: 1: 2729

MSI (s) (74:F8) [03:50:44:351]: Product: Microsoft SQL Server Setup Support Files (English) — Installation failed.

 

MSI (s) (74:F8) [03:50:44:367]: MainEngineThread is returning 1635

This patch package could not be opened.  Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi

MSI (c) (B0:C0) [03:50:44:508]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (c) (B0:C0) [03:50:44:523]: MainEngineThread is returning 1635

=== Verbose logging stopped: 3/20/2011  3:50:44 ===

Action Plan:

===============================================================================================================================================================================

First you need to know what all the patches has been applied to SQL Server instance for which SP3 fails. Follow these steps:

First you need to go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and search for the instance name in my case its Robert

The “ModifyPath” and “UinstallString” contains the GUID in reverse order for my instance Robert. So we need to un-reverse it to get the actual GUID. In my case 2373A92B-1C1C-4E71-B494-5CA97F96AA19

Copy this key and go to location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products search for it B29A3732C1C117E44B49C59AF769AA91.

Under this guid you will find patches folder. Expand that and it will give you something like this.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\4507ED630A831454F9E910BAB13A3B13\Patches\5CCC6FF17E99624A8558E75D7650B18

If you see multiple folders under patches that mean multiple patches has been applied to your instance already.

Inside this key hive you will find a key called “DisplayName” that will tell you what patch(s) has been applied to your instance. For eg,

Hotfix 3024 for SQL Server Database Services 2005 ENU (KB000000)

For our instance we have only applied SP1 and SP2 which was confirmed from the above steps. So in this scenario SP3 installation is looking for old SP1 and SP2 in the C:\windows\installer folder but it’s not able to find them. It fall backs to the source temp folder which the Service pack or any SQL Server patch creates during the time of installation, it was not able to find that either.

Ran repairSP1Source.js (This is run to fix the SP1 files extracted in windows/installer folder. These files are created during the installation of SP1)

Rebuild the SP1 and SP2 setup files.

1. SQLServer2005SP1 x86-ENU.exe /X

2. cscript RepairSP1Source.js “<path to SP1 files>”

3. Similarly repeat the Step 1 and 2 for SP2 files as well.

RepairSP1Source.js Script: (copy the following script in a notepad and save it as RepairSP1Source.js)

if( WScript.Arguments.Length < 1 )

{

     WScript.Echo( “Usage: RepairSP1Source.js \”<path to extracted SP1 files>\”” );

    WScript.Quit( 1 );

}

var filesystem = new ActiveXObject( “Scripting.FileSystemObject” );

var newSource = WScript.Arguments( 0 );

if( !filesystem.FolderExists( newSource ) )

{

    WScript.Echo( “The path to the extracted SP1 package does not exist.  Please correct the path and run the tool again.” );

    WScript.Quit( 1 );

}

var installer = WScript.CreateObject( “WindowsInstaller.Installer” );

 // Look for MSPs at the extracted location

EnumerateMSPs( newSource );

function EnumerateMSPs( extractedSp1PatchPath )

{

    var folder = filesystem.GetFolder( extractedSp1PatchPath );

    var fileEnum = new Enumerator( folder.Files );

     for( ; !fileEnum.atEnd(); fileEnum.moveNext() )

     {

         var nextFile = fileEnum.item();

         if( filesystem.GetExtensionName( nextFile.Name ) == “msp” )

         {

 

            WScript.Echo( “Found patch located at: ” + nextFile.Path );

 

            var extractedSp1PatchSummaryInfo = installer.SummaryInformation( nextFile.Path );

 

            // Retrieve the PatchCode from the SummaryInformation

 

            var extractedSp1PatchCode = new String( extractedSp1PatchSummaryInfo.Property( 9 ) ).substring( 0, 38 );

   // Look to see if we need to repair the cached MSP for this Patch

            RepairCachedMSP( extractedSp1PatchCode, nextFile.Path );

             WScript.Echo();

         }

 

    }

    // Now look in subfolders for MSPs

    var folderEnum = new Enumerator( folder.SubFolders );

    for( ; !folderEnum.atEnd(); folderEnum.moveNext() )

    {

        var nextFolder = folderEnum.item();

         EnumerateMSPs( nextFolder.Path );

     }

 }

 function RepairCachedMSP( extractedSp1PatchCode, extractedSp1PatchPath )

 

{

 

    var sp1Patch = null;

 

    var cachedSp1PatchFileName = null;

     WScript.Echo( “Attempting to repair the local cache for PatchCode \”” + extractedSp1PatchCode + “\”” );

    // Enumerate all products installed on the machine to see if any have been patched by

    // this MSP

     var products = installer.ProductsEx( “”, “”, 4 );

     // Look for the first product that is patched with this MSP.

    for( var x = 0; (sp1Patch == null) && (x < products.Count); x++ )

     {

         var nextProduct = products.Item( x );

         var nextProductPatches = installer.PatchesEx( nextProduct.ProductCode, “”, 4, 1 );

         for( var y = 0; (sp1Patch == null) && (y < nextProductPatches.Count); y++ )

 

        {

 

            var nextProductPatch = nextProductPatches.Item( y );

 

            var nextPatchURL = nextProductPatch.PatchProperty( “MoreInfoURL” );

 

            var nextPatchURLString = new String( nextPatchURL );

             // See if this patch is SP1 and if it matches the PatchCode of what the user

 

            // extracted to the hard drive.

 

            if ( extractedSp1PatchCode == nextProductPatch.PatchCode )

 

            {

 

                cachedSp1PatchFileName = nextProductPatch.PatchProperty( “LocalPackage” );

 

                 // Only re-cache if the MSP is missing

 

                if( !filesystem.FileExists( cachedSp1PatchFileName ) )

 

                {

 

                    sp1Patch = nextProductPatch;

 

                }

 

            }

 

        }

 

    }

 

 

 

    if( !cachedSp1PatchFileName )

 

    {

 

        WScript.Echo( “No action can be taken as the patch has not been applied on the local machine.” );

 

    }

 

    else

 

    {

 

        if( sp1Patch == null )

 

        {

 

            WScript.Echo( “No action will be taken since the provided SP1 patch appears to exist locally.” );

 

        }

 

        else

 

        {

 

            var extractedSp1Patch = filesystem.GetFile( extractedSp1PatchPath );

             WScript.Echo( “Re-caching patch for the product code \”” + sp1Patch.ProductCode

 

                + “\” and patch \”” + sp1Patch.PatchCode + “\” to \”” + cachedSp1PatchFileName + “\”” );

 

            extractedSp1Patch.Copy( cachedSp1PatchFileName );

              var updatedSp1Patch = filesystem.GetFile( cachedSp1PatchFileName );

 

            var currentAttributes = updatedSp1Patch.Attributes;

  

            // If the file isn’t read-only mark it as such.

 

            if( ( currentAttributes & 1 ) == 0 )

 

            {

 

                updatedSp1Patch.Attributes = (currentAttributes | 1 );

 

            }

 

        }

 

    }

 

}

SP3 should install now.

2 Responses to “Installation of SP3 fails.”

  1. Idris Chambas said

    Balaji. You saved my day with this cool stuff. This was absolutely a lifeline. Many thanks.

  2. I do trust all the ideas you’ve presented in your post. They are really convincing and will certainly work. Nonetheless, the posts are too quick for newbies. Could you please extend them a little from next time? Thank you for the post.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: