After running the SP2 on 3 development servers I started installing it on the production & authoring server farms tonight. Production went without a problem but naturally the more critical Authoring environment failed on me. I'm not very accomplished at reading the logs and could use some help. KB954713 walks you through checking the errors. First it has you look in Opatchinstall() for occurences of sys.proc.result to find the error codes. Problem is I saw every single code they list in the site in the log. There were about 40 references spaced throughout the log. For example. OPatchInstall: CAction::CreateActionFromElement started OPatchInstall: Creating CActionSetProperty OPatchInstall: CActionSetProperty::initFromElement starts OPatchInstall: Will set the property 'SYS.PROC.RESULT' to value '17021' OPatchInstall: CActionSetProperty::initFromElement ends Then it has you look in the ####_MSPLOG files. In here I found an error (3010) at the end that claims the install succeeded but tried to reboot. MSI (s) (54:B0) [19:20:03:090]: Product: Microsoft Windows SharePoint Services 3.0 -- Configuration completed successfully. MSI (s) (54:B0) [19:20:03:090]: The Windows Installer initiated a system restart to complete or continue the configuration of 'Microsoft Windows SharePoint Services 3.0'. MSI (s) (54:B0) [19:20:03:090]: Attempting to delete file C:\WINDOWS\Installer\17f3e88.msp MSI (s) (54:B0) [19:20:03:090]: Unable to delete the file. LastError = 32 MSI (s) (54:B0) [19:20:03:105]: Cleaning up uninstalled install packages, if any exist MSI (s) (54:B0) [19:20:03:105]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\17f3e88.msp' MSI (s) (54:B0) [19:20:03:105]: MainEngineThread is returning 3010 MSI (s) (54:C4) [19:20:03:105]: Destroying RemoteAPI object. MSI (s) (54:50) [19:20:03:105]: Custom Action Manager thread ending. === Logging stopped: 5/18/2010 19:20:03 === MSI (c) (60:14) [19:20:03:121]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (60:14) [19:20:03:137]: MainEngineThread is returning 3010 === Verbose logging stopped: 5/18/2010 19:20:03 === So do I have 40 something errors or did the install succeed except for a reboot (none of the other servers rebooted or recieved notices to do so)? Central Admin and the sites all load and I see that the server (single server farm) version number is .6421. If it is the reboot do I need to run the SP again after rebooting? (I'm not thrilled with finishing on the error message) I'm out of my depth here a bit and really could use some help.

Thanks for the reply. While looking through the event log I found another log referenced, the "uppgrade.log". Great name. In this log an error comes up that one of the web apps' web.config can't be found. Looking at the server I see that is correct, it is an old dev site from about 2 years ago and there is no sign of the web.config. I'm thinking if I get rid of this site and run it again I may have more luck. I'm hesitant to try to delete a site though in the middle of this process, since the event log says the CA connection db has been blocked to avoid data loss. Can I simply paste in a web.config from one of the other sites on the server, or perhaps stop the site in IIS? [SPIisWebSiteWssSequence] [ERROR] [5/18/2010 7:27:34 PM]: Action 3.0.5.0 of Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence failed. [SPIisWebSiteWssSequence] [ERROR] [5/18/2010 7:27:34 PM]: The access control list on C:\Inetpub\wwwroot\wss\VirtualDirectories\98\web.config could not be modified because the path could not be located in the file system. [SPIisWebSiteWssSequence] [ERROR] [5/18/2010 7:27:34 PM]: at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ResetAcl(FileSystemInfo fi, Boolean append)