Recently I had a problem in a farm I was deploying, everything was fine, but when I tried to see “servers in this farm” option I could see that one of the servers has the state as “Upgrade Required”. At first instance I thought, ok I have installed the same CU in all the servers, but in this one I am having some problems, I will try to reboot the server and check it again.
So, I rebooted the server and I checked it again, for my surprise, it was stuck in the same state as before. So, I tried the next option, run the SharePoint configuration wizard. I run the configuration wizard, and it showed an error while upgrading the server… the thing started to become weird… I checked the log file, expecting to find something that points me with the solution, but nothing…
Thus, I fired my next bullet which was PowerShell, I opened the shell and executed the following: Get-SpProduct -local expecting that probably it will show me that a CU or LP was missing or something like that, but still no luck 😦
I tried by PS and I was receiving the following error:
“An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown. Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20160429-101200-949 was updated by MYDOMAINspinstall, in the PSCONFIG (3540) process, on machine SERVER1. View the tracing log for more information about the conflict.”
So, what was happening? I tried my last chance which was to clean the SharePoint cache and try another time with PS. So I clean the cache (if yo don’t know how to do it, I have a post about it), and then I run the following:
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures