FG

August 2007 - Posts

Sharepoint Hotfix 936867 renders Sharepoint unuseable

After requesting an and applying Windows Sharepoint Services 3.0 hotfix 936867 our Sharepoint stopped working completely.

I've found the following error messages in the application log:

Event Type:        Error

Event Source:     Windows SharePoint Services 3

Event Category:               Topology

Event ID:             5617

Date:                    23.08.2007

Time:                   17:57:34

User:                    N/A

Computer:          WEB3

Description:

The schema version (3.0.149.0) of the database SharePoint_AdminContent_f80b1f17-ff1d-4df2-93d3-66bbbaf5790f on x64a is not consistent with the expected database schema version (3.0.150.0) on WEB3.  Connections to this database from this server have been blocked to avoid data loss.  Upgrade the web front end or the content database to ensure that these versions match.

 

Solution: called "stsadm -o upgrade -inplace -url http://{central_admin_url}"

That seemed to have solved the problem.

 

-> related KB Article Number(s): 934577, 935958, 936867, 937038

 

 

The story goes on...

I've attempted to run a repair installation of WSS 3.0 before finding the above mentioned solution - this seemed to have reset some other settings and we then did get some other sharepoint related errors in the application log.

Therefore I wanted to try the patch again. Unfortunately the patch did not run again, always exited with the error that the system were up to date already.

So we've run the patch with the "/extract:" option to get the sts.msp file.

Running that worked but obviously did not succeed completely.

 

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Timer
Event ID: 6398
Date:  24.08.2007
Time:  10:13:44
User:  N/A
Computer: WEB3
Description:
The Execute method of job definition Microsoft.SharePoint.Administration.SPUpgradeJobDefinition (ID 8a563582-7181-417a-992f-1300d3474227) threw an exception. More information is included below.

Requested registry access is not allowed.


Event Type: Error
Event Source: SharePoint Products and Technologies Configuration Wizard
Event Category: None
Event ID: 104
Date:  24.08.2007
Time:  10:13:46
User:  N/A
Computer: WEB3
Description:
Failed to upgrade SharePoint Products and Technologies.
Failed to upgrade SharePoint Products and Technologies.  Further information regarding this failure can be found at E:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\Upgrade.log.
An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information: Failed to upgrade SharePoint Products and Technologies.
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
   at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

 

Event Type: Error
Event Source: SharePoint Products and Technologies Configuration Wizard
Event Category: None
Event ID: 100
Date:  24.08.2007
Time:  10:13:48
User:  N/A
Computer: WEB3
Description:
Configuration of SharePoint Products and Technologies failed.  Configuration must be performed in order for this product to operate properly.  To diagnose the problem, review the extended error information located at E:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_8_24_2007_10_9_34_258_1671849275.log, fix the problem, and run this configuration wizard again.

 

So we've got to run the Configuration wizard again...

Started sysinternals procmon and started configuration wizard: that now fails with "Requested registry access is not allowed."...

 

 

I've remembered Soeren Nielsens post at: http://soerennielsen.wordpress.com/2007/06/ - and indeed I've found access denied messages related to certificates and put myself into the two WPG groups...

However, the error running Configuration wizard is still the same...