Microsoft Dynamics Navision

Before investigating any DataShare Connect error validate that the SME can access the data through their Accounting Package.

This is the best way to double check the SME is using the correct credentials and has the correct access permissions for the data they are trying to upload.

If the user is unable to access the data using the credentials in their possession then it follows that DataShare connect will be unable to access the data using the same credentials.

For DataShare Connect to access the Microsoft Dynamics Navision data you will need to know;

• Which version of Microsoft Dynamics Naivison you wish to upload data from.
• The SQL Server Instance Name.
• The SQL Server User ID and Password that can access the Microsoft Dynamics data.
• Which Database you want to upload data from.

Single Installation + Single Company = Automatic Upload

In some circumstances DataShare Connect will launch and upload data automatically. This situation will occur when the following condition are true;

1. There is only one installation of Microsoft Dynamics Navision installed on the local desktop
2. There is only one company in the Microsoft Dynamics Navision database
3. The user performing the upload has sufficient Windows permissions to access the Microsoft Dynamics Navision database files as a part of their login credentials.

Uploading from a Remote Navision Database

If the Microsoft Dynamics Navision database is not on the same desktop where you have launched DataShare Connect then by default DataShare Connect will no be able to automatically find the Navision database.

In this scenario DataShare Connect will prompt the SME for the SQL Server Instance Name and Database name. If the database can be contacted across the network successfully DataShare Connect will request a username and password for the specified database.

If DataShare Connect fails to find the SQL Server or fails to login to the specified database using the credentials supplied verify the SQL server instance name, location and database by attempting to connect to the database using SQL Server Manaement Studio or similar.

If DataShare Connect does not detect Microsoft Dynamics Navision correctly.

If DataShare Connect does not detect the Microsoft Dynamics Navision package correctly when both DataShare Connect and Micorosoft Dynamics Navision are running on the same desktop check;

1. "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services" registry key must be checked. It must contain at least one subkey that matches “^MicrosoftDynamicsNavServer\$DynamicsNAV” regex.

Errors will be reported in the log file in the %appdata%\validis\logs folder.

This is the file that will be used by support to investigate and fix your issue. Visit this page for more information.

If DataShare Connect refuses the Microsoft Dynamics Navision credentials.

If the credentials the SME is supplying to DataShare Connect are refused you need to check that the current user actually has access to the SQL Server database where the Micrsosoft Dynamics Navision database exists. The current user must be at least a member of “db.datareader” user group.