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 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?
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
Same situation in our brand new Windows Server 2022 cluster.
After the described "repair" everything is back in the green zone.Is and remains a very ugly BUG.
Unfortunately, I don't have enough resources at the moment to report the issue to MSFT in a way that takes it seriously.UPDATE
After the next restart of the cluster nodes, the problem is back again 😕
- Hello, My customer run a Windows2019 Std server as WSFC cluster 2nodes.
I have exactly same problem since last April.
I tried some modification .... and finally get resolved.
I see that the cause of issue was "WSMAN", Windows Remote Management service.
I followed an instruction here :
> https://www.checkyourlogs.net/fixed-s2d-cluster-data-retrieval-failures-occurred-error/
Run Powershell as Administrator
Command :
Get-WSManInstance -ResourceURI winrm/config
Set-WSManInstance -ResourceURI winrm/config -ValueSet @{MaxEnvelopeSizekb = “700”}
Then the Server Manager shows only "Online" .... !
Hope everybody to get to the same happy-end. Makotosigh, you are giving a great reply to the wrong question - that solution is for a DIFFERENT data retrieval error. This thread is not about max envelope size. It is about certain event logs being missing or corrupted as show in the event log on the server ilke this
- This worked for me!
Thanks alot!
I rebuilt a 3-node cluster with Server 2022 Data Canter over a dozen times, I even rebuilt the DC on each occasion to reduce the chance of left over or invalid settings in the metadata. Every time, I was able to get a perfect cluster with no errors or warnings on the cluster diagnostic tests however as soon as the first server rebooted after creating the cluster, these errors started on all nodes and they even applied to the local server, ie. server1 couldn’t access its own logs according to the warnings. Even leaving the systems for 24 hours in case the errors went away had no effect.
I am not sure if ignoring these warnings would have any long-term effect on the running of the system, I couldn’t find anything online about the repercussions of doing this and I didn’t want to take a chance since this will be a production environment hosting my customers VMs and data.
The final straw was that I changed from using Server 2022 to Server 2019 Datacentre (just as a test), leaving everything else identical down to the server names, procedures I used and the order in which I performed them, the passwords and user accounts, everything identical other than the version of Server I installed and I didn’t get ANY of these data retrieval warnings, everything worked perfectly first go. I can only assume that there is a major bug in Server 2022 or at least a bug that happens when using my combination of hardware, all desktop 12th gen i9-12900K CPU, 128GB DDR4, and Z690 motherboards. and Dell / Intel dual copper 10GB ethernet adapters, 4 x 9tb HDDs, 3 x 2TB NVMe SSDs and OS drive on each server node and a smart 10GB switch and brand new cat7 cables.
I made sure to install all available updates and drivers at each stage of the setup on each node, made sure the hardware and software was exactly the same on all nodes, I followed all the various online suggestions like changing registry keys, changing permissions on the winevt folder and winevt\data folder, wiping the logs and starting fresh, giving all cluster nodes and objects permissions as domain, local and enterprise admins, and nothing worked for me. I did come across a few "fixes" online that simply supressed the warnings but none of them actually fixed the cause of the warnings. I can only assume the warnings are correct and there were issues with accessing logs so supressing the warning messages was not a proper solution since the problem isn’t fixed, its just hidden from view.
My advice to anyone who can, is to change to Server 2019 if you aren’t able to get things working with 2022 - perhaps MS will create a patch to fix this problem but as of writing this, June 12 2023, I found it impossible to setup a stable working cluster on server 2022 despite over a dozen tries, each time with a completely clean slate, wiped drives and fresh DC.
- Windows Server 2022 clusters are stable, it's a cosmetic issue in Server Manager. Everything else runs fine in production and issues otherwise are not related to this.
- I'm finding the same, I had a cluster working with a working Cluster Shared Volume too and now it wont work, currently feel like I'm sat with 30k's of dead server, I cant migrate my production environment into!
Hello, My customer run a Windows2019 Std server as WSFC cluster.
I have exactly same problem since last April.
I tried some modification .... and finally get resolved.The cause of issue was "WSMAN", Windows Remote Management service.
I followed an instruction here :
> https://www.checkyourlogs.net/fixed-s2d-cluster-data-retrieval-failures-occurred-error/
Run Powershell as Administrator
Command :
Get-WSManInstance -ResourceURI winrm/config
Set-WSManInstance -ResourceURI winrm/config -ValueSet @{MaxEnvelopeSizekb = “700”}Then the Server Manager shows only "Online" .... !
Hope everybody to get to the same happy-end. Makoto
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!
- try this at your own risk
#fix servermanager events
$VerbosePreference = 'SilentlyContinue';
$delete = $true;
$backup = $true;
$backupRoot = "c:\temp";
$code45 = "Failure opening metadata of the owning provider for channel";
$code46 = "Generic failure querying the localized name for channel";
$rkey = "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels";
if ($backup) { REG EXPORT $rkey "$backupRoot\channels.reg" /y }
$slogs = Get-WinEvent Microsoft-Windows-ServerManager-MgmtProvider/Operational | Where-Object Id -In 45, 46 | Select-Object message -Unique;
if ($null -ne $slogs) {
$smessage = $slogs.message;
$smessage | ForEach-Object {
if ($_ -match $code45 -or $_ -match $code46) {
$eventId = $_.Split(":").Split("[")[1].Trim();
$finalkey = "$rkey\$eventId";
$targetreg = $eventId -replace '/', '-';
$finalfile = "$backupRoot\$targetreg.reg";
if ($backup) { REG EXPORT $finalkey $finalfile /y }
if ($delete) { REG DELETE $finalkey /f }
}
}
#Restart-Service EventLog -Force;
restart-computer -force
}- I appreciate the suggestion but I have no idea what key it's trying to delete?
- Hi All.
I can confirme server manager issue was resolved by performing WMI repository autorecover steps today.
Elevated prompt:
cd C:\Windows\System32\wbem\Autorecover
for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
Close Server Manager and relaunch. Data will start to flow back in and then you see what genuine items you need to attend to.
Originally I found this post as I already had repaired WMI and MECM agent and was awaiting hardware inventory (HINV), however the HINV was stuck on collecting server features. This was a historical issue with this server (Server 2016 and SQL 2016). So even this was solved due to WMI correction and MOF registration.
Nice work shout out to Austin_M and PharmaConsult.
Don't hide issues by editing Registry. Solve your issues at the root cause.- didn't work with mine - guess I've got bigger problems
Hi,
Unfortunately, performing WMI repository autorecover did not help me and the error still appears in the server manager and in the event viewer when opening Administrative Events. I returned the reg key with the enabled option and reset the server. I did the procedure according to the instructions, but unfortunately the error still occurs. I also tried to reset the server after the procedure, but it didn't help.
A strange thing appears in the log:
WARNING: File 01C0F3A81F9A4314BBA9813A02D602AA.mof does not contain #PRAGMA AUTORECOVER.
Here is the log:
Microsoft Windows [Version 10.0.20348.1129]
(c) Microsoft Corporation. All rights reserved.C:\Windows\system32>cd wbem
C:\Windows\System32\wbem>cd AutoRecover
C:\Windows\System32\wbem\AutoRecover>for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s
C:\Windows\System32\wbem\AutoRecover>mofcomp 00744A75F86D5BA0D35F673723E49EBE.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 00744A75F86D5BA0D35F673723E49EBE.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 01C0F3A81F9A4314BBA9813A02D602AA.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 01C0F3A81F9A4314BBA9813A02D602AA.mof
MOF file has been successfully parsed
Storing data in the repository...
WARNING: File 01C0F3A81F9A4314BBA9813A02D602AA.mof does not contain #PRAGMA AUTORECOVER.
If the WMI repository is rebuilt in the future, the contents of this MOF file will not be included in the new WMI repository.
To include this MOF file when the WMI Repository is automatically reconstructed, place the #PRAGMA AUTORECOVER statement on the first line of the MOF file.
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 079AAE2A462B9E15D843B46ABA01B257.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 079AAE2A462B9E15D843B46ABA01B257.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 08C18351E9E713EB47A11790CA0CE94A.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 08C18351E9E713EB47A11790CA0CE94A.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 0CF494C661F4CE4927C40F5293B1309C.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 0CF494C661F4CE4927C40F5293B1309C.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 0F9498A8C3A78092022C9CC49955C6EC.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 0F9498A8C3A78092022C9CC49955C6EC.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 135B74A698486C6F06BDC384690867B6.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 135B74A698486C6F06BDC384690867B6.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 15046DBDCBEEF92CCD2BEFEF67A544E2.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 15046DBDCBEEF92CCD2BEFEF67A544E2.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 1B054D14ED32B6C986A4B80A1971B507.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 1B054D14ED32B6C986A4B80A1971B507.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 1D554E50A17FD1E08ECF90A5936D29E4.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 1D554E50A17FD1E08ECF90A5936D29E4.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 1DE7BE7BA35D977F49656C02C66058FC.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 1DE7BE7BA35D977F49656C02C66058FC.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 21BD8E9B6A3575C7E6CFD05471F4DE86.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 21BD8E9B6A3575C7E6CFD05471F4DE86.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 26514409CC4910118B040726189DED3D.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 26514409CC4910118B040726189DED3D.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 270E6F495B767FBDF4DB07F5DE16055F.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 270E6F495B767FBDF4DB07F5DE16055F.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 2D291BC2C93E41CE963CDDECD5CEEDC9.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 2D291BC2C93E41CE963CDDECD5CEEDC9.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 2E6E576003AC48B631A669B2932BB1C2.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 2E6E576003AC48B631A669B2932BB1C2.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 343E2AF1057A8BA8148BB735067E817A.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 343E2AF1057A8BA8148BB735067E817A.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 3A01647A9113490045B9D4AE10390941.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 3A01647A9113490045B9D4AE10390941.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 4232C9D6829B409B5D825D0F97ACEC63.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 4232C9D6829B409B5D825D0F97ACEC63.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 44BD58CF87D84E4D08B2223F1EDD24E4.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 44BD58CF87D84E4D08B2223F1EDD24E4.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 4D06958C26E8EE4ED93ADDC0E43A3DFB.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 4D06958C26E8EE4ED93ADDC0E43A3DFB.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 54BDD8DB6504771BB43BAAA596324930.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 54BDD8DB6504771BB43BAAA596324930.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 5B56FCB55A56653EDA41E8A7D5D36A32.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 5B56FCB55A56653EDA41E8A7D5D36A32.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 61D69B6E1564ACF7B6E32F6D0B951CF5.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 61D69B6E1564ACF7B6E32F6D0B951CF5.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 669532D3E0C12013ED00C40C8307310F.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 669532D3E0C12013ED00C40C8307310F.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 69D23F5E6BF4F0DA0498649351B6046D.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 69D23F5E6BF4F0DA0498649351B6046D.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 6EF6778A71129DDBCE093A02799E28DD.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 6EF6778A71129DDBCE093A02799E28DD.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 6FC2693FFECCC30FD2B0C42B0443B9C9.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 6FC2693FFECCC30FD2B0C42B0443B9C9.mof
MOF file has been successfully parsed
Storing data in the repository...
WARNING: File 6FC2693FFECCC30FD2B0C42B0443B9C9.mof does not contain #PRAGMA AUTORECOVER.
If the WMI repository is rebuilt in the future, the contents of this MOF file will not be included in the new WMI repository.
To include this MOF file when the WMI Repository is automatically reconstructed, place the #PRAGMA AUTORECOVER statement on the first line of the MOF file.
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 7073EBB8E2F3C70E0FA1F650B7DEA970.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 7073EBB8E2F3C70E0FA1F650B7DEA970.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 7989C664815B7AF909AB221E34890DEA.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 7989C664815B7AF909AB221E34890DEA.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 7DFE8C6791931712E5E8C76E2B3612A6.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 7DFE8C6791931712E5E8C76E2B3612A6.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 7E9A06269FE9F368EE7F5DF6350AA315.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 7E9A06269FE9F368EE7F5DF6350AA315.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 85CE57E0C8E10DD2E6175DA8B8C40F48.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 85CE57E0C8E10DD2E6175DA8B8C40F48.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 8742AF6B78D6A2FC4AB9AC090C6E391E.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 8742AF6B78D6A2FC4AB9AC090C6E391E.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 88744D2A29102FC88ECF505DD2E984FC.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 88744D2A29102FC88ECF505DD2E984FC.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 88F6A2F38C8C6430B59F31477479C304.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 88F6A2F38C8C6430B59F31477479C304.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 8BA70471D298E2919940ACECA2CC9754.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 8BA70471D298E2919940ACECA2CC9754.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp 8E599464072F15C56474A50D8756349A.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: 8E599464072F15C56474A50D8756349A.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp A359F193EB73A77290BA1CA931BC06CB.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: A359F193EB73A77290BA1CA931BC06CB.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp A5E01B1838C9AEEA0C0CC412768C8A01.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: A5E01B1838C9AEEA0C0CC412768C8A01.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp AC220A8791FC6D7B8E8F2B26C21FE74A.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: AC220A8791FC6D7B8E8F2B26C21FE74A.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp ADC76C6473F1C3722A0A86C2A9AED340.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: ADC76C6473F1C3722A0A86C2A9AED340.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp AE3832D9BEFB84DEB5BB187912DF2345.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: AE3832D9BEFB84DEB5BB187912DF2345.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp B355992E8BD649C24023BB7FD49A4C6F.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: B355992E8BD649C24023BB7FD49A4C6F.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp B8B54A0F9FF06190F8DF8AFE871AD0BA.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: B8B54A0F9FF06190F8DF8AFE871AD0BA.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp C178855BCF87ACB74F467532808B7EA6.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: C178855BCF87ACB74F467532808B7EA6.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp C599AFA5A6F053BAD70179501868318E.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: C599AFA5A6F053BAD70179501868318E.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp C59FAE5604BA27360FE3C8145302C43C.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: C59FAE5604BA27360FE3C8145302C43C.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp C8463ECBE33BC240263A0B094E46D510.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: C8463ECBE33BC240263A0B094E46D510.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp D0A59D2AF9A904A77DC6E7C92B8A3E0C.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: D0A59D2AF9A904A77DC6E7C92B8A3E0C.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp D5D286F205A8518EDCCF33465D7869CD.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: D5D286F205A8518EDCCF33465D7869CD.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp D5D6BB480217F9DCEC357F57222DEE59.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: D5D6BB480217F9DCEC357F57222DEE59.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp D9B050B7A24E09624652E41AC4639DDE.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: D9B050B7A24E09624652E41AC4639DDE.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp DF66BF7FE8B151CD01B5A759CD88E60A.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: DF66BF7FE8B151CD01B5A759CD88E60A.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp E449DF8E37B700427A984BAC1AD11EF0.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: E449DF8E37B700427A984BAC1AD11EF0.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp E64DEFC698F67BCC2EBDE5C8BB24CA93.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: E64DEFC698F67BCC2EBDE5C8BB24CA93.mof
MOF file has been successfully parsed
Storing data in the repository...
WARNING: File E64DEFC698F67BCC2EBDE5C8BB24CA93.mof does not contain #PRAGMA AUTORECOVER.
If the WMI repository is rebuilt in the future, the contents of this MOF file will not be included in the new WMI repository.
To include this MOF file when the WMI Repository is automatically reconstructed, place the #PRAGMA AUTORECOVER statement on the first line of the MOF file.
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp E75B84BF30D37D54881678B1E35246BC.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: E75B84BF30D37D54881678B1E35246BC.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp ED57484AAC7475D8631352D817AB6A43.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: ED57484AAC7475D8631352D817AB6A43.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp F4F9B78B4B4537617EAF17FFC1BB4624.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: F4F9B78B4B4537617EAF17FFC1BB4624.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp F7D2F5DD6AD538F08A78FE75923B0C37.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: F7D2F5DD6AD538F08A78FE75923B0C37.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp F868406B4813AB4041346B98EFFA5DA7.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: F868406B4813AB4041346B98EFFA5DA7.mof
MOF file has been successfully parsed
Storing data in the repository...
WARNING: File F868406B4813AB4041346B98EFFA5DA7.mof does not contain #PRAGMA AUTORECOVER.
If the WMI repository is rebuilt in the future, the contents of this MOF file will not be included in the new WMI repository.
To include this MOF file when the WMI Repository is automatically reconstructed, place the #PRAGMA AUTORECOVER statement on the first line of the MOF file.
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp FAB4FD1F41BAD00B53FE8A2B9DD19520.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: FAB4FD1F41BAD00B53FE8A2B9DD19520.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>mofcomp FBC22038FB1BD86499891CF935882F20.mof
Microsoft (R) MOF Compiler Version 10.0.20348.1
Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
Parsing MOF file: FBC22038FB1BD86499891CF935882F20.mof
MOF file has been successfully parsed
Storing data in the repository...
Done!C:\Windows\System32\wbem\AutoRecover>
- Try perfmon.msc /s and remove the offender.
Martinik Amigo yo tenia ese mismo problema con Windows Server 2016 y me di cuenta que el problema era de hora y fecha que no estaban bien
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
We have exactly the same problem. Server 2022 in 2-node Failover Cluster.
We use Intel(R) Ethernet Converged Network Adapter X710 10 GB in SET mode dedicated only for Hyper-V and Intel(R) PLAN EM 1GB T OCP, two ports in Teaming for only Cluster network. There is also an additional error with Microsoft-Windows-Kernel-IoTrace/Diagnostic when opening the event viewer - administrative events see picture.At the beginning, we didn't have any problems, but when testing live migration of virtual machines and higher network load, one of our nodes crashed and after that, errors occurred, but everything is still working properly now for several month.
By changing the registry the errors can be removed but I don't know if that's the right way?Hi,
I have absolutely no problems with the cluster. The errors never appeared again after I deleted that key. Now my cluster has been in production for 15 months. I really don't have any problems. All cumulative and other updates are installed properly and until now, no one has returned that key.
I haven't tried the fixes above because everything works fine for me.
After all, if a problem arises, the registry key can always be restored...
Regards,
Zeljko
No. I'm still waiting for an answer from the Microsoft team, if they have one. 🙂
Martinik Did you solved this problem? I have the same error on Windows Server 2022. I don't want to change the register HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic.
- I have had the same issue like yours for several days:
2-member nodes in a cluster have the same problem once restarting each.
I have fixed it just very simple by changing a register keyword like this:[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic]
"Enabled=dword:1"
modify to
"Enabled=dword:0"
That is ok to solve this problem perfectly!
regards!
