You’re offline. This is a read only version of the page.
I have management reporter installed on a production server and it is working fine (the SQL database, web site and service process are all on the same server).
I am testing a disaster recovery plan and attempting to restore the ManagementReporter SQL database to another server, that also has the web site and service processes installed. After restoring the database, I run this command:
OPEN MASTER KEY DECRYPTION BY PASSWORD = 'password'
ALTER MASTER KEY ADD ENCRYPTION BY SERVICE MASTER KEY
After doing this, I can edit reports from this new server. However, when I try to generate a report, it just gets stuck in the Queue and never processes. No error messages are appearing on the server event log. The Management Reporter process is running and it is running under a user ID that has access to the SQL database.
Any idea's on what is wrong? What is the proper procedure for moving the ManagementReporter SQL database to a new server?
Thank you,
*This post is locked for comments
I have the same question (0)
This may be an issue with the service broker for the Management Reporter database.
Close all active connections to the ManagmentReporter database (note: this may require detaching and attaching the database and\or stopping the Application and Process service)
Re-enable the Broker service through SQL Server Manager:
Right-click on the ManagementReporter database
Select Properties
Click on 'Options' on the left tree pane
Under 'Service Broker' set 'Broker Enabled' to 'True'
Click OK
Restart the Application and Process service if disabled. Reports should being to get dequeued and processed.
Jill
Share
Report
All responses (
Answers (
1,846
