We recently encountered a problem when connecting to a new installation of Management Reporter and received the ubiquitous “Can’t connect to the Management Reporter server. Do you want to specify a different server address?” message. This error typically is related to domain security or a firewall configuration, but not this time.
When troubleshooting this error, one of the first things we do is confirm the Management Reporter service can actually receive connections by using the netstat command. Running “netstat –an |find /i “LISTENING” at a command prompt will show you what IP addresses and ports are listening for connections. The default Management Reporter IP port is 4712, so we want to look for that in our output. Here is the netstat output for this particular case:
The highlighted text indicates that all IP addresses for the computer (0.0.0.0) are listening for connections on port 4712; if this line was missing from the output, it would likely indicate a firewall on the machine was blocking that port. The Management Reporter setup process can create a Windows firewall exception to open that port for us, and I usually choose that option to simplify the installation. If you’re running another firewall product, you will need to manually create an exception to allow inbound traffic on port 4712 or whatever port you chose during setup. In this case, there was no firewall or networking issue involved.
I verified the Management Reporter service was started, which meant the user account and credentials I provided were valid. I also verified the Management Reporter application pool was using a valid domain account—in this case, the same account as the service—and that it was started. Everything seemed to be correct, and restarting services and recycling the application pool didn’t resolve the problem or generate any errors.
Another way to validate that MR is running and accessible is to browse to http://MRservername:MRport/SecurityService.svc in a web browser. An HTTP 404 message would indicate a problem with Internet Information Services (IIS). In this case, we received a 404, so it was time to take a closer look at IIS.
One of the prerequisites for Management Reporter is .NET Framework 4.0, which installed without any issues on this particular system. .NET Framework also includes the ASP.NET v4.0 Web Service Extension for IIS. One difference between this server and all of the others to which I have deployed Management Reporter: This one was running Windows Server 2003 instead of Server 2008. Server 2003 includes IIS 6.0 which, by default, will set ASP.NET v4.0 to “Prohibited” rather than “Allowed.” Once the web extension was set to “Allowed”, connections to MR worked correctly. The screenshot below shows the correct IIS configuration:
For more information about Management Reporter, including troubleshooting errors and information on migrating from FRx to Management Reporter, contact our Microsoft Dynamics GP Support Center at email@example.com.