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 for business | Windows Server | User experience | Other

15 answers

Sort by: Most helpful
  1. Eric McStravick 20 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.)

    4 people found this answer helpful.

  2. JustAnotherUser 41 Reputation points
    2023-08-14T15:37:37.6666667+00:00

    I've had this problem with many versions of Windows over the years and found, during the in-place upgrade, some older and no longer necessary installed "windows features" were removed. In my specific case, it was the "Media Foundation" which was a requirement long ago for desktop mode. After removing this feature, I have to go in and remove the no-longer-needed media foundation items from the registry here: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels

    Looking at some of the error logs here, I see some "file services" features were removed when upgraded to 2022. Check the Channels key for signs of the file services and or compare a fresh 2022 install with the upgraded server and remove registry entries related to features that were removed during the in-place upgrade.

    1 person found this answer helpful.
    0 comments No comments

  3. ZacZG 1 Reputation point
    2022-07-15T13:37:32.43+00:00

    Hi, after backup I just deleted REG_DWORD "Enabled"=dword:00000001 that's enough so that the error no longer appears.

    221123-dword.jpg

    0 comments No comments

  4. Peter MacKay 1 Reputation point
    2022-07-15T01:11:34.427+00:00

    At the top of this article the recommendation says:

    I do NOT recommend this workaround:
    delete/rename the registry keys HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\xxx

    Sorry for being such a stickler for details here, but are you recommending I delete everything in that registry folder or are you suggesting I delete a single item called "xxx" because I do not see an object called xxx, but there must be maybe 400 folders in there. Maybe even more than that.

    Are you suggesting I wipe out the entire ** HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\ ** section? or perhaps rename it to channels-old

    Do I understand you correctly?


  5. 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. 211692-2022-event.jpg

    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?

    0 comments No comments

Your answer

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