Error message when you start Microsoft Management Reporter: “Can’t connect to the Management Reporter server”

When you start Microsoft Management Reporter (MR) you receive one of the following error messages: "A connection to the server could not be established. Check the server address and try again or contact your system administrator." or "Can't connect to the Management Reporter server. Do you want to specify a different server address?"

To troubleshoot Management Reporter connection problems you need to click OK to this message and then click Test Connection to get an additional error message. You also need to go to Event Viewer to get additional information on the error. In Event Viewer click Windows Logs and then click Application. Under the Source column look for Management Reporter Report Designer or Management Reporter Services




If you check the Event Viewer, you may find the following error messages:

• Message: System.ServiceModel.ServerTooBusyException: The HTTP service located at http://servername:4712/InformationService.svc is too busy. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable

This can happen if you have recently had your Management Reporter service account password changed.

Please use the below link to resolve your issue:

http://support.microsoft.com/kb/2666579

If you have not changed the password use the below link instead:

http://support.microsoft.com/kb/2406829

" The selected company is not configured as a company of the current Microsoft Dynamics GP system database. You must resolve the database configuration to log in to the company"

" The selected company is not configured as a company of the current Microsoft Dynamics GP system database. You must resolve the database configuration to log in to the company"

You receive the above error after restoring one database to another.

• To resolve the error you need to go to the SY01500 table of the DYNAMICS database and take note of the CMPANYID value for the database being restored to. 
• Next go to the SY00100 table of the company database where the restore was made to and update the 'CMPANYID" field with that value. 
• Also update the "DBNAME" with the relevant DYNAMICS database name if you are using a separate DYNAMICS database for this company.