Online Data Retrieval Failures Occurred Server 2012 r2: Solution

Learn how to resolve the erro online data retrieval failures occurred server 2012 r2. Our Server Management Support team is here to help you with your questions and concerns.

Error: online data retrieval failures occurred server 2012 r2

Online data retrieval failures may happen when there is a communication issue between the computer and the server hosting the website we are attempting to access.

Symptoms For online data retrieval failures occurred server 2012 r2

A newly deployed 2 x AX650 cluster has been set up, and TSR along with Cluster Diagnostic information has been provided. The error message “Hyper-V Manageability – Online Data Retrieval Failures Occurred” has appeared. Some research has been conducted, but further guidance would be helpful.

Symptoms For online data retrieval failures occurred server 2012 r2

Several factors can contribute to online data retrieval failures, disrupting communication between a server and the required resources. Below are the most common causes:

• Corrupted Event Log: The Microsoft-Windows-Kernel-IoTrace/Diagnostic log may be damaged, preventing proper data retrieval.
• Network Instability: Unstable or slow network connections can hinder access to online resources.
• System File Issues: Missing or corrupted system files may impact the system’s ability to retrieve data.
• DNS Configuration Problems: Incorrect DNS settings or unreachable DNS servers can interfere with data requests.
• Server Misconfiguration: The server may have incorrect settings that affect its performance.
• Scripting Errors: Faulty scripts within the server may cause retrieval issues.
• Temporary Server Overload: High traffic or excessive load may slow down server responses.
• Out-of-Memory (OOM) Issues: Insufficient memory allocation can impact performance.
• Unhandled Exceptions: Errors that the server cannot process may cause failures.
• File Permission Errors: Incorrect permissions may restrict access to necessary files.
• Network-Related Issues: Problems within the network can disrupt communication.
• Server Downtime: The server may be undergoing maintenance or temporarily unavailable.
• User Settings and Configurations: Misconfigured user settings could interfere with system functionality.

Identifying and addressing these issues promptly can help restore normal operations and prevent future disruptions.

Solution

Patching Windows Server 2022 (the target OS for remote management) resolved the issue. Since a corrupted Microsoft-Windows-Kernel-IoTrace/Diagnostic event log causes this problem, we can disable the log by following these steps on both nodes:

Steps to Disable Microsoft-Windows-Kernel-IoTrace/Diagnostic Event Log

1. Log in to the target terminal with administrator privileges.
2. Open Windows PowerShell as an administrator.
3. Check the current DumpPolicy value by running the code given below:

   (Get-Cluster).DumpPolicy

   Example Output

   Code: PS C:\Users\Administrator> (Get-Cluster).DumpPolicy 1376850201
4. Convert the decimal value to binary using an online converter

   Example conversion:

   1:

   Decimal: 1376850201

   2:

   Binary: 01010010000100010001000100011001
5. Modify the binary value by changing the 21st bit from the right to 0.

   Example conversion:
   1:

   Before: 01010010000100010001000100011001

   2:

   After: 01010010000000010001000100011001
6. Convert the modified binary value back to decimal.

   Example conversion:
   1:

   Binary after change: 01010010000000010001000100011001

   2:

   After: 01010010000000010001000100011001
7. Apply the new value:

   (Get-Cluster).DumpPolicy=1375801625
8. Verify the updated value by running:

   (Get-Cluster).DumpPolicy

   Example OutPut

    PS C:\Users\Administrator> (Get-Cluster).DumpPolicy 1375801625
9. Disable the event log in the Windows Registry:

   1: Open Registry Editor and navigate to:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Kernel-IoTrace/Diagnostic

   2: Modify the Enabled key:

   Name: Enabled
   
   Type: REG_DWORD
   
   Value: 0
10. Restart the system to disable the:

    Microsoft-Windows-Kernel-IoTrace/Diagnostic event log

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

By following these steps, we successfully disabled the Microsoft-Windows-Kernel-IoTrace/Diagnostic event log and resolved the online data retrieval failure. Additionally, ensuring that Windows Server 2022 is fully patched helps prevent similar issues in the future.

With the support of Bobcares server management services, we effectively cleared the “Online Data Retrieval Failures Occurred” issue on Windows Server 2012 R2. Regular monitoring, proper server configuration, and proactive maintenance are essential to keeping systems stable and minimizing disruptions.