DMT Common Errors

This page lists the common errors that can occur with DMT. It's constantly updated, so check it regularly.

Note: If you encounter new errors, please don't hesitate to contact support to let us know.

 

Install and Launch DMT

 
Error: Multiple errors occur when installing DMT on Windows Server 2012 R2.
Fix: Before installing DMT on Windows Server 2012 R2, you need install .NET Framework 3.5 by following the instructions on this page: Enable .NET Framework 3.5 by using the Add Roles and Features Wizard
Do not try to download the .NET Framework installer and install it directly because it doesn't work on Windows Server 2012 R2. You must follow the instructions on page mentioned above.
 

ODBC Connections

 
Issue: I cannot see my ODBC Data Source in DMT.
Possible Cause 1: DMT can only see 32 bits ODBC Data Sources, so you must use the "ODBC Data Sources (32-bit)" entry in the control panel if you use a 64 bit version of windows. You can also access it from the Settings page.
Possible Cause 2: DMT can only see System DSN (Data Source Names) so make sure you select the "System DSN" tab when you create your ODBC DSN in the ODBC control panel.
 

Pre and Post Processes

 
Error: The pre-process of a load job (a batch file) copies the data file to load from a network drive to the local drive. It works well when the load job is run from the DMT client, but not when run from the Scheduler.
Possible Cause: If you use network drive(s) in your pre-processes, try using the full UNC path rather than network drive letters. e.g. \\ServerName\Folder rather than T:\
 

Scheduling

 
Error: An extract or load job that works well when run from DMT client, fails when run by the scheduler.
Possible Cause: The scheduling service runs under a different user (i.e. Network service) so it might not have the same user rights that when you log on to DMT client. Try changing the user that logs on to the DMT Service in the Windows Service Control Panel.
 

Miscellaneous

 
Error: DMT hangs and I can't close the application.
Possible Cause: There might be an error message displayed in the background. Try to flick through the windows with Alt + Tab and you might see the error message. Click ok on it to regain access to the application.