August 28, 2008

MOSS: Infrastructure Update for Microsoft Office Servers throws PostSetupConfigurationTaskException

Problem:
After applying Infrastructure Update for Windows SharePoint Services 3.0 (KB951695) and Infrastructure Update for Microsoft Office Servers (KB951297) and trying to run the SharePoint Products and Technologies Configuration Wizard, the wizard stops on task 8 of 9 and gives error message:

An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: Failed to upgrade SharePoint Products and Technologies.

How to start solving:
Looking at the log provided below the error message leads you to PSCDiagnostics file, but that file doesn't really contain any good error messages. However, it mentions that you should look at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\Upgrade.log for further information regarding the failure.

Looking at Upgrade.log tells us what the problem is.

Error 1:
The access control list on C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\template\layouts\web.config could not be modified because the path could not be located in the file system.

Solution 1:
Trying to locate the web.config file quickly reveals the real cause of the problem: there is no such file in that folder. Reasons for that are (again) unknown at least to me, but copying that file from another SharePoint 2007 installation to the correct folder and restarting the Configuration Wizard should get you around this issue.

If the file exists, you may want to verify that the syntax of web.config is valid.

NOTE! There are several other possibilities for PostSetupConfigurationTaskException, so please post your errors and solutions here and I keep updating the article. Thanks!

15 comments:

  1. Ok so I'm getting the same error, but That file exsists... now what ...

    Cheers

    ReplyDelete
  2. Hey Dan,
    The upgrade could fail for a number of reasons. In my case there were some question marks all over the web.config.
    Don't know how they got there. but after I replaced with the correct character everything went fine.

    You have to read the upgrade.log file for the first occurrence of some kind of failure and go on from there.

    That's what did it in my case.

    ReplyDelete
  3. Thank you Robert for your input!

    ReplyDelete
  4. I have the web.config file in that location, and I get this error on both servers in farm [SPManager] [ERROR] [2008-12-16 21:47:25]: at Microsoft.SharePoint.Library.SPRequestInternalClass.GetSiteQuota(String bstrUrl, UInt16& pdwQuotaTemplateID, Int64& plDiskQuota, Int64& plDiskWarning, Int32& plUserQuota)
    at Microsoft.SharePoint.Library.SPRequest.GetSiteQuota(String bstrUrl, UInt16& pdwQuotaTemplateID, Int64& plDiskQuota, Int64& plDiskWarning, Int32& plUserQuota)
    [SPManager] [ERROR] [2008-12-16 21:47:25]: at Microsoft.SharePoint.Library.SPRequest.GetSiteQuota(String bstrUrl, UInt16& pdwQuotaTemplateID, Int64& plDiskQuota, Int64& plDiskWarning, Int32& plUserQuota)
    at Microsoft.SharePoint.Administration.SPQuota..ctor(SPSite site)
    at Microsoft.SharePoint.SPSite.get_Quota()
    at Microsoft.SharePoint.Upgrade.SPSiteSequence.PreUpgrade()
    at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)

    ReplyDelete
  5. Do you have custom Quota Templates on the sites that might not be working or are causing some issues?

    ReplyDelete
  6. I get this error
    [SharedServiceDatabaseSequence] [ERROR] [2009-02-10 16:32:12]: Upgrade object too new (build version = 12.0.6219.1000, schema version = 12.0.1.0). Current server (build version = 12.0.4518.1016, schema version = 12.0.1.0).
    [SPManager] [ERROR] [2009-02-10 16:32:12]: CanUpgrade [SharedDatabase Name=MOSS2007_DPWEB_SSP_Content Parent=SPDatabaseServiceInstance Name=datapolissql] failed.

    ReplyDelete
  7. You absolute legend. Thanks so much. Why the heck the web.config wouldn't exist on one server is beyond me but a simple file copy from my app server to my wfe server fixed the issue.

    ReplyDelete
  8. I'm getting an access denied error. To what, I wonder... any thoughts?

    [SPManager] [ERROR] [2/24/2009 3:31:27 PM]: Grow [SPTree Value=SPWebApplication Name=Portal Parent=SPWebService] failed.
    [SPManager] [ERROR] [2/24/2009 3:31:27 PM]: Access is denied.
    [SPManager] [ERROR] [2/24/2009 3:31:27 PM]: at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
    at System.DirectoryServices.DirectoryEntry.Bind()
    at System.DirectoryServices.DirectoryEntry.get_IsContainer()
    at System.DirectoryServices.DirectoryEntries.ChildEnumerator..ctor(DirectoryEntry container)
    at System.DirectoryServices.DirectoryEntries.GetEnumerator()
    at Microsoft.SharePoint.Administration.SPIisWebSite.LookupByServerComment(String serverComment, Int32& instanceId)
    at Microsoft.SharePoint.Administration.SPWebApplication.GetLocalIisWebSites()
    at Microsoft.SharePoint.Upgrade.SPWebApplicationSequence.AddNextLevelObjects()
    at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, Boolean bRecursing)
    at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root)
    at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse)

    ReplyDelete
  9. I am getting following error... please any resolution???

    04/08/2009 16:29:22 7 ERR Task initialize has failed
    04/08/2009 16:29:22 7 INF friendlyMessage for task initialize is An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: Unable to upgrade SharePoint Products and Technologies because an upgrade is already in progress. Upgrade progress can be monitored using the Central Administration Web Application or by monitoring the upgrade log on server [Machine Name].
    04/08/2009 16:29:22 7 INF debugMessage for task initialize is An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: Unable to upgrade SharePoint Products and Technologies because an upgrade is already in progress. Upgrade progress can be monitored using the Central Administration Web Application or by monitoring the upgrade log on server [Machine Name].
    Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException: Exception of type 'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
    at Microsoft.SharePoint.PostSetupConfiguration.TaskCommon.CheckIfUpgrading(TaskBase task)
    at Microsoft.SharePoint.PostSetupConfiguration.InitializeTask.Run()
    at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

    ReplyDelete
  10. Sanjay: have you tried to run "stsadm -o upgrade -url http://servername" and ater that, run the Wizard again?

    ReplyDelete
  11. thanks but I think i have a different case bt same result :(
    I upgraded an SPS2003 installation to MOSS 2007 SP1 (small farm, 1 sharepoint server, 1 database server). Then I tried to install the infrastructure update, worked for wss but failed for MOSS (on step 8 and 9 too) with the same error. Tried to restart (about 6 times) but no luck( i was using a domain schema enterprise administrator so that security should not be an issue :D )
    Now I am stuck, strangely though all new links for search administration, portal and central administration are working (at least that is what is appearing, no errors in eventvwr). But i am annoyed with the inability to complete the upgrade. Any tips?plz????

    ReplyDelete
  12. You are my Sharepoint idol. Thanks a lot ...

    ReplyDelete
  13. Thanks it is a fantastic help, now to code is without a doubt simple and easy with your advice. Thank you

    ReplyDelete
  14. I am facing issue same as Paul...any idea?

    ReplyDelete