SharePoint site inaccessible after installing WSS 3.0 and MOSS 2007 Infrastructure Updates

We applied the WSS 3.0 and MOSS 2007 Infrastructure Updates (found here) recently on our SharePoint Server. The "SharePoint Productions and Technologies Configuration Wizard" which needs to be run after these Updates are installed did not complete successfully. It reported the error shown in the screen shot below:





At this point, the SharePoint Portal site was inaccessible. The Central Admin site was still accessible, but not the "user-facing" Portal site.

The SharePoint ULS log contained these errors:

02/27/2009 19:37:11 6 INF Resource retrieved id PostSetupConfigurationFailedEventLog is 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 {0}, fix the problem, and run this configuration wizard again.

02/27/2009 19:37:11 6 ERR 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 C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_2_27_2009_19_9_39_988_1181254095.log, fix the problem, and run this configuration wizard again.

02/27/2009 19:37:11 6 INF Resource retrieved id PostSetupConfigurationFailedUserMessage is Configuration of SharePoint Products and Technologies failed. Configuration must be performed before you use SharePoint Products and Technologies. For further details, see the diagnostic log located at {0} and the application event log.

02/27/2009 19:37:11 6 INF Sending a task driver stop event: TaskDriverEventArgs.EventCriticalityType error, TaskDriverEventArgs.EventType.stop, Configuration of SharePoint Products and Technologies failed. Configuration must be performed before you use SharePoint Products and Technologies. For further details, see the diagnostic log located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\PSCDiagnostics_2_27_2009_19_9_39_988_1181254095.log and the application event log.


The Applciation Event Log reported these errors:

Error 1

Failed to upgrade SharePoint Products and Technologies.
Failed to upgrade SharePoint Products and Technologies. Further information regarding this failure can be found at C:\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()


Error 2

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: (807)
Event ID: 5617
Date: 2/27/2009
Time: 7:58:51 PM
User: N/A
Computer: xxxxxxx

Description:
The schema version (3.1.3.0) of the database WSS_Portal on is not consistent with the expected database schema version (3.1.5.0) on . 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.

Error 2 in the Application Event Log gave me a fighting chance to fix this issue. I learned that I need to run the following stsadm command to upgrade the database schema version. So I ran the following command on the SharePoint Server:

stsadm –o upgrade –inplace –url http://your_site_url_here

This took a few minutes and then reported that the upgrade completed successfully.

I then re-ran the "SharePoint Products and Technologies Configuration Wizard" and this time it completed successfully...no errors. And I was able to access our Portal site again.

This particular stsadm upgrade command is a life-saver.

Be sure to include this awesome command in your SharePoint Survivor toolkit.