When applying WSS3 SP2 to my environment everything at first seemed to go ok until the Configuration Wizard ran. The Configuration Wizard got stuck at task 8 of 9 for over an hour. The Upgrade.log showed the following line over and over: [SPManager] [DEBUG] [6/24/2010 3:20:38 PM]: SyncUpgradeTimerJob: sleeping for 10 seconds Eventually I gave up and tried to cancel the configuration which wouldn't cancel. In desparation I killed the process, rebooted the machine and issued the following command found online: psconfig -cmd upgrade -inplace b2b -wait -force This started to run fine but then returned with the following error: 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 upgrade.log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server 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_24_2010_15_31_17_773_1233930332.log and the application event log. In the log file there are 5 errors all of the following form: [SPManager] [DEBUG] [6/24/2010 3:32:35 PM]: Using cached [SPContentDatabase Name=XXXX Parent=SPDatabaseServiceInstance Name=YYY] NeedsUpgrade value: False. [SPManager] [ERROR] [6/24/2010 3:32:35 PM]: ReflexiveUpgrade [SPContentDatabase Name=XXXX Parent=SPDatabaseServiceInstance Name=YYY] failed. [SPManager] [ERROR] [6/24/2010 3:32:35 PM]: Could not find stored procedure 'proc_LogChange'. [SPManager] [ERROR] [6/24/2010 3:32:35 PM]: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand command, CommandBehavior behavior) at Microsoft.SharePoint.Administration.SPWebApplication.LogSecurityPolicyChange() at Microsoft.SharePoint.Administration.SPWebApplication.Update() at Microsoft.SharePoint.Administration.SPContentDatabase.Upgrade(Boolean recursively) at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse) Central Admin loads okay but I feel the upgrade did not work properly. We are running MOSS SP1 against SQL Server 2008 in on Windows 2003 R2 64 bit. Greatly appreciate any help. Thanks, Raman

Run the Update again: post by Bill Bear : KB934525 Troubleshooting "Cannot start service SPAdmin on computer '.'." , now the answer was not directly found in the post but in the comments section where Chris Fields had the same problem I had. His problem was the following : We noticed that in our from dev and stage farms this message was only logged for a minute or two before the upgrade process proceeded. We also noticed that the upgrade had stopped the sptimerv3 service but we had an automated MOM rule that had restarted it. We simply stopped sptimerv3 for a few minutes then re-started it. Within 5 minutes the upgrade had proceeded passed the sleeping phase and was upgrading databases. It completed successfully. Start the SPAdmin service net start spadmin and after that restart the patch process happily continued and the environment had SP1 on it ;) Post by http://community.zevenseas.com/Blogs/Robin/archive/2008/04/19/syncupgradetimerjob-sleeping-for-10-seconds.aspx -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.

Hi Raman, Please ping back the post and let us know if the issue is resolved.. -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.