Forum Discussion
Server Manager problem: Online - Data retrieval failures occurred
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.
DG00 I am sorry to hear this. I had a fair number of our customers affected.
For me it is gone when WS 2022 (target OS you want to manage remotely) is patched.
The only situation where I still see the issue is the WS 2025 DC created by mslab, when added to a remote Server Manager. Doesn't matter the remote OS or LCU.
I have reported everything with SR 2411120050002891. Including videos and repro steps.
As you are still affected, please open a business support case and refer to the SR number above in the case description.
I see no other way to get yours addressed.
Could you please try the following and report back:
- spin up a VM with WS 2022 latest ISO + LCU 10-2024 or newer (alternatively WS 2025, when licensed)
- Join OS to the same network and domain of the cluster
- Add your cluster / nodes to Server Manager on this VM
- Does this change anything?
- Have you tried any of the many workarounds on the cluster or is it in default state?
Just want to give a bit of an update here. Today we applied the January 2025 CU to our Server 2019 Cluster joined hosts, and upon reboot it did not require the usual workaround. Just as a preliminary thing, it seems to be corrected for us in this update? I'll be watching it over the next while here to see if we encounter the issue again.
I have been looking for a solution to this issue for months now. Even though the original post did not metion clusters, all the replies seem to imply clustering. I suspect that admins who manage clusters use Server Manager more than many others.
My case is different, and many of the proposed solutions simply will not work. First, because this is not a clustering issue. Second, because the machines in question are Domain Controllers.
3 DCs. Call them DC-6, DC-7, and DC-8. There are no DC-[1-5]. All in the root domain. At three different physical locations, but all in the same site. Gigabit speed between locations.
Looking at Server Manager on each machine, I see the following:
DC-6 shows a manageability warning for DC-07. Online - Data retrieval failures occurred. DC-6 and DC-8 are fine. On the DNS tab, only 6 and 8 are shown.
DC-7 shows a manageability warning for DC-06. Online - Data retrieval failures occurred. DC-7 and DC-8 are fine. On the DNS tab, only 7 and 8 are shown.
DC-8 shows all devices fine. On the DNS tab, all machines are shown.
ACUC, Sites & Services, etc. all appear to be fine, and you can manage any DC from any DC using these these tools.
This started happening about 5 months after the domain was created.Hi Karl,
I have a 2 node cluster with 'data retrieval errors' displayed in Server Manager on each server pretty soon after going into production in Jan 2024. It seemed like the only changes made prior to that was Windows Updates but that could be a coincidence.
Each is running Windows Server 2022 Standard. Version 10.0.20348 Build 20348
Both are patched to Jan 2025.
I have not seen these on any of our 2022 DCs using server manager from the console.
Let me know if you need more info.
Hi all,
is anyone still affected by this issue. Could you please comment with- the OS version and build of the remote management VM
- the OS version and build of the cluster nodes
I have tried to repro the issue with Windows Server 2022 RTM build 20348.169 and patched LCU 10-2024.The clustered or not all nodes showed up as "Online".
Only VMs that were newer than the Management VM OS showed up with the respective error.
mgmt-2022 - OS: WS 2022 RTM
Management - OS: WS 2025 vNext
DC - OS: WS 2025 RTM
S2D-Clus01 Nodes S2D-101024-1 / Nodes S2D-101024-2 - OS WS 2022 patched LCU 10-2024
S2D-Clus02 Nodes WS2022-S2D1 / Nodes WS2022-S2D2 - OS WS 2022 RTMDefinitely affected by something that looks the same.
Not related to clusters, though.utcl_ken DG00
could it be that the OS where you are adding remote Windows Server in Server Manager is older than the target OS?
I mean imagine you have a WS 2022 cluster or DC and adding it to a WS 2019 Server Manager.Is there any difference doing the same adding remote servers in WS 2022 Server Manager?
Hi Karl,
So we just patched up to the November CU, and are still affected by this it seems.
DCs- OS:WS 2019 Version 1809 (OS Build 17763.6532)
Cluster Nodes 01-03 - OS: WS 2022 Version 21H2 (OS Build 20348.2849)
We're just managing directly from one of the cluster nodes. Issue occurs on every restart of a node.DG00 I am sorry to hear this. I had a fair number of our customers affected.
For me it is gone when WS 2022 (target OS you want to manage remotely) is patched.
The only situation where I still see the issue is the WS 2025 DC created by mslab, when added to a remote Server Manager. Doesn't matter the remote OS or LCU.
I have reported everything with SR 2411120050002891. Including videos and repro steps.
As you are still affected, please open a business support case and refer to the SR number above in the case description.
I see no other way to get yours addressed.
Could you please try the following and report back:
- spin up a VM with WS 2022 latest ISO + LCU 10-2024 or newer (alternatively WS 2025, when licensed)
- Join OS to the same network and domain of the cluster
- Add your cluster / nodes to Server Manager on this VM
- Does this change anything?
- Have you tried any of the many workarounds on the cluster or is it in default state?
I have filed a SR today with 2411120050002891. Describing the issue and kindly requesting a backport of a fix to WS 2022 Std / Datacentre. I have named Azure Stack HCI 22H2 as an affected product, but since EOS is May 2025 I marked it as optional.
It cannot hurt to follow this example and open SRs for the same.
The selection is "Windows Server > Windows Server 2022 > System Management Components > Server Manager". One could argue it is an WinRM / WMI issue, but since there is no productive impact (as of I know), and just an irritating display issue in Server Manager I'v chosen this category.
Thank you everyone!afaik there is no solution yet. Elden_Christensen may I ask for looking into this? It is so easily reproducible. It happens as soon WS 2022 or vNext are clustered Server objects. Do you need an existing SR to work on this?
Has anyone here opened a support request?
Please share me your SR number via DM. TYVM.- Did you find a solution? I have the same issue
Hi everyone
Christian_Feuersteinhas found the clean and persistant solution
"To get rid of the errors in Server Status you just need to add the Cluster Object (cluster computer account) to "Event Log Readers" as described in Workaround 2. Then those warning messages will no longer appear and the server will be shown as "Online".
edit: unfortunately this could not be proved after testing and reports from different users and different customers on my own. Regardless the OS version.
Tested WS 2019, WS 2022, Azure Stack HCI 22H2.DB2024 This is proper solution: KB article from Dell. It fixed the issue.
Step to disable the event log Microsoft-Windows-Kernel-IoTrace/Diagnostic (Apply on both nodes)
- Log on to the target terminal as a user with administrator privileges.
- Start Windows PowerShell with administrator privileges.
- Execute the following command to check the current value.
Command: (Get-Cluster).DumpPolicy
Example execution result:
PS C:\Users\Administrator> (Get-Cluster).DumpPolicy
1376850201 - Convert the above decimal value to binary (converter tools)
The following are the values in our verification environment, so please use the actual values. Decimal: 1376850201
Binary: 01010010000100010001000100011001 - Change the 21st value count from the right to 0 in the above binary number.
The following are the values in our verification environment, so please use the actual values. Current value: 01010010000100010001000100011001
After change: 01010010000000010001000100011001 - Convert the above binary value back to decimal.
The following are the values in our verification environment, so please use the actual values. Binary number after change: 01010010000000010001000100011001
Modified decimal number: 1375801625 - Execute the following command in Windows PowerShell started with administrator privileges. Command: (Get-Cluster).DumpPolicy=Modified decimal number
Example execution result: PS C:\Users\Administrator> (get-cluster).DumpPolicy=1375801625 (Nothing is displayed if successful.) - Confirm that the changed value is output by executing the following command again.
Command: (Get-Cluster).DumpPolicy
Example execution result: PS C:\Users\Administrator> (Get-Cluster).DumpPolicy 1375801625 - In Registry Editor, change the following registry data to 0 (disabled).
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic
Name: Enabled
Type: REG_DWORD
data: 0 - Restart the OS, Make sure the event log Microsoft-Windows-Kernel-IoTrace/Diagnostic is disabled.
- seems like some has found a technically and persistent clean solution. Reiterate, do not do MOF compilations.
https://techcommunity.microsoft.com/t5/windows-server-insiders/issue-server-manager-remote-management-error-for-clustered/m-p/4009699/highlight/true#M3236 This error has been plaguing my server since I upgraded from 2008 R2 to 2012 R2. I tried running this in Command Prompt as an admin a few times, but it didn't fix the error by itself (probably a good idea to run anyways):
cd C:\Windows\System32\wbem\Autorecover
/f %s in ('dir /b *.mof *.mfl') do mofcomp %s
Someone on another forum recommended opening the event viewer to see the failure status and check if there was a deeper underlying issue. Once I opened the event viewer, it gave me this warning:
"One or more logs in the query have errors. Microsoft-Windows-DxpTaskRingtone/Analytic. The system cannot find the file specified"I found information in another forum that stated this particular event log was deprecated in Server 2012 R2 and was no longer valid. - https://answers.microsoft.com/en-us/windows/forum/all/microsoft-windows-dxptaskringtoneanalytic-the/5f2dd93d-c9cc-40a8-b331-e4710e19a50d
I went ahead and found the Microsoft-Windows-DxpTaskRingtone key in the registry and deleted it (I did make a backup first just in case): HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-DxpTaskRingtone
Once the key was deleted, the errors went away immediately and did not return even after a restart. This also did not seem to break any other processes that I can tell. Everything appears to be functioning normally and Server Manager is happy.
TLDR; Open Event Viewer and see if a Query Error pops-up when it opens. If so - find, backup, and then delete the registry key, and the error should be gone.
stowellg2000 thank you very much for posting your workaround.
On the issue of it cannot hurt to recompile MOF. It shouldn't be done.
Please have a read. It seems that important, that it was linked in the OP by the same author in his techcommunity article from 2009.
- This problem usually occurs when the Windows Server 2022 is part of a Failover Cluster. It's reproducibly the case then. Please contact support to raise the chance for a fix.
Yes there are no negative impacts despite being irritating and soak people into useless troubleshooting.
I have to file a bug report but the blocker I've changed my company and role and need to get into things.
"One cannot simply open a support case (walk) for on-premises products (into Mordor)" - BoromirDanAshby can you help me here eventually, to file a bug report and asking for a backport of the fix from Azure Stack HCI 23H2 to WS 2022. I am unsure if it's fixed in 2025 b26100. Not tested that.
