none
Upgrade Session Failed @ 100% Complete?

    Question

  • So..I might have an issue with my recent installation of the March 2013 CU for SP2013.  Although everything appears to be functional - all sites and services (so far at least) work as they did before - I do have a disturbing updgrade session status = Failed on all my farm servers.

    Farm Configuration

    • 2 web front-ends
    • 1 app server
    • 1 SQL server

    What I did:

    • Logged in as my farm setup account and installed the update using the script here http://blogs.msdn.com/b/russmax/archive/2013/04/01/why-sharepoint-2013-cumulative-update-takes-5-hours-to-install.aspx on the app and web servers.
    • This step seemed to complete w/o issue and all systems show version 15.0.4481.1005 in "Manage Patch Status"
    • After this step, "Manage Database Upgrade Status" in CA showed upgrades needed on most DBs.
    • Removed the WFEs from service and ran the SP Configuration Wizard on the APP server.
    • Upgrade on first APP server seemed to fail so I restarted the box and ran it again.  Configuration seemed to complete and CA was available again. 
    • At this time, all DBs in "Manage Database Upgrade Status" showed "No action required"
    • Repeated on both WFE's with the same results.

    What I see now:

    • Everything appears to work.
    • "Manage Patch Status" shows all servers at same version, 15.0.4481.1005.
    • "Managed Database Status" reports "No action Required" on all DBs.
    • "Check Upgrade Status" shows Failed but 100% Complete on all systems with 8 Errors.
    • ULS Logs show the same 8 ERROR lines on all 3 systems:

    ULS Logs

    Timestamp               Process                                  TID    Area                           Category                       EventID Level      Message  Correlation
    11/17/2013 19:12:31.14  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:12:31.14  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      Exception: The system cannot find the path specified.  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:12:31.15  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)     at System.DirectoryServices.DirectoryEntry.Bind()     at System.DirectoryServices.DirectoryEntry.get_AdsObject()     at System.DirectoryServices.PropertyValueCollection.PopulateList()     at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)     at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)     at Microsoft.SharePoint.Administration.SPIisVirtualDirectory.get_Path()     at Microsoft.SharePoint.Administration.SPProvisioningAssistant.GetBuildVersionOnIisWebSite(Int32 iisInstanceId)     at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:12:31.15  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxnf    ERROR      Cannot upgrade [Microsoft.SharePoint.Administration.SPIisWebSite].  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:13:52.84  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:13:52.93  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      Exception: The system cannot find the path specified.  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:13:52.96  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)     at System.DirectoryServices.DirectoryEntry.Bind()     at System.DirectoryServices.DirectoryEntry.get_AdsObject()     at System.DirectoryServices.PropertyValueCollection.PopulateList()     at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)     at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)     at Microsoft.SharePoint.Administration.SPIisVirtualDirectory.get_Path()     at Microsoft.SharePoint.Administration.SPProvisioningAssistant.GetBuildVersionOnIisWebSite(Int32 iisInstanceId)     at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:13:53.10  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               aj0ur    ERROR      Upgrade Timer job is exiting due to exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS\Upgrade-20131117-190950-531.log.  The number of errors and warnings is listed at the end of the upgrade log file.     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()     at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId)  08af579c-d49a-a0ca-455b-06fbcb2f76bb

    Is there something actually awyr here??

    Thanks heaps!

    Brian


    Brian

    Monday, November 18, 2013 7:16 PM

Answers

  • Hi Brian,

    From the below error it clearly states that SharePoint PSconfig is not able to find the IIS web site:

    11/17/2013 19:12:31.14  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:12:31.14  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      Exception: The system cannot find the path specified.  08af579c-d49a-a0ca-455b-06fbcb2f76bb


    11/17/2013 19:12:31.15  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)     at System.DirectoryServices.DirectoryEntry.Bind()     at System.DirectoryServices.DirectoryEntry.get_AdsObject()     at System.DirectoryServices.PropertyValueCollection.PopulateList()     at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)     at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)     at Microsoft.SharePoint.Administration.SPIisVirtualDirectory.get_Path()     at Microsoft.SharePoint.Administration.SPProvisioningAssistant.GetBuildVersionOnIisWebSite(Int32 iisInstanceId)     at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)  08af579c-d49a-a0ca-455b-06fbcb2f76bb

    You may have extended any of your SharePoint web application and then it maight have been removed from IIS and SharePoint still has referrence of the site and hence while running PSConfig it is looking for that IIS site and as it is not available in IIS it is giving above exception.

    Steps to Resolve:
    -----------------------------------

    Open Central Admin - Manage Web Applications - Select web application - Click on Delete Drop Down (Do not click on Delete Button) - Select Remove SharePoint from IIS Web site - Click following drop down - Remove SharePoint from IIS - Select IIS web site and zone to remove - Check if you see any web site which is not present in IIS - If you see any web site which is not under IIS then just select that and remove it from SharePoint.

    Note:- Follow above steps on all SharePoint web servers.

    Once above steps are done you can again run the PSConfig upgrade wizard and it should be successfull.

    Upgrade command: psconfig.exe -cmd upgrade -inplace b2b -wait -force


    Regards,
    Bhavik Jain

    Tuesday, November 19, 2013 3:49 AM

All replies

  • So..I might have an issue with my recent installation of the March 2013 CU for SP2013.  Although everything appears to be functional - all sites and services (so far at least) work as they did before - I do have a disturbing updgrade session status = Failed on all my farm servers.

    Farm Configuration

    • 2 web front-ends
    • 1 app server
    • 1 SQL server

    What I did


    Brian

    Monday, November 18, 2013 6:57 PM
  • could you please sharepoint upgrade log, and any error you see on the screen, 

    what about the db status on central admin?


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

    Monday, November 18, 2013 7:00 PM
    Moderator
  • AARRG....the forum double-posted me...

    http://social.technet.microsoft.com/Forums/en-US/f6f30ede-b614-4773-be98-0c9fac29ca37/upgrade-session-failed-100-complete?forum=sharepointadmin

    But...here's the nitty gritty on the logs:

    Timestamp               Process                                  TID    Area                           Category                       EventID Level      Message  Correlation
    11/17/2013 19:12:31.14  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:12:31.14  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      Exception: The system cannot find the path specified.  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:12:31.15  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)     at System.DirectoryServices.DirectoryEntry.Bind()     at System.DirectoryServices.DirectoryEntry.get_AdsObject()     at System.DirectoryServices.PropertyValueCollection.PopulateList()     at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)     at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)     at Microsoft.SharePoint.Administration.SPIisVirtualDirectory.get_Path()     at Microsoft.SharePoint.Administration.SPProvisioningAssistant.GetBuildVersionOnIisWebSite(Int32 iisInstanceId)     at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:12:31.15  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxnf    ERROR      Cannot upgrade [Microsoft.SharePoint.Administration.SPIisWebSite].  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:13:52.84  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:13:52.93  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      Exception: The system cannot find the path specified.  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:13:52.96  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)     at System.DirectoryServices.DirectoryEntry.Bind()     at System.DirectoryServices.DirectoryEntry.get_AdsObject()     at System.DirectoryServices.PropertyValueCollection.PopulateList()     at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)     at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)     at Microsoft.SharePoint.Administration.SPIisVirtualDirectory.get_Path()     at Microsoft.SharePoint.Administration.SPProvisioningAssistant.GetBuildVersionOnIisWebSite(Int32 iisInstanceId)     at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:13:53.10  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               aj0ur    ERROR      Upgrade Timer job is exiting due to exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS\Upgrade-20131117-190950-531.log.  The number of errors and warnings is listed at the end of the upgrade log file.     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()     at Microsoft.SharePoint.Administration.SPUpgradeJobDefinition.Execute(Guid targetInstanceId)  08af579c-d49a-a0ca-455b-06fbcb2f76bb


    Brian

    Monday, November 18, 2013 7:18 PM
  • Looks like there was an error getting a virtual directory in IIS.  You can re-run the Config Wizard to see if it goes through without throwing an 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.

    Monday, November 18, 2013 7:19 PM
    Moderator
  • Howdy Trevor and thanks for the reply....

    I did, and it did seem to complete but on the second attempt it (the SP2013 Products Configuration Wizard) didn't mention anything about DB upgrades, simply offering up a 'repair your SP' dialogue.  Is there something to do to trigger the specific upgrade bit after a failure of first-run-after-CU-installation??

    I suspect I'm OK though I've also noticed a new failure with the userprofileimportjob in the Application log of the APP server:

    The Execute method of job definition Microsoft.Office.Server.UserProfiles.UserProfileImportJob (ID aa746fc3-6b41-4b86-9656-5f9cf4e20fb9) threw an exception. More information is included below.

    Generic failure


    Brian

    Monday, November 18, 2013 8:39 PM
  • You can run the config wizard at any time, just re-run it to completion.

    You'll want to take a look at the ULS logs for your User Profile Import 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.

    Monday, November 18, 2013 8:55 PM
    Moderator
  • did you see this one, talking about the default website, make sure your default website is their on all servers.

    http://blogs.technet.com/b/sushrao/archive/2011/12/02/exception-the-system-cannot-find-the-path-specified.aspx

    also check this one 

    http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2012/01/09/CanUpgrade-_5B00_Microsoft.SharePoint.Administration.SPIisWebSite_5D00_-failed_2E00_.aspx


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog


    Monday, November 18, 2013 9:33 PM
    Moderator
  • Hi Brian,

    From the below error it clearly states that SharePoint PSconfig is not able to find the IIS web site:

    11/17/2013 19:12:31.14  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      CanUpgrade [Microsoft.SharePoint.Administration.SPIisWebSite] failed.  08af579c-d49a-a0ca-455b-06fbcb2f76bb
    11/17/2013 19:12:31.14  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      Exception: The system cannot find the path specified.  08af579c-d49a-a0ca-455b-06fbcb2f76bb


    11/17/2013 19:12:31.15  OWSTIMER (0x0880)                        0x0970 SharePoint Foundation Upgrade  SPUpgradeSession               ajxme    ERROR      at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)     at System.DirectoryServices.DirectoryEntry.Bind()     at System.DirectoryServices.DirectoryEntry.get_AdsObject()     at System.DirectoryServices.PropertyValueCollection.PopulateList()     at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)     at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)     at Microsoft.SharePoint.Administration.SPIisVirtualDirectory.get_Path()     at Microsoft.SharePoint.Administration.SPProvisioningAssistant.GetBuildVersionOnIisWebSite(Int32 iisInstanceId)     at Microsoft.SharePoint.Upgrade.SPSequence.get_CanUpgrade()     at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CanUpgrade(Object o)  08af579c-d49a-a0ca-455b-06fbcb2f76bb

    You may have extended any of your SharePoint web application and then it maight have been removed from IIS and SharePoint still has referrence of the site and hence while running PSConfig it is looking for that IIS site and as it is not available in IIS it is giving above exception.

    Steps to Resolve:
    -----------------------------------

    Open Central Admin - Manage Web Applications - Select web application - Click on Delete Drop Down (Do not click on Delete Button) - Select Remove SharePoint from IIS Web site - Click following drop down - Remove SharePoint from IIS - Select IIS web site and zone to remove - Check if you see any web site which is not present in IIS - If you see any web site which is not under IIS then just select that and remove it from SharePoint.

    Note:- Follow above steps on all SharePoint web servers.

    Once above steps are done you can again run the PSConfig upgrade wizard and it should be successfull.

    Upgrade command: psconfig.exe -cmd upgrade -inplace b2b -wait -force


    Regards,
    Bhavik Jain

    Tuesday, November 19, 2013 3:49 AM
  • Bhavik, please do not propose your own answers on this forum.  Let the original poster or other posters do that.

    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.

    Tuesday, November 19, 2013 3:54 AM
    Moderator
  • I think this has it fixed!

    To the best of my now jogged memory, once upon a time, before we introduced a HW loadbalancer I'd made SP do it's own re-directs so had extended one of the web apps for SSL...apparently I'd cleaned up the sites but not the extend in SP...

    Thank you very much sir - all my upgrade status looks 'green and clean' now...so...on to the newest CU now that the March one seems to be safely in place.

    Thanks again to everyone for all their help and advice!

    b


    Brian

    Tuesday, November 19, 2013 10:32 PM