ISSUE: Server Manager remote management error for clustered servers

[Karl-WE]

Dear Windows Server Insider Team, 

After long puzzles someone finally found a solution that Windows Server 2022 and vNext will appear "online" with no errors in Server Manager.

Warning: do not recompile WMI MOFs, especially when not broken, there's is an article on techcommunity.microsoft.com about it. Refer [1]

Scenario:

Windows Server 2022

Azure Stack HCI 22H2 

Windows Server vNext 

Part of Hyper-V fail-over cluster

Issue:

Server Manager reports nodes as Online. 

Yet indicating an error /limitation

Refer [2]

Reproducible:

yes, 100% on cluster nodes

Impact:

Errors in event log 

Customers might needlessly try to troubleshoot or contact support 

Workaround:

Add the Cluster computer account to the local Event Log Reader group of each Cluster nodes. 

References

[1] https://techcommunity.microsoft.com/t5/ask-the-performance-team/wmi-repository-corruption-or-not/ba-...

[2] https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/server-manager-problem-online-data-...

[3] https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/server-manager-problem-online-data-...

[#2]

@Karl-WE 

Thanks for your great description! Workaround2 helped a lot!

[#3]

Dear @EldenChristensen do you know if this item is already in triage and a fix is coming for vNext or even earlier versions? there are meanwhile several techcommunity articles about people tinkering around with this issue. This could harm more than solving the issue (registry changes and needless MOF recompiling). Thank you very much for your time!

[#4]

@Deleted To get rid of the errors in Server Status you just need to add the Cluster Object to "Event Log Readers" as described in Workaround 2. Then those warning messages will no longer appear and the server will be shown as "Online". 

About the others - I personally won't do a thing since each and every Server 2022 is showing those Warning Messages in Eventlog. I wouldn't mess with the registry and MOF Files either. 

[#5]

sounds like a clean solution. TYVM!

[#6]

I have updated the original post and removed other workarounds with the one named by @Christian_Feuerstein.

Thank you for adding a concise solution, which can be implemented best by group policy GPP, to make it transparent and lasting. 

[#7]

@Christian_Feuerstein unfortunately this doesn't solve the issue tried that today on 3 Azure Stack HCI 22H2 nodes. 

[#8]

@Deleted 

Strange - could you let me know which warnings occur in "Microsoft-Windows-ServerManager-DeploymentProvider/Operational" Eventlog? 

[#9]

@Christian_Feuerstein  Here is the warning from Microsoft-Windows-ServerManager-DeploymentProvider/Operational:

Generic failure querying the localized name for channel: Microsoft-Windows-Kernel-IoTrace/Diagnostic [hResult = Function failed during execution., hLastResult = The instance name passed was not recognized as valid by a WMI data provider.].

I get a similar error when I go to the Microsoft/Windows/Kernel-IoTrace/Diagnostic log in Event Viewer:

Event Viewer cannot open the event log or custom view. Verify that Event Log service is running or query is too long. The instance name passed was not recognized as valid by a WMI data provider. (4201)

I also get the same WMI error referring to the Kernel-IoTrace/Diagnostic log when I go to the Administrative Events Custom View in Event Viewer.

Thanks.

[#10]

That looks like the same error and I suspect that it is still the permissions that are causing the problem. Since I myself do not work with HCI but only with a HyperV Cluster 2022, it could theoretically be that the nodes are actually making requests here and therefore need to be added to the permission group in addition to the cluster object. Could you try that?

[#11]

@Christian_FeuersteinThanks for the reply. I have already added each host to its Event Log Viewer group and it didn't help. Did you mean add each host to all hosts' Event Log Viewer groups? I'm not working with HCI either, just Hyper-V on Server 2022.

[#12]

Hi all. had tried above references, then saw this post then I follow the solution.
https://www.checkyourlogs.net/fixed-s2d-cluster-data-retrieval-failures-occurred-error/
5. According to this, the WS-Management Service has a packet limit by default. Run the following cmdlets to fix this error.
Get-WSManInstance -ResourceURI winrm/config
Set-WSManInstance -ResourceURI winrm/config -ValueSet @{MaxEnvelopeSizekb = “700”}
6.Restarted the Service.
This solve the "DATA RETRIEVAL FAILURES OCCURRED ERROR"

[#13]

Hello. Thanks for the reply, but that fix is for a different issue than the one we're seeing.

The error that is fixed by changing the WMI packet size is something like "Configuration refresh failed with the following error: The WS-Management service cannot process the request. The computed response packet size (517916) exceeds the maximum envelope size that is allowed (512000)." See https://blog.expta.com/2022/11/fix-for-online-data-retrieval-failures.html as an example.