How to: Troubleshoot Data Director 3.02.xx
The following are basic steps on how to handle errors that may come up in DD3.
CFront is not correct version, either too old or never
The files in the cfront folder are pulled from the NAV installation or Hotfixes that may have been applied. To match the version of the current NAV Server, update the files in the cfront folder with files from your installation. Most files can be found in the NAV Client folder and the cfront dll files are located in Devkit folder on the NAV CD or in the latest Hotfix that may have been applied.
DD License file is invalid
If you have an older version of the DD License file, you need an updated file. To check if your file is an older version or not, open it with Notepad, and if it starts with DD_LIC you have an older file, but if it starts with DD_LIC1 then you have a newer file and it should work with DD3.
Error: Dynamic NAV Developer client is not installed, but it is....
DD 3.2.16 has a fixed path for the NAV 2013 Developer client, so if you are running the newer 2013 R2 or later, DD may come up with this error. There is a work around to fix this, but a later version of DD will also have fix for this.
Add Registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Dynamics NAV\70\RoleTailored Client
Value: Path=
You will have this value under different version folder, for example 71, but DD 3.2.16 or older only looks under version 70 for the path.
Date value is off by a day when sending data with TS
If Date value is off by a day (ahead or behind), modify the Codeunits: 99008908 & 99008920 function: AddValuesGeneric change the Code for 'Date' to:
'Date':
BEGIN
tmpDate := FldRef.VALUE;
DataClient3.SetAsString(BOUtil.STDDateToString(tmpDate)) //LS7.1-03
END;
Note: The code is twice in within the function, change both sections to same code.
After Installing DD 3.2.8 or later, Nav gives error message when running job
Registration process of the TransAutomClient changed for support with NAV 2013, and it may cause an error when running codeunits that point to the older DD3 client control.
Uninstall older DD, clear the Registry out of any trace of TransAutomClient entry (delete the key that includes the entry), and then install DD again.
Check if the DataClient variable in NAV Codeunit Global Variables is pointing to TransAutomClient 3.2 and does not show Unknown Automation Server.TransAutomClient
LS NAV Codeunits that need to be validated are:
- 99001474 Data Distribution v3.0
- 99001475 Distribute FOB Objects v3.0
- 99001476 Data Director Utils v3.0
- 99008920 POS Data Client Utility v3.0
PlusCFrontClient: ConnectServerAndOpenDatabase error
Check the document Troubleshot DD2 for more details on this error.
Data Director hangs, and does not process jobs or always shows Error
First upgrade to the latest DD from the LS Retail Portal (Latest Version). If that does not help, activate debugging and catch the error and see if it is something that points out what could be wrong, if not send the logs to LS Retail Support. Any DD version older than 3.2.22 should be upgraded to the latest version, if there is any strange error or behavior.
DD fails to start up after upgrading from 3.2.12 or older
The configuration file may be out of date and missing necessary data for DD to start. In the DD Configuration Tool, click Get Config for the DD Host, then click Send Config. This will update the configuration file to the latest version without overriding any modifications that have been done to it. If you want fresh configuration files with default settings, go to the System Config tab and click the Reset Config button.
Error 12305
Error 12305 is a general error for communication. To find out what is going on, open the Configuration Tool, go to the Debug tab, open the Debug on the DD Old and Router applications, and connect to it. You will see a more detailed error log there why the DD cannot process the request. See the Manual for information on using the DD3 TransAutomClient that can display the real error message to the NAV Client.
Error 12306
Error 12306 is a general error from the Database processing. To find out what is going on, open the Configuration Tool, go to the Debug tab, open the Debug on the Database application, and connect to it. You will see a more detailed error log there why the DD cannot process the request. See the Manual for information on using the DD3 TransAutomClient that can display the real error message to the NAV Client.
Null Data, Wrong Field Type or Wrong DateTime when replicating NAV 2013
Use DD 3.2.16 or newer. Do not do any field mapping or if you have, check if Field types are the same on both fields. Check the connection string that it has plugin version parameter |ms|nav7xx.
A Call to TransAutomClient failed because object type cannot be converted or DLL cannot be found
If the DD DLL cannot be found, copy the latest DLL from the DD bin folder and add them to the Add-ins folders, both for Role Tailor Client and Service Tier.
If there is a convert error, there is a mismatch in DD DLLs version in the Add-ins folders. Copy the latest DLL from the DD bin folder and replace all files in all Add-ins folders, both for Role Tailor Client and Service Tier.
The DD DLLs that are needed are:
- DDConfigClient.dll
- LSRetail.DD.Common.Data.dll
- LSRetail.DD.Common.dll
- TransAutomClient.dll.
In some cases it is needed to import all the CodeUnits that use the TransAutomClient.dll again and recompile them. The codeunits can be found under the Objects\TXT folder in the LS Retail Nav release package.
LS NAV Codeunits that need to be validated are:
- 99001474 Data Distribution v3.0
- 99001475 Distribute FOB Objects v3.0
- 99001476 Data Director Utils v3.0
- 99008920 POS Data Client Utility v3.0
DD is holding up user sessions on NAV Database
When DD is used for Transaction request, like from POS, it may take up a lot of sessions if there are many requests coming in at same time. To release the session, set the Timeout value under App Data for Database connection to timeout after 1 min. Also use the latest version of DD as there may have been some fixes done to help releasing the session if they get locked for long time.
How to activate File Debug Logging
- Open the DD Configuration Tool.
- Go to the Debugging tab.
- For DD Processing Logging, click the Get Config button, type in 15 in the Startup Level box for Router, Database and DD Old, click the Send Config button or Restart DD. The log files will appear under Log folder in Data Folder (see Base Config tab).
- For Errors that show up in NAV, like connection problems or Scheduler job error, type in 15 in to the Client Control Field. Restart NAV Client/NAS Service. The log files will appear under Log folder in Data Folder (See Base Config tab). For NAV Client you may need to run it As Administrator for logging to work.
How to activate Live Debug Logging
- Open the DD Configuration Tool.
- Go to the Debugging tab.
- For DD Processing Logging, click the Open button next to the Startup Level box for Router, Database, or DD Old, depending on what you want to debug. A new window will open for each process, and to connect to Debugging stream click Connect.
- To see detailed debugging, select Detail L1 and/or Detail L2.
- To see if the process is locked and not doing anything, select Tick, which will show a lot of status messages on current process for 5 seconds, if the DD process is in middle of doing something or waiting for something.
How to check Job Queue status and frozen processing status
- Open the DD Configuration Tool.
- Go to the Debugging tab.
- Click on Queue button.
- Queue status window will open that show status of all active queues. Open up the Queue and detailed information will be displayed.
- Check Waiting status, if it is True, it means the queue is waiting for result status from job processing. If DD seem to be frozen and nothing is happening, press Reset button.
- To see the first job in the queue, and the one that is causing error, press Show 1st Pk button and it will display the Guid and job id for the job. This can be used to look up information about the job in the log files to see what happen during the job processing and why DD stopped.
-