Forum Discussion
Server Manager problem: Online - Data retrieval failures occurred
Has anyone come up with a DURABLE solution to this? One that survives more than one reboot? I tried the MOF rebuild, I tried removing the event log registry key, which worked on reboot to not register the log, but the registry key got set back every time on reboot, which turned out was from AutoLogger, which I removed with Powershell commands, but I can get it turned off for the next reboot, but the one after that will re-enable all of it again.
It seems like some component or driver is re-registering something, and I can't figure out what's doing it?
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...
- 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.
