Other Reporting Issues
適用於: 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:
|
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:
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:
|