Online - Data Retrieval Failures Occurred Windows Server 2022 __exclusive__ -

: The most frequent culprit is the Microsoft-Windows-Kernel-IoTrace/Diagnostic channel, which can become corrupted or lose its metadata .

Environment variables:

Alternatively, some users recommend doubling the default 512,000 to winrm set winrm/config @MaxEnvelopeSizekb="1024000" in Command Prompt 2. Reset the Kernel-IoTrace Diagnostic Channel

: When managing nodes remotely or within complex Windows Server Failover Clusters (WSFC) and Exchange Database Availability Groups (DAG), the volume of manageability data frequently exceeds the default maxEnvelopeSize limit of 512 KB. While the error appears in non-clustered environments, it

While the error appears in non-clustered environments, it is particularly common in Windows Server 2022 . In a cluster, Server Manager must retrieve consolidated data from multiple nodes, and its internal mechanisms are subject to the same constraints of WinRM packet sizes, permissions, and log integrity. Any break in this data flow from a single node can trigger the error for the entire cluster view. In some cases, you may see a bidirectional issue where Server DCB01 cannot retrieve data from DCB02, and vice versa .

To verify that WinRM is listening properly on the correct ports (5985 for HTTP, 5986 for HTTPS), use: powershell winrm e winrm/config/listener Use code with caution.

Did this error start appearing immediately after installing a ? In some cases, you may see a bidirectional

If you are in a clustered environment (like an Exchange DAG), try increasing the maxEnvelopeSize to allow larger data transfers. Run this command in an Administrative Command Prompt : winrm set winrm/config @MaxEnvelopeSizekb="8192" .

Set-NetConnectionProfile -InterfaceIndex -NetworkCategory Private Use code with caution.

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 Invoke-WebRequest https://www.howsmyssl.com/a/check -UseBasicParsing Event ID: 98 .

Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic in the Registry Editor. Change the value from 1 to 0 .

Schedule via Task Scheduler with trigger: On event – Log: System, Source: Ntfs, Event ID: 98 .

If a channel is identified as broken, you can force Windows to rebuild its metadata. Registry Editor Navigate to:

Get-NetFirewallRule | Where-Object $_.Direction -eq "Outbound" -and $_.Action -eq "Block"

Are you seeing this error on a or within a Failover Cluster ?