CM 1910 prerequisites check failing for clustered SQL Server

[hybrid]

The bad news is that we were not successful at figuring this out elegantly. In the end we bit the bullet and rebuilt the cluster in the following way.

If I recall, we removed one node leaving only one node in the cluster (our SQL Server SKU allowed only two nodes in the cluster at any time). We then did a fresh install of Windows and SQL Server and then added this new node to the cluster. Then we repeated for the other node — remove, reinstall, re-add the new node.

 

Hopefully your answer @chrisjones123is more successful than the destructive approach we took. I unfortunately no longer have this setup to try your suggestion on!

[billybob]

  On 10/26/2022 at 7:52 PM, chrisjones123 said:

figure this out for anyone interested, found an article from 2012 that outlines some registry key changes you need to make on you cluster nodes.

https://forum.red-gate.com/discussion/15396/error-monitoring-clustered-sql-server

snippet taken from the article above.

Of the tests we conducted above the root cause of the short file name error during the Pre-req checks was found to be the fact that we were not able to remotely access the registry using the SQL Virtual name which we should have been able to do. On contacting Microsoft Support we were informed that there are known issues around NoRemap registry key needing to be set if you are using Network Name resource that is dependent on a separate new IP Address resource – see http://support.microsoft.com/?id=306985

The final solution was to add a new REG_MULTI_SZ registry key to BOTH cluster nodes called:-
NoRemapPipes to:-
HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters\

This key should contain the values of:-
WINREG
EVENTLOG
svcctl

After adding the above key and values we needed to reboot both cluster nodes and then we were able to connect to the SQL Virtual names (CLUSQL02 + CLUSQL01) using Regedit (Remote registry). Running the SCCM Pre –req checker now returns no errors.

Hope this soluton helps someone else.

 

Expand  

3 years later this reply helped me resolve an issue upgrading sccm to 2409. Thank you!