Pages

Monday, October 1, 2012

SharePoint Cumulative Update: Missing Patches on the Server

So you installed the SharePoint 2010 Cumulative Updates from the Microsoft TechNet site on every server of your farm. Next, you run the SharePoint Products Configuration Wizard and it seems to be working fine and you start getting optimistic when it tells you that the farm is being upgraded in the Timer Service process. All of a sudden, you get a message saying “Configuration was failed”. You close the SharePoint Configuration Wizard and start it again and at this time, it complains that it couldn’t find the hotfixes on one of your servers. You are 100% sure that you have applied the Cumulative Update on all servers and asking yourself what did I do wrong? Well, don’t get frustrated. What has happened is when the configuration failed, somehow the patch information got corrupted in the configuration database. Follow these steps to resolve this issues.
  1. Reset the IIS.
  2. Start SharePoint 2010 Management Shell and issue the “Get-SPProduct” command with the –local parameter on the local server which will retrieve the list of SharePoint related products installed on the server including the hotfixes. This also refreshes the hotfix information in the content database for the local server.

    Get-SPProduct –local

    image
  3. Once you have repeated the step 1 and 2 on every server of your farm, start the SharePoint Products and Configuration Wizard again and start the update process. This time, hopefully, the process will be successful.

If you continue to get the missing patch error after repeating the above steps, we will have to fix this issue manually. Start a command prompt and change your directory to 14 hive BIN folder. Type the following command:

psconfig.exe -cmd installcheck -noinstallcheck

The noinstallcheck flag basically tells PSCONFIG to ignore the patch verification on the server. After this process is complete, run the SharePoint Products Configuration Wizard again to be on the safe side. This time it should run without a problem.

2 comments: