Operations Manager Reporting - Resolving Those Errors
Sometimes working with Operations Manager Reporting and SQL Server 2005 Reporting Services can be a bit frustrating or challenging because the error displayed are often ambiguous. Some common situations I have come across are the following (including the solution):
Operations Manager 2007 Reporting Setup states "SRS Validation Error." Check the following:
- That SQL Reporting Services service is running.
- Verify you can access SRS by launching the browser and referring to URL's - https://[computername]/Reports and https://[computername]/ReportServer
- Verify the browser is not configured to use a configuration script in the connection settings or that if it is configured to use a Proxy Server, that you select the check box to bypass for local addresses. An HTTP Error 502 will be logged in the MOMReporting<n>.Log file.
- Execute the SQL Reporting Services Configuration tool and verify the configuration of SRS.
- Review the Reporting Setup log that is located in the temp folder of the user profile that you are logged on as. The log file is named - MOMReporting<n>.Log.
- Run the ResetSRS Tool located off of the Operations Manager 2007 media in the SupportTools folder. This will reset the configuration of SRS back to its default state. I recommend using this as an absolute last resort.
- Make sure you are logged on with an account that is a member of the Operations Manager Administrators role.
When you click on the Reports link in the Operations Console and you receive a HTTP Status Code error such as 401, 404, etc.
- Check the connection settings for the browser where you are running the Operations Console.
- Verify you can access SRS by launching the browser and referring to the two SRS URL's.
- Verify you can resolve the name of the server hosting SRS and the Operations Manager Reporting component.
Current KB Articles on the topic of installing Operations Manager Reporting are:
If I uncover other scenarios and solutions, I'll post an update.