Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
"Server connection timeout occurred" in Dynamics NAV App on Android
kev_santos
Member Posts: 2
Hello guys!
I am trying to resolve the "Server connection timeout occurred" in Dynamics NAV Universal App on Android and we're only doing this for demo purposes. I am able to connect to the NAV Web Client but not for Universal App.
I made it worked before (in reference to Saurav Dhyani's blog using NAV 2017) until there's an update that probably affects recognizing SSL certificate. I made it using Android Lollipop before but now we're using Android Nougat and Oreo (Samsung Galaxy J2 Pro and Nokia 7 plus to be exact)
So to recap, here's what I did:
1. Created SSL certificate (I used New-SelfSignedCertificateEx.ps1) for my hostname and local IP address
- Entrust the certificate in the Trusted Root Certification Authorities
- Enable Allow permissions for everyone in Manage Private Keys...
2. Created user in Dynamics NAV 2017 (for NAV User Password authentication)
3. Had my NAV instance set to following:
- Enter Certificate Thumbprint based on the generated thumbprint by the PowerShell
- Changed Credential Type to NavUserPassword
- Enable SSL for both SOAP and OData Services
- Set URL for the following:
* Web Client Base URL: https://[hostname/IP address]:443/DynamicsNAV100/WebClient
* SOAP Base URL: https://[hostname/IP address]:10047/DynamicsNAV100/WS
* OData Base URL: https://[hostname/IP address]:10048/DynamicsNAV100/OData
- Save configuration
4. Navigated C:\Users\[User]\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\100 and edit ClientUserSettings.config file
5. Navigated C:\inetpub\wwwroot\DynamicsNAV100 and edit web.config file
6. Binded the created certificate in IIS
7. Exported the certificate to be installed in phone (both bearing the hostname and IP address) and installed it in them
I did all of them and what's weird is it only works in Windows Phone (Microsoft Lumia 950 XL) perfectly. I used both IP address and hostname.
I wonder where did I get wrong or is there an update from Android or the app that keeps itself from accessing NAV. It pisses me off when nobody got the right answer even in Microsoft Community.
I also read some of the questions same as mine but no one answered correctly. I hope this time I can have it right!
Thanks in advance!
I am trying to resolve the "Server connection timeout occurred" in Dynamics NAV Universal App on Android and we're only doing this for demo purposes. I am able to connect to the NAV Web Client but not for Universal App.
I made it worked before (in reference to Saurav Dhyani's blog using NAV 2017) until there's an update that probably affects recognizing SSL certificate. I made it using Android Lollipop before but now we're using Android Nougat and Oreo (Samsung Galaxy J2 Pro and Nokia 7 plus to be exact)
So to recap, here's what I did:
1. Created SSL certificate (I used New-SelfSignedCertificateEx.ps1) for my hostname and local IP address
- Entrust the certificate in the Trusted Root Certification Authorities
- Enable Allow permissions for everyone in Manage Private Keys...
2. Created user in Dynamics NAV 2017 (for NAV User Password authentication)
3. Had my NAV instance set to following:
- Enter Certificate Thumbprint based on the generated thumbprint by the PowerShell
- Changed Credential Type to NavUserPassword
- Enable SSL for both SOAP and OData Services
- Set URL for the following:
* Web Client Base URL: https://[hostname/IP address]:443/DynamicsNAV100/WebClient
* SOAP Base URL: https://[hostname/IP address]:10047/DynamicsNAV100/WS
* OData Base URL: https://[hostname/IP address]:10048/DynamicsNAV100/OData
- Save configuration
4. Navigated C:\Users\[User]\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\100 and edit ClientUserSettings.config file
5. Navigated C:\inetpub\wwwroot\DynamicsNAV100 and edit web.config file
6. Binded the created certificate in IIS
7. Exported the certificate to be installed in phone (both bearing the hostname and IP address) and installed it in them
I did all of them and what's weird is it only works in Windows Phone (Microsoft Lumia 950 XL) perfectly. I used both IP address and hostname.
I wonder where did I get wrong or is there an update from Android or the app that keeps itself from accessing NAV. It pisses me off when nobody got the right answer even in Microsoft Community.
I also read some of the questions same as mine but no one answered correctly. I hope this time I can have it right!
Thanks in advance!
0