Health Check on Microsoft Dynamics Web Service Communication Fails

Symptom

A communication with Microsoft Dynamics Web Service is not possible showing one of the following errors.

(401) Unauthorized, (404) Not found, The remote name could not be resolved, Invalid URI: Invalid port specified. …

Cause

The URL is not correct, Microsoft Dynamics web service is not set-up properly or username and password is incorrect.

Solutions

1. (401) Unauthorized – follow this link.
2. (404) Not found.
   Instance name of Microsoft Dynamics Web Service is is wrong.
   
   
3. The remote name could not be resolved: ‘servername’
   The servername is wrong.
   
   
4. Invalid URI: Invalid port specified.
   The port of Microsoft Dynamics web service does not exist. Check your port settings.
   
   
5. Unable to connect to remote server:
   Check the port in your URL syntax. Default is 7047.
   
   
6. Dynamics NAV 2009 R2 only: msxsml.dll: The system cannot find the file…
   In some Anveo versions, you have to turn off Server Logging in Anveo Setup to run a Health Check, if Classic Client runs on a different machine than Dynamics NAV web services – or if logging folder does not exsits or is not writable.

 Note: This article is for Anveo Client Suite 6 and newer.