We have a four server farm. After laying down the bits for the June 2012 CU on all four servers, our system administrator began to run PSCONFIG on each of the four servers (I know, I know...) None of them ever truly successfully completed.
Now that the damage has been done, PSCONFIG will run to 100% on each of the four servers but "completes with errors" every time. The upgrade logs reveal no specific errors. Sometimes, the failure will be an SPUpgradeConcurrencyException that another upgrade session is in progress and an update conflict occurred.
After completion, Central Administration will show "No action required" for each of the servers on which PSCONFIG has been run, but after a restart, the servers will again show "Upgrade available" as though the CU had never been successfully applied. We have seen other problems in conjunction with this, such as search crawls not running as scheduled even though the timer jobs are there.
In running the STSADM -o localupgradestatus checks, none of the content databases in the farm appear to need upgrading. There are 3 sites that fail the pre-upgrade check, but I am told those are "relics" from the migration from 2007 to 2010, and that previous CUs and SP1 for SharePoint 2010 installed on this farm without any issues.
We are running the following PSCONFIG command:
PSCONFIG.exe -cmd upgrade -inplace b2b -force -wait
Any thoughts on how this environment can be salvaged? Thanks in advance for your help!