You’re offline. This is a read only version of the page.
582
I believe I posted this question some time ago, and the answer was that I needed to apply patches to Mgmt Reporter, as I was on a very old version. Well, I successfully patched up to CU 15 this weekend, including the subsequent Hot Fixes, so I am completely up-to-date on Management Reporter 2012.
The following error persists, even after successfully patching MR:
Whenever the services get recycled, for whatever reason, reboot, etc. at the initial start up I receive the following error:
Cannot open database "ManagementReporterDM" requested by the login. The login failed.
Login failed for user 'sa'. Cannot open database "ManagementReporterDM" requested by the login. The login failed.
Login failed for user 'sa'.
Component: Microsoft.Dynamics.Integration.Common.TraceLog
User: XXXXX\MRService
Machine: XXXXXXXX-SQL12
This is strange because the Data Mart database in my installation of Mgmt Report is NOT named ManagementReporterDM, it is named MRDM. I did not perform the installation of MR in this case, it was done by a GP Partner who is no longer working with the company.
I cannot understand why MR is looking for this database name. I cannot find it referred to in any config files, etc. Its almost like it is tripping up in the beginning because the Data Mart database is not named with the expected default name.
I do not think this error is catastrophic because everything works, but, I would really like to know why this happens and fix it so that it doesn't cause any problems down the road.
I have thoroughly looked through config files and the ManagementReporter database and I CANNOT FIND any reference to the "ManagementReporterDM" database ANYWHERE.
Does anyone have any idea why it is doing this?
*This post is locked for comments
I have the same question (0)
It sounds like you have a stuck integration. Either there was an integration pointed to ManagementReporterDM at some point in the past or something went wrong on the earlier version to cause something to get stuck. If the error isn't causing any harm, it may not be worth correcting. If you would like to pursue it, I would suggest the following:
1. Get all users out of MR and back up the ManagementReporter SQL database.
2. Start the MR Configuration Console as a user who is an Administrator in MR and a sysadmin in SQL.
3. Disable and remove the data mart integration.
4. Stop and remove both MR services.
5. Delete the MRDM database from SQL.
6. Restart the Configuration Console.
7. Deploy just the 2 MR services. Choose the connect to an existing database option to point to the ManagementReporter database.
8. Restart the Configuration Console again and check for the error. If it persists, I would suggest logging a support case so we can examine the tables to determine what is stuck. If everything looks good, click File -> Configure and deploy a new data mart integration. You can name it anything you want. There are no issues with using a different name.
Share
Report
All responses (
Answers (
