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.

everything has become normal after removing these update but removing the security update is not a solution for a problem, I hope Microsoft fix this issue soonest.

I can only confirm that after 5 months, the cluster production works properly without the errors mentioned above or any system crashes. The REG_DWORD 'Enabled' is still deleted from the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic on both cluster nodes and I haven't found any other solution except deleting REG_DWORD 'Enabled' I also tried WMI repository autorecover according to these instructions but without success. https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/server-manager-problem-online-data-retrieval-failures-occurred/m-p/3011953

Hi I have the same Error Server 2022 since I install the WU KB5019081 KB5020619 , Servicing Stack 10.0.20348.1066 Exchange KB5019758 , in this Server is also Exchange 2019 The error goes away once I renamed the reg file Microsoft-Windows-Kernel-IoTrace/Diagnostic_old

Last night I uninstalled the Update KB5020619 , rename the Regeistry KEY back , Server Restarted and since yestarday are no errors anymore . Im not sure if removing Update did help or restart from the Server 2022

If you click on refresh error (Server manager noitification), you will see the exact error. If your error match with below then follow my instructions. " 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). " Solution Open the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WSMAN\Client Check if maxEnvelopeSize is already exist. If yes then set 2000 hexadecimal ( 8192 decimal). and if it does not exist the create a DWORD (32-bit) value named maxEnvelopeSize Restart Windows Remote Management (WS-Management) , aka WinRM , Of course credit goes to [https://blog.expta.com/2022/11/fix-for-online-data-retrieval-failures.html

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.

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.
Stephen Wills 6 Reputation points

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?
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.
Mukesh Yadav 31 Reputation points

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
Ricdronski 1 Reputation point

2022-08-05T17:08:18.187+00:00

Hi @Marian MATEI , have you found the proper solution for this? please let us know steps and solution for this.

Thank you.

-Rick
WCW65 91 Reputation points

2022-09-20T02:22:35.947+00:00

Experiencing the same issue. Built out 3 separate 2 node clusters. One cluster is physical and the other two are virtualized. Clean installs on all the nodes. However 4 of the 6 nodes have this error, 2 do not. Even the local server retrieving its own data in server manager generates the error on itself, not just remote mgt servers. Only thing in common for the 6 installs, is each reused a computer name/account that exists in the domain. Also seeing the same issue as @ZacZG with Administrative Events in event viewer.

Very frustrating for sure.
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?
Zvonimir Bregeš 1 Reputation point

2022-11-12T23:29:47.53+00:00

Same problem here, server 2022, 2 node cluster, no errors when logged in as local administrator.
Anyone found the solution?
Adil Elamin 1 Reputation point

2022-11-13T21:09:42.793+00:00

one hour after removing the update, the issue come back again :(
Sebastian 1 Reputation point

2022-11-24T14:27:33.317+00:00

@Toni

We have the same problem on a freshly installed Server 2022 in a Hyper-V Cluster ( 2 Hosts).
The updates listed above were not installed. Instead the following:

Unfortunately, we cannot confirm the Intel theory. We use 10G Broadcom Network Adapter.

Renaming the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic Key to "OLD" on both Hosts
has helped. The Server Manager no longer displays errors.

However, the error in the event viewer persists:

It would be nice if the real cause was found...
Toni 21 Reputation points

2022-11-24T15:15:42.71+00:00

@Sebastian

See updates installed on my Server
ZacZG 1 Reputation point

2022-11-24T16:51:41.967+00:00

Same here....
Sebastian 1 Reputation point

2022-11-24T17:18:36.207+00:00

As you can see, not the same Updates...
ZacZG 1 Reputation point

2022-11-24T17:27:42.037+00:00

Same as Tony-7979 posted...
Peter V. Hove Sunesen 0 Reputation points

2023-01-24T14:34:08.8433333+00:00

Have anybody found the core corse to this: Online - Data retrieval failures occurred
ScrubMaster 0 Reputation points

2023-04-27T20:28:24.5+00:00

Looking for a core fix to this other than modify registry settings on extremely important hosts. Anyone found anything else on this one by chance?
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?
MiSo 0 Reputation points

2023-07-19T09:19:07.52+00:00

I have same issue with 2 Cluster Node W22. Same Server manager error.
Event Viewer - Administrative Events it give me an WMI error but then i can access it.

Unfortunalety no solution up to now
Makoto_MAT 10 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
FJ1 0 Reputation points

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

accidentally commented...
ΝΙΚΟΣ ΑΘΑΝΑΣΑΚΗΣ 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.

15 answers

Adil Elamin 1 Reputation point

2022-11-13T19:27:33.787+00:00

everything has become normal after removing these update

but removing the security update is not a solution for a problem, I hope Microsoft fix this issue soonest.
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-11-14T09:15:41.157+00:00

I can only confirm that after 5 months, the cluster production works properly without the errors mentioned above or any system crashes.

The REG_DWORD 'Enabled' is still deleted from the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic on both cluster nodes and I haven't found any other solution except deleting REG_DWORD 'Enabled'

I also tried WMI repository autorecover according to these instructions but without success.
https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/server-manager-problem-online-data-retrieval-failures-occurred/m-p/3011953
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.
Toni 21 Reputation points

2022-11-16T10:35:01.707+00:00

Hi
I have the same Error Server 2022 since I install the WU
KB5019081 KB5020619 , Servicing Stack 10.0.20348.1066 Exchange KB5019758 ,
in this Server is also Exchange 2019
The error goes away once I renamed the reg file Microsoft-Windows-Kernel-IoTrace/Diagnostic_old
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.
Toni 21 Reputation points

2022-11-17T06:56:56.773+00:00

Last night I uninstalled the Update KB5020619 , rename the Regeistry KEY back , Server Restarted and since yestarday are no errors anymore .
Im not sure if removing Update did help or restart from the Server 2022
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.
Mohd Arif 946 Reputation points

2023-01-17T09:21:42.4566667+00:00

If you click on refresh error (Server manager noitification), you will see the exact error. If your error match with below then follow my instructions.

"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)."

Solution

Open the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WSMAN\Client

Check if maxEnvelopeSize is already exist. If yes then set 2000 hexadecimal (8192 decimal). and if it does not exist the create a DWORD (32-bit) value named maxEnvelopeSize

Restart Windows Remote Management (WS-Management), aka WinRM,

Of course credit goes to [https://blog.expta.com/2022/11/fix-for-online-data-retrieval-failures.html
Please sign in to rate this answer.
Troy Spetter 0 Reputation points

2023-05-31T16:01:52.9033333+00:00

Checked on this and this value is already correct. So this is not the issue.
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

15 answers

Your answer