Management Reporter Errors and Resolutions

JUST FIND YOUR ERROR BELOW.......

Symptoms :

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.
Here is a list of errors received when you click Test Connection and the possible associated error(s) seen in Event Viewer.  Find your error in the list and use the appropriate Cause\Resolution sections.

• "Connection attempt failed.  There is a version mismatch between the client and the server.  Contact your system administrator."
  
  
  • See Cause 1
• "Connection attempt failed.  Server is unable to connect to the database.  Contact your system administrator." If you check the Event Viewer, you may find the following error messages:
  
  • Message: Microsoft.Dynamics.Performance.Common.ReportingDatabaseConnectivityException: Database user lacks sufficient permission to run this application. ---> System.Da Data.SqlClient.SqlException: The EXECUTE permission was denied on the object 'pGetSchemaVersion', database 'ManagementReporter', schema 'dbo'.
  • Message: Microsoft.Dynamics.Performance.Common.ReportingDatabaseConnectivityException: Database user lacks sufficient permission to run this application. ---> System.Da Data.SqlClient.SqlException: The SELECT permission was denied on the object 'SecurityPrincipal', database 'ManagementReporter', schema 'dbo'.
    
    • See Cause 2
• "The version of the database is incorrect.  Install the correct version of the database."
  
  • See Cause 2
  • See Cause 13
• "Connection attempt failed.  User does not have appropriate permissions to connect to the server.  Contact your system administrator."
  
  • See Cause 3
• "A connection to the server could not be established.  Check the server address and try again or contact your system administrator."

Note Servername is a placeholder for your actual server name and 4712 is a placeholder for the actual port selected during the MR install. 
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
  • See Cause 4
• Message: System.ServiceModel.Security.SecurityNegotiationException: SOAP security negotiation with 'http://servername:4712/SecurityService.svc' for target 'http://servername:4712/SecurityService.svc' failed. See inner exception for more details. ---> System.ComponentModel.Win32Exception: The Security Support Provider Interface (SSPI) negotiation failed.
  • See Cause 5
  • See Cause 12
  • See Cause 13
  • See Cause 17
• Message: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://servername:4712/InformationService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it
• See Cause 6
• Message: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://servername:4712/InformationService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
• See Cause 10
• Message: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http://servername:4712/InformationService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: The remote server returned an error: (404) Not Found
• See Cause 13
• Message: System.ServiceModel.EndpointNotFoundException: Could not connect to http://servername:4712/InformationService.svc.  TCP error code 10061: No connection could be made because the target machine actively refused it
  • See Cause 6
• Message: System.ServiceModel.ProtocolException: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly.
  • If the error also included "Detailed Error - 500.24 - Internal Server Error"
    • See Cause 7
  • If the error also included "Detailed Error - 500.19 - Internal Server Error"
    • See Cause 8
  • If Event Viewer also includes a Warning about ASP.NET saying "A configuration error has occurred."
    • See Cause 15
• Message: System.ServiceModel.Security.MessageSecurityException: The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was ''. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.
  • See Cause 8
• Message: System.ServiceModel.Security.MessageSecurityException: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. ---> System.ServiceModel.FaultException: An error occurred when verifying security for the message.
  • See Cause 9
• Message: System.TimeoutException: The request channel timed out attempting to send after 00:00:40. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The HTTP request to 'http://servername:4712/InformationService.svc' has exceeded the allotted timeout of 00:00:39.9660000. The time allotted to this operation may have been a portion of a longer timeout. ---> System.Net.WebException: The operation has timed out
  • See Cause 10
• Message: System.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)
  • See Cause 11
• Message: System.ServiceModel.Security.SecurityNegotiationException: The caller was not authenticated by the service. ---> System.ServiceModel.FaultException: The request for security token could not be satisfied because authentication failed.
  • See Cause 12
• Message: System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (405) Method Not Allowed. ---> System.Net.WebException: The remote returned an error: (405) Method Not Allowed.
• See Cause 14
• ISAPI Filter 'C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_filter.dll' could not be loaded due to a configuration problem. The current configuration only supports loading images built for a AMD64 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.
• See Cause 16

• Message: Microsoft.Dynamics.Performance.Common.ReportingServerNotFoundException: The server could not be found. Make sure the server address is correct.
• See Cause 10

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Cause :

Cause 1
The Management Reporter Client installed is a different version than the MR Server.  See Resolution 1 in the "Resolution" section.
Cause 2
The Identity user of the Management Reporter Application Pool does not have the GeneralUser and public roles to the Management Reporter SQL Server database.  See Resolution 2 in the "Resolution" section.
Cause 3
The user trying to run MR has not been setup as a user in MR and therefore cannot connect.  See Resolution 3 in the "Resolution" section.
Cause 4
The Management Reporter Application Pool is not running. See Resolution 4 in the "Resolution" section.
Cause 5
The computer is not connected to the domain where Management Reporter is installed.  See Resolution 5 in the "Resolution" section.
Cause 6
The Management Reporter Web Site is not running.  See Resolution 6 in the "Resolution" section.
Cause 7
The Management Reporter Web Site has ASP.NET Impersonation enabled.  See Resolution 7 in the “Resolution” section.
Cause 8
The Anonymous User of the Management Reporter Site in IIS does not have access to the Management Reporter install folder (by default this will be: C:\Program Files\Microsoft Dynamics ERP\Management Reporter).  See Resolution 8 in the “Resolution” section.
Cause 9
The time on the client and server are more than five minutes different (differences in time zones are permitted).  See Resolution 9 in the "Resolution" section.
Cause 10
The port used during the MR installation is not set up as an exclusion within the Firewall software.  See Resolution 10 in the "Resolution section.
Cause 11
The Encrypt connection option was selected during the install but SSL was not configured.  See Resolution 11 in the "Resolution" section.
Cause 12
The computer is having problems communicating or authenticating with the domain.  See Resolution 12 in the "Resolution" section.
Cause 13
ASP.NET is not allowed in IIS.  See Resolution 13 in the "Resolution" section.
Cause 14
WCF HTTP Activation is not installed on the MR Server.  See Resolution 14 in the "Resolution" section.
Cause 15
Version conflicts between WCF and .NET.  See Resolution 15 in the "Resolution" section.
Cause 16
ISAPI filter being used is 32-bit but the Operating System is 64-bit.  See Resolution 16 in the "Resolution" section.
Cause 17
MR Services are being run as a Domain user and WCF Authentication is failing when using the UPN (User Principal Name). See Resolution 17 in the "Resolution" section.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Resolution :

Resolution 1

Check the Management Reporter Client install on the workstation and also check the Management Reporter Server install on the server.  To check the version in Management Reporter, click Help, and then click About Management Reporter. The MR Client install needs to be the same version as the MR Server install.
Resolution 2
Check the Identity user is Internet Information Services Manager:

• In IIS 7:
  • Expand the server name and then click Application Pools.
  • Make a note of the user in the Identity column for the Management Reporter Application Pool.
• In IIS 6:
  • Expand the server name and then expand Application Pools.
  • Right-click Management Reporter and click Properties.
  • Click the Identity tab and make a note of the user.

Change the Identity user's permissions in SQL.

• Open Microsoft SQL Server Management Studio.
• Expand the Security folder and then expand Logins.
• Right-click the user that was listed as the Identity user and select Properties.
• Click User Mapping and select the Management Reporter database.
• In the Database role membership section, mark GeneralUser and public.
• Click OK.

Resolution 3
Setup the user receiveing the connection error within MR.

• Run MR as a user that is setup as an MR administrator.
• In MR click Go and then click Security.
• Add the user who is receiving the connection error.

Note If it is not known what user(s) exist in MR you can run 'select * from SecurityUser' against the ManagementReporter database to find out.
Resolution 4
Start the Management Reporter Application Pool.

• In IIS 7
  • Expand the server name and then click Application Pools.
  • Check the Status of the Management Reporter Application Pool.
  • If it is not started, right-click the Management Reporter application pool and then click Start.
• In IIS 6
  • Expand the server name and then expand Application Pools.
  • Click Management Reporter and verify that it is started.
  • If it is not started, right-click the Management Reporter application pool and then click Start.

Note Once these steps are completed and you get the same error, repeat these steps to check the Application Pool.  If it is stopped, the password of the Identity account is incorrect and needs to be reset.
Resolution 5
Management Reporter will only function while connected to the domain used during the install. Even if all MR server components are on one computer, that computer still needs to be connected to the domain you were using when you installed MR.
Note  This means that Management Reporter will not work when demonstration laptops are not physically connected to the domain or not connected using a VPN connection.
Resolution 6
Start the Management Reporter Web Site.

• In IIS 7
  • Expand the server name and then expand Sites.
  • Right-click the Management Reporter Site, point to Manage Web Site and then click Start.
• In IIS 6
  • Expand the server name and then expand Web Sites.
  • Right-click the Management Reporter Site (or Default Web Site) and then click Start.

Resolution 7
Disable ASP.NET Impersonation.
Note This only applies to IIS 7.

• In IIS 7, expand the server name and then expand Sites.
• Click the Management Reporter Site and then double-click Authentication under the IIS category.
• Right-click ASP.NET Impersonation and then click Disable.

Resolution 8
Give the Anonymous User permissions to the Management Reporter install folder.

• In IIS 7
  • Expand the server name and then expand Sites.
  • Click the Mangement Reporter Site and then double-click Authentication under the IIS category.
  • Right-click Anonymous Authentication and then click Edit.
  • Make note of the user.
• In IIS 6
  • Expand the server name and then expand Web Sites.
  • Right-click the Management Reporter Site and then click Properties.
  • Click the Directory Security tab and then click Edit.
  • Make note of the anonymous user.
• In Windows Explorer on the MR Server.
  • Go to the folder where MR is installed (by default this path is: C:\Program Files\Microsoft Dynamics ERP\Management Reporter\2.0).
  • Right-click the Application Services folder and then click Properties.
  • Click the Security tab and make sure the anonymous user has at least Modify permissions. 

Resolution 9
Verify the time on the client and server. Change the time that is incorrect. The time must be within five minutes of each other.
Resolution 10
Setup an exception in your Firewall program. Steps will vary depending on the Firewall program used but here are high level steps.

• Click Start and then click Run.  Type WF.MSC and then press Enter.
• Click Inbound Rules.
• Click New Rule.
• Click Port and then click Next.
• Click Specific local ports and then type 4712. If you are not using the default port of 4712, you will need to type that here. Click Next.
• Click Allow the connection and then click Next.
• Select Domain, Private, and Public.  Click Next.
• Type Management Reporter as the Name and then click Finish.

Resolution 11

The MR Install Guide has the following information regarding the encrypt connection option:

You must configure SSL on the server and install certificates before you can use this option. For more information about encryption in Microsoft SQL Server, see the SQL Server documentation on MSDN (http://msdn.microsoft.com/en-us/library/ms189067.aspx).
You could also modify the config files to turn Encryption off (make a backup copy of the files before you modify them).

• In Windows Explorer, go to the MR install folder (the default install is: C:\Program Files\Microsoft Dynamics ERP\Management Reporter\2.0)
  • In the Application Service folder find the web.config file and right-click the file to open it in Notepad.
  • Locate the <connectionstrings> and change the setting Encrypt= from True to False.
  • Save the changes.
  • In the Process Service folder find the MRProcessService.exe.config file and right-click the file to open it in Notepad.
  • Locate the <connectionstrings> and change the setting Encrypt= from True to False.
  • Save the changes.

Resolution 12
Remove the computer from the domain and then add it back to the domain.  Warning A local administrator account will need to be used to logon to the computer one time after it is removed from the domain.

• Click Start, click Run and type: sysdm.cpl to open System Properties.
• Click Change and make a note of the Domain name.
• Click Workgroup, type a name (i.e. workgroup), click OK to accept changes and then restart the computer.
• After restarting, click Start, click Run and type: sysdm.cpl to open System Properties.
• Click Change and then click Domain.
• Enter the domain noted above, click OK to accept changes and then restart the computer.

Resolution 13
In IIS set ASP.NET to Allowed:

• In IIS 7
  • Click the server name and then double-click ISAPI and CGI Restrictions under the IIS category.
  • Right-click ASP.NET vX.XX and then click Allow.
• In IIS 6
  • Expand the server name and then click Web Service Extensions.
  • Click ASP.NET vX.XX and then click Allow.  

Note Where vX.XX is a placeholder for the actual ASP.NET version. Beginning with MR V2 SP1 (2.0.1663.3) the version of ASP.NET used with MR is v4.0.30319.

Resolution 14

Install WCF HTTP Activation.

• In Windows Server 2008, open Server Manager and then click Features.
• Click Add Features and then expand .NET Framework.
• Expand WCF Activation and then mark HTTP Activation.
• Click Next and then click Install.

Resolution 15
For IIS 7.0:
Register ASP.NET.

• Click Start, point to Programs, and then click Accessories.
• Right-click Command Prompt and then click Run as administrator.
• Browse to the appropriate directory:
  • 32-bit systems: %SystemRoot%\Microsoft.NET\Framework\v4.0.30319
  • 64-bit systems: %SystemRoot%\Microsoft.NET\Framework64\v4.0.30319
• In the command prompt, type: aspnet_regiis.exe -iru

Note On a 64-bit system that has the 64-bit .Net v4.0.30319 Framework registered, you will need to set the Enable 32-bit Applications property to False on the Management Reporter Application Pool in IIS Manager.

For IIS 6.0:
Note IIS 6.0 does not support running both 32-bit and 64-bit modes at the same time.
Register ASP.NET:

• Click Start, point to Programs, and then click Accessories.
• Right-click Command Prompt and then click Run as administrator.
• Browse to the appropriate directory:
  • 32-bit systems: %SystemRoot%\Microsoft.NET\Framework\v4.0.30319
  • 64-bit systems: %SystemRoot%\Microsoft.NET\Framework64\v4.0.30319
• In the command prompt, type: aspnet_regiis.exe -iru
• Expand the server node and click Web Service Extensions.
• Set all ASP.NET v4.0.30319 web service extensions to Allowed. If you registered the 64-bit version:
  
  • Click Start, point to Programs, and then click Accessories.
  • Right-click Command Prompt and then click Run as administrator.
  • Type the following command to enable the 64-bit mode:
    cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0

After registering ASP.NET you will need to set the Enable32bitAppOnWin64 property to match the version you registered:

If you registered the 32-bit version:

• Click Start, point to Programs, and then click Accessories.
• Right-click Command Prompt and then click Run as administrator.
• Type the following command to enable the 32-bit mode:
  cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1

 Resolution 16

• Open Internet Information Services (IIS) Manager.
• Expand the server name, then expand Sites and then click Management Reporter.
• Double-click ISAPI Filters in the IIS Section.  Then double-click the ASP.NET_4.0.30319.0 line. In the Edit ISAPI Filter window, edit the Executable box so that is is C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_filter.dll 
• Click OK and then restart the Management Reporter website.  To do this, click Management Reporter and then click Restart. 

  Resolution 17

Create an SPN on the IIS machine for the domain account running the MR Service.  To create an SPN for this domain account, run the Setspn tool at a command prompt on the IIS server with the following commands:

setspn -A HTTP/webservername domain\customAccountName

setspn -A HTTP/webservername.fullyqualifieddomainname domain\customAccountName

Note

• "webservername" should be replaced with the IIS server name where the MR Application Service is installed.
• "webservername.FullyQualifiedDomainName" should be replaced with the fully qualified domain name of the IIS server where the MR Application Service is installed.
• "domain\customAccountName" should be replaced with the domain account running the MR Services.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
More Information :

Some of the changes above may require IIS be restarted so be sure that IIS is restarted as needed.
If you still receive error messages after making changes contact Microsoft Management Reporter support with the errors including details from Event Viewer.Click Start, point Administrative Tools, and then click Internet Information Services (IIS) Manager. 

You may also refer the following website.
http://support.microsoft.com/kb/2406829