Overview
Dynamics NAV's Web Services is a powerful tool that can be used in conjunction with the Jet Excel add-in to provide you with access to your NAV data.
Occasionally, something needs to be adjusted - and some of the error messages generated by Web Services can be a bit cryptic.
Here are a few key suggestions to help you in your initial stages of troubleshooting.
Messages
-
Server Unavailable
Complete text of error message is:
The url 'http://[servername:port]/[NAV Server Instance]/WS/SystemService' is not valid. The following error was reported:
The remote server returned an error: (503) Server Unavailable.
Troubleshooting:
Applicable to NAV 2013 Web Service
Using the Dynamics NAV Administration Console, validate that the NAV Server Instance (shown in the error message) is running.
- Locate the correct NAV Instance
- If not running, restart
- Troubleshoot the code Units. Check the codeunit, validate multiple codeunits that are published:
- Unpublish all codeunits and pages
- Republish just the Jet Codeunit and retest the connection
- Locate the correct NAV Instance
-
Invoking the web service failed
Complete text of error message is:
Invoking the web service failed with the following message:
Unable to connect to the remote server.
Troubleshooting:
Applicable to NAV 2015 (and higher) Web Service
Using the Dynamics NAV Administration Console, validate that the NAV Server Instance (shown in the error message) is running.
- Locate the correct NAV Instance
- If not running, restart
- Follow the steps for troubleshooting codeunits as listed in error #1
- Locate the correct NAV Instance
-
The remote name could not be resolved
Complete text of error message is:
The url 'http://[servername:port]/[NAV Server Instance]/WS/SystemService' is not valid. The following error was reported:
The remote name could not be resolved: 'servername'
Troubleshooting:
In the Jet Excel add-in...
- Access the Data Source Settings
- Go to the Web Services tab
- Verify that the name entered for the server is correct
- If not, correct it and then re-test
-
(404) Not Found
Complete text of error message is:
The url 'http://[servername:port]/[NAV Server Instance]/WS/SystemService' is not valid. The following error was reported:
The remote server returned an error: (404) Not Found.
Troubleshooting:
In the Jet Excel add-in...
- Access the Data Source Settings
- Go to the Web Services tab
- Verify that the name entered for the instance is correct
- If not, correct it and then re-test
-
Unable to connect to the remote server
Complete text of error message is:
The url 'http://[servername:port]/[NAV Server Instance]/WS/SystemService' is not valid. The following error was reported:
Unable to connect to the remote server.
Troubleshooting:
- Verify that the port number listed in the error is correct and also matches what is shown in the Dynamics NAV Administration Console.
- Using the Dynamics NAV Development Environment, verify that the server name you are using in your Jet Data Source Settings is correct (File|Database|Information).
-
(500) Internal Server Error
Complete text of error message is:
The url 'http://[servername:port]/[NAV Server Instance]/WS/ CRONUS%20USA,%20Inc/Codeunit/Jet_Data_Source' is not valid. The following error was reported:
The remote server returned an error: (500) Internal Server Error.
Troubleshooting:
Use the Development Environment's Object Designer to confirm that the Jet Codeunits are installed and are of the correct version for the version of the Jet Excel add-in you are using:
-
The Dynamics NAV web service is improperly configured.
Complete text of error message is:
The Dynamics NAV web service is improperly configured. A web service server and instance name must be specified and the port number must be between 1 and 65535 .
Troubleshooting:
In the Jet Excel add-in...
- Access the Data Source Settings
- Go to the Web Services tab
- Verify that the Instance field is populated with the correct information.
-
Company ' ' does not exist
Complete text of error message is:
Company '' does not exist.
Troubleshooting:
In the Jet Excel add-in...
- Access the Data Source Settings
- Go to the Web Services tab
- Verify that the correct Company can be selected from the drop-down list
- If able to do so, select that company and re-test the connection
-
The codeunit '' does not exist
Complete text of error message is:
The codeunit '' does not exist.
Troubleshooting:
In the Jet Excel add-in...
- Access the Data Source Settings
- Go to the Web Services tab
- Verify that Codeunit Jet_Data_Source can be selected from the drop-down list
- If able to, select Jet_Data_Source
(note: typing in the name of the codeunit will result in an error... it must be selected from the list) - Select the correct Company from the drop-down list
- Save the settings and re-test the connection
-
The underlying connection was closed
Complete text of error message is:
The url 'http://[servername:port]/[NAV Server Instance]/WS/SystemService' is not valid. The following error was reported:
The underlying connection was closed: An unexpected error occurred on a send.
Troubleshooting:
- Access the Data Source Settings
- Go to the Web Services tab
- Check whether or not Use SSL encryption is enabled or disabled
- Access the Dynamics NAV Administration Console
- Open the SOAP Services section for the specific NAV Service Instance being used
- Check whether or not Enable SSL is checked.
-
(401) Unauthorized
Complete text of error message is:
The url 'http://[servername:port]/[NAV Server Instance]/WS/SystemService' is not valid. The following error was reported:
The remote server returned an error: (401) Unauthorized.
Troubleshooting:
- Ensure you are using one of the following five types of Dynameics NAV authentication supported by Jet Reports:
- Windows Authentication
- User Name Authentication
- NAV User Password Authentication
- Access Control Service Authentication
- Office 365 Authentication (also known as OAuth authentication)
For detailed information for each authentication type, please see NAV 2015 Authentication Types - Check if user is a user in NAV
- Try using IP Address instead of Server name
- Ensure that the user is able to get the NAV.xml file to open by entering the server URL (shown in the error message) in Internet Explorer's address bar.
- Ensure you are using one of the following five types of Dynameics NAV authentication supported by Jet Reports:
-
Either the URL is incorrect or the server is currently not available
Complete text of error message is:
A server was not found at "net.tcp://[servername:port]/[NAV Server Instance]/Service". Either the URL is incorrect or the server is currently not available.
Troubleshooting:
Issue encountered when attempting to connect to NAV 2013 R2 (or higher) RoleTailored Client (RTC).
- Confirm that the server shown in the error message is correct
- In the ‘Services.msc’ Management Console, confirm that SQL Server{SQLversion} and SQL Server Agent {SQLversion} are both ‘Started’
- In the Dynamics NAV Administration Tool, confirm that the status of the NAV Server Instance is ‘running’
- Unpublish all codeunits and pages
- Republish just the Jet Codeunit and retest the connection
-
Cannot interpret data as a URL
Complete text of error message is:
Cannot interpret data as a URL .
Troubleshooting:
If Client Services port setting is incorrect, above error will occur.
To located the necessary information:
- Access the NAV RTC
- Click the blue drop-down arrow:
- Click Select Server...
-
To configure your drilldown settings:
- Access the Data Source Settings
- Go to the Drilldown tab
- Configure the RTC folder for the location where your RTC is installed
- Configure the RTC Server, Client Service Port, and RTC Instance from the information you gathered from within NAV:
Comments