*** Short answer to the error is to check “Upgrade.log” in your 12 hive and look for the REAL error behind this message and fix that error, then run config wizard again.

SharePoint 2007 SP2 came out at the end of April as we all know and naturally my client wanted to install it the second it came out.  I managed to be the voice of reason and convinced them to hold off installing it for awhile so that we could do testing of it in their environment, as well as to monitor the SharePoint blogs/forums to see what errors we might be in store for as well as hopefully fixes for those errors.

I finally got around to installing SharePoint 2007 SP2 on the client environment and all went smooth until when I ran the config wizard after the install, the SP2 upgrade died on step 8 of 9 and I got the following error: “The B2B upgrader timer job failed”.  The screen told me to take a look a the upgrade log in the 12 hive.  I opened the log it told me too and got the following error:

05/21/2009 18:49:13  6  ERR                    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()

At first glance I thought that the error really doesn’t tell me anything other than what I obviously already know….I have a F’n error!.  Once I composed myself I read the message again and saw that it was telling me to look at “Upgrade.log” for the real error.  After digging in the file I saw this:

   at Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
   at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o, Boolean bRecurse)
[SPManager] [INFO] [5/21/2009 6:49:01 PM]: Resetting the status of PersistedUpgradableObject: SPWebService Parent=SPFarm Name={DBNAME} to Online.
[SPManager] [ERROR] [5/21/2009 6:49:01 PM]: ReflexiveUpgrade [SPWebService Parent=SPFarm Name={DBNAME}] failed.
[SPManager] [ERROR] [5/21/2009 6:49:01 PM]: Cannot open database "WSS_Content_MSSupport" requested by the login. The login failed.
Login failed for user '{AD}\{USER NAME}'.
[SPManager] [ERROR] [5/21/2009 6:49:01 PM]:    at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()

etc. etc.

Turns out that the error was pretty easy to fix.  The error was telling me that it couldn’t open one of my content databases.  Luckily the farm involved was small and really only had 1 production site, therefore I knew all the content db names and this was one of the content DB’s I had created when working with MS support on an unrelated issue.  The database wasn’t needed anymore and since the client had some pretty tight DB standards in place they had deleted the unneeded DB but I never deleted the web app/site collection that referenced this DB, therefore I got the above error.  So the fix was easy…go into Central Admin, delete the problem web app/site collection referencing the content DB, then run the config wizard again.  After running it this time, it ran through to completion and I was a happy man.  All in all it was about a 45min set back after all the digging and running config wizard.


Posted in:   Tags:
Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2017 Tony Testa's World