Freigeben über

FAQ for Companion Apps

  • Artikel

As we see activity in configuring environments for AX mobile apps, we are seeing some common questions. We’ll keep this post updated with frequently asked questions. Feel free to post your questions.

Q. How do I set up Fiddler?

A. Fiddler is a great tool for debugging network traffic!

Here are some instructions on how to get Fiddler up and running.

Getting Started with Fiddler: https://docs.telerik.com/fiddler/configure-fiddler/tasks/configurefiddler

Monitor Windows Phone: https://www.spikie.be/blog/post/2013/01/04/Windows-Phone-8-and-Fiddler.aspx

Configure Fiddler for Windows 8 applications: https://docs.telerik.com/fiddler/configure-fiddler/tasks/configurefiddlerforwin8

 

 Q. After installing the mobile apps hotfix and completing setup, the timesheet app times out and sends me back to the sign in page.

The event viewer log on the machine running the mobile connector shows the following errors:

Unhandled Exception calling Microsoft.Dynamics.Framework.RapidStart.Connector.Modules.AXMobile.TimeService.GetProjectDetails.
User: (domain\username(domainnamehere)).

System.ServiceModel.ActionNotSupportedException: The message with Action 'https://schemas.microsoft.com/dynamics/2011/01/services/TSTimesheet/getProjectDetails' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver. Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None).

 A. This can happen in cases where the service was not deployed properly. Launching the AOT and redeploying the TimesheetServices under AOT\Service Groups\ will resolve this issue.

  

Q. After deploying the mobile apps hotfix and creating and configuring a new service bus. Logging into the mobile application gives me the following error (retrieved from fiddler):

ID4175: The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this issuer, configure the IssuerNameRegistry to return a valid name for this issuer.

A. In this particular instance, the ADFS setup was done correctly.

This error can be caused if the thumbprint was copy/pasted into the thumbprint field in the Connector for Mobile Applications. Deleting the thumbprint and manually retyping it fixes this issue. It could
also be the case when using a self-signed token signing certificate, that certificate has not been imported into the certificate store of the machine running the mobile connector. Importing the certificate will resolve the issue.

Comments

  • Anonymous
    June 25, 2014
    I am getting below error .I have followed all the stepsID4175: The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this issuer, configure the IssuerNameRegistry to return a valid name for this issuer
  • Anonymous
    June 25, 2014
    24A Receivera:InternalServerErrorInternal Server ErrorID4175: The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this issuer, configure the IssuerNameRegistry to return a valid name for this issuer. 0
  • Anonymous
    November 04, 2014
    I am also getting the ID4175 error mentioned above and I have set my 3rd party SSL issued certificate as the PRIMARY certificate in ADFS for Service Communications, Token-decrypting, and Token-signing.  I have hand typed the thumbprint for the 3rd party cert into the Mobile App connector and restarted the connector with no luck.  I have also installed the secondary self-signed cert in the Trusted Root Cert store on the server running the connector just in case.  No go.  Any help you can give would be fantastic.  Thank you
  • Anonymous
    December 07, 2015
    I am getting following error when accessing Windows Expense app The message with Action 'tempuri.org/.../getSections& cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This may be because of either a contract mismatch (mismatched Actions between sender and receiver) or a binding/security mismatch between the sender and the receiver.  Check that sender and receiver have the same contract and the same binding (including security requirements, e.g. Message, Transport, None). Can you help me on this?