Management Reporter – Troubleshooting and Errors

Management Reporter Troubleshooting

1. Check out the Event Viewer (Application), and review the Management Reporter Events. This is pretty important, as Doug mentioned here
2. Search in the forums from GPWindow, and from the Management Reporter Forum here (this is not yet indexed by GPWindow) http://social.microsoft.com/Forums/en-US/managementreporterBeta/
3. Refresh the cached Financial Data - On the Tools menu, click Refresh Cached Financial Data.
4. Confirm whether or not the Application Service is running correctly is to type in the following in IE:
   http://MRservername:MRport/SecurityService.svc
5. Stop and Start the Management Reporter application pool (From IIS). Check the Event Viewer for errors.
6. Stop and Start the Management Reporter Process Service. Check the Event Viewer for errors. This is found under Control Panel | Administrative Tools | Services | Management Reporter Process Service.
7. Restart the Web Service in IIS

#6 Restarting the Process Service

Errors

If you get the following error when you launch Management Reporter -"Connection attempt failed.  User does not have appropriate permissions to connect to the server." -

You need to add their users - Add user- enter domain\username.  They can only launch if they are login to windows using their own domain account.

Check out this post from Cecile for details.

---

If you get the “Unable to connect to the specified server. Verify that the Management Reporter application service has been installed on the server and that the specified address is correct” error -

There is a great checklist by Ryan from Microsoft here.

1. Management Reporter will only function while connected to the domain it was installed on. Even if all MR server components are on one machine, that machine still needs to be connected to the domain you were on when you installed MR.

2. Confirm the Application Service application pool is running. This is found in Internet Information Services Manager and is the Management Reporter app pool.

3. Confirm the Management Reporter Process Service is running. This is found under Control Panel | Administrative Tools | Services | Management Reporter Process Service.

4. Confirm the Identity of the Application Service app pool has GeneralUser and public SQL roles to the Management Reporter SQL database.

5. Confirm the user running the Management Reporter Process Service has GeneralUser and public SQL roles to the Management Reporter SQL database.

6. Confirm the IIS machine has the port used in the MR installation set up as an exclusion on any Firewalls (Windows Firewall included).

7. Another way to test to confirm whether or not the Application Service is running correctly is to type in the following in IE:

http://MRservername:MRport/SecurityService.svc

This should return a page with code samples. If you get an HTTP error then ASP.NET 2.0 may not be enabled or the Application Service may not be running.

8. Check the Event Viewer for more information

9. Stop and Start the Management Reporter application pool. Check the Event Viewer for errors.

10. Stop and Start the Management Reporter Process Service. Check the Event Viewer for errors.

11. Windows Server 2003 – Web Service Extensions in IIS, Active Server Pages can’t be set to Prohibited.

---

Reports being stuck in Queue

Check out the Event Viewer (Application), and review the Management Reporter Events.  The error details will guide you to fixing the problem

---

Data not shown in reports

This could be due to a number of reasons. One crazy reason we found (again via the Event Viewer), was that no functional currency was set in GP.

Solution:  Set functional currency in Multicurrency Setup window (Microsoft Dynamics GP menu >> Tools >> Setup >> Financial >> Multicurrency)