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?
Durable solution for now is here for me:
https://learn.microsoft.com/en-us/answers/questions/643354/server-manager-problem-online-data-retrieval-failu.html?page=1&pageSize=10&sort=oldest
Hi, after backup I just deleted REG_DWORD "Enabled"=dword:00000001 that's enough so that the error no longer appears.
I can only confirm that after 5 months, the cluster production works properly without the errors mentioned above or any system crashes.
The REG_DWORD 'Enabled' is still deleted from the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic on both cluster nodes and I haven't found any other solution except deleting REG_DWORD 'Enabled'
So, I spent a couple of days, on and off, trying this in many variations. It always started out looking hopeful, and then the log would reappear.
I found that this log was being created by a PerfMon Startup event trace session, so I went to PerfMon -> Data Collector Sets -> Startup Event Trace Sessions, and disabled the EventLog-Microsoft-Windows-Kernel-IoTrace-Diagnostic Session. I then ran Remove-AutoLoggerConfig -Name EventLog-Microsoft-Windows-Kernel-IoTrace-Diagnostic for good measure, to remove the setup. Then I rebooted.
Then I applied your change - I found Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic, and deleted the Enabled value. Then I rebooted.
When it came back up, at the start, things looked promising. I rebooted again, and again, and everything looked great. I went to a different machine and started applying the same "recipe". About 20 minutes later, I came back to the first machine, and the log is back.
There is _something_ going on somewhere, in a driver or some other component, that is reconfiguring this log in the background. I'm convinced of it. I just don't know what it is.
Thanks for the suggestion, though!
My 2 node cluster (Fujitsu PRIMERGY RX2540 M5) is working for now almost 6 months without problems with this DWord deleted but I would also like to know the real cause of the problem...
- I had do delete the whole node (not just the setting you highlight on the 25 errors i was getting.
given the error is generally "file not found" they are not logging anything so can be deleted - many of mine were for things not even installed on server - like broadband diags. I have a thesis that MS pushes out additional tracing and diagnostics for windows client and is applying it erroneously to windows server. tl;dr deleting the regist keys can't make the problem worse - these event logs were already not logging anything.... - Yeah, it's strange. I have seen _something_ spin this log back up again, even when the Microsoft-Windows-Kernel-IoTrace/Diagnostic key is completely removed.
- Maybe it's because you did additional actions as you wrote? Try with a fresh installation for test and just delete the key on both nodes.
