In my recent experience while installing WSS 3.0 SP2 we got a error as below

Windows SharePoint services 3.0 Service Pack 2(SP2) has encountered a problem and needs to close. we are sorry for the inconvenience.

Dialog box to send Error report / Don’t send

let me give some background on why we got into this issue

- We wanted to remove it completely again and install it this time with the BASIC option , in the installation wizard.

- The installation completed and started the PS config wizard, the wizard completed all the 10 steps and we saw the same error when tried to open the central admin.

- We observed the following odd things –

1-> The version of the product in the ADD/REMOVE programs section for WSS 3.0 is 12.0.0.6425

2-> All the SQL Dbs that it is creating is under the version -12.0.0.4518

3-> The separate installation of Sp1 and Sp2 on WSS 3.0 also is unsuccessful.

when we ran the WSS 3.0 SP2 it failed with an error  “Windows SharePoint services 3.0 Service Pack 2(SP2) has encountered a problem and needs to close. we are sorry for the inconvenience.”

We ran an Inventory tool called ROIScan.vbs (Internal script – for more details contact Microsoft support)  and got the below results

Review Items
============
Error:                       Local patch package 'C:\WINDOWS\Installer\6633ba94.msp' missing for patch '{88591C3A-E392-4B2C-98B7-F123862FD540}'
Error:                       Local patch package 'C:\WINDOWS\Installer\6633b71a.msp' missing for patch '{4A35EF4A-D868-4B15-A84D-3E8925AA9558}'
Error:                       Local patch package 'C:\WINDOWS\Installer\901e67a6.msp' missing for patch '{D93F9C7C-AB57-44C8-BAD6-1494674BCAF7}'
Error:                       Local patch package 'C:\WINDOWS\Installer\6633b91d.msp' missing for patch '{464FBCDB-72F8-4C39-AC19-D2E7CFC82287}'
Error:                       Local patch package 'C:\WINDOWS\Installer\6633b990.msp' missing for patch '{A1665382-302F-476F-99B3-1B6148B1AB16}'

Products Inventory
==================

Microsoft Windows SharePoint Services 3.0
-----------------------------------------
ProductVersion               12.0.4518.1016
ServicePack Level            RTM
Architecture                 x86/32bit
ProductCode                  {90120000-1014-0000-0000-0000000FF1CE}
Msi ProductName              Microsoft Windows SharePoint Services 3.0
Configuration SKU            WSS
InstallDate                  20100708
UserSid                     
ProductContext               Machine
ProductState                 Installed
Transforms                   |C:\Program Files\Common Files\Microsoft Shared\SERVER12\Server Setup Controller\WSS.EN-US\WShellUI.MST
Original .msi Name           sts.msi
Cached .msi Package          C:\WINDOWS\Installer\294d2.msi
ProductID (MSI)             
Build/Origin                 4518_1014\x86\ship\0\sts
Package Code                 {CB8170A7-3E73-4E4D-8442-767FE90EFF05}
Notes                        -
Errors                       -
Config ProductName           WSS
Config PackageID             wss

-Then we merged the verbose on registry  and ran the setup again .

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"logging"= "voicewarmup"
"debug"=dword:00000007

We got the same error and when we review the log which was stored in %temp% we got the log as below

===Verbose logging started: 7/07/2010  21:44:27  Build type: SHIP UNICODE 3.01.4000.4042  Calling process: E:\wssv3sp2-kb953338-x86-fullfile-en-us.exe ===

-We extracted the WSS 3.0 SP2 to a new folder and copied the OPUTIL.vbs (Internal script – for more details contact Microsoft support)

-Ran the OPUTIL.vbs /ApplyPatch and it failed again with the same message.

then we looked at the summary of the OPUTIL.vbs we got the below details

then looked at the log file

(UNKNOWN)     ?=== Verbose logging started: 8/07/2010 17:28:50 Build type: SHIP UNICODE 3.01.4000.4042 Calling process: C:\WINDOWS\system32\msiexec.exe ===
(CLIENT)     MSI (c) (E4:3C) [17:28:50:296]: Resetting cached policy values
(POLICY)     MSI (c) (E4:3C) [17:28:50:296]: Machine policy value 'Debug' is 7
(CLIENT)     MSI (c) (E4:3C) [17:28:50:296]: ******* RunEngine:
(UNKNOWN)      ******* Product: {90120000-1014-0000-0000-0000000FF1CE}
(UNKNOWN)      ******* Action:
(UNKNOWN)      ******* CommandLine: PATCH="E:\Software\SharePoint Service 3.0\WSS3.0 extract\Updates\stssp2-x86.msp" REBOOT=ReallySuppress
(CLIENT)     MSI (c) (E4:3C) [17:28:50:296]: Client-side and UI is none or basic: Running entire install on the server.
(CLIENT)     MSI (c) (E4:3C) [17:28:50:296]: Grabbed execution mutex.
(CLIENT)     MSI (c) (E4:3C) [17:28:50:343]: Cloaking enabled.
(CLIENT)     MSI (c) (E4:3C) [17:28:50:343]: Attempting to enable all disabled priveleges before calling Install on Server
(CLIENT)     MSI (c) (E4:3C) [17:28:50:359]: Incrementing counter to disable shutdown. Counter after increment: 0
(SERVER)     MSI (s) (94:3C) [17:28:50:375]: Grabbed execution mutex.
(SERVER)     MSI (s) (94:C0) [17:28:50:375]: Resetting cached policy values
(POLICY)     MSI (s) (94:C0) [17:28:50:375]: Machine policy value 'Debug' is 7
(SERVER)     MSI (s) (94:C0) [17:28:50:375]: ******* RunEngine:
(UNKNOWN)      ******* Product: {90120000-1014-0000-0000-0000000FF1CE}
(UNKNOWN)      ******* Action:
(UNKNOWN)      ******* CommandLine: PATCH="E:\Software\SharePoint Service 3.0\WSS3.0 extract\Updates\stssp2-x86.msp" REBOOT=ReallySuppress CURRENTDIRECTORY="E:\Software\SharePoint Service 3.0\WSS3.0 extract\Updates" CLIENTUILEVEL=2 CLIENTPROCESSID=6372
(POLICY)     MSI (s) (94:C0) [17:28:50:375]: Machine policy value 'DisableUserInstalls' is 0
(SERVER)     MSI (s) (94:C0) [17:28:50:390]: End dialog not enabled
(SERVER)     MSI (s) (94:C0) [17:28:50:390]: Original package ==> C:\WINDOWS\Installer\294d2.msi
(SERVER)     MSI (s) (94:C0) [17:28:50:390]: Package we're running from ==> C:\WINDOWS\Installer\294d2.msi
(SERVER)     MSI (s) (94:C0) [17:28:50:390]: APPCOMPAT: looking for appcompat database entry with ProductCode '{90120000-1014-0000-0000-0000000FF1CE}'.
(SERVER)     MSI (s) (94:C0) [17:28:50:390]: APPCOMPAT: no matching ProductCode found in database.
(SERVER)     MSI (s) (94:C0) [17:28:50:390]: MSCOREE not loaded loading copy from system32
(SERVER)     MSI (s) (94:C0) [17:28:50:421]: Opening existing patch 'C:\WINDOWS\Installer\1ed46549.msp'.
(SERVER)     MSI (s) (94:C0) [17:28:50:421]: Opening existing patch 'C:\WINDOWS\Installer\845b409a.msp'.
(SERVER)     MSI (s) (94:C0) [17:28:50:421]: File will have security applied from OpCode.
(SERVER)     MSI (s) (94:C0) [17:28:50:484]: Original patch ==> E:\Software\SharePoint Service 3.0\WSS3.0 extract\Updates\stssp2-x86.msp
(SERVER)     MSI (s) (94:C0) [17:28:50:484]: Patch we're running from ==> C:\WINDOWS\Installer\b56a6.msp
(SERVER)     MSI (s) (94:C0) [17:28:50:484]: Opening existing patch 'C:\WINDOWS\Installer\18bab474.msp'.
(SERVER)     MSI (s) (94:C0) [17:28:50:484]: Note: 1: 2203 2: C:\WINDOWS\Installer\18bab474.msp 3: -2147287038
(POLICY)     MSI (s) (94:C0) [17:28:50:500]: Machine policy value 'AllowLockdownBrowse' is 0
(POLICY)     MSI (s) (94:C0) [17:28:50:500]: Machine policy value 'DisableBrowse' is 0
(SERVER)     MSI (s) (94:C0) [17:28:50:500]: Couldn't find local patch 'C:\WINDOWS\Installer\18bab474.msp'. Looking for it at its source.
(SERVER)     MSI (s) (94:C0) [17:28:50:500]: Resolving Patch source.
(POLICY)     MSI (s) (94:C0) [17:28:50:500]: User policy value 'SearchOrder' is 'nmu'
(POLICY)     MSI (s) (94:C0) [17:28:50:500]: User policy value 'DisableMedia' is 0
(POLICY)     MSI (s) (94:C0) [17:28:50:500]: Machine policy value 'AllowLockdownMedia' is 0
(SERVER)     MSI (s) (94:C0) [17:28:50:500]: SOURCEMGMT: Media enabled only if package is safe.
(SERVER)     MSI (s) (94:C0) [17:28:50:500]: SOURCEMGMT: Looking for sourcelist for product {ADE5B215-6E47-40F8-8CAE-D41313D77D11}
(SERVER)     MSI (s) (94:C0) [17:28:50:500]: SOURCEMGMT: Adding {ADE5B215-6E47-40F8-8CAE-D41313D77D11}; to potential sourcelist list (pcode;disk;relpath).
(SERVER)     MSI (s) (94:C0) [17:28:50:500]: SOURCEMGMT: Now checking product {ADE5B215-6E47-40F8-8CAE-D41313D77D11}
(SERVER)     MSI (s) (94:C0) [17:28:50:500]: SOURCEMGMT: Media is enabled for product.
(SERVER)     MSI (s) (94:C0) [17:28:50:500]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
(SERVER)     MSI (s) (94:C0) [17:28:50:500]: SOURCEMGMT: Trying source C:\DOCUME~1\DA-800~1\LOCALS~1\Temp\5\OWP5.tmp\.
(SERVER)     MSI (s) (94:C0) [17:28:50:531]: Note: 1: 2203 2: C:\DOCUME~1\DA-800~1\LOCALS~1\Temp\5\OWP5.tmp\stswwsp2.msp 3: -2147287037
(SERVER)     MSI (s) (94:C0) [17:28:50:531]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
(SERVER)     MSI (s) (94:C0) [17:28:50:531]: Note: 1: 1706 2: -2147483647 3: stswwsp2.msp
(SERVER)     MSI (s) (94:C0) [17:28:50:531]: SOURCEMGMT: Processing net source list.
(SERVER)     MSI (s) (94:C0) [17:28:50:531]: Note: 1: 1706 2: -2147483647 3: stswwsp2.msp
(SERVER)     MSI (s) (94:C0) [17:28:50:531]: SOURCEMGMT: Processing media source list.
(SERVER)     MSI (s) (94:C0) [17:28:50:531]: SOURCEMGMT: Resolved source to: 'stswwsp2.msp'
(SERVER)     MSI (s) (94:C0) [17:29:24:640]: Note: 1: 1314 2: stswwsp2.msp
(SERVER)     MSI (s) (94:C0) [17:29:24:640]: Unable to create a temp copy of patch 'stswwsp2.msp'.
(SERVER)     MSI (s) (94:C0) [17:29:24:640]: Note: 1: 1708
(SERVER)     MSI (s) (94:C0) [17:29:24:640]: Note: 1: 2729
(SERVER)     MSI (s) (94:C0) [17:29:24:656]: Note: 1: 2729
(SERVER)     MSI (s) (94:C0) [17:29:24:656]: Product: Microsoft Windows SharePoint Services 3.0 -- Installation failed.
(UNKNOWN)     
(SERVER)     MSI (s) (94:C0) [17:29:24:671]: Attempting to delete file C:\WINDOWS\Installer\b56a6.msp
(SERVER)     MSI (s) (94:C0) [17:29:24:671]: MainEngineThread is returning 1635
(UNKNOWN)     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.
(UNKNOWN)     C:\WINDOWS\Installer\294d2.msi
(CLIENT)     MSI (c) (E4:3C) [17:29:24:671]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1

NOTE: Look at few lines above for clues on error
(ERROR)      MSI (c) (E4:3C) [17:29:24:671]: MainEngineThread is returning 1635

The trick that worked for us

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

From the log file we found this line

(SERVER)     MSI (s) (94:C0) [17:28:50:500]: SOURCEMGMT: Looking for sourcelist for product {ADE5B215-6E47-40F8-8CAE-D41313D77D11}

KB 954711, {ADE5B215-6E47-40F8-8CAE-D41313D77D11}, STSSP2.MSP, E:\MS WSS Media\extract\Updates\stssp2-x86.msp

You just need to revert the first 8 characters to get the patch code ,which would be

ADE5B215 -> 512B5EDA

{512B5EDA-6E47-40F8-8CAE-D41313D77D11}

searched the registry for the patch GUID as {512B5EDA-6E47-40F8-8CAE-D41313D77D11}

or find the key in below location

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

2.HKEY_CLASSES_ROOT\Installer\Patches

We need to check if a subkey of this name exists
512B5EDA74E68F04C8EA4D31317DD711

Export that key and deleted it

Ran the WSS 3.0 SP2 and this time it completed successfully!!!!!

Hope this helps !!!!!

When i tried to install MOSS SP2 we got an error as below

Report 2007 Microsoft Office System Servers Service Pack 2(SP2) Installation Failure

An error report containing information about the updates that failed installation has been generated.

We apologize for the update installation failure

Please tell Microsoft about this problem.

Using the information in the report we can investigate and potentially fix the problem you

experienced. We will treat this report as confidential and anonymous.

What data does this error report contain?

Send Report/ Cancel

Tried to enable verbose logging for windows installer and still got the same error

Reviewed the MSI log which was found in %temp% with latest date modified  and found the following

I tried to run the installation again and we got an error as above

Then we decided to click on the “What data does this error report contain?” as below

Then we “View the Contents of the error report”

Then Reviewed the Coreserverwwso2_MSPLOG.LOG and found the following

Then we found that that Osearch was in stopping state

- Tried to Stop OSearch using Net stop Osearch and it failed

- Rebooted the server and the we found that the Osearch was started .

Ran the SP2 installation and it completed successfully

If the Beta version of SHAREPOINT 2010 is already installed and if we uninstalled it and installed it with RTM bits .I faced the below error when I ran the configuration wizard it failed at Step 2

Error:

System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for microsoft.identityModel: Could not load file or assembly 'Microsoft.IdentityModel, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Reviewed the PSCDiagnostics logs

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

04/27/2010 21:26:26  9  ERR                    Task configdb has failed with an unknown exception

04/27/2010 21:26:26  9  ERR                    Exception: System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for microsoft.identityModel: Could not load file or assembly 'Microsoft.IdentityModel, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Root\web.config line 4) ---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.IdentityModel, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

File name: 'Microsoft.IdentityModel, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

   at System.Configuration.TypeUtil.GetTypeWithReflectionPermission(IInternalConfigHost host, String typeString, Boolean throwOnError)

   at System.Configuration.MgmtConfigurationRecord.CreateSectionFactory(FactoryRecord factoryRecord)

   at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

   --- End of inner exception stack trace ---

   at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)

   at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)

   at System.Configuration.ConfigurationSectionCollection.Get(String name)

   at Microsoft.SharePoint.Administration.SPIisWebServiceSettings.ProvisionWebSiteSettings()

   at Microsoft.SharePoint.Administration.SPIisWebServiceInstance.Provision()

   at Microsoft.SharePoint.Administration.SPFarm.Join()

   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()

   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()

   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

04/27/2010 21:26:26  9  INF                    Entering function Common.BuildExceptionMessage

04/27/2010 21:26:26  9  INF                      Entering function StringResourceManager.GetResourceString

04/27/2010 21:26:26  9  INF                        Resource id to be retrieved is ExceptionInfo for language English (United States)

04/27/2010 21:26:26  9  INF                        Resource retrieved id ExceptionInfo is An exception of type {0} was thrown.  Additional exception information: {1}

04/27/2010 21:26:26  9  INF                      Leaving function StringResourceManager.GetResourceString

04/27/2010 21:26:26  9  INF                    Leaving function Common.BuildExceptionMessage

04/27/2010 21:26:26  9  INF                    Entering function Common.BuildExceptionInformation

04/27/2010 21:26:26  9  INF                      Entering function Common.BuildExceptionMessage

04/27/2010 21:26:26  9  INF                        Entering function StringResourceManager.GetResourceString

04/27/2010 21:26:26  9  INF                          Resource id to be retrieved is ExceptionInfo for language English (United States)

04/27/2010 21:26:26  9  INF                          Resource retrieved id ExceptionInfo is An exception of type {0} was thrown.  Additional exception information: {1}

04/27/2010 21:26:26  9  INF                        Leaving function StringResourceManager.GetResourceString

04/27/2010 21:26:26  9  INF                      Leaving function Common.BuildExceptionMessage

04/27/2010 21:26:26  9  INF                    Leaving function Common.BuildExceptionInformation

04/27/2010 21:26:26  9  ERR                    An exception of type System.Configuration.ConfigurationErrorsException was thrown.  Additional exception information: An error occurred creating the configuration section handler for microsoft.identityModel: Could not load file or assembly 'Microsoft.IdentityModel, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Root\web.config line 4)

System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for microsoft.identityModel: Could not load file or assembly 'Microsoft.IdentityModel, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Root\web.config line 4) ---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.IdentityModel, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

File name: 'Microsoft.IdentityModel, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

   at System.Configuration.TypeUtil.GetTypeWithReflectionPermission(IInternalConfigHost host, String typeString, Boolean throwOnError)

   at System.Configuration.MgmtConfigurationRecord.CreateSectionFactory(FactoryRecord factoryRecord)

   at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)

WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure logging.

To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

   --- End of inner exception stack trace ---

   at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)

   at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)

   at System.Configuration.ConfigurationSectionCollection.Get(String name)

   at Microsoft.SharePoint.Administration.SPIisWebServiceSettings.ProvisionWebSiteSettings()

   at Microsoft.SharePoint.Administration.SPIisWebServiceInstance.Provision()

   at Microsoft.SharePoint.Administration.SPFarm.Join()

   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()

   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()

   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Found that  the Geneva Frame work was installed on the server and also the KB 974405 

I uninstalled it and Ran the configuration wizard and it failed at step 2 and gave the same error.

As per the Prerequisites requirement we need first uninstall Geneva Frame work  and to install the KB 974405 for windows 2008 server (Microsoft.IdentityModel)

But I then decided to uninstall sharepoint 2010, run the PreRequisiteInstaller and installed the KB 974405

Ran the configuration wizard and it completed successfully

I had clicked on cancel and getting he was getting this message.

SharePoint Products and Technologies Configuration Wizard

Configuring SharePoint Products and Technologies

Please wait while SharePoint Products and Technologies is configured. :

Performing configuration tasks of 8 of 9

Please wait while configuration of SharePoint Products and Technologies is stopped. Configuration will be stopped as soon as the upgrade SharePoint Products and Technologies settings have been applied...

Reviewed the upgrade.log and found that it was idle for more 2 hours

[SearchSP2AnchorTextDatabaseAction] [12.2.506.0] [DEBUG] [3/5/2010 9:47:03 PM]: SearchSP2AnchorTextDatabaseAction.Upgrade on database stuspssql:TCCPassportSSP2_Search_DB

[SPManager] [DEBUG] [3/5/2010 9:47:08 PM]: SyncUpgradeTimerJob: sleeping for 10 seconds

[SPManager] [DEBUG] [3/5/2010 9:47:18 PM]: SyncUpgradeTimerJob: sleeping for 10 seconds

[SPManager] [DEBUG] [3/5/2010 9:47:28 PM]: SyncUpgradeTimerJob: sleeping for 10 seconds

[SPManager] [DEBUG] [3/5/2010 9:47:38 PM]: SyncUpgradeTimerJob: sleeping for 10 seconds

Pasted from <file:///C:\Users\paulpa\AppData\Local\Microsoft\Windows\Temporary%20Internet%20Files\Content.MSO\4AC45E7.log>

Killed the PSCONFIG.UI in the task manager

Then ran the command

psconfig.exe —cmd upgrade —inplace b2b —force

03/06/2010 00:25:30 4 ERR An exception of type System.ServiceProcess.TimeoutException was thrown. Additional exception information: Time out has expired and the operation has not been completed.

System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.

at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)

at Microsoft.SharePoint.PostSetupConfiguration.ServiceHelper.Stop(String serviceName)

at Microsoft.SharePoint.PostSetupConfiguration.InitializeTask.StopServicesListedInRegistry(RegistryHelper registry)

at Microsoft.SharePoint.PostSetupConfiguration.InitializeTask.StopAllServices()

at Microsoft.SharePoint.PostSetupConfiguration.InitializeTask.PrepareForUpgrade()

at Microsoft.SharePoint.PostSetupConfiguration.InitializeTask.Run()

at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Found that the OSEARCH was in stopping state

Tried to run the net stop OSEARCH , it did not complete

Rebooted the server

After reboot the OSEARCH was still in starting

Disabled it and rebooted it again

Ran the command

psconfig.exe —cmd upgrade —inplace b2b —force

Reviewed the upgrade. log

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

[NewWebParts] [12.1.6301.0] [INFO] [3/6/2010 1:10:39 AM]: ERROR - Adding web part (_catalogs/wp/SummaryResults.webpart) caused by the following error:

[SiteSequence] [ERROR] [3/6/2010 1:10:39 AM]: Action 12.1.6301.0 of Microsoft.SharePoint.Portal.Upgrade.SiteSequence failed.

[SiteSequence] [ERROR] [3/6/2010 1:10:39 AM]:

[SiteSequence] [ERROR] [3/6/2010 1:10:39 AM]: at Microsoft.SharePoint.SPFileCollection.Add(String urlOfFile, Byte[] file, Boolean overwrite, String checkInComment, Boolean checkRequiredFields)

at Microsoft.SharePoint.SPFileCollection.Add(String urlOfFile, Byte[] file, Boolean overwrite)

at Microsoft.SharePoint.Portal.Upgrade.GenericWebPartGalleryUpgrade.AddWebPart(SPFileCollection rootWebFiles, String dwpWebPath, String dwpFilePath, String dwpGroup)

at Microsoft.SharePoint.Portal.Upgrade.GenericWebPartGalleryUpgrade.UpdateWebParts(SPSite site, String[] deleteDwps, String[] newDwps, String wpGroup, String strPath)

at Microsoft.SharePoint.Portal.Upgrade.NewWebParts.Upgrade()

at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade()

[NewWebParts] [12.1.6301.0] [DEBUG] [3/6/2010 1:10:39 AM]: Begin Rollback()

[NewWebParts] [12.1.6301.0] [DEBUG] [3/6/2010 1:10:39 AM]: End Rollback()

[NewWebParts] [12.1.6301.0] [DEBUG] [3/6/2010 1:10:39 AM]: Begin Dispose()

[NewWebParts] [12.1.6301.0] [DEBUG] [3/6/2010 1:10:39 AM]: End Dispose()

[NewWebParts] [12.1.6301.0] [DEBUG] [3/6/2010 1:10:39 AM]: Elapsed time: 00:00:00.2031250.

[SPManager] [ERROR] [3/6/2010 1:10:39 AM]: Upgrade [SPSite Url=https://servername/personal/acun] failed. Microsoft.SharePoint.Portal.Upgrade.SiteSequence has the ContinueOnFailiure bit set. Moving on to the next object in sequence.

[SPManager] [ERROR] [3/6/2010 1:10:39 AM]:

[SPManager] [ERROR] [3/6/2010 1:10:39 AM]: at Microsoft.SharePoint.SPFileCollection.Add(String urlOfFile, Byte[] file, Boolean overwrite, String checkInComment, Boolean checkRequiredFields)

at Microsoft.SharePoint.SPFileCollection.Add(String urlOfFile, Byte[] file, Boolean overwrite)

at Microsoft.SharePoint.Portal.Upgrade.GenericWebPartGalleryUpgrade.AddWebPart(SPFileCollection rootWebFiles, String dwpWebPath, String dwpFilePath, String dwpGroup)

at Microsoft.SharePoint.Portal.Upgrade.GenericWebPartGalleryUpgrade.UpdateWebParts(SPSite site, String[] deleteDwps, String[] newDwps, String wpGroup, String strPath)

at Microsoft.SharePoint.Portal.Upgrade.NewWebParts.Upgrade()

I disabled the forefront service by running the command

c:\program files\Microsoft forefront security\SHAREPOINT\ FSCutility /disable

before that stop FSC controller and IIS admin

Ran the command

psconfig.exe —cmd upgrade —inplace b2b —force

It completed without error

Then we ran the command to the attach the content DB using the command

Stsadm-o addcontentdb -url <> -databasename

It completed successfully

Ran the Wizard on all the server and it completed successfully

Started the forefront security

Ran the wizard and it completed successfully ]]> https://docs.microsoft.com/archive/blogs/paulpaa/sharepoint-2007-hotfix-failed-with-an-error-the-detection-failed-this-can-be-due-to-a-corrupted-installation Fri, 26 Mar 2010 02:16:20 GMT https://blogs.technet.microsoft.com/paulpaa/2010/03/26/sharepoint-2007-hotfix-failed-with-an-error-the-detection-failed-this-can-be-due-to-a-corrupted-installation/ Unable to install the patch getting an error " The detection failed, this can be due to a corrupted installation"

So I decided to merge the verbose logging for MSI installer and found that following

reviewed the log and found that the installation source was not accessible

MSI (s) (A8:40) [22:42:39:412]: Machine policy value 'DisableUserInstalls' is 0

MSI (s) (A8:40) [22:42:39:412]: Warning: Local cached package 'C:\WINDOWS\Installer\fdb3fcf.msi' is missing.

MSI (s) (A8:40) [22:42:39:412]: User policy value 'SearchOrder' is 'nmu'

MSI (s) (A8:40) [22:42:39:412]: User policy value 'DisableMedia' is 0

MSI (s) (A8:40) [22:42:39:412]: Machine policy value 'AllowLockdownMedia' is 0

MSI (s) (A8:40) [22:42:39:412]: SOURCEMGMT: Media enabled only if package is safe.

MSI (s) (A8:40) [22:42:39:412]: SOURCEMGMT: Looking for sourcelist for product {90120000-1080-0409-1000-0000000FF1CE}

MSI (s) (A8:40) [22:42:39:412]: SOURCEMGMT: Adding {90120000-1080-0409-1000-0000000FF1CE}; to potential sourcelist list (pcode;disk;relpath).

MSI (s) (A8:40) [22:42:39:428]: SOURCEMGMT: Now checking product {90120000-1080-0409-1000-0000000FF1CE}

MSI (s) (A8:40) [22:42:39:428]: SOURCEMGMT: Media is enabled for product.

MSI (s) (A8:40) [22:42:39:428]: SOURCEMGMT: Attempting to use LastUsedSource from source list.

MSI (s) (A8:40) [22:42:39:428]: Note: 1: 2203 2: 3: -2147287037

MSI (s) (A8:40) [22:42:39:428]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.

MSI (s) (A8:40) [22:42:39:428]: Note: 1: 1706 2: -2147483647 3: osrvmui.msi

MSI (s) (A8:40) [22:42:39:428]: SOURCEMGMT: Processing net source list.

MSI (s) (A8:40) [22:42:39:428]: Note: 1: 1402 2: UNKNOWN\Net 3: 2

MSI (s) (A8:40) [22:42:39:428]: Note: 1: 1706 2: -2147483647 3: osrvmui.msi

MSI (s) (A8:40) [22:42:39:428]: SOURCEMGMT: Processing media source list.

MSI (s) (A8:40) [22:42:39:428]: Note: 1: 1706 2: -2147483647 3: osrvmui.msi

MSI (s) (A8:40) [22:42:39:428]: SOURCEMGMT: Processing URL source list.

MSI (s) (A8:40) [22:42:39:428]: Note: 1: 1402 2: UNKNOWN\URL 3: 2

MSI (s) (A8:40) [22:42:39:428]: Note: 1: 1706 2: -2147483647 3: osrvmui.msi

MSI (s) (A8:40) [22:42:39:428]: Note: 1: 1706 2: 3: osrvmui.msi

MSI (s) (A8:40) [22:42:39:428]: SOURCEMGMT: Failed to resolve source

MSI (s) (A8:40) [22:42:39:428]: MainEngineThread is returning 1612

MSI (c) (C8:08) [22:42:39:428]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1

MSI (c) (C8:08) [22:42:39:428]: MainEngineThread is returning 1612

=== Verbose logging stopped: 2/17/2010 22:42:39 ===

then we tired to change the source path in the registry

HKEY_CLASSES_ROOT\Installer\Products\<GUID>\SourceList

but still it was not able to pull the details mentioned in the registry

Ran the Microsoft internal Script called OPSUTIL.vbs

cscript.exe OPUtil.vbs

gave the below details

{90120000-1080-0409-1000-0000000FF1CE} - Microsoft Office Shared Coms English Language Pack

Error: Local .msi package missing. Attempt failed to restore C:\WINDOWS\Installer\fdb3fcf.msi (PackageCode: {77CB92A3-B1AD-4F91-9154-F32481270338})

Error: Local .msp package missing. Attempt failed to restore 'c:\windows\installer\884fa763.msp' - '{DE436CD5-7346-4BE1-A9C5-137FB6E0A072}' - 'Infrastructure Update for Microsoft Office Servers

Error: Local .msp package missing. Attempt failed to restore 'c:\windows\installer\d5d56ce5.msp' - '{0D4C8AE6-5396-4CAC-85B2-10AA0777CFA8}' - '2007 Microsoft Office System Servers Service Pack 1 (SP1)

{90120000-1103-0409-1000-0000000FF1CE} - Microsoft Office Document Lifecycle Components English Language Pack

Error: Local .msi package missing. Attempt failed to restore C:\WINDOWS\Installer\fdb400d.msi (PackageCode: {D4DA3E65-8E10-4B5B-A566-4E358600A44D})

Error: Local .msp package missing. Attempt failed to restore 'c:\windows\installer\d5d56d6f.msp' - '{44C242A1-F448-4293-BE81-2C0A99FB4128}' - '2007 Microsoft Office System Servers Service Pack 1 (SP1)

Note: Restore is possible from 'RestoreLocation' (C:\WINDOWS\Installer\12d55f5c.msp) to restore local .msp package c:\windows\installer\1c194d78.msp' - '{80E17CBA-ABF7-4565-B8E2-62454A903669}' - 'Hotfix for Office (KB955586)

{90120000-1104-0409-1000-0000000FF1CE} - Microsoft Office Slide Library English Language Pack

Error: Local .msi package missing. Attempt failed to restore C:\WINDOWS\Installer\fdb401a.msi (PackageCode: {27BC90F4-C3B7-4469-A6AB-7EBA52A2B6A5})

Error: Local .msp package missing. Attempt failed to restore 'c:\windows\installer\d5d56d75.msp' - '{487B60F3-BA3B-4831-9ABE-3CEF4D23FBFB}' - '2007 Microsoft Office System Servers Service Pack 1 (SP1)

{90120000-1014-0000-1000-0000000FF1CE} - Microsoft Windows SharePoint Services 3.0

Error: Local .msi package missing. Attempt failed to restore C:\WINDOWS\Installer\fdb402c.msi (PackageCode: {860704F7-510A-4859-A223-F7E2BC6644C4})

Error: Local .msp package missing. Attempt failed to restore 'c:\windows\installer\d5d56db8.msp' - '{EDD957F1-6879-49E2-AD94-04F0DF713B5E}' - 'Hotfix for WSS (KB948945)

Error: Local .msp package missing. Attempt failed to restore 'c:\windows\installer\19a3501d.msp' - '{F44F9F42-03C6-4247-A434-A13988DA39CC}' - 'Hotfix for WSS (KB939592)

Error: Local .msp package missing. Attempt failed to restore 'c:\windows\installer\d5d56e5d.msp' - '{2CD31384-B0AA-46DF-997B-006CCC2D7326}' - 'Hotfix for WSS (KB950484)

Note: Restore is possible from 'RestoreLocation' (C:\WINDOWS\Installer\12d55f82.msp) to restore local .msp package c:\windows\installer\1c194d9d.msp' - '{1516EFE8-96B9-42C1-A327-7F027780747A}' - 'Hotfix for WSS (KB956057)

Error: Local .msp package missing. Attempt failed to restore 'c:\windows\installer\d5d56c81.msp' - '{235EC23A-712E-4F18-A1B8-C50458A6D3EF}' - 'Windows SharePoint Services 3.0 Service Pack 1 (SP1)

Error: Local .msp package missing. Attempt failed to restore 'c:\windows\installer\883b3967.msp' - '{6D26530B-7C54-4F19-A873-86A2372BA902}' - 'Infrastructure Update for Windows SharePoint Services 3.0

Error: Local .msp package missing. Attempt failed to restore 'c:\windows\installer\d3ad36a3.msp' - '{EA5FAE1B-500C-44F3-87B9-506B2752D212}' - 'Hotfix for WSS (KB941422)

{90120000-1015-0409-1000-0000000FF1CE} - Microsoft Windows SharePoint Services 3.0 1033 Lang Pack

Error: Local .msi package missing. Attempt failed to restore C:\WINDOWS\Installer\fdb3fd6.msi (PackageCode: {0BA44367-EB13-41D1-88F2-6AEAE47CDFED})

Error: Local .msp package missing. Attempt failed to restore 'c:\windows\installer\d5d56c8f.msp' - '{64F71C35-2A93-4739-8477-4E877B0AB61D}' - 'Windows SharePoint Services 3.0 Service Pack 1 (SP1)

Error: Local .msp package missing. Attempt failed to restore 'c:\windows\installer\d5d56e35.msp' - '{84331BB6-9876-4BD6-B1A4-87F8A2F947AC}' - 'Hotfix for WSS (KB948957)

Note: Restore is possible from 'RestoreLocation' (C:\WINDOWS\Installer\12d55f8c.msp) to restore local .msp package c:\windows\installer\1c194dab.msp' - '{C6B1BABD-7988-48B7-92D5-B31A91A154DE}' - 'Hotfix for WSS (KB957109)

This confirmed that the local cache of the MSP file is missing under c:\windows\installer directory

Since the only option that is left is repair the product to get back the local cache.

Since the Farm was at APRIL CU , Extracted the SP2 patch and the APRIL CU to the updates folder

and Run the repair of each MSI file manually which is under this folder

This Step will help you to get the local cache of the missing MSP

Once all the MSI file is repaired , you will be able to get the Patch installation working

More details on the utility please contact Microsoft Support.

Reviewed the Perquisites log in %temp% folder and found the following

2010-03-25 11:40:18 - Beginning download of Hotfix for Microsoft Windows (KB976462)

2010-03-25 11:40:19 - _https://go.microsoft.com/fwlink/?LinkID=166369

2010-03-25 11:40:24 - Size of download of "Hotfix for Microsoft Windows (KB976462)" in bytes is "4331740"

2010-03-25 11:40:24 - Download of "Hotfix for Microsoft Windows (KB976462)" completed successfully

2010-03-25 11:40:24 - Installing Hotfix for Microsoft Windows (KB976462)

2010-03-25 11:40:24 - "C:\Windows\system32\wusa.exe" "C:\Users\ADMINI~1.AVA\AppData\Local\Temp\2\KB93556.tmp.msu" /quiet /norestart

2010-03-25 11:40:26 - Install process returned (0X652=1618)

2010-03-25 11:40:26 - [In HRESULT format] (0X80070652=-2147023278)

2010-03-25 11:40:27 - Last return code (0X652=1618)

2010-03-25 11:40:27 - Error: The tool was unable to install Hotfix for Microsoft Windows (KB976462).

2010-03-25 11:40:27 - Last return code (0X652=1618)

2010-03-25 11:40:27 - Options for further diagnostics: 1. Look up the return code value 2. Download the prerequisite manually and verify size downloaded by the prerequisite installer. 3. Install the prerequisite manually from the given location without any command line options.

2010-03-25 11:40:27 - Cannot retry

Downloaded the KB976462 manually and tried to install the same it doesn't do anything other than the wusa.exe just stays there saying - searching for the updates as below

The only way to stop is to kill the WUSA.exe from the windows Task manager.

I tried to merge the verbose logging for MSI installer , but it did not give any log

The hotfix was of the Windows6.1-KB976462-v2-x64.msu (Microsoft Update Standalone Package file )

Generally the hotfix will be of .MSP file

I tried to extract the Windows6.1-KB976462-v2-x64.msu file by giving /extract command ,

An .MSU file contains the following contents:

• Windows Update metadata
  This metadata describes each update package that the .msu file contains.
• One or more .cab files
  Each .cab file represents one update.
• An .xml file
  This .xml file describes the .msu update package. Wusa.exe uses the .xml file when you perform an unattended installation of the update by using the Package Manager tool (Pkgmgr.exe).

Since it was windows update file, I tried to run windows setup and that also got struck as how the patch installation was stuck.

Verified the Proxy setting and all seems fine.

Later did some Bing and found that the Msu is not a windows update file but kind of Windows update stand alone installer file.

Found an KB https://support.microsoft.com/kb/934307

Followed the step mentioned as below

you download hotfix KB976462.

The Windows6.1-KB976462-v2-x64 file is in the C:\KB976462 folder.

You type the following command at a command prompt to expand the .msu file to a temporary folder:

expand -f:* "C:\KB976462\Windows6.0-KB976462-x64.msu" %TEMP%

Then, you type the following command at a command prompt:

pkgmgr.exe /n:%TEMP%\Windows6.0-KB976462-x64.xml

The command completed successfully.

Then tried to double click on the Windows6.1-KB976462-v2-x64.msu file , I got an message that the patch is already applied

Ran the Perquisite installer and that completed successfully ]]> https://docs.microsoft.com/archive/blogs/paulpaa/windows-installer-error-messages Fri, 05 Feb 2010 20:52:00 GMT https://blogs.technet.microsoft.com/paulpaa/2010/02/05/windows-installer-error-messages/ *** WARNING ***
Error numbers and messages presented here may not be the latest. 

 The standard errors are listed under Error Codes in the appendix.

This document explains the main concepts of how to read a verbose log file created by the Windows Installer.  Non-verbose logs may not contain as much information talked about below and may not provide enough useful information for a failed setup installation.

Verbose logs will contain at least the following information:

• Errors that occur during the installation including internal Windows Installer errors
• All standard actions executed as well as any custom actions that were executed
• If a reboot was requested and completed
• The source location of the installation media
• If the installation was completed
• If the installation was rolled back, this will also be notated in the log

On Windows NT 4, Windows 2000 and Windows XP, the Windows Installer executes an installation in two distinct processes.  One is a client process and the other is a server process.  The log file will show the installation information for both processes.  An installation on a Windows 98, Windows 98 or Windows Millennium will run only in a client process, there is no concept of a server process on these platforms.  In a typical verbose log file, you will see lines like the following for a line that denotes the information presented was done on the client context of the installation:

        MSI (c) (29:28) : Resetting cached policy values

In a typical verbose log file, you will see lines like the following for a line that denotes the information presented was done on the server process of the installation:

        MSI (s) (A0:EC): Original package ==> D:\TEMP\Default.msi

The (29:28) and (A0:EC) entries above represent the last two digits of the process and thread ids respectively that generated the entry in the log file.  Generally, this information is not too useful but can shed some light on which process and thread is associated with log entry.  In the above entry, we also see where the original source package is located at.  In this case, if an uninstall or repair is performed, the location of the package will be first read from d:\temp\default.msi.

The log file will first show the client process while the setup user interface is running.  After the setup user interface has been completed by the end user, the log file will show the a line like the following:

This line signals that the installation execution is now passing to the server process.  Only approved public properties which will be in all uppercase are propagated to the server process to enforce the final changes of the setup installation.  Non-uppercase properties are considered private properties and are not passed to the server process.

The beginning of the server process will look very similar to the beginning of the client process.  The service must re-evaluate all of the settings to prevent a user without sufficient privileges from performing a setup request that should not allowed.  This includes revaluating the private properties, policies and other installation state settings such as the features and components to be installed.

The  server process performs the actual installation functions such as copying files, writing to the registry, etc.  Most actions appear in two forms in a verbose log file.  The first form is to add it to the installation script that will be ran later on in the installation.

    MSI (s) (24:24): Doing action: RegisterTypeLibraries
    Action start 13:02:32: RegisterTypeLibraries.
    GenerateScript: Registering type libraries
    Action ended 13:02:32: RegisterTypeLibraries. Return value 1.

The second form is the actual execution of the action:

        MSI (s) (24:24): Executing op: ActionStart(Name=RegisterTypeLibraries,Description=Registering type libraries,Template=LibID: )
        Action 13:04:42: RegisterTypeLibraries. Registering type libraries

For standard and custom actions, the return values can be one of the following values in the table.  For more information on the return values, please see the help file topic Logging of Action Return Values in the the Windows Installer SDK.

In the example above, we see that the return value for the RegisterTypeLibraries standard action was 1 meaning the action completed successfully.  If this action failed and caused an error, a return value of 3 would have been returned and would have caused the rest of the installation to stop and the rollback process would begin which would return the system back to the same state before the installation began.

When copying  files, the log file will explain why a particular file was or was not copied.  This can be useful when trying to determine why a particular file is or is not copied to the machine.  An example line in the log file may look like the following, note the areas highlighted in bold.

Another useful item that is included in a verbose log file is the feature and component state values that are used during the installation.  The following  is an example entry in a verbose log file for a feature state, note the areas highlighted in bold.

       MSI (s) (34:A1): Feature: _MainFeature; Installed: Absent; Request: Local; Action: Local

For a feature state entry in the log file, the entry will be prefaced with Feature: and the feature name will follow.  In this case, the feature state being displayed is for the feature named _MainFeature. The Installed entry represents the current state of the feature on the machine.  When the setup package is being in installed for the first time, this value following Installed: will typically be Absent meaning the feature is not currently installed on the machine.  Other values are possible such as Local, Null, Request, etc.  For the complete list and their meaning, consult the MsiGetFeatureState documentation in the Windows Installer SDK.  The Request entry represents what the user has requested for the particular feature.  For this example, the user has requested to install the _MainFeature Local.  If this was an uninstall and the user selected to remove the _MainFeature feature, Request would be set to Absent which means to uninstall this feature.  A value of Null for Request would represent the feature will neither be installed nor removed.  The last entry, Action, represents what the Windows Installer is going to actually do for Request entry.  It would be rare that the Action entry did not equal the Request entry.  In this case, the Action to be taken is to install the _MainFeature locally to disk.

The following  is an example entry in a verbose log file for a component state, note the areas highlighted in bold.
        MSI (s) (34:A1): Component: Global_Notepad; Installed: Local; Request: Null; Action: Null

For a component state entry in the log file, the entry will be prefaced with Component: and the component name will follow.  In this case, the component state being displayed is for the component named Global_Notepad. The Installed entry represents the current state of the feature on the machine.  When the setup package is being in installed for the first time, this value following Installed will typically be Absent meaning the component is not currently installed on the machine.  For this example, Installed is set to Local meaning that the underlying component is already installed on the machine.  There are other values are possible for Installed such as Local, Null, Request, etc.  For the complete list and their meaning, consult the MsiGetComponentState documentation in the Windows Installer SDK.  The Request entry represents what the user has requested for the particular feature that this component belongs to.  For this example, the Windows Installer engine has determined based on the user's feature selection to do nothing for the Global_Notepad component which is denoted by Request being set to Null.  If this was an uninstall and the user selected to remove the feature that the Global_Notepad component belong to, Request could be set to Absent which means to uninstall this component.  The last entry, Action, represents what the Windows Installer is going to actually do for Request entry.  It would be rare that the Action entry did not equal the Request entry.  In this case, the Action to be taken is to neither install nor remove the Global_Notepad component.

If a setup installation encounters an error, a verbose log file will contain information about rolling back the installation.  You can find rollback information in the log file by searching for Rollback:.  The following line is an example line which states what action is currently being rolled back

        Rollback: Registering type libraries

In this example, we can see that the RegisterTypeLibraries standard action is rolling back the previous work done earlier in the installation when the RegisterTypeLibraries action executed.

At the end of the verbose log file is a complete property dump of the property names and values which can have either client and server properties listed, client only or server only depending on what operating system the log was generated on and what the user interface level was set to.  For example, in a quiet mode installation on Windows NT, 2000 or XP, only the server process is executed and only server process properties would be displayed at the end of the log file.  The following is an example line found in a verbose log file of a property and its value at the end of the client part of the installation before switching to the server process.

        Property(C): USERNAME = someuser

This line shows the value of the USERNAME property on the client side of the installation before switching over to the server process was set to someuser.  You can tell this is a client property by noticing the C in the Property (C) notation.

The following is an example line found in a verbose log file of a property and its value at the end of the server part of the installation just before the installation terminated.

        Property(S): USERNAME = someuser

This line shows the value of the USERNAME property on the server side of the installation was set to someuser.  You can tell this is a server property by noticing the S in the Property (S) notation.  Please note that the USERNAME property in this case has the same value on both the client and server side, however this may not always be the case for all properties as some properties may change on the server side due to custom actions changing the property.

Our farm is currently running MOSS 2007 SP2 we are strying to install the October 2009 Cumulative Update.

When installing office-kb974988-fullfile-x64-glb.exe on the server i got an error "installation pakage failed"

I was unable to install binary on one of the WFE server.   Event log displays error:

Product: Microsoft Office SharePoint Portal - Update 'Hotfix for Office (KB974988)' could not be installed. Error code 1603.

To resolve this issue , I enabled  the verbose logging for MSI installer by adding the below registry on the WFE server

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]

"logging"= "voicewarmup"

"debug"=dword:00000007

Started the installation again and it failed with the same error.

The log file was stored in %temp% with an name MSIb139c.LOG

Reviewed the log file and found the below details

Looking at the log file we found that its trying to do some action related to Single Sign on (SSO)

We tried to stop that service from services.msc and found that it would not stop . I got an error

Specified path was not found.

Looked at the file C:\Program Files\Common Files\Microsoft Shared\Microsoft Office 12 Single Sign-on\SSOCNTR.INI and found that the file does not exist , rather the folder itself was not there

Since it was an WFE role on the server ,as a workaround I copied the files from another server where the installation was successful to the server on the same path and ran the installation again.

This time it completed successfully.

Hope this helps .