I wanted to share a link that goes through all the install prerequisites for Management Reporter: http://www.jivtesh.com/2010/07/management-reporter-installation-guides.html.
I also wanted to share a few common causes and easy fixes for a Report Queue Status issue.
THE ISSUE: After generating a report, the Report Queue Status window lists the Status as Queued rather than Processing, and the report never finishes.
THE CAUSES: There are five possible causes for this error (and, as noted below, five corresponding fixes).
- Cause 1: If the Management Reporter Process Service is on the same machine as the machine hosting your SQL database, then the Process Service may have errored out by attempting to start before the SQL Server was accepting connections. See Fix 1.
- Cause 2: An SQL Server connection error has occurred, and the Management Reporter Process Service needs to be restarted. See Fix 2.
- Cause 3: The user running the Management Reporter Process Service does not have sufficient permissions to read from the SQL Server database. See Fix 3.
- Cause 4: The SQL Service Broker on the Management Reporter SQL Server database is not enabled. See Fix 4.
- Cause 5: This can also happen if the owner of the Management Reporter database is a Windows User, while the SQL Server Service is being run simultaneously by a local user. If you check the Event Viewer, you may see this message: An exception occurred while enqueueing a message in the target queue. Error 15404, State 19. Could not obtain information about Windows NT group/user ‘domain\user’, error code 0x5. See Fix 5.
- Fix 1: a) If you’re using Windows Server 2008 you can set the Set Process Server Service to “Automatic (Delayed Start)” rather than “Automatic.” ORb) Try restarting the Process Service manually or with a script similar to the following: NET STOP MRProcessService NET START MRProcessService
- Fix 2: See Fix 1 (b)
- Fix 3: Grant the user running this service the General User role under the Management Reporter database in SQL Server. This user can be found on the Log On tab under the Services Control panel.
- Fix 4: Run the following statement on the SQL Server where your Management Reporter database resides: SELECT name, is_broker_enabled FROM sys.databases WHERE name = DB_NAME() AND is_broker_enabled = 1. This statement should return a row for the Management Reporter SQL Server database. If it does not, run the statement below to re-enable the SQL Service Broker on the Management Reporter SQL Server database: ALTER DATABASE [ManagementReporter] SET ENABLE_BROKER WITH ROLLBACK IMMEDIATE;
- Fix 5: Change the database owner to “sa” or change the SQL Server Service user to a domain user.
Hope this helps.