Forum Discussion
Solved
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 c...
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?
Hello Martinik,
The error shown above is a server manager issue. Thus it gave us an error "data retrieval failures occurred" while retrieving the data from the server manager.
Here are the steps you can follow to overcome the data retrieval failure occurred issue,
Open the command prompt with administrator access and execute the below command:
cd C:\Windows\System32\wbem\Autorecover
Now, /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
When the above command completes, you can start the Server Manager and start adding roles and features again.
If this doesn't work, you can check the below fixes,
The error can also be caused when the system cannot find the specified file.
HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > then, Windows > CurrentVersion > WINEVT > Channels > Microsoft-Windows-DxpTaskRingtone > Analytic
"ChannelAccess" -> "O:BAG:SYD:(A;;0xf0007;;;SY)(A;;0x7;;;BA A;;0x3;;;BO)(A;;0x5;;;SO)(A;;0x1;;;IU > (A;;0x3;;;SU)(A;;0x1;;;S-1-5-3)(A;;0x2;;;S-1-5-33)(A;;0x1;;;S-1-5-32-573)
Enabled = dword:00000000
Isolation= dword:00000001
"OwningPublisher"="{3df0c2c1-5a04-4966-9790-df6ef0ccde9c}"
Type -> dword > 00000002
You should compare the above to other entries. Looking at the Isolation and Type of other entries, this should not even show up in the event log. You must edit the key's name and ensure that it disappears from the event log. Then, try changing the name back and check if gone or persists.
Lastly, refresh the Server Manager and check if it became green, but if you see red, then back up the key and delete it. Thus, with the key gone, the server manager also refreshes without any error, and all of my manageability icons will get green without giving any error.
I hope the above solution will work for you to fix the data retrieval failure error.
-----------------
Regards,
Austin_M
Hi, when I write /f %s in ('dir /b *.mof *.mfl') do mofcomp %s in C:\Windows\System32\wbem\Autorecover it shows an error 😞
