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?
Karl-WE Do you have any further solutions for this? Adding the cluster object to Event Log Readers doesn't fix anything for me (Hyper-V Cluster with Server 2022 Standard on each host). Neither does adding the hosts to the same. I would rather not edit the registry if I can help it.
Thanks.
DB2024 This is proper solution: KB article from Dell. It fixed the issue.
Step to disable the event log Microsoft-Windows-Kernel-IoTrace/Diagnostic (Apply on both nodes)
- Log on to the target terminal as a user with administrator privileges.
- Start Windows PowerShell with administrator privileges.
- Execute the following command to check the current value.
Command: (Get-Cluster).DumpPolicy
Example execution result:
PS C:\Users\Administrator> (Get-Cluster).DumpPolicy
1376850201 - Convert the above decimal value to binary (converter tools)
The following are the values ​​in our verification environment, so please use the actual values. Decimal: 1376850201
Binary: 01010010000100010001000100011001 - Change the 21st value count from the right to 0 in the above binary number.
The following are the values ​​in our verification environment, so please use the actual values. Current value: 01010010000100010001000100011001
After change: 01010010000000010001000100011001 - Convert the above binary value back to decimal.
The following are the values ​​in our verification environment, so please use the actual values. Binary number after change: 01010010000000010001000100011001
Modified decimal number: 1375801625 - Execute the following command in Windows PowerShell started with administrator privileges. Command: (Get-Cluster).DumpPolicy=Modified decimal number
Example execution result: PS C:\Users\Administrator> (get-cluster).DumpPolicy=1375801625 (Nothing is displayed if successful.) - Confirm that the changed value is output by executing the following command again.
Command: (Get-Cluster).DumpPolicy
Example execution result: PS C:\Users\Administrator> (Get-Cluster).DumpPolicy 1375801625 - In Registry Editor, change the following registry data to 0 (disabled).
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic
Name: Enabled
Type: REG_DWORD
data: 0 - Restart the OS, Make sure the event log Microsoft-Windows-Kernel-IoTrace/Diagnostic is disabled.
S_DiasamidzeThanks for the reply, but that's not a fix for the issue at hand. Firstly, there's no reason to believe the event log is corrupted in my case, which is what the Dell article assumes. My hosts are all brand new installs. Secondly this just disables the event log in question, which is a workaround, not a fix. It makes the error go away (maybe) but it doesn't fix what's broken.
I'm having the same issue with Server 2022 Hyper-V Hosts.
Tried all the various fixes listed on this thread and nothing deals with the messages. I have the same type of errors in the ServerManager-ManagementProvider log, in the vein of "hLastResult = The system cannot find the file specified". ID's 46 & 46. But I have them on quite a number of logs. Here is about 60% of them.
Microsoft-Windows-Containers-CCG/Admin
Microsoft-Windows-Containers-Wcnfs/Debug
Microsoft-Windows-Containers-Wcnfs/Operational
Microsoft-Windows-International/Operational
Microsoft-Windows-Kernel-IoTrace/Diagnostic
Microsoft-Windows-Mobile-Broadband-Experience-Parser-Task/Analytic
Microsoft-Windows-Mobile-Broadband-Experience-Parser-Task/Operational
Microsoft-Windows-Mobile-Broadband-Experience-SmsRouter/Admin
Microsoft-Windows-Mobile-Broadband-Experience-SmsRouter/Analytic
Microsoft-Windows-NetworkStatus/Analytic
Microsoft-Windows-NFC-Class-Extension/Analytical
Microsoft-Windows-PackageStateRoaming/Analytic
Microsoft-Windows-PackageStateRoaming/Debug
Microsoft-Windows-PackageStateRoaming/OperationalDoes that hint at a deeper issue to everyone else's or is this pretty much just the same thing?
Thank in advance.
have you found a solution yet? I just setup a new cluster and have the same exact issue. AronVDavies
