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.

Same issue here, 2 fresh builds of 2022 in a 2 node cluster. same manageability error, same event viewer error. @Marian Matei did MS provide a solution?

I am curious if both of theses servers are physical servers and are they running Intel nic cards? I am running into the same thing in 4 clusters. I am not seeing the same thing in 2022 VM's at all. I have done tons of research and I find old articles about the issue in 2012 but I never saw that issue in 2012.

I have the exact same issue, I'm running Intel NIC Cards. Was there ever a solution to this?

Did anyone find a solution for this? I am also getting the same error on my both Hyper-V servers. I have configured them in a failover cluster Thank you

We have exactly the same problem. Server 2022 in 2-node Failover Cluster. We use Intel(R) Ethernet Converged Network Adapter X710 10 GB in SET mode dedicated only for Hyper-V and Intel(R) PLAN EM 1GB T OCP two ports in Teaming for only Cluster network. There is also an additional error with Microsoft-Windows-Kernel-IoTrace/Diagnostic when opening the event viewer - administrative events see picture. At the beginning, we didn't have any problems, but when testing live migration of virtual machines and higher network load, one of our nodes crashed and after that, errors occurred, but everything is still working properly. By changing the registry it can be removed but I don't know if that's the right way?

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

Steven J 6 Reputation points

2022-10-11T20:24:31.087+00:00

Same issue here, 2 fresh builds of 2022 in a 2 node cluster. same manageability error, same event viewer error. @Marian Matei did MS provide a solution?
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Ryan Oord 1 Reputation point

2021-12-24T05:46:41.867+00:00

I am curious if both of theses servers are physical servers and are they running Intel nic cards? I am running into the same thing in 4 clusters. I am not seeing the same thing in 2022 VM's at all. I have done tons of research and I find old articles about the issue in 2012 but I never saw that issue in 2012.
Please sign in to rate this answer.
FJ1 0 Reputation points

2023-08-23T11:18:23.2933333+00:00

accidentally commented...
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Stephen Wills 1 Reputation point

2022-03-07T15:54:51.043+00:00

I have the exact same issue, I'm running Intel NIC Cards.

Was there ever a solution to this?
Please sign in to rate this answer.
Tom Mitchell 1 Reputation point

2022-03-10T16:20:38.197+00:00

Also having the same problem. Physical Servers, Server 2022, Intel NICs (X722). Have tried recreating listeners, no change. Anyone found a solution?

Thank you.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Mukesh Yadav 1 Reputation point

2022-05-12T07:24:04.087+00:00

Did anyone find a solution for this?
I am also getting the same error on my both Hyper-V servers. I have configured them in a failover cluster

Thank you
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.
ZacZG 1 Reputation point

2022-06-15T11:57:35.203+00:00

We have exactly the same problem. Server 2022 in 2-node Failover Cluster.
We use Intel(R) Ethernet Converged Network Adapter X710 10 GB in SET mode dedicated only for Hyper-V and Intel(R) PLAN EM 1GB T OCP two ports in Teaming for only Cluster network.
There is also an additional error with Microsoft-Windows-Kernel-IoTrace/Diagnostic when opening the event viewer - administrative events see picture.

At the beginning, we didn't have any problems, but when testing live migration of virtual machines and higher network load, one of our nodes crashed and after that, errors occurred, but everything is still working properly.
By changing the registry it can be removed but I don't know if that's the right way?
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