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?
I hope this helps for the rest of you too.
I have a Hyper-V 2022 cluster setup with 2 nodes and have the same issues described in this thread.
Errors that I have:
- Errors in de server manager with “Online – Data retrieval failures occurred”.
- Error when opening the event viewer to show administrative events.
The solution for me was as following and is important to follow the order as below:
Add the affected node itself (computer object) to the local group "Event Log Readers".
If you got CAU configured then also add the computer object of CAU as show below.
Next step is to disable the REG_DWORD "Enabled" value from 1 to 0 in the key "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic".
Reboot the node. The registry value that we have changed from 1 to 0 should be enabled back to 1 after reboot. It does this automatically, at least it does in my situation.
Follow the same steps described above on the second node. All errors mentioned should go away.
Give it a try and check if this also solves it in your environment.
Regards.
SekoBayo, thank you.
The problem appeared after setting up CAU, and this seems to be the solution for me.
I would only recommend trying this, or even just part two of it, if you see the following error message in the log:
Generic failure querying the localized name for channel: Microsoft-Windows-Kernel-IoTrace/Diagnostic [hResult = Function failed during execution., hLastResult = The instance name passed was not recognized as valid by a WMI data provider.].
Log location: %SystemRoot%\System32\Winevt\Logs\Microsoft-Windows-ServerManager-MgmtProvider%4Operational.evtx
In my case the registry value reverted itself after restarting the nodes. Weird, but okay.
Hi All,
I have found out that this message appeared in my case when my user authorizations was changed from Administrator to Standard user and then reverting back to Administrator (with Settings->Add,Edit User). The solution was to remove the Standard user group in Control Panel-User Accounts- Give Users access to this computer - Users for my user.
Thanks.
BR M
