Mobile Apps will not connect

(0) Share

Report

Posted on by Community Member

Everyone,

I have been working to get mobile apps working for our environment but am running into an issue I can not resolve. I have followed the White Paper for Configure MS Dynamics AX environment for companion apps and successfully have ADFS working internally and externally for our users. The Dynamics AX Connector for Mobile Apps starts great and verified that in the Azure Service it sees all the relays.

With all of this working when I go through a Windows 8 app or Android app I am unable to log in. I get the generic message of "Sorry Something Went wrong. Please contact your system Administrator". If I sign in with an incorrect username/password I am able to see ADFS errors so I know it is talking to my environment.

I have checked the event viewer on both the AOS and ADFS server and do not see any errors. My user account has all roles in AX (dev environment).

We are running AX 2012 R3 and ADFS 3.0 on 2012 R2 server

Any suggestions on what to try next???

*This post is locked for comments

I have the same question (0)

All responses (15)

Answers (1)

Suggested answer

André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (0)

Report

Hi Don,

Please check what certificate you are using. A wildcard certificate is not working. Also you can use Fiddler to find out about the error. The next link will guide you how to use Fiddler. If you have a trace and cannot find the cause yourself, then please update this thread. blogs.msdn.com/.../faq-for-companion-apps.aspx

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thank you for the quick response. The cert is not a wildcard cert. Is there any configuration inside of AX under Windows Azure Service Bus Configuration that needs completed? I will check Fiddler out for further troubleshooting information.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I have found an error in Fiddler "Error:Code:401:SubCode:T0:Detail:ACS50008: SAML token is invalid" I am researching this now, have you seen this issue before and if so do you know a quick resolution?

Was this reply helpful? Yes No
André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (0)

Report

This message can have various causes. E.g. the default company for the user is not having the project setup. Or the thumbprint of the certificate is typed incorrectly (should be without spaces). And some more...

The Fiddler trace can be helpful to see when the traffic is interrupted.

Was this reply helpful? Yes No
André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (0)

Report

During my writing you also updated the thread. This is certificate related. Check the thumbprint in the mobile connector first.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I have verified that the thumbprint was incorrect and updated. I have restarted the services and attempted again with no luck. I am using a Authorized CA cert and even copied it to the Trusted people section of the server where mobile is installed. Below is the Fiddler data

Was this reply helpful? Yes No
Verified answer

André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (0)

Report

Hi Don,

When I look at the trace, it stops after 'adfs/services/trust/13/usernamemixed'. This is the part where the service bus wants to "shake hands" with the ADFS server. So I would suggest to review the ACS settings on the Azure service bus and also the settings on the ADFS server.

Do you have any firewalls, proxy settings that could block traffic?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I have reviewed the ACS settings and found one issue that I have corrected. After that a different error occured of "The SSL certificate does not contain all UPN suffix values that exist in the enterprise."

I found a resolution to the issue for UPN and updated our ADFS server with Add-AdfsDeviceRegistrationUpnSuffix -UpnSuffix "DomainName". Now I am getting a different message in Fiddle, it is below.

Error:Code:403:SubCode:T0:Detail:ACS50000: There was an error issuing a token. ACS60000: An error occurred while processing rules for relying party

I am not seeing any errors on ADFS at this time but still getting the error on the AX mobile apps.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I have reviewed the ACS settings and found one issue that I have corrected. After that a different error occurred of "The SSL certificate does not contain all UPN suffix values that exist in the enterprise."

I found a resolution to the issue for UPN and updated our ADFS server with Add-AdfsDeviceRegistrationUpnSuffix -UpnSuffix "DomainName". Now I am getting a different message in Fiddle, it is below.

Error:Code:403:SubCode:T0:Detail:ACS50000: There was an error issuing a token. ACS60000: An error occurred while processing rules for relying party

I am not seeing any errors on ADFS at this time but still getting the error on the AX mobile apps.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I believe I have this working.... When I get signed in I do not see any option for Timesheets even though the user has the role Project Timesheet.

Was this reply helpful? Yes No