Server 2019 Server Manager Dashboard Red

Winona 0 Reputation points
2024-03-25T13:32:48+00:00

Hello,

I ran some updates on my SQL server and when it came back online, I am getting red across my entire dashboard in server manager. The roles I have installed are AD LDS, File & Storage, Hyper V and IIS. The item that is red on all of them is manageability. The error is, "Online - Cannot get event data". I have obviously done a few reboots to clear. I am at a loss of what else to try, so I am hoping someone has ran across this particular error and knows how to resolve it. Any help would be appreciated.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,749 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Daisy Zhou 23,806 Reputation points Microsoft Vendor
    2024-03-26T02:20:11.0166667+00:00

    Hello Winona,

    Thank you for posting in Q&A forum.

    The "Online - Cannot get event data" error in the Server Manager dashboard can be indicative of various underlying issues. 

    Here are some steps you can take to troubleshoot and potentially resolve the problem: 

    1.Check Event Viewer: The first step is to check the Event Viewer for any specific error messages that might give more insight into what's going wrong. Look under Windows Logs > Application and Windows Logs> System, look for any critical errors or warnings that occurred around the time you noticed the issue. 

    2.Windows Management Instrumentation (WMI) Service: The Server Manager relies on the WMI service to gather information about the roles and features installed on the server. Ensure that the WMI service is running by checking the Services console ("services.msc"). If it's not running, start the service and see if that resolves the issue. 

    3.Rebuild WMI Repository: If the WMI service is running but you're still experiencing issues, the WMI repository might be corrupted. You can rebuild the WMI repository by running the following commands in an elevated Command Prompt: 

    net stop winmgmt winmgmt /resetrepository 

    net start winmgmt

     

    Note: Rebuilding the WMI repository can cause loss of information and should be done with caution. 

    4.System File Checker (SFC): Run the System File Checker tool to repair missing or corrupted system files. Open an elevated Command Prompt and run the following command: 

    sfc /scannow 

    5.DISM Tool: If SFC doesn't resolve the issue, you can use the Deployment Image Service and Management Tool (DISM) to repair Windows images. 

    Run the following commands in an elevated Command Prompt: 

    DISM /Online /Cleanup-Image /CheckHealth

    DISM /Online /Cleanup-Image /ScanHealth 

    DISM /Online /Cleanup-Image /RestoreHealth

     

    6.SQL Server Logs: Check the SQL Server error logs to see if there are any indications of issues with the SQL Server itself. You can find the error logs in SQL Server Management Studio under Management > SQL Server Logs. 
    7.Check for Updates: Sometimes, subsequent updates can fix issues introduced by earlier ones. Make sure your server is fully updated with the latest patches and updates from Microsoft. 

    8.Consider Rolling Back Updates: If the issue started after installing specific updates, consider removing those updates to see if it resolves the issue. You can do this from the Control Panel under Programs and Features > View installed updates. 

     

    Remember to back up any important data before making significant changes to your system, and proceed with caution when making changes to system services and files.

    I hope the information above is helpful.

    If you have any questions or concerns, please feel free to let us know.

    Best Regards,

    Daisy Zhou

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.