none
Configuration Wizard fails on KB2589280/MS12-066

    Question

  • I've been fighting with this patch off and on for a few weeks. A little background, this is a multi-server developement teir farm recently upgraded from 2007 via database upgrades. This is not the first patch that has been installed since the upgrade but it is the first that is failing. I've tried disabling AV, running via psconfig, restarting admin/timer services. I've verified and corrected DCOM security settings http://www.ericjochens.com/2013/06/sharepoint-server-eventid-10016-dcom.html

    I'm not seeing anything in the SQL logs or the eventlogs of consequence.

    As the patch runs I get a series of (15 or so) "patchca not found. Falling back" errors EventID 999p in the trace logs.

    I see this prior to that and am unsure if it's related: "The health rule contained in Microsoft.Office.InfoPath.Server.Util.InfoPathStateServiceConfigurationHealthRule could not be registered. A file with the name InfoPath Forms Services forms cannot be filled out in a Web browser because no State Service connection is configured. already exists. It was last modified by ********* on 1/23/2013 2:46 AM."

    In the SharePoint error logs themselves I see loads of warnings about missing features but it skips through those, I see several of the below errors, this is from one web app, it will repeat the errors for all the web applications: [PSCONFIG] [CmsImageLibrarySiteAction (13.0.16.0)] [ERROR] [7/19/2013 9:53:40 AM]: at Microsoft.SharePoint.Publishing.AssetLibrary.AddNewViews(SPDocumentLibrary docLib, SPLog log) at Microsoft.SharePoint.Publishing.AssetLibrary.UpgradeDocumentLibrary(SPDocumentLibrary docLib, Boolean addViews, Boolean accessFileStreams, SPLog log) at Microsoft.SharePoint.Publishing.Internal.Upgrade.CmsVersionToVersionImageLibraryUpgradeAction.UpgradePublishingSite(SPSite site) [PSCONFIG] [MossSiteSequence] [INFO] [7/19/2013 9:53:40 AM]: SPSite Url=http://************************ [PSCONFIG] [MossSiteSequence] [ERROR] [7/19/2013 9:53:40 AM]: Action 13.0.16.0 of Microsoft.SharePoint.Portal.Upgrade.MossSiteSequence failed. [PSCONFIG] [MossSiteSequence] [INFO] [7/19/2013 9:53:40 AM]: SPSite Url=http://************************ [PSCONFIG] [MossSiteSequence] [ERROR] [7/19/2013 9:53:40 AM]: Exception: Could not load type 'Microsoft.SharePoint.SPViewToolbarType' from assembly 'Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'. [PSCONFIG] [MossSiteSequence] [INFO] [7/19/2013 9:53:40 AM]: SPSite Url=http://************************ [PSCONFIG] [MossSiteSequence] [ERROR] [7/19/2013 9:53:40 AM]: at Microsoft.SharePoint.Publishing.AssetLibrary.AddNewViews(SPDocumentLibrary docLib, SPLog log) at Microsoft.SharePoint.Publishing.AssetLibrary.UpgradeDocumentLibrary(SPDocumentLibrary docLib, Boolean addViews, Boolean accessFileStreams, SPLog log) at Microsoft.SharePoint.Publishing.Internal.Upgrade.CmsVersionToVersionImageLibraryUpgradeAction.UpgradePublishingSite(SPSite site) at Microsoft.SharePoint.Publishing.Internal.Upgrade.BaseUpgradeAction.Upgrade(Boolean siteCollectionOnly) at Microsoft.SharePoint.Portal.Upgrade.CmsImageLibrarySiteAction.Upgrade() at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade() [PSCONFIG] [SPUpgradeSession] [INFO] [7/19/2013 9:53:40 AM]: SPSite Url=http://************************ [PSCONFIG] [SPUpgradeSession] [ERROR] [7/19/2013 9:53:40 AM]: Upgrade [SPSite Url=http://************************] failed. Microsoft.SharePoint.Portal.Upgrade.MossSiteSequence has the ContinueOnFailiure bit set. Moving on to the next object in sequence. [PSCONFIG] [SPUpgradeSession] [INFO] [7/19/2013 9:53:40 AM]: SPSite Url=http://************************ [PSCONFIG] [SPUpgradeSession] [ERROR] [7/19/2013 9:53:40 AM]: Inner Exception: Could not load type 'Microsoft.SharePoint.SPViewToolbarType' from assembly 'Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c'. [PSCONFIG] [SPUpgradeSession] [INFO] [7/19/2013 9:53:40 AM]: SPSite Url=http://************************ [PSCONFIG] [SPUpgradeSession] [ERROR] [7/19/2013 9:53:40 AM]: at Microsoft.SharePoint.Publishing.AssetLibrary.AddNewViews(SPDocumentLibrary docLib, SPLog log) at Microsoft.SharePoint.Publishing.AssetLibrary.UpgradeDocumentLibrary(SPDocumentLibrary docLib, Boolean addViews, Boolean accessFileStreams, SPLog log) at Microsoft.SharePoint.Publishing.Internal.Upgrade.CmsVersionToVersionImageLibraryUpgradeAction.UpgradePublishingSite(SPSite site) at Microsoft.SharePoint.Publishing.Internal.Upgrade.BaseUpgradeAction.Upgrade(Boolean siteCollectionOnly) at Microsoft.SharePoint.Portal.Upgrade.CmsImageLibrarySiteAction.Upgrade() at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade() [PSCONFIG] [SPUpgradeSession] [INFO] [7/19/2013 9:53:40 AM]: SPSite Url=http://************************ [PSCONFIG] [SPUpgradeSession] [ERROR] [7/19/2013 9:53:40 AM]: Exception: Action 13.0.16.0 of Microsoft.SharePoint.Portal.Upgrade.MossSiteSequence failed. [PSCONFIG] [SPUpgradeSession] [INFO] [7/19/2013 9:53:40 AM]: SPSite Url=http://************************ [PSCONFIG] [SPUpgradeSession] [ERROR] [7/19/2013 9:53:40 AM]: at Microsoft.SharePoint.Upgrade.SPActionSequence.Upgrade() at Microsoft.SharePoint.Upgrade.SPUpgradeSession.Upgrade(Object o, Boolean bRecurse) Any ideas?????


    
    Friday, July 19, 2013 5:23 PM

Answers

  • Hi WinSysAdm,

    thank you for the result,

    perhaps you may try to disable the publishing feature at the sharepoint first then you try to upgrade again?

    I talked with my colleague regarding this, seems from the error code, there was something with publishing feature, and if stop/disable the publishing feature the issue still persist, I suggest you to open a case to check the code and the feature that was not able to be accessed by administrator permission.


    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


    • Edited by Aries - MSFT Tuesday, July 23, 2013 3:47 AM typo
    • Marked as answer by WinSysAdm Tuesday, July 23, 2013 8:40 PM
    Tuesday, July 23, 2013 3:44 AM

All replies

  • What is the current farm patch level?

    (Get-SPFarm).BuildVersion

    The InfoPath error is just due to a State Service not having been provisioned and won't have anything to do with your patching error.


    Trevor Seward, MCC

    Follow or contact me at...
      

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, July 19, 2013 5:56 PM
  • 14.0.6029.1000
    Friday, July 19, 2013 6:52 PM
  • Hi,

    Thank you for your question. I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience. Thank you for your understanding and support.

    Thanks,

    Entan Ming


    Entan Ming
    TechNet Community Support

    Monday, July 22, 2013 7:47 AM
  • Hi WinSysAdm,

    please have a try to clean up the cache.ini method, then re-do the config, for the first step.

    if you already did this, then try to open the sharepoint command shell and select "run As Admin.." option, 

    to run the psconfig from the command shell: PSConfig.exe -cmd upgrade -inplace b2b -force

    if the issue persist please have a try to run at the sharepoint command shell: Get-SPProduct –local



    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Monday, July 22, 2013 9:28 AM
  • I thought I had tried clearing the cache when this first popped up but I went ahead and did it again on all the servers in the farm. After it finished rebuilding I tried the command you posted running as administrator (previously I had been using the -wait switch as well).

    I got the same set of errors with the "patchca not found. Falling back" in the ULS log just before it failed.

    Here's the output from the Get-SPProduct -local

    Microsoft SharePoint Server... True {}

    Microsoft® Office Web Apps True {}

    Monday, July 22, 2013 4:48 PM
  • Hi WinSysAdm,

    thank you for the result,

    perhaps you may try to disable the publishing feature at the sharepoint first then you try to upgrade again?

    I talked with my colleague regarding this, seems from the error code, there was something with publishing feature, and if stop/disable the publishing feature the issue still persist, I suggest you to open a case to check the code and the feature that was not able to be accessed by administrator permission.


    Regards,
    Aries
    Microsoft Online Community Support


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


    • Edited by Aries - MSFT Tuesday, July 23, 2013 3:47 AM typo
    • Marked as answer by WinSysAdm Tuesday, July 23, 2013 8:40 PM
    Tuesday, July 23, 2013 3:44 AM
  • Aries, you are my hero!

    I found this simple powershell script to run through and deactivate the Publishing feature on all site collections in a web app (I have a lot):

    How to: Activate a feature on multiple site collections using PowerShell

    Once it finished I tried the update again and it finished!!!!  I was able to reactivate the feature and finish the patch still ran successfully on all the other servers in the farm.  Thank you so much for your help!

    Tuesday, July 23, 2013 8:40 PM