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?
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
}
#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?
Great news everyone. I am seeing this one fixed after in-place upgrade of Azure Stack HCI 22H2 to 23H2
Azure Stack HCI 22H2 clustered nodes are affected by this, same as Windows Server 2022 clustered nodes
Hope that this fix could be backported.
Please leave me like if you want to see this one fixed in Windows Server 2022, too.
- Yes, please fix it in Server 2022. It's going to be around as a customer OS for a while yet.
I have the same issue Environment: 2 node win server 2022 with cluster and sql 2022 alway on mode . I solved removing Antivirus and also win defender. I tried on 2 clean environment with same servers infrastructure and every time the solution is the same....No AV or defender installed.
steve-down the script will backup and delete any key(s) found to cause an issue. i found this works on all server version server managers 100% of the time.
- Hi to all
My environment are two server 2022 with Exchange 2019 installed in a DAG.
I solved the problem with:
https://blog.expta.com/2022/11/fix-for-online-data-retrieval-failures.html
I hope this helps someone- I have a GPO which raises this already. The errors typically occur when roles are removed or inplace upgrades occur. New installs should consider default WinRM params as needed. Inplace upgrades will add/remove events that may no longer be relevent, same with roles/features.
