Health Analyzer Issue: Product/patch installation or server upgrade required

In this article, I will explain How to solve the below detected Health Analyzer error:

Product / patch installation or server upgrade required

Product patch installation or server upgrade required


Cause

This problem usually occurs in case your farm suffer from patch level mismatch in one or more servers where all required products must be installed on all servers in the farm, and all products should have the same patching and upgrade level across the farm.

Below are the possible related scenarios that maybe raise theProduct/patch installation or server upgrade requiredissue.

  • One or more SharePoint servers in the farm were patched with low or high patching version.

noteAll SharePoint servers must have the same software update and upgrade level across the farm.

All required products must be installed on all servers in the farm, and all products should have the same patching and upgrade level across the farm.

  • All SharePoint servers have been patched with the same Cumulative Update/Service Pack .. etc. but the SharePoint Configuration wizard hasn’t been run on all SharePoint servers in the farm.

hint-iconIt’s recommended to start SharePoint Configuration wizard on the main application server that host Central administration and then runs it on all other SharePoint servers at the same time, the sequence doesn’t matter.

Ex: Consider you have a farm that consists of six SharePoint servers. so the steps should be as the following:

  • Start Running the config wizard on the app server that hosts the central administration.
  • At the same time, for the other five SharePoint servers, run the config wizard, the sequence doesn’t matter.
  1. App server (that hosts the central admin) –> Run the config wizard.
  2. Server 1 –> At the same time, go to server 1 to run the config wizard that will wait until the previous wizard finish that is now running on App Server.
  3. Server 2 –> At the same time, go to server 2 to run the config wizard that will wait until the previous wizard finish on Server 1 then it will start automatically.
  4. Server 3 –> At the same time, go to server 3 to run the config wizard that will wait until the previous wizard finish on Server 2 then it will start automatically.
  5. Server 4 –> At the same time, go to server 4 to run the config wizard that will wait until the previous wizard finish on Server 3 then it will start automatically.
  6. Server 5 –> At the same time, go to server 5 to run the config wizard that will wait until the previous wizard finish on Server 4 then it will start automatically.

This way is recommended especially in case you have a large farm. In this case, you don’t need to wait until each server finishes then start the config wizard on the other servers one by one manually! so it’s preferred to start all other config wizard at the same time on other SharePoint servers to let it start automatically, once the previous wizard finish based on your running order!

  • Microsoft / Windows updates (that has the SharePoint security fixes) are not installed on all SharePoint servers within the farm and the SharePoint Configuration wizard has been run on all SharePoint servers.
    • All SharePoint servers that have not applied the Microsoft / Windows Updates will be affected and this will cause patch mismatch issue.
  • Microsoft / Windows updates are installed on all SharePoint servers within the farm with the same update plan settings but the SharePoint Configuration wizard hasn’t been run on all SharePoint servers within the farm.

noteBecause of SharePoint Security update is a part of Microsoft / Windows Update. So in case you enabled Microsoft / Windows Update on all SharePoint servers within the farm. you must schedule running the SharePoint Configuration Wizard after the Microsoft/ Windows update has been applied on SharePoint servers  to make sure that the patches have been applied successfully.

  • Sometimes one of the server within the farm is out of sync with SharePoint configuration database.

Solution

You should be aware of the Patching/Updating SharePoint is performed through a three-step process:

  1. Install the package update like CU, Service Pack, PU …etc.
  2. Run the SharePoint Configuration wizard on all SharePoint Servers within the farm.
  3. Check Upgrade Status.

And to avoid “Product/patch installation or server upgrade required” issue, you should make sure that:

  • All required update/products must be installed on all SharePoint servers across the farm.
  • All products should have the same patching and upgrade level across the farm.
  • The Microsoft update / Windows update (MU/WU) plan setting is the same on all SharePoint Servers across the farm.

Below, I’ll show How to fixProduct/patch installation or server upgrade requiredissue by following the below steps:

Steps

  • In Health Analyzer Click on the issue item to check its details.

Product patch installation or server upgrade required

  • In remedy section checks what’re the servers that have patch issue?

Product patch installation or server upgrade required details

  • Go to System Settings > Servers in Farm.

System Settings

  • Below Status column checks the servers that require upgrade

servers-in-farm-upgrade-required

hint-iconIt’s suggested to run theGet-SPProduct -Localon all affected server as an easy fix in many situations to update the installed products in the Configuration database. 


Get-SPProduct -Local

For more details check Get-SPProduct

  • Click on “Upgrade Required” to open Upgrade and Migration settings.
  • Click on Check upgrade status to check the previous upgrade status.

Upgrade and Migration - Check Upgrade Status

  • If the previous upgrade attempt status is failed, you must resolve any upgrade issues before attempting the upgrade.

SharePoint Upgrade startus failed.png

  •  If all previous upgrade attempt has been applied successfully, go back to Upgrade and Migration settings.
  • Click on Check product and patch installation status to open Manage Patch Status.

Check product and patch installation status

  • In view list > Select the server that requires an upgrade based on the mentioned inHealth Analyzer error message details.

Manage Patch Status SharePoint.png

  • Compare the patches build numbers of the server that require upgrading with other SharePoint servers that have status with “No Action Required“.

Manage Patch Status Details SharePoint

If the patch build numbers are identical on all SharePoint servers within the farm

In this case, you only need to run SharePoint Configuration Wizard on the SharePoint server that requires upgrade.

If the patch build numbers are not identical on all SharePoint servers within the farm

In this case, you should first check the windows update status on all SharePoint servers and make sure that the last installed updates are identical for all SharePoint servers within the farm.

Windows Update Details.png

View Windows Update History.png

If it’s not identical, you should do the following:

  • Run MU/WU on all SharePoint Servers.
  • Run the SharePoint Configuration Wizard on all SharePoint Servers.

If it’s identical, you should do the following:

  • Check the corresponding last update build number for each SharePoint server that.not require upgrade
  • Download and installs it on each server that require upgrade to match all SharePoint servers with the same build number.

hint-iconCheck also, How to get the latest Cumulative Update / Farm Patch Level that has been installed in a SharePoint Farm.

  • Run the SharePoint Configuration Wizard on all SharePoint Servers.

How to run Run the SharePoint Configuration Wizard on your farm?

As I mentioned above, It’s recommended to

  • Run the SharePoint 2013 Configuration wizard first on the main application server that host the Central administration. Once it started, you will be able to run SharePoint 2013 Configuration wizard on each other SharePoint servers at the same time without order.

hint-iconThe other wizards will pause until the previous wizard finishes based on the running order that you have done. Once the previous wizard finished, the next one will start automatically.

SharePoint Products Configuration Wizard - Step 1

hint-iconThis is should be useful in case of you are configure a large farm with for example 40 SharePoint servers. so in this case, it’s unreasonable to wait until each server finishes then start the config wizard on the other servers one by one manually! 

Run the SharePoint configuration wizard via PSConfigUI.exe

  • Log in to the main application server with the Farm account.
  • Go to Start menu > Type SharePoint Configuration Wizard.

Run SharePoint Products Configuration Wizard

Start SharePoint Products Configuration Wizard

warning-iconIn the second step, make sure that the ‘Do not disconnect from this server farm‘ is selected.

In the third step, make sure that ‘No, this machine will continue to host the website‘ is selected

  • In step 9 it performing an upgrade to SharePoint Products.

SharePoint Products Configuration Wizard - Step 9

Run the SharePoint Configuration Wizard via SharePoint Management Shell

  • Log in to the main application server with the Farm account.
  • Open SharePoint Management Shell as Administrator.

Run SharePoint Management Shell as Administrator

  • Run PSConfig.exe command as the following

PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

PSCONFIG Completed

run-psconfig-exe

  • Repeat the previous steps on all SharePoint servers.

Checking the Upgrade Status

Once the SharePoint Configuration Wizard is finished successfully on each SharePoint Server in the farm.

  • Go back to the Central Administration > Upgrade and Migration > Check upgrade status.

Upgrade and Migration - Check Upgrade Status

noteyou can’t rollback the Cumulative Update Installation, so It’s heavily recommended to perform a full backup before starting the update process.

  • Ensure the status of each server is succeeded.

SharePoint Upgrade Status

noteIf the previous upgrade attempt has failed, you must resolve upgrade issues before attempting a new upgrade.

  • Go back to the Central Administration > Monitoring > Review problems and solutions.

Review problem and solutions

  • Click on the error.

Product patch installation or server upgrade required

  • From the above ribbon > Select the Reanalyze Now.

Reanalyze Now SharePoint Health Analyzer

  • Go back to Health Analyzer Reports list where the error should not be now listed.

Applies To
  • SharePoint 2016.
  • SharePoint 2013.
  • SharePoint 2010.
Advertisements

4 thoughts on “Health Analyzer Issue: Product/patch installation or server upgrade required

  1. Great article with lots of information.
    Just a little note about point mentioned in your article “It’s recommended to start SharePoint Configuration wizard on the main application server that host Central administration and then runs it on all other SharePoint servers at the same time.”
    I don’t think its a good idea to run PSConfig/Config wizard at the same time on any 2 servers.

    Application server can be first one and then rest of servers, but one by one, as per most Technet articles. Personally I have seen and tested many times that even if you run wizard on WFE first and application sever last it works well too.

    Thanks again !

    Like

    1. Hello Umar,
      Thank you for your comment!

      Regarding your concern, “Starting with the APP server that host central administration” is the correct order that confirmed by Stefan Goßner (Senior Escalation Engineer in Microsoft),

      He said in his article: “The guidance for PSConfig is unchanged: start with the app server hosting the central admin”, you can check the Ref at https://blogs.technet.microsoft.com/stefan_gossner/2015/09/09/why-we-recommend-require-to-run-the-configuration-wizard-also-for-security-fixes/ (try to search by “The guidance for PSConfig is unchanged” to get it.

      Regarding “run PSConfig/Config wizard at the same time”.

      You don’t complete what I have said! I said, “The others wizard will wait until the previous wizard to finish and continue automatically” that means “The other wizards will pause until the previous wizard finishes based on the running order that you have done. Once the previous wizard finished, the next one will start automatically, ”

      This way is recommended especially in case you have a large farm with for example 10 SharePoint servers. In this case, do you think it’s recommended to wait until each server finishes then start the config wizard on the other servers one by one manually! or it’s preferred to let the wizard start automatically, once the previous wizard finish!


      Let’s summarize the above mentioned with a simple example.

      Ex: Consider you have a farm that consists of six SharePoint servers. so the steps should be as the following:

      • Start Running the config wizard on the app server that hosts the central administration.
      • At the same time, for the other five SharePoint servers, run the config wizard, the sequence doesn’t matter.

      *App server (that hosts the central admin) –> Run the config wizard.
      **Server 1 –> At the same time, go to server 1 to run the config wizard that will wait until the previous wizard finish that is now running on App Server.
      ***Server 2 –> At the same time, go to server 2 to run the config wizard that will wait until the previous wizard finish on Server 1 then it will start automatically.
      ****Server 3 –> At the same time, go to server 3 to run the config wizard that will wait until the previous wizard finish on Server 2 then it will start automatically.
      *****Server 4 –> At the same time, go to server 4 to run the config wizard that will wait until the previous wizard finish on Server 3 then it will start automatically.
      ******Server 5 –> At the same time, go to server 5 to run the config wizard that will wait until the previous wizard finish on Server 4 then it will start automatically.

      Hope it now clear, please don’t hesitate to inform me in case you have any further questions!

      Thanks 🙂

      Like

Leave a Reply

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

WordPress.com Logo

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

Google+ photo

You are commenting using your Google+ 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