Understanding error messages, troubleshooting and fixes to ETL+ problems
In this section
-
ETL+ Error Messages ETL+ error and warning messages. Text of messages found in ETL+ log files or on ETL+ screens , their meaning and appropriate actions to take in response.
-
ETL+ Installation Troubleshooting ETL+ not starting or crashing.
-
Testing Connections to DS Cloud Server Testing connections to DataSelf Cloud Servers databases using Microsoft SSMS or Excel.
-
Extraction Errors -
Upsert Missing or Duplicating Rows Troubleshooting Upsert.
-
"Driver installation failure" "Access database engine" / Excel Error message when attempting to open an Excel, .csv or MS Access file.
-
Access Database Engine: Required for ETL+ Excel, .csv & MS Access ETL+ requires the Microsoft Access database engine 2016 in order to connect to and extract Excel workbooks, .CSV, text, and MS Access databases. How to verify the engine/driver is installed and how to manually the driver. This driver is required by the ETL+ Source Driver for Microsoft Excel.
-
Convert version? Message. Message: Convert version? Please confirm you want to convert from version
to version . -
Warning: CSV ... has duplicated column name(s) Warning: CSV
has duplicated column name(s): . ETL+ is mapping only the first occurrence of each column. -
ETL+'s "Hidden Folders" How to delete the so called “hidden folders”. These folders contain configuration information/metadata and are store locally on the computer server executing any copy of ETL+.
-
No Log Records for Run Job After Run Job > Run Job via Agent on Job page no log records are added to ETL Log.
Other Troubleshooting Pages
-
ETL+ Issues Importing from Excel Also .csv and Microsoft Access files
-
Microsoft T-SQL – T-SQL is the SQL dialect used by the ETL+ Design Page, and the ETL+ Load Upsert, and ETL+ Load Replace panels.
-
DataSelf Windows Service - Configure for Auto Start – The DataSelf Agent service may not startup at Windows bootup unless properly configured.
The SQL statements and syntax used in the Extract SQL Statement panel must work with the SQL syntax supported by the ETL+ Source Driver used to connect to the associated Source Object.