I have the database in azure sql, the server instance on a VM in azure and the dev environment and NAV client on my own local PC.
If I manually from my local PC run the NAV windows client it connects fine by using the settings I set up in ClientUserSettings.config.
But when I from my local PC run the dev environment and connect to the database and try to click on run on e.g. a page the NAV client does not connect because it tries to connect to NAVserver:port/instance and that NAVserver is not on my local network.
Tried “tricking” it by changing my hosts file so that NAVserver resolved to the IP of the NAVserver in the Azure vm but that didn’t work.
All nessesary ports are open (Management, Client, Soap, Odata, Help etc…) on the Azure VM.
What i’m I missing here? or is what I’m trying impossible?
Since my last post I found out that I edited my hosts file wrong. So now the name NAVserver correctly resolves to the IP of the NAVserver of the Azure vm.
The error that i’m now getting is:
“Identity check failed for outgoing message. The expected DNS identity of the remote endpoint was ‘NAVserver’ but the remote endpoint provided DNS claim ‘mydomain.com’. If this is a legitimate remote endpoint, you can fix the problem by explicitly specifying DNS identity ‘mydomain.com’ as the Identity property of EndpointAddress when creating channel proxy.”
That is the same error I got before editing the CustomSettings.config of my users NAV windows client and using mydomain.com as the DNSidentity value.
But the Dev environment doesn’t use that CustomSettings.config file and I see no place to specify that in the options in the dev environment??
Is there any particular reason why you have selected this architecture for a NAV development environment?
While the Azure SQL is great for production sites, then you are going to have a lot of extra work in connection with upgrades etc.
Ideally then you should run the finsql.exe (dev env) directly on the NAV services.
Personally then for a fresh development environment I always use the standard NAV Azure VM. That comes with both SQL, IIS, NAV and everything else configured. Even VS. You can have it up and running in 15-30 minutes, even with certificates.
And when I don’t need it anymore, I can either just delete or set it offline until I need it again.
I’m kinda new to NAV and SQL, but i’ve dived head first into setting up and managing NAV on Azure and the plan is to run a production environment for multiple companies with the databases in Azure SQL, the instances and web on a VM manually installed, and the clients out in the field.
My goal is to not have more than one VM running in Azure, and lets the few customers who wants to develop and our internal Dev folks connect directly from their own machines. I know that requires firewall whitelisting in the Azure SQL.
You mention that it requires a lot of extra work with upgrades - could you expand on that?
Yeah running it on the production VM or a VM on the same Vnet in Azure works but my goal was to be able to develop directly from a local PC and run the windows client from the dev environment.
I think the only thing missing is that I in the Dev environment options can’t find the DnsIdentity entry like I can in the clients CustomSettings.config:
which I change to
only server name, instance name and port are available…
So how to I “tell” the Dev environment to use DnsIdentity to be = mydomain.com ?
