Dynamics NAV / MSDYN365BC - The Hostname could not be parsed or Invalid.

Hi Readers,

This is a quick blog about some recent findings that we had during a Project.

This is in relation to the URL specified in the service tier.

In this article, we will see what kind of issues can happen due to invalid URL is Service Tier and How to fix those issues that you found.

Multiple Errors that this article will help to fix -

1. The Hostname could not be parsed.
2. Invalid URI: The hostname could not be parsed.

Let's start it where these Error messages will appear -

1. When you try to use Help About This Page, client crash with Error Message - The Server was unable to process the request. The Application will close.

2. Approval Emails are generating the wrong URL.

3. Approval Notifications are not be sent via Job Queue with Error Message The Hostname could not be parsed.

4. Issues in Web Services, wrong URL.

Investigation - 

I love to start my investigation from Event Viewer. When I started checking here is what I Found -  The Hostname could not be parsed.

When I tested trick in my book and did not find anything. Then I created a new service map to the database and everything started working fine.

What Next?
I compared both service tier Files, and there was the culprit.

So What You need to check?

• Check all the URL's that you have mapped in the service tier.
• There are 04 URLs in one Service where you can mess up.
• Web Client URL - Check the suggestion in the Last tab as shown below.
• Windows Client Base URL - Check the suggestion in the Last tab as shown below. It normally starts with DynamicsNAV:// which we miss most of the time.

• SOAP Base URL - Check the suggestion in the Last tab as shown below.
• ODATA Base URL - Check the suggestion in the Last tab as shown below.

Once you set all these 04 URLs correctly, restart your services and you should be good to go.

Hope this article helps to fix issues if you get stuck in a project.

Regards,
Saurav Dhyani
www.sauravdhyani.com