Just found out my installing a SharePoint patch in my lab has now fully broken the site and made it unusable. In my case this is a SharePoint 3.0 installation on a Windows 2003 R2 x86 server. Unfortunately this comes at a bad time and who really ever wants something broken by a patch?
So FYI consider laying off installing this patch if you can.
You got a love an explanation that starts off backpedaling some CYA:
"The first thing we want to clarify is how SharePoint 3 updates are being installed. There are two main phases (detailed description <link>) Phase one is the binary deployment, this is where the actual SharePoint files are updated. The second phase is the provisioning of the databases, if for any reason the provisioning doesn’t complete, your sites will be inaccessible. You may see errors similar to the ones mentioned on this blog post “Companyweb Inaccessible After SharePoint 3.0 Service Pack 2”, also, you may see an event with an error mentioning the text “Invalid Signature” or “missing Windows Internal Database signatures.". Almost all of this issues we have seen on this update is phase two failing."
Here’s how my failure of their fix went from my command prompt:
C:\Documents and Settings\dale>C:\Program Files\Common Files\Microsoft Shared\We
b server extensions\12\BIN\psconfig -cmd upgrade -inplace b2b -wait -force
‘C:\Program’ is not recognized as an internal or external command,
operable program or batch file.
;REM note that I had to put quotations around the path for it to work (article incorrectly implied cut and paste were sufficient)
C:\Documents and Settings\dale>"C:\Program Files\Common Files\Microsoft Shared\W
eb server extensions\12\BIN\psconfig" -cmd upgrade -inplace b2b -wait -force
SharePoint Products and Technologies Configuration Wizard version 12.0.6500.5000
Copyright (C) Microsoft Corporation 2005. All rights reserved.
Performing configuration task 1 of 4
Initializing SharePoint Products and Technologies upgrade…
Successfully initialized SharePoint Products and Technologies upgrade.
Performing configuration task 2 of 4
Initiating the upgrade sequence…
Successfully initiated the upgrade sequence.
Performing configuration task 3 of 4
Upgrading SharePoint Products and Technologies…
Failed to upgrade SharePoint Products and Technologies.
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown.
Additional exception information: Upgrade completed with errors. Review the u
pgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Se
rver Extensions\12\Logs\Upgrade.log. The number of errors and warnings is listed
at the end of the upgrade log file.
Total number of configuration settings run: 3
Total number of successful configuration settings: 2
Total number of unsuccessful configuration settings: 1
Successfully stopped the configuration of SharePoint Products and Technologies.
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_6_28_2010_21_14_15_740_7
85893312.log and the application event log.