Error when running the configuration wizard after applying CU's (Feb 2023) for Sharepoint 2016 server after a fresh install.

Question

Error when running the configuration wizard after applying CU's (Feb 2023) for Sharepoint 2016 server after a fresh install.

Greg Booth 1,371

I completed a fresh install of Sharepoint 2016 (pre-reqs install successful, then sharepoint install, then run config wizard 1st time). All completed successfully.

This is on a single server farm, with a seperate database server.

Next step was to apply the latest CU's to I applied the Feb 2023 CU's by running

wssloc2016-kb5002325-fullfile-x64-glb.exe

sts2016-kb5002350-fullfile-x64-glb.exe

in that order, reboot after each one.

Then I ran the configuration wizard, which reported errors.

The configuration failed dialog box says:

"Failed to upgrade SharePoint Products.

This is a critical task. You have to fix the failures before you can continue. Follow this link for more information about how to troubleshoot upgrade failures: https://go.microsoft.com/fwlink/?LinkId=259653

An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown.  Additional exception information:

Failed updating SecurityMode and ProtectionLevel in cluster. [Exception=System.Management.Automation.ParameterBindingException: A parameter cannot be found that matches parameter name 'Path'.]          (EventID:0)

Upgrade completed with errors.  Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS\Upgrade-20230223-145750-839-9d8983cac2ac4de698971fc66610e9bf.log.  The number of errors and warnings is listed

To diagnose the problem, review the application event log and the configuration log file located at:C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS\PSCDiagnostics_2_23_2023_14_57_24_899_1593132773.log"

i.e. error message appears to be

Failed updating SecurityMode and ProtectionLevel in cluster. [Exception=System.Management.Automation.ParameterBindingException: A parameter cannot be found that matches parameter name 'Path'.]

there is an error line in the log file that says

SharePoint Foundation Upgrade UpdateClusterConfigurationInSPDistributedCache (16.0.4.1) 0

ERROR Failed updating SecurityMode and ProtectionLevel in cluster. [Exception=System.Management.Automation.ParameterBindingException: A parameter cannot be found that matches parameter name 'Path'. at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input) at Microsoft.SharePoint.DistributedCaching.Utilities.SPVelocityPowerShellWrapper.ExportCacheClusterConfig(String provider, String connectionString, String path) at Microsoft.SharePoint.Upgrade.UpdateClusterConfigurationInSPDistributedCache.Upgrade()] 00000000-0000-0000-0000-000000000000

And another

02/23/2023 15:00:54.30 OWSTIMER (0x1BD8) 0x056C SharePoint Foundation Upgrade SPUpgradeSession aj0ur

ERROR Upgrade completed with errors. Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS\Upgrade-20230223-145750-839-9d8983cac2ac4de698971fc66610e9bf.log. The number of errors and warnings is listed at the end of the upgrade log file. 710f99a0-f9f5-2015-1576-e2396198769d

02

(it says review the upgrade log which is the same file)

Towwards the bottom of the log file it says

INFO Upgrade session failed. 2 errors and 0 warnings encountered. 710f99a0-f9f5-2015-1576-e2396198769d

Greg Booth 1,371 Reputation points

2023-02-23T16:50:51.1366667+00:00
I can see that https://blog.stefan-gossner.com/2023/02/16/trending-issue-distributed-cache-problems-after-applying-january-2023-cu/ mentions some changes in the Jan 23 CU - if i export my cace config to a file, the advancved props section looks like

<advancedProperties>

<partitionStoreConnectionSettings leadHostManagement="false"/>

<securityProperties mode="None" protectionLevel="None">

<authorization>

<allow users="WSS_ADMIN_WPG"/>

<allow users="WSS_WPG"/>

</authorization>

</securityProperties>

</advancedProperties>

which is bad apparently

and maybe can be fixed by running

Stop-CacheCluster Set-CacheClusterSecurity -SecurityMode Transport -ProtectionLevel EncryptAndSign Start-CacheCluster

But then goes on to say

"There is one final step that needs to be completed: the worker process needs to be able to access the registry on the Distributed Cache servers to read the Distributed Cache registry key. To ensure that this works grant read access to the WSS_WPG group on the following registry key on all servers hosting the Distributed Cache service:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg

"

I have only one server in the farm - so will this be running the distributed cache ?
Greg Booth 1,371 Reputation points

2023-02-23T16:52:01.4366667+00:00
I can see that https://blog.stefan-gossner.com/2023/02/16/trending-issue-distributed-cache-problems-after-applying-january-2023-cu/ mentions some changes in the Jan 23 CU - if i export my cace config to a file, the advancved props section looks like

<advancedProperties>

<partitionStoreConnectionSettings leadHostManagement="false"/>

<securityProperties mode="None" protectionLevel="None">

<authorization>

<allow users="WSS_ADMIN_WPG"/>

<allow users="WSS_WPG"/>

</authorization>

</securityProperties>

</advancedProperties>

which is bad apparently

and maybe can be fixed by running

Stop-CacheCluster Set-CacheClusterSecurity -SecurityMode Transport -ProtectionLevel EncryptAndSign Start-CacheCluster

But then goes on to say

"There is one final step that needs to be completed: the worker process needs to be able to access the registry on the Distributed Cache servers to read the Distributed Cache registry key. To ensure that this works grant read access to the WSS_WPG group on the following registry key on all servers hosting the Distributed Cache service:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg

"

I have only one server in the farm - so will this be running the distributed cache ? and how do i grant acess to the WSS_WPG group
Greg Booth 1,371 Reputation points

2023-02-23T17:37:34.51+00:00

Thanks Stefan - followed the steps on your blog - including granting access to the reg , rebooted and re-ran the config wizrd - completed with no errors this time!
Greg Booth 1,371 Reputation points

2023-02-23T17:38:44.7533333+00:00

Hi Stefan - could you post a link to you blog as your answer - and i will mark as answered ?

Accepted answer

0 additional answers

Your answer

Greg Booth 1,371 Reputation points

2023-02-23T16:50:51.1366667+00:00

I can see that https://blog.stefan-gossner.com/2023/02/16/trending-issue-distributed-cache-problems-after-applying-january-2023-cu/ mentions some changes in the Jan 23 CU - if i export my cace config to a file, the advancved props section looks like

<advancedProperties>

<partitionStoreConnectionSettings leadHostManagement="false"/>

<securityProperties mode="None" protectionLevel="None">

<authorization>

<allow users="WSS_ADMIN_WPG"/>

<allow users="WSS_WPG"/>

</authorization>

</securityProperties>

</advancedProperties>

which is bad apparently

and maybe can be fixed by running

Stop-CacheCluster Set-CacheClusterSecurity -SecurityMode Transport -ProtectionLevel EncryptAndSign Start-CacheCluster

But then goes on to say

"There is one final step that needs to be completed: the worker process needs to be able to access the registry on the Distributed Cache servers to read the Distributed Cache registry key. To ensure that this works grant read access to the WSS_WPG group on the following registry key on all servers hosting the Distributed Cache service:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg

"

I have only one server in the farm - so will this be running the distributed cache ?
Greg Booth 1,371 Reputation points

2023-02-23T16:52:01.4366667+00:00

I can see that https://blog.stefan-gossner.com/2023/02/16/trending-issue-distributed-cache-problems-after-applying-january-2023-cu/ mentions some changes in the Jan 23 CU - if i export my cace config to a file, the advancved props section looks like

<advancedProperties>

<partitionStoreConnectionSettings leadHostManagement="false"/>

<securityProperties mode="None" protectionLevel="None">

<authorization>

<allow users="WSS_ADMIN_WPG"/>

<allow users="WSS_WPG"/>

</authorization>

</securityProperties>

</advancedProperties>

which is bad apparently

and maybe can be fixed by running

Stop-CacheCluster Set-CacheClusterSecurity -SecurityMode Transport -ProtectionLevel EncryptAndSign Start-CacheCluster

But then goes on to say

"There is one final step that needs to be completed: the worker process needs to be able to access the registry on the Distributed Cache servers to read the Distributed Cache registry key. To ensure that this works grant read access to the WSS_WPG group on the following registry key on all servers hosting the Distributed Cache service:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg

"

I have only one server in the farm - so will this be running the distributed cache ? and how do i grant acess to the WSS_WPG group
Greg Booth 1,371 Reputation points

2023-02-23T17:37:34.51+00:00

Thanks Stefan - followed the steps on your blog - including granting access to the reg , rebooted and re-ran the config wizrd - completed with no errors this time!
Greg Booth 1,371 Reputation points

2023-02-23T17:38:44.7533333+00:00

Hi Stefan - could you post a link to you blog as your answer - and i will mark as answered ?

Answer 1

Stefan Goßner 656 Microsoft Employee

Hi Greg,

if you have a single server farm with distributed cache configured then this will be the server hosting the distributed cache. And it seems you already used that server to export the configuration where you identified the incorrect configuration. With other words: the reg permission change needs to be on the one server you have in this scenario.

Cheers,

Stefan

More details: https://blog.stefan-gossner.com/2023/02/16/trending-issue-distributed-cache-problems-after-applying-january-2023-cu/

Yanli Jiang - MSFT 31,596 Reputation points Microsoft External Staff

2023-02-27T05:30:33.05+00:00

Hi Greg,

If this answer is helpful to you, please remember to accept it. It will help others who meet the similar question in this forum. Thanks for your understanding.
Yanli Jiang - MSFT 31,596 Reputation points Microsoft External Staff

2023-02-28T09:53:04.88+00:00

Hi @Greg Booth ,

Do you have further question on this , could we offer more support?

If this helps on your issue, you could mark it as answer so other user with similar problem could see this easier. :)

Share via

Error when running the configuration wizard after applying CU's (Feb 2023) for Sharepoint 2016 server after a fresh install.

0 additional answers

Your answer