A part of the NAV 2015 Web Client is to be able to use part of the host header to decide wich tenant to connect to.  For example the domain name kappi.example.com will look for that Alternate Id in the tenant registration to find the correct tenant Id to connect to.  This requires a small change in the WebClient web.config file.

This week I was installing a new NAV environment on Azure.  I wanted to be able to use the Remote App to access and manage the server machines and since I can’t create a NAT rule to use more than one machine for a single port I must install the Remote Desktop Gateway and the Remote Desktop Web Access on that same Web Server.

I use a different host name for the Remote Desktop deployment and by defining the host header in the Default Site binding I make sure that all my Remote Desktop Services are working correctly.

In the Web Client binding I clear the host header to make sure that everything else is directed to NAV.

When starting up the Web Client everything looks fine until the NAV Role Center starts.  Then I get the error “Communication with the server failed, and the content cannot be displayed. Refresh the page or open a new browser window.” and everything stops.

CommunicationFailed

To fix this I needed to update the web.config file in the WebClient folder.  There I found the line

<serviceHostingEnvironment aspNetCompatibilityEnabled=”true” />

and modified to

<serviceHostingEnvironment aspNetCompatibilityEnabled=”true” multipleSiteBindingsEnabled=”true” />

Now everything works fine.

 

Leave a Reply

%d bloggers like this: