none
Upgrade Status of Failed - after Installing Dec 2016 CU but build numbers are correct...

    Question

  • All,

    Just installed the Dec 2016 CU cumulative-update-for-sharepoint-server-2013-kb3128005 on one of my farms. The build numbers in Central Admin are correct - but the Upgrade Status shows failed for one of my WFE's and for Central Admin. The error is as such - so what is the best way to remedy as it's odd that the build numbers are correct but the status shows as failed. One of the errors says in the Command Line field: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN\psconfigui.exe  Remedy says "This upgrade session has been stopped. Possible causes include the process being terminated abruptly or the OS has rebooted. Please restart the upgrade again." So when trying this again via a command line as such: psconfigui.exe -cmd upgrade -inplace b2b -wait -force then the status still fails and the Command Line field says "PSConfig.exe -cmd upgrade -inplace b2b -wait -force " Remedy says "This upgrade session has been stopped. Possible causes include the process being terminated abruptly or the OS has rebooted. Please restart the upgrade again."  

    Monday, March 27, 2017 8:29 PM

All replies

  • Hi,

    Please run the command below instead:

    PSCONFIG.EXE -cmd Upgrade -inplace b2b –wait

    If above cannot work, please check the PSCDiagnostics log to get more detailed error message for further research.

    Best Regards,

    Victoria

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Tuesday, March 28, 2017 10:24 AM
    Moderator