
My client has had MR for several years. There has been no changes to accounts, etc. Last week all reports ran fine, this week some of the reports run, and others get the above error.
Yesterday MR was stopped and we had to re-enter the password and start both services again. We do not know why it was stopped. We entered the password and started the services again and we thought all was well, until trying to print additional reports. It seems to be reports that are using certain Reporting Trees, not sure if this is a coincidence or not. There is one small Reporting Tree that works.
Any ideas? I have started and stopped, I have looked at security.
Any help is greatly appreciated.
Tracey D
*This post is locked for comments
I have the same question (0)Hi Tracey,
A couple of things to check with this error:
1. In Report Designer go to Tools | Options. Is the Management Report files location a valid path and does the user have access to it? Can they add\delete things to that folder?
2. Related to #1, there is a registry key tied to that path that might be missing on the MR server for the MR service account. Open the Registry (Start | Run and then type regedt32).
a. If you are logged onto the server as the MR service account you can go to HKEY_CURRENT_USER\Software\Microsoft\Dynamics\ManagementReport\21
b. If you are logged onto the server as another user you will need to go to HKEY_USERS\<sid of the service account>\Software\Microsoft\Dynamics\ManagementReport\21
c. In there you should have a DocumentPath key with the path to the Management Report folder. If it is missing add a new key with type of Expandable String Value. The path will be something like C:\Users\<MR Service user>\Documents\Management Reporter
d. To get the SID of the service account if it is not known you can download PSGetSid from here - https://technet.microsoft.com/en-us/sysinternals/bb897417.aspx
e. Extract the utility, open a command prompt and then change the directory to where you extracted the files. Then run PSGETSID.exe XXXXXXXXX (name of the service account)
3. Mismatch between the service account and the MR site\port
a. Verify the account running the MR services.
b. On the MR server at a command prompt run netsh http show urlacl
c. Find the address of http://+4712 (assuming 4712 is used by MR) and see which user is listed. d. If the user listed is not the service account user, change the services to this account.
4. If the services are running as a local account (i.e. Local System) change to a domain account.