For IT system administrators, encountering unexpected errors on server infrastructure is a daily reality. One particularly common and frustrating issue that can arise in Windows Server 2022—as well as in previous versions like Windows Server 2019 and 2016—is the cryptic “Online – Data retrieval failures occurred” warning. This message typically appears within the interface, specifically in the “Manageability” column, and can cause significant concern as it suggests a breakdown in the server’s ability to report its own status.
This is a specific known quirk in WS2022 builds prior to 20348.169. The NVMe driver may report Online but generates Event 129 after 30 seconds of no read response. This is a specific known quirk in WS2022
Leftover or corrupted XML results from previous BPA scans can crash the console's parser. If you performed an in-place upgrade to Windows
If you performed an in-place upgrade to Windows Server 2022, removed features like "Media Foundation" or "File Services" may leave behind ghost registry entries. WINEVT\Channels If no value exists
You can also adjust the maxEnvelopeSize via the Registry. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WSMAN\Client . If no value exists, create a new DWORD (32-bit) named maxEnvelopeSize with a decimal value of 8192 (or higher) and restart the WinRM service.
When Server Manager queries local or remote nodes, it acts as an inventory aggregator. It pulls data via Windows Management Instrumentation (WMI) and Windows Remote Management (WinRM). If any underlying data provider fails to report cleanly, Server Manager halts the inventory collection and throws the generic data retrieval error.
Open diskmgmt.msc (Disk Management) to ensure all disks are visible and online.