Share via

Server Manager problem: Online - Data retrieval failures occurred

Marian Matei 1 Reputation point
2021-11-28T15:02:34.517+00:00

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.

153124-servermanager1.png153080-servermanager2.png153151-winrm-error-10149.png153132-cmd.png153152-eventviewer.png

Windows Server Management
Windows Server Management
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Management: The act or process of organizing, handling, directing or controlling something.
442 questions

27 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. 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?

    1 person found this answer helpful.
    0 comments
  2. 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.)

    1 person found this answer helpful.
    0 comments
  3. 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.

  4. 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?

  5. 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

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.