Common Reporting Problems
適用於: Operations Manager 2007 R2, Operations Manager 2007 SP1
Permission and access errors can occur when SQL Server Reporting Services (SSRS) does not have the appropriate permissions that Operations Manager Reporting requires for its installation.
The following table lists the most common errors and their causes:
| Error | Cause |
|---|---|
When a user tries to open a report, they see a “Cannot initialize report” error message. |
Permissions are missing for the user. |
The program cannot determine if current user is in the sysadmin role. |
Permissions are missing for the SSRS database. |
A user receives an UnauthorizedAccessMonitoringException error message. |
The user does not have authorized access for SRS reporting. |
Loading the reporting hierarchy fails. |
The password for the Application pool has expired. |
A user receives an Account verification error message. |
The Account name for the reader is longer than 20 characters. |
To address these errors, try the following:
Add the Operations Manager Administrator group to the Administrators group on SQL Reporting Server.
Reconfigure SSRS for appropriate permissions by granting the “sysadmin” role on the SQL Reporting server to the user account that is running the Reporting installation.
In Reporting Services Configuration Manager, under Windows Service Identity and Web Service Identity, change the account to one that has Administrative permissions on the SQL Reporting Server.
Reset passwords.
Shorten account names to less than 20 characters.