web

You’re offline. This is a read only version of the page.

Dynamics 365 CommunityForums Microsoft Dynamics 365 | Integration, Dataverse... Microsoft Dynamics 365...

Microsoft Dynamics 365 | Integration, Dataverse...

Unanswered

Microsoft Dynamics 365 for Mobile - Certificate trusted on PCs but not on Android?

(0) Share

Report

Report

Posted on by MichaelE

20

For a test lab I have Dynamics 365 (D365) on premises installed. Internet facing.
Microsoft Dynamics 365 Version 1612 (9.0.2.3034) (DB 9.0.2.3034) on-premises IFD. All green flagged.
With only -one- IP address at my disposal I have installed Dynamics 365 and ADFS on the same box, meaning Dynamics 365 is using a different port than the standard port 443 which ADFS is using.

I don’t know if this is the root of my sorrows here.

The setup involves a completely green flagged PKI with an Offline Root and an Enterprise CA as a subordinate CA - certificates issued and in place.

This setup of course needs the relevant certificate to be copied to each clients Trusted Root Certification Authorities store in order to be able to connect without certificate warnings. But when done – it works. Flawlessly. From any PC.

..this scenario is completely different with the dedicated Android app “Dynamics 365 for Mobile”.

Trying this exact same approach (copying the certificate to the certificate store of the mobile phone) with Android v9 and trying to log on to Dynamics 365 on premises (on a different port than 443) throws an immediate error. The error unequivocally concerns a distrust with the “SSL” certificate and the mobile app refuses to connect.

The log on from Microsoft Dynamics 365 for Mobile would be: https://[org].[domain].com[:port]

Trying to connect exactly like this via the Android phones browser -also- complains about the certificate in place, but -does- allow for connection, although with the expected stripped down and not very functional mobile phone browser version.

Why does the dedicated Android app “Dynamics 365 for Mobile” not allow for the same seamless connection as the PCs in this setup, and is there no way to have the internal PKI issue a certificate that will satisfy Android and hence have “Dynamics 365 for Mobile” work without going through a third party certificate issuer? (..and will this last option even solve the issue of having the dedicated Android app connecting to D365 using a different port other than the standard 443?)

I have the same question (0)

All responses Img

All responses (5)

Answers Img

Answers (0)

LuHao 40,890 on at

Like (0)

Report

RE: Microsoft Dynamics 365 for Mobile - Certificate trusted on PCs but not on Android?

Hi partner,

I would recommend you raise a support ticket to get timely and professional help from the Microsoft team.

Was this reply helpful? Yes No

ISMAIL TUTUMLUER

399 on at

Like (0)

Report

Report

RE: Microsoft Dynamics 365 for Mobile - Certificate trusted on PCs but not on Android?

We're using Microsoft Dynamics 365 Version 1612 (9.0.2.3034) (DB 9.0.2.3034) on-premise. ADFS is installed without any error. I can use and login on the Dynamics 365 For Phones on IOS , everthing is ok , no any error or connectivity problem. Also I can use Microsoft Dynamics CRM application on Windows 10, everthing is ok , no any error or connectivity problem. But when I want to use Dynamics 365 For Phones on Android with same server and connection information, I cannot connect to crmi gives an error. Has anyone solved this connectivity issue on Android?

The error log is below;

2020-02-13 19:59:24.004 0300, 22607, 2, V, EventReporter, startLogger, 25, "************************************* STARTING MSCRM HOST *************************************"
2020-02-13 19:59:24.005 0300, 22607, 2, V, EventReporter, updateLogSettings, 26, "Stored Logging Preferences (loggingEnabled: true)"
2020-02-13 19:59:24.005 0300, 22607, 2, I, EventReporter, updateLogSettings, 26, "Log Settings (logLevel: INFO, webScriptLogLevel: Verbose)"
2020-02-13 19:59:25.097 0300, 22607, 1821, "ScenarioStart force-update-retrieve (201cab5f-818b-4ace-ac84-213f24c50331) | Context: {}"
2020-02-13 19:59:25.137 0300, 22607, 1821, "ScenarioEnd force-update-retrieve (201cab5f-818b-4ace-ac84-213f24c50331): SUCCESS No update needed - Took 54ms | Context: {}"
2020-02-13 19:59:25.157 0300, 22607, 1821, "ScenarioStart start-screen-navigation (59c99096-8886-497e-aef3-666dfb36bd3a) Redirecting to default screen | Context: {"authState":1.0,"isConfigured":false,"isUserSignedInUsingEmail":false,"inputServerUrl":"","appOpenUrl":"","appModuleName":"","crmServerVersion":""}"
2020-02-13 19:59:25.215 0300, 22607, 1821, "ScenarioEnd start-screen-navigation (59c99096-8886-497e-aef3-666dfb36bd3a): SUCCESS - Took 49ms | Context: {"authState":1.0,"isConfigured":false,"isUserSignedInUsingEmail":false,"inputServerUrl":"","appOpenUrl":"","appModuleName":"","crmServerVersion":""}"
2020-02-13 19:59:25.219 0300, 22607, 1821, "ScenarioStart force-update-check (1e9966ef-6d16-466d-bebb-7d0ecd503185) Call to the update server | Context: {"queryUrl":"https://go.microsoft.com/fwlink/?linkid\u003d2109000\u0026os\u003dandroid\u0026version\u003d4.3.20021.17\u0026appType\u003dd365"}"
2020-02-13 19:59:25.221 0300, 22607, 1821, "ScenarioStart http-call (33cd0f60-b5f8-4c42-92d7-fcdc81a901db) Initiating http query | Context: {"request":{"requestId":"e45fc7b3-14dc-4fb4-a9f0-c6f80ee5726c","url":"https://go.microsoft.com/fwlink/?linkid\u003d2109000\u0026os\u003dandroid\u0026version\u003d4.3.20021.17\u0026appType\u003dd365","method":"GET","headers":{}}}"
2020-02-13 19:59:26.150 0300, 22607, 1821, "ScenarioEnd http-call (33cd0f60-b5f8-4c42-92d7-fcdc81a901db): SUCCESS - Took 952ms | Context: {"request":{"requestId":"e45fc7b3-14dc-4fb4-a9f0-c6f80ee5726c","url":"https://go.microsoft.com/fwlink/?linkid\u003d2109000\u0026os\u003dandroid\u0026version\u003d4.3.20021.17\u0026appType\u003dd365","method":"GET","headers":{}},"response":{"url":"https://www.microsoft.com/library/errorpages/smarterror.aspx?version\u003d4.3.20021.17\u0026appType\u003dd365","statusCode":404.0,"responseType":"default"}}"
2020-02-13 19:59:26.156 0300, 22607, 1821, "ScenarioEnd force-update-check (1e9966ef-6d16-466d-bebb-7d0ecd503185): SUCCESS Non 200 response received - Took 955ms | Context: {"queryUrl":"https://go.microsoft.com/fwlink/?linkid\u003d2109000\u0026os\u003dandroid\u0026version\u003d4.3.20021.17\u0026appType\u003dd365","result":{"shouldUpdate":false},"responseCode":404.0}"
2020-02-13 19:59:33.003 0300, 22607, 1821, "ScenarioStart onprem-telemetry-dialog (b17a922f-458f-4687-aba2-a7760470f24f) | Context: {}"
2020-02-13 19:59:33.830 0300, 22607, 1821, "ScenarioEnd onprem-telemetry-dialog (b17a922f-458f-4687-aba2-a7760470f24f): SUCCESS - Took 816ms | Context: {"canShare":true}"
2020-02-13 19:59:33.880 0300, 22607, 1821, "ScenarioStart url-org-configuration (f245d645-ddcf-4eca-8387-e77867c55c81) Validating server | Context: {"serverUrl":"https://crm.domain.com","orgType":"onprem"}"
2020-02-13 19:59:33.882 0300, 22607, 1821, "ScenarioStart Verify Server (cb140dce-8870-4cfe-9f5a-57e151c10ca6) | Context: {"url":"https://crm.domain.com"}"
2020-02-13 19:59:33.885 0300, 22607, 1821, "ScenarioEnd Verify Server (cb140dce-8870-4cfe-9f5a-57e151c10ca6): FAILURE USER_ERROR The server url is malformed - Took 4ms | Context: {"url":"https://crm.domain.com"}"
2020-02-13 19:59:33.896 0300, 22607, 1821, "ScenarioEnd url-org-configuration (f245d645-ddcf-4eca-8387-e77867c55c81): FAILURE USER_ERROR Exception raised during server verification - Took 16ms | ExceptionString: {"framesToPop":1,"nativeStackAndroid":[],"userInfo":null,"code":"NetworkError","line":18,"column":1799,"sourceURL":"index.bundle","name":"Error","message":"ServerNotAvailable","stack":"h@index.bundle:18:1799\nindex.bundle:18:1193\nvalue@index.bundle:27:3600\nindex.bundle:27:1144\nvalue@index.bundle:27:2565\nvalue@index.bundle:27:1114\nvalue@[native code]"} | Context: {"serverUrl":"https://crm.domain.com","orgType":"onprem"}"
2020-02-13 19:59:40.719 0300, 22607, 1821, "ScenarioStart onprem-telemetry-dialog (c847ab89-0162-4ec6-a829-56ca433aec35) | Context: {}"
2020-02-13 19:59:42.309 0300, 22607, 1821, "ScenarioEnd onprem-telemetry-dialog (c847ab89-0162-4ec6-a829-56ca433aec35): SUCCESS - Took 1583ms | Context: {"canShare":false}"
2020-02-13 19:59:42.328 0300, 22607, 1821, "ScenarioStart url-org-configuration (e01d51a0-763a-45c2-9ef9-3f43c13d9e2b) Validating server | Context: {"serverUrl":"https://crm.domain.com/","orgType":"onprem"}"
2020-02-13 19:59:42.329 0300, 22607, 1821, "ScenarioStart Verify Server (c204f1de-a585-42ef-b1b4-a8ca66e52a45) | Context: {"url":"https://crm.domain.com/"}"
2020-02-13 19:59:42.331 0300, 22607, 1821, "ScenarioEnd Verify Server (c204f1de-a585-42ef-b1b4-a8ca66e52a45): FAILURE USER_ERROR The server url is malformed - Took 3ms | Context: {"url":"https://crm.domain.com/"}"
2020-02-13 19:59:42.343 0300, 22607, 1821, "ScenarioEnd url-org-configuration (e01d51a0-763a-45c2-9ef9-3f43c13d9e2b): FAILURE USER_ERROR Exception raised during server verification - Took 16ms | ExceptionString: {"framesToPop":1,"nativeStackAndroid":[],"userInfo":null,"code":"NetworkError","line":18,"column":1799,"sourceURL":"index.bundle","name":"Error","message":"ServerNotAvailable","stack":"h@index.bundle:18:1799\nindex.bundle:18:1193\nvalue@index.bundle:27:3600\nindex.bundle:27:1144\nvalue@index.bundle:27:2565\nvalue@index.bundle:27:1114\nvalue@[native code]"} | Context: {"serverUrl":"https://crm.domain.com/","orgType":"onprem"}"
2020-02-13 20:00:13.865 0300, 22607, 2, W, PermissionsListenerHolder, onRequestPermissionsResult, 21, "PermissionsListenerHolder: No permissions listener has been set"

Was this reply helpful? Yes No

Muslim Dayi 20 on at

Like (0)

Report

RE: Microsoft Dynamics 365 for Mobile - Certificate trusted on PCs but not on Android?

Hi ;

I got same error on Android Tablet , Did you find a solution to the problem?

Was this reply helpful? Yes No
MichaelE 20 on at

Like (0)

Report

RE: Microsoft Dynamics 365 for Mobile - Certificate trusted on PCs but not on Android?

@Muslim Dayi and anyone else with similar issues:

I am not sure how to answer that, really, as I am not sure if we do indeed face similar issues.

Did I solve that -particular- case: no!

Recap: I was trying to use "Dynamics 365 for Phones" on Android 9 with Dynamics 365 Server in what appeared to be v8.2. I was using a PKI setup for the certificate structure and with only one IP at my disposal I had Dynamics 365 and ADFS on the same box.

Essentially I was probably violating all priciples of best practice - but the curiosity remains.

It worked.

In every other instance, it actually worked.

Just -not- with that damned combination of "Dynamics 365 for Phones" and my PKI setup (Microsoft specifically advice a Public certificate - I never tested that).

But I was derailed.

Fiddling with all sorts of crazy workarounds I was eventually (probably mis-) led to believe that maybe all my sorrows were caused from being stucked with v8.2 on Dynamics 365 Server. Why stucked? Because I was somehow not able to upgrade any further. The database in particular became an issue.

This is where all my nightmares seriously mounted.

Trying to "convert" a legacy DB from all the way back from 2013 turned out to be an unbelievable challenge.

I ended up tearing the whole *** down and rebuild.

Pretty much to no avail.

But after having spent my entire life for several months on the internet (probably even ruining the entire internet in the process) I stumbled across a very -very- strange "upgrade path"..

So.. to keep what is already an unbearably long story just not suicidably long: I now have a test setup with -one- likely important change: I am now on Dynamics 365 Server v9.

Did it solve the original problem? No!

Did it make the problem irrelevant? Yes!

..oh, but why so?

Because this version seemingly has a much more powerful functionality when it comes to a browser based experience from any mobile device: PowerApps.

I was primarily envy at the nice chart functionality with "Dynamics 365 for Phones".

With PowerApps you can easily achieve super-cool and super-customized stuff.

Kudos to Microsoft for this achievement - seriously!

..don't know what the hell happened to the teams developer brains with regards to legacy database upgrade paths ( - seriously!)

Was this reply helpful? Yes No
Muslim Dayi 20 on at

Like (0)

Report

RE: Microsoft Dynamics 365 for Mobile - Certificate trusted on PCs but not on Android?

hi ;

İ resolved this problem with Global SSL certificate.

Local SSL Certificate is not accept in mobile applications, even if you import to the device

We replaced the local SSL certificate with the global SSL certificate.

Users login succesfully.

Was this reply helpful? Yes No

Join the conversation

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1

Sahan Hasitha 271

#2

Sohaib Cheema 97 User Group Leader

#3

André Arnaud de Cal... 83 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Identifying an Org as CDS or Dynamics

Get batch job history log from D365 FO to Power Automate

Gross and Net Weight of Shipments feeding back into Sales Order (from External Source)

Product updates

Dynamics 365 release plans