Fix: Configuration Manager Status Message Retrieval Issue
In this article, I will explain how to fix the Configuration Manager status message retrieval issue that occurs on Windows servers. There are two solutions to address the status message retrieval issue in SCCM, and I am going to share both of these solutions in this article.
When I was working on a distribution point-related problem, I ran into another problem. With the configuration manager status message, I discovered a retrieval issue. In other words, the configuration manager was unable to retrieve status messages.
The Configuration Manager status message retrieval issue was observed on SCCM server installed on Windows Server with all the latest updates installed. I hadn’t seen this error before, so I wasn’t sure why it appeared in my setup. This issue is not related to the distribution point server that I was working on.
In some cases, Configuration Manager status message retrieval issue appears when the site server and SQL are installed on one system or the SMS Provider is installed on another remote system. Troubleshooting this issue is very tricky and fortunately, there are solutions available.
In Configuration Manager, status messages are the universal means for components to communicate information about their health to the Configuration Manager administrator. Status messages are similar to Windows NT Events; they have a severity, ID, description, and so on.
Also Read: How to View Content Distribution Status in SCCM | ConfigMgr
Configuration Manager could not provide the data that you requested
In the SCCM console, upon checking component messages under Monitoring > Overview > System Status > Component Status, I noticed some errors. The messages were displayed in the following sequential order: Clicking OK displayed the next message box.
- Configuration Manager could not provide the data that you requested. Please refer to the configuration manager documentation for troubleshooting.
- An unexpected error has occurred processing status messages [query not open]. Further processing for this query has been stopped.
- The status viewer was unable to retrieve the stored queries list from the database.
Recommended Article: 4 Tools to Translate SCCM Error Codes To Error Messages
Opening the Status Message Viewer and checking the status message for any component shows the below message box. Configuration Manager could not provide the data that you requested.
Clicking OK shows the other two message boxes.
- The status viewer was unable to retrieve the stored queries list from the database.
- An unexpected error has occurred processing status messages [Query Not Open]. Further processing for this query has been stopped.
If you keep getting the same errors when you try to get status messages in Configuration Manager, you can look through the SCCM log files to find major errors or warnings. Unfortunately, I couldn’t find anything important in the log files that helped me resolve this issue. I started to look for this error on the internet and found some answers. The solutions are listed in the next section.
Fix Configuration Manager Status Message Retrieval Issue
If you are encountering the configuration manager status message retrieval issue, you can resolve this issue with the below-mentioned solutions.
- Solution 1: Login to SCCM primary site server and open services console (services.msc). Right click SMS_EXECUTIVE and SMS_SITE_COMPONENT_MANAGER services and select Properties. Set the startup type to Automatic (Delayed Start). Finally, reboot the system after you make these changes. By implementing the delayed start of these services on the site server we ensure all required elements are starting in timely and sequential manner.
- Solution 2: If the above solution didn’t work for you, try this solution. Login to SCCM server and open services console. Restart SMS_EXECUTIVE and SMS_SITE_COMPONENT_MANAGER services. This method worked for many admins and resolved the above issue.
Need more help?
If you need further assistance on the above article or want to discuss other technical issues, check out some of these options.