Sign Up for Training |
Jet Express Support |
Jet Reports Company Site
Jet 365 Financials
Jet Professional
Jet Enterprise
Downloads
Community
Submit a Request
Give Feedback

Troubleshooting the Dynamics NAV Web Service Data Source


Overview

NAV's Web Services is a powerful tool that can be used in conjunction with Jet Essentials 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


Error #1:

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

Possible issue: Check Codeunits that are published

  • Validate if Dynamics NAV 2013 Server Instance is running in Dynamics NAV Administration Console.
  • Locate the correct NAV Instance
  • If not running, restart
  • Check the codeunit, validate multiple codeunits that are published;
    • Unpublish all codeunits and pages
    • Republish just the Jet Codeunit and retest connection



Error #2:

Invoking the web service failed with the following message:

Unable to connect to the remote server

Troubleshooting:

Applicable to NAV 2015 Web Service

  • Validate if the Dynamics NAV Server Instance is running in the Dynamics NAV Administration Console .
  • Locate the correct NAV Instance
    • If the instance is not running, restart it
  • Follow the steps for troubleshooting Codeunits as listed above with Error #1



Error #3:

T he url 'http://[servername:port]/[NAV Service Instance]/WS/SystemService' is not valid. The following error was reported:

The report name could not be resolved: "[servername]"



Troubleshooting:

In the Data Source Settings [Jet ribbon > Data Sources > {select data source}], under the Web Service tab,

  • Verify that the name entered for the server is correct.
  • If not, update with the correct information and retest connection.



Error #4:

The url 'http://[servername:port]/[NAV Service Instance]/WS/SystemService' is not valid.  The following error was reported:

Unable to connect to the remote server


Troubleshooting:

  • Verify that the port number is correct and also matches what is shown in the NAV Administration Console .



Error #5:

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:

On the Web Service tab of the Jet Essentials Data Source Settings...

  • Verify that the instance field is populated with correct information.



Error #6:

Company '' does not exist


Troubleshooting:

On the Web Service tab of the Data Source Settings...

  • Verify that the correct Company can be selected from drop-down
  • If able to, select the company and re-test connection



Error #7

The codeunit '' does not exist

Troubleshooting:

On the Web Service tab of the Data Source Settings...

  • Verify that Codeunit {Jet_Data_Source} can be selected from drop-down
  • If able to, select Jet_Data_Source and re-test connection
  • Check if codeunit is published
  • Typing in “Jet Data Source” will present an error
    • Instead, be sure to select Jet_Data_Source from the Jet Codeunit drop-down menu
  • Select the correct Company from the Company drop-down menu
  • Test connection when completed.


Error #8:

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.


Root cause/Troubleshooting:

On the Web Service tab of the Data Source Settings...

  • Validate if “Use SSL encryption” is enabled/disabled
  • If enabled, confirm if enabled/disable in NAV Administration Tool [SOAP Services for the specific NAV Server Instance]. The settings should match.





Error #9:

The url 'http://[servername:port]/[NAV Service Instance]/WS/SystemService' is not valid.  The following error was reported:

The remote server returned an error: (401) Unauthorized.


Note: Jet Essentials 2012 R2 (v12.5.13072) and higher supports all four types of Dynamics NAV 2013 authentication:

  • WIndows Authentication
  • Username Authentication
  • NAV User Password Authentication
  • Access Control Service Authentication

(please see NAV 2013 Authentication Types )


Root cause/Troubleshooting:

In the Jet ribbon > Data Source Settings > Authentication

  • Validate authentication settings configured i.e. “Windows authentication”, “User Name authentication”, “NAV User  Password authentication”, “Access Control Service authentication”
  • Settings should match what is configured in the Dynamics NAV Administration Tool for that NAV Instance.

Example taken from an actual support case:


Troubleshooting/Root Cause:

  • Domain information should not be populated in both the User name and Domain fields
    • Remove domain (@island.com) from the Username field
  • Check if user is a user in NAV
  • Try using IP Address instead of Server name
  • Validate if user is able to get NAV.xml file to open via Internet Explorer by entering the server URL show in the error message.
  • Validate Authentication method selected for the Instance and in the Data Source


Error #10:

Issue encountered when attempting to connect to NAV 2013/R2 or higher RoleTailored Client.

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.


Root cause/Troubleshooting:

  • Validate server address is correct as shown.
  • In the ‘Services.msc’ Management Console, validate that SQL Server{SQLversion} and SQL Server Agent {SQLversion} are both ‘Started’
    • If not, ‘Restart’ the services
  • In the NAV 2013/2015 Administration Tool, validate the status of the Microsoft Dynamics NAV Server Instance is ‘running’
    • If in ‘stopped’ status, attempt to restart the server.
    • If successful, relaunch the RoleTailored Client



Error #11

Attempting to drilldown using RTC in a NAV SQL Server Data Source connection

Cannot interpret data as a URL.


Root cause/Troubleshooting:

If Client Services port is incorrect, above error will occur.


In the Data Source Settings...

  • Click Test Connection
  • Click “Drilldown” tab
  • Confirm “Use the Dynamics NAV RoleTailored Client (RTC)” is selected
  • Confirm the RTC Folder information is pointing to the correct RoleTailored Client directory
    • C:\Program Files (x86)\Microsoft Dynamics NAV\{version}\RoleTailored Client

To locate the necessary information:

  • launch the NAV RTC
  • select blue drop-down arrow

Populate the following information (example shown):

  • RTC server
  • Client Services port
  • RTC Instance


Note: After correcting the Client Services port number, refresh the report and then attempt drill-down once again.






Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments