Microsoft Dynamics AX (Archived)

Management Reporter 365 Server communicate error (on premises)

(1) Share

Report

Posted on by Community Member

When I try to open any financial report or try to open Management Reporter it gives me the following error.

7658.Untitled.png

the version i'm using Dynamics 365 Finance and Operations 365 on premises.

anyone faced the same issue. please help.

Thank you,

Regards,

Zarar Mahmood

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Sohaib Cheema 49,438 User Group Leader on at

Like (0)

Report

I am not sure, but I can doubt the certificate? can you make sure if you got the MR certificate on your Local\MyCerts

Secondly, have a look at logs, by trying to run MR on the MR server itself.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Dear Sohaib,

certificate is added.

the log file give the following details when I tried to connect

warning 1:

errorMessage

exceptionMessage There is no download group named "en-US".

exceptionSource System.Deployment

exceptionType System.Deployment.Application.InvalidDeploymentException

stackTrace at System.Deployment.Application.ComponentStore.CheckGroupInstalled(DefinitionAppId appId, AssemblyManifest appManifest, String groupName) at System.Deployment.Application.SubscriptionStore.CheckGroupInstalled(SubscriptionState subState, DefinitionAppId appId, String groupName) at System.Deployment.Application.ApplicationDeployment.IsFileGroupDownloaded(String groupName) at Microsoft.Dynamics.Performance.Common.ClickOnceDeploymentUtility.GetSatelliteAssemblies(String cultureName)

Error 1:

exceptionMessage The remote server returned an error: (500) Internal Server Error.

exceptionSource System

exceptionType System.Net.WebException

stackTrace at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)

failureBucketId 1240b633-b6e8-4e49-bc1d-655b7bb8861e

Error 2:

The content type application/json; charset=utf-8 of the response message does not match the content type of the binding (multipart/related; type="application/xop+xml"). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 36 bytes of the response were: '{"Message":"An error has occurred."}'.

exceptionSource mscorlib

Was this reply helpful? Yes No
Nathan Clouse AX 140 on at

Like (0)

Report

Was this ever resolved? I am facing a similar issue.

Was this reply helpful? Yes No
Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hello Nathan Close,

What error do you see?

Best regards,

Ludwig

Was this reply helpful? Yes No
Nathan Clouse AX 140 on at

Like (0)

Report

Hey Ludwig,

I am seeing the same behavior and error messages that Zarar is. However, I was able to collect a few other errors that also were being written at the same time as the errors that Zarar mentioned so MR may just have some less than spectacular error trapping which may be pointing folks in the wrong direction. For diagnostic testing, I am attempting to launch MR from an AOS node desktop as the user that installed the service fabric and has the certs ProtectTo'd that user so cert acl issues should be eliminated by all of that, if present.

The additional error i was able to find was:

There was no endpoint listening at 1.20.3.4/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.

the IP address of my primary MR node is (obfiscated) 1.2.3.4 so it would appear the fabric is doing its job and passing the request to the node that would actually process it. So that keys me into its either a cert or cluster issue so i'll do some more digging and report what i find.

Was this reply helpful? Yes No
Nathan Clouse AX 140 on at

Like (0)

Report

I think my issue was presenting similar to Zarar's issue but may be unrelated. After some digging, it appears as though the MR node lost the ACLs for the SessionAuthentication and FinancialReporting certs after a cluster upgrade. Not sure how but after re-installing those two certs on the MR nodes and re-applying ACLs (plus a restart), MR started working as expected.

Was this reply helpful? Yes No