On [start date], the Windows Server 2022 environment began experiencing recurring failures when attempting to retrieve data from external online sources (APIs, cloud storage endpoints, and web services). These failures resulted in incomplete data synchronization, delayed batch processing, and application timeouts. Initial troubleshooting pointed to a combination of network configuration drift, TLS protocol mismatches, and Windows update-related changes.
The "Online - Data retrieval failures occurred" warning is most prominently displayed within the dashboard. Specifically, you will notice a " Manageability " error status listed for servers in your management pool, indicating that Server Manager is unable to collect or refresh management data for that node. In some cases, this may be accompanied by a " Configuration Refresh Failed " message. You might also experience a complete "Refresh Failed" error when attempting to manually refresh the view. Beyond the graphical user interface, the Event Viewer will often log accompanying errors. The two most frequent errors are a failure opening metadata for a specific event channel, commonly with the message "The system cannot find the file specified," or an Event ID 5858 , which typically points to a problem with the Windows Management Instrumentation (WMI) service.
Compare this section with a fresh Server 2022 installation, looking for File Services entries that should not be there. Summary Checklist Description Look for Kernel-IoTrace errors in Event Viewer . Delete Key
Provide Microsoft with:
To resolve online data retrieval failures on Windows Server 2022, try the following solutions: On [start date], the Windows Server 2022 environment
Fixing "Online – Data Retrieval Failures Occurred" on Windows Server 2022 If you’ve recently opened Server Manager
KB: Set-WSManInstance -ResourceURI winrm/config -ValueSet @MaxEnvelopeSizekb = "8192" .
Solution 1: Fix the Corrupted Kernel-IoTrace Diagnostic Channel
If you performed an in-place upgrade to 2022, outdated keys in ...\WINEVT\Channels from removed features (like File Services or Media Foundation) can trigger this error. 🛡️ Best Practices to Prevent Future Failures The "Online - Data retrieval failures occurred" warning
Incident Report: Online Data Retrieval Failures on Windows Server 2022
| Cause | Description | |-------|-------------| | | Temporary link flaps, iSCSI session timeouts, or FC/FCoE signal issues | | Corrupted metadata | Storage Spaces or CSV cache metadata mismatch | | Disk firmware issues | Outdated or buggy firmware on SSDs/HDDs | | Driver incompatibility | Storage controller drivers not fully compatible with Windows Server 2022 | | Sector read failures | Bad blocks in critical metadata regions (e.g., GPT header, LDM database) | | MPIO misconfiguration | Improper Multipath I/O settings causing path failures |
If you want, provide: cluster logs (Get-ClusterLog), relevant Event IDs/messages, results of Get-ClusterSharedVolume and Get-StoragePool outputs — and I’ll suggest next exact commands and remediation.
If the ServerManager-ManagementProvider log shows errors for missing or corrupt event providers, you can attempt to fix them. You might also experience a complete "Refresh Failed"
When this error appears, the Server Manager has been successfully able to connect to the target server (“Online”), but when it attempted to collect specific data points—such as event logs, performance counters, or the results of a Best Practices Analyzer (BPA) scan—the operation failed.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels .
Navigate to Applications and Services Logs > Microsoft > Windows > Kernel-IoTrace .