Other Reporting Issues

  • Article

Applies To: Operations Manager 2007 R2, Operations Manager 2007 SP1

The following table lists the issues that you might experience while you are using Operations Manager Reporting. It also includes the steps that you can take to resolve these issues.

Issue Resolution

SQL Reporting Error log (Default - %Program Files%\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\LogFiles):  System.Data.SqlClient.SqlException: Could not locate entry in sysdatabases for database 'Mom'. No entry found with that name. Make sure that the name is entered correctly.

This error occurs when you install Operations Manager Reporting on a SQL Server Reporting Services (SSRS) database that is using a custom name.  To fix the problem, reinstall SQL Reporting Services by using the default names of ReportServer and ReportserverTempDB.  Then, reinstall Operations Manager Reporting.

Reporting Services Configuration Manager shows Web Service Identity as Not configured.  When you try to configure the Web Service Identity, you receive the following exception - "ReportServicesConfigUI.WMIProvider.WMIProviderException: A virtual directory must first be created before performing this operation." (SQL 2005 specific)

This error occurs when the virtual directory was not configured correctly during the SQL Reporting Services (SRS) installation.  To fix the problem, do the following:

  1. In IIS Manager, delete the Reports and ReportServer Web sites under Default Web site.

  2. Create new Reports and ReportServer Web sites by using Reporting Services Configuration Manager:

    1. In Windows, click Start, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click Reporting Services Configuration.

    2. In the Report Server Installation Instance Selection dialog box, specify the name of the server that is hosting SQL Reporting Services, select the database instance from the list, and then click Connect.

    3. In Reporting Services Configuration Manager, click Server Status. Verify that Service Status is set to Running. If it is not, click Start, and then click Apply.

    4. Click Report Server Virtual Directory, and then click New to specify a new virtual directory.

    5. In the Create a New Virtual Directory dialog box, select Default Web Site from the Website list, specify a name for the virtual directory that is created by Reporting Services (or use the default ReportServer), and then click OK.

    6. Ensure that Apply default settings is selected, and then click Apply.

    7. Click Report Manager Virtual Directory, and then click New to specify a new virtual directory.

    8. In the Create a New Virtual Directory dialog box, select Default Web Site from the Website list, specify a name for the Report Manager virtual directory that is created by Reporting Services (or use the default Reports), and then click OK.

    9. Ensure that Apply default settings is selected, and then click Apply.

    10. Click Web Service Identity. If you do not want to change the default settings in this section, click Apply.

    11. Click Database Setup, and then click Connect.

    12. In the SQL Server Connection Dialog dialog box, specify the SQL Server name and connection details for the Reporting Services server, and then click OK.

    13. Click New.

    14. In the SQL Server Connection Dialog dialog box, specify a name for the new Reporting Services database (or use the default, ReportServer), and then click OK.

    15. Click Apply, and then click OK.

    16. Click Exit to close Reporting Services Configuration Manager.

  3. Restart the IIS Admin service.

Security event logs: “ Event Source: MSSQLSERVER Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <local machine>]” and “Event Source: Reporting Server (MSSQLSERVER) Report Server (MSSQLSERVER) cannot connect to the report server database.

This error occurs when the permissions for the SQL Report Server database are missing.  To fix this problem, reset the permissions by using the Reporting Services Configuration tool, as follows:

  1. Open Reporting Services Configuration Manager.

  2. Under Database Setup, update the Account Name to a domain account.

For more information, see https://go.microsoft.com/fwlink/?LinkID=144636.

Application event log: Application pool 'ReportServer' is being automatically disabled due to a series of failures in the process(es) serving that application pool.  (SQL 2005-specific)

This error occurs when the SQL Reporting Server Service is disabled due to multiple failures.  To fix this problem, run the IISReset.exe tool, available from https://go.microsoft.com/fwlink/?LinkID=39969.

Application event log:  SQL Server Reporting Service, Service cannot be started.  The user or group name ‘LocalSystem’ is not recognized

This error occurs when the Application Pool account is switched to LocalSystem.  To fix the problem, do one of the following:

  • Open IIS Manager, find ReportServer or ReportServer$InstanceName under Application Pools, and then set the Identity to a domain account.

  • Open Reporting Services Configuration Manager. Under Web Service Identity, update the ASP.NET Service Account to a domain account.