Financial Reporting – Fix The Management Reporter Process Service

If you’re using a local copy of the AX7 Update 1 (aka May Update) virtual machine (.vhd) and experience issues with starting the Management Reporter 2012 Process Service (in Windows Services) that might be because you needed to rename the machine name. This is a very common scenario, of course. Here’s how to handle it.

First of all thanks to Rick Davis who mentioned this first on yammer.
If you want to read common things about Financial reporting please visit the right places in the Microsoft Dynamics AX Help Wiki.

Cause

As mentioned the issue is caused by the fact that usually you rename the local machines to avoid all kinds of issues when you use several of them for development, for example. Financial Reporting (which is the name for it in the new Dynamics AX – it’s pretty much the same thing that was called Management Reporter before) assumes a local address equal to the former machine name and has some connection problems due to that.

Error

Financial Reporting Management Reporter 2012 Process Service

You’ll find that the service (Management Reporter 2012 Process Service) takes very long to start at first and produce some crash after it seemed to be started. In the Event Viewer there’s an error message

	{"Class":20,"ConnectionId":"00000000-0000-0000-0000-000000000000","ErrorCode":-2146232060,"Errors":[{"Class":20,"LineNumber":0,"Message":"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)","Number":5,"Procedure":null,"Source":".Net SqlClient Data Provider","State":0}],"LineNumber":0,"Message":"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)","Number":5,"Procedure":null,"Source":".Net SqlClient Data Provider","State":0}

Fix

Fixing this is rather easy. When I saw the error message the first thing I did was to activate Named Pipes in SQL Server Configuration Manager – most unsuccessfully.
Actually you have to map the former machine name to the local IP address simply. Therefore, open the hosts file that is located in C:\Windows\System32\drivers\etc and add the following line at the end:

127.0.0.1 WIN-33FS1TD8OB2

Financial Reporting Hosts File

Save the file and (re-) start the service. It’ll start almost immediately and try do to what it’s supposed to do.
Please be aware of the fact that this might be different with other releases of Microsoft Dynamics AX (because the original machine name changes, for example). And stay tuned for more about this topic!

2 thoughts on “Financial Reporting – Fix The Management Reporter Process Service

  1. You can also fix this by correcting the connection string in this file C:\FinancialReporting\Server\Services\MRServiceHost.connections

Leave a Comment