Hello, I'm using Windows Server 2022 and I have this problem: data retrieval on Server Manager. Is there a fix for this issue? Obs: this is a test lab all servers are domain members I'm connecting on all servers with the domain Administrator account. tested with both Firewall on and off do NOT recommend this workaround: delete/rename the registry keys HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\xxx Thank you.

I have posted hopefully a solution on the tech community website: https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/server-manager-problem-online-data-retrieval-failures-occurred/m-p/3935651/highlight/true#M10567

For anyone coming into this and still looking for a different answer, I had the same issue and was having lots of issues with the nodes of the cluster saying they couldn't communicate or lost communication with other nodes. Mine was caused by WinRM packet sizes being bigger than the default maximum. Running the following command on each node instantly fixed all my issues without reboots: winrm set winrm/config @{MaxEnvelopeSizekb="1024000"} Default as 512000 so I doubled it (FYI, needs to be run in administrative cmd, powershell will throw an error on the above without some tweaking.)

Server Manager problem: Online - Data retrieval failures occurred

Marian Matei 1

Hello,

I'm using Windows Server 2022 and I have this problem: data retrieval on Server Manager.
Is there a fix for this issue?

Obs:

this is a test lab
all servers are domain members
I'm connecting on all servers with the domain Administrator account.
tested with both Firewall on and off
do NOT recommend this workaround: delete/rename the registry keys HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\xxx

Thank you.

Jeffrey Espinosa 0 Reputation points

2023-07-13T03:35:22.4133333+00:00

I have same issue here, 2 fresh installed 2022 on a cluster. Same Server manager error and event viewer error. Did anyone got a solution already?
Makoto_MAT 5 Reputation points

2023-07-25T09:48:32.68+00:00

Hello, My customer run a Windows2019 Std server as WSFC cluster 2nodes.
I have exactly same problem since last April.
I tried some modification .... and finally get resolved.
I see that the cause of issue was "WSMAN", Windows Remote Management service.

I followed an instruction here :

https://www.checkyourlogs.net/fixed-s2d-cluster-data-retrieval-failures-occurred-error/
Run Powershell as Administrator
Command :
Get-WSManInstance -ResourceURI winrm/config
Set-WSManInstance -ResourceURI winrm/config -ValueSet @{MaxEnvelopeSizekb = “700”}

Then the Server Manager shows only "Online" .... !
No "Data retrieval failures" there.
Hope everybody to get to the same happy-end. Makoto
ΝΙΚΟΣ ΑΘΑΝΑΣΑΚΗΣ 0 Reputation points

2023-09-09T13:22:06.91+00:00

Makoto_MAT Thanks Working!!
Marcos Nyamanga 0 Reputation points

2024-01-09T06:39:52.34+00:00

Hi @Marian Matei Did you eventually find a solution for the above? I have similar errors with my cluster environment and I'm not comfortable doing the registry change on a live production environment. Please advise.

27 answers

SekoBayo 1 Reputation point

2023-09-22T19:28:30.94+00:00

I have posted hopefully a solution on the tech community website:

https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/server-manager-problem-online-data-retrieval-failures-occurred/m-p/3935651/highlight/true#M10567
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Eric McStravick 0 Reputation points

2024-09-17T23:12:39.68+00:00

For anyone coming into this and still looking for a different answer, I had the same issue and was having lots of issues with the nodes of the cluster saying they couldn't communicate or lost communication with other nodes. Mine was caused by WinRM packet sizes being bigger than the default maximum. Running the following command on each node instantly fixed all my issues without reboots:

winrm set winrm/config @{MaxEnvelopeSizekb="1024000"}

Default as 512000 so I doubled it (FYI, needs to be run in administrative cmd, powershell will throw an error on the above without some tweaking.)
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Server Manager problem: Online - Data retrieval failures occurred

27 answers

Your answer