PSConfig Fails with Missing / Required Error Message After Applying CU or Service Pack in SharePoint 2010

I had this happen with a CU recently, and I saw someone that had the same problem with SP1.  You download and install some patch – a CU or service pack.  The final step after installation is to run psconfig on each server in the farm.  However, psconfig tells you that it can’t proceed because one or more of the servers are missing a required patch.  It shows the server name, the patch name, and it says “Missing/Required”.  The thing it says is missing though is the exact patch you just got done installing.  Frustrating, yes?

Fortunately, Sam from the UK Premier Field Engineering team had a work-around that fixed it for me, so I’m sharing it here on his behalf in the hopes that it will help you.  Try running the command Get-SPProduct –local on the server that says it’s missing the required patch.  Doing so forces a timer job to run that does some version fix up.  This solved the problem for me; hope it helps you if you find yourself in this position.

15 thoughts on “PSConfig Fails with Missing / Required Error Message After Applying CU or Service Pack in SharePoint 2010

  1. Get-SPProduct –local did not work for us. Then we checked Services and started all the SP Services that were stopped by the update. Then in IIS we had to Start several SP application pool. Then the command worked! 🙂


  2. I have just received this error two days ago on one of my prod. 4 front-end web servers. it was related to SP2 (KB2687453). and your suggestion was very helpful.


  3. Here’s a workaround / fix Ive used to resolve this issue. Many times.
    Also, restarts may be required before PSConfig reports everything is ok.. You might think you installed something, yet it gets reported as not there until reboot, you may need to run OPUtil more than once for same reason.

    1) Copy the installer cache from one of your ‘good’ servers in the farm to a temp directory on the ‘bad’ server. (c:\temp\installercachebackup for example)

    2) Get the OpUtil.vbs script referenced in the post and put it in the installer cache on the bad server:
    OpUtil.vbs is an internal Microsoft Support tool: (rename -.txt)

    3) Open a command prompt local to c:\windows\installer and run the script. For example using the directory referenced above:
    oputil.vbs /RepairCache /srestorelocation=c:\temp\installercachebackup
    and / or
    oputil.vbs /ApplyPatch /SUpdateLocation=d:\stage\installerfiles

    This will take the files (MSI files for the most part) from the good config cache that you backed up and transform them to be valid for the bad server.
    The config cache is unique to each machine based on values in the registry, so you can’t just copy the cache from one server to another. The script does what you need to line everything back up.

    4) In the SharePoint 2010 Management Shell (powershell) run:
    Get-SPProduct -Local

    This will update the SP Farm Configuration Database with the patch chain on the bad server. You will now see PSConfig return a valid status when going through the initial screens as well as seeing a good install status on the ‘Manage Patch Status’ screen in Central Admin (/_admin/PatchStatus.aspx)

    5) Re-run the Sharepoint Products Configuration Wizard (not the CA Farm config Wizard) or PSConfig.exe -cmd upgrade -inplace b2b -wait -force from the SP management console.
    This should be all you need to do, but in my ewxperience Ive sometimes had to troubleshoot further…

    Further troubleshooting Config wizard issues:

    Description of issue:
    – The psconfig wizard freezes at 10% in the upgrade (you need the “-wait” switch in your psconfig – as seen in step 5)
    – The psconfig wizard fails with an SPUpdatedConcurrencyException error (this is included in steps 3 and 4 below)
    – EndpointNotFoundException error (the net stop/start steps needed “w3svc” in there as well – as seen in steps 1 and 6)
    (Note: run all PowerShell (PS) commands in an elevated PowerShell window – *may need 2 pre-opened windows*)

    – Turn off all the following services (you can do this in your first PowerShell window)
    net stop SPTraceV4; net stop SPWriterV4; net stop SPAdminV4; net stop SPTimerV4; net stop w3svc

    – Manually stop both search services (in the services GUI on the SP server) – Note: SP 2010 only has 1 Search Service.
    Run the following command in your second PowerShell window
    stsadm -o setproperty -pn command-line-upgrade-running -pv No

    – Flush the Config Cache

    – Run the following PowerShell in your second PowerShell window
    PSConfig.exe -cmd upgrade -inplace b2b -wait -force
    As soon as it reaches step #3 in the upgrade process, in the first elevated PS window, run the following PS
    net start SPTraceV4; net start SPWriterV4; net start SPAdminV4; net start SPTimerV4; net start w3svc
    Quickly manually start the two search services (in the Services GUI on the SP Server)
    The upgrade process should complete successfully after this.

    Other things you may have to do, unlikely, but you never know.. (don’t do these during the procedure – if the above doesn’t work, try these afterwards and repeat the procedure above):
    -CHECK DB alias is on all servers (cliconfg.exe)
    -Restart IIS or Reboot the server
    -Deal with SQL exception 297 (if it appears) in the event log
    -Grant access to DOMAIN\SERVERNAME$ and NT AUTHORITY\Network Service (sysadmin?) in SQL Server
    – check the DB status for “not responding”


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s