Product/patch installation or server upgrade required

Occasionally Health Analyzer shows the patch-mismatch error even after fully applying SharePoint cumulative updates. You even confirmed the successful upgrade status on the Upgrade Status page at https://caUrl/_admin/UpgradeStatus.aspx, but the Servers in Farm and Review Problems and Solutions pages show some servers are still not patched:




Diagnosis


Health Analyzer can produce the false report on some servers due to:
  1. One or more content databases still need to be upgraded. They get upgraded when you run psconfig or Config Wizard, but the upgrade status doesn't seem to “stick” afterwards sometimes. To verify, go to Upgrade and Migration > Review database status on Central Admin.

  2. A job or registry key is not in the correct state. The CreateProductVersionJob registry key was the culprit in the past (ref: http://blog.stefan-gossner.com/2016/08/09/sharepoint-patching-and-get-spproduct-local). However, it appears that something else is also causing the error, as the false report gets generated with the value of 0. To verify the registry:

    Get-ItemProperty -Path "HKLM:\Software\Microsoft\Shared Tools\Web Server Extensions\16.0\WSS" | select CreateProductVersionJob

Remedy


Start with the operation that requires minimal effort as follows:
  1. If the Manage Database Upgrade Status page (https://caUrl/_admin/DatabaseStatus.aspx) doesn't show "No action required" on a content database, remote into any SharePoint servers in the farm and run Upgrade-SPContentDatabase. Example:


    Note that this status is not always triggered by the NeedsUpgrade = $true property value of the database:



    Alternatively, in lieu of targeting just the reported databases, you can also run the Upgrade command on all content databases to check and ensure that all of them are upgraded (make sure your account has the sufficient permissions):

    Get-SPContentDatabase | Upgrade-SPContentDatabase -Confirm:0

    Note: Even with the successful upgrade of the content database, the Manage Database Upgrade Status page will not refresh the upgrade status promptly.

    Hit Reanalyze on the Health Analyzer and see if the error disappears. If it doesn't, move on to the next step.

  2. Remote into the affected servers and update the state of the wrong registry key by running “Get-SPProduct -Local”. Don't run it remotely as it will fail like this:



  3. Run the psconfig with a minimal number of parameters. But note this will still bring down the IIS and SharePoint services while the command is running. As a result, make sure to run it in the HA environment:

    PSConfig.exe -cmd upgrade -inplace b2b

Popular posts from this blog

October 2025 SharePoint CU Failed to Install After Applying September 2025 SharePoint CU

Image
[Tested on SharePoint 2016 only] Applying the September 2025 SharePoint Cumulative Updates to SharePoint On-Prem was a bit chaotic as it introduced a number of bugs. It would have been better if I had the option to skip it and go straight to the October CU. Stefan, the Sr. SharePoint Escalation Engineer at Microsoft, has summarized the issues very well on  his blog . While many of the issues have been fixed in the October CU release, the fix for the "installation of this package failed" error  was not included for those who had already applied the September CU before the fix was made. That is, the System and Local Service accounts have to be manually removed from the WSS_WPG and IIS_IUSRS groups before applying the October CU. Without this step, I encountered a new popup error that said: Error 2349. An internal error has occurred. ( ) Contact Microsoft Product Support Services (PSS) for assistance. For information about how to contact PSS, see PSS10R.CHM. Remedy Remove...
Read more

September 2025 SharePoint 2016 CU - Configuration Wizard failed

Image
[Applies  to SharePoint 2016; not tested on other versions of SharePoint] While the farm account is in the local admins group (regardless of being present in the  WSS_WPG  group), running the psconfigui.exe (SharePoint Configuration Wizard) or psconfig.exe with the farm account gets stuck at the last step (step 10 of 10). Associated behaviors are: CopySideBySideFiles_*.log showing the endless repetition of: “\16\TEMPLATE\LAYOUTS\accessrequestcontrol.debug.js Access is denied. Waiting 30 seconds… Retrying…”. Unable to close the Config Wizard by hitting the Cancel or X button on the GUI; it has to be killed in Task Manager. The “Upgrade Status” page on Central Admin, however, shows the green status “Succeeded” even though it's not. Diagnosis Microsoft has deployed the security hardening with the 2025 September CU. The farm service account can no longer be used interactively from now on. Previously, this was not a requirement, despite the documentation at  https://lear...
Read more

Broken Site Collection

Image
[Tested on SharePoint 2016 only] Suppose the following error occurs while creating a new site collection with a farm admin user account: ## Assume all declared variables are correct ## PS C:\FarmAdminUserAccount> New-SPSite -Url $spSite -Name $scName -Description $scDesc -ContentDatabase $cdb -QuotaTemplate $scQuota -Template $scTemplate -Language 1033 -OwnerAlias $scPrimaryAdmin -OwnerEmail $scPrimaryEmail -SecondaryOwnerAlias $scSecondaryAdmin -SecondaryEmail $scSecondaryEmail ********************** PS>CommandInvocation(Out-String): "Out-String" >> ParameterBinding(Out-String): name="InputObject"; value="Calling extension methods on object Microsoft.SharePoint.Administration.SPContentDatabase+<>c__DisplayClass16 failed with exception(s): The UPDATE permission was denied on the object 'MSP_TVF_WEB_ADMIN', database 'WSS_Content_DbName', schema 'pjpub'." New-SPSite : Calling extension methods on object Microsoft.Sha...
Read more