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?
Hi all,
is anyone still affected by this issue. Could you please comment with
- the OS version and build of the remote management VM
- the OS version and build of the cluster nodes
I have tried to repro the issue with Windows Server 2022 RTM build 20348.169 and patched LCU 10-2024.
The clustered or not all nodes showed up as "Online".
Only VMs that were newer than the Management VM OS showed up with the respective error.
mgmt-2022 - OS: WS 2022 RTM
Management - OS: WS 2025 vNext
DC - OS: WS 2025 RTM
S2D-Clus01 Nodes S2D-101024-1 / Nodes S2D-101024-2 - OS WS 2022 patched LCU 10-2024
S2D-Clus02 Nodes WS2022-S2D1 / Nodes WS2022-S2D2 - OS WS 2022 RTM
Definitely affected by something that looks the same.
Not related to clusters, though.utcl_ken DG00
could it be that the OS where you are adding remote Windows Server in Server Manager is older than the target OS?
I mean imagine you have a WS 2022 cluster or DC and adding it to a WS 2019 Server Manager.Is there any difference doing the same adding remote servers in WS 2022 Server Manager?
Hi Karl,
So we just patched up to the November CU, and are still affected by this it seems.
DCs- OS:WS 2019 Version 1809 (OS Build 17763.6532)
Cluster Nodes 01-03 - OS: WS 2022 Version 21H2 (OS Build 20348.2849)
We're just managing directly from one of the cluster nodes. Issue occurs on every restart of a node.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?
from latest reports it is still unclear that the marked solution does not work for everyone. The situation is very inconsistent. The SR has been archived with no solution.
