ODBC Troubleshooting
Unable to establish connection with data source
Issue: the connection status of the ODBC data source shows a red dot
 |
Solution:
Perform a test connection from the Plant Integration API Console. Follow these instructions.
Common error messages and possible causes:
Error message
Possible causes
"Message": "ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"
Incorrect DSN in connection.txt file or not using compatible driver for configuring ODBC System Data Source (32-bit vs 64-bit)
"Message": "[Microsoft][ODBC Driver 13 for SQL Server][SQL Server] Login failed for user ‘ed-cs’.”
Incorrect username or password in connection.txt file
"ExceptionMessage": "Format of the initialization string does not conform to specification starting at index xx.”
Unrecognized parameter or error in the connection.txt file.
Getting incorrect tag name, description, units or tag type in TrendMiner
Make sure the list.sql query returns the fields in the same order as specified in "How to set up an ODBC/OLEDB/SQLite data source?"
Getting the wrong tag type shown in TrendMiner
The tag type in TrendMiner is determined by the ‘type’ field returned for each tag in the list.sql query. That ‘type’ should match one of the supported tag types in TrendMiner, ‘ANALOG’, ‘DISCRETE’ or ‘DIGITAL’. If different from one of these, the type.csv file maps each type to one of the TrendMiner supported tag types.
Tag partially indexed or not indexing in TrendMiner
If a tag does not index or only partially indexes, make sure the output of the values.sql meets the following requirements:
Timestamps should be in chronological order, oldest first
All timestamps returned should be inside of the requested time interval
The complete response should be returned within a reasonable timeframe of 5-30 seconds. A well performing data source returns 1 month of data in around 1 second. The response time can be influenced by tweaking the index granularity setting in ConfigHub. Check the user documentation for more info.
Acceptable amount of datapoints within the given timeframe. The number of data points returned can be influenced by tweaking the index granularity setting in ConfigHub. Check the user documentation for more info.
The installed ODBC driver can't read the timestamps correctly. Learn more about this issue here.
Object of type 'System.Double' cannot be converted to type 'System.String'
"system.double cannot be converted to system.string" error in the connector logs usually means the timestamps and values are queried in the wrong order in the values.sql. Please make sure the timestamp gets requested first, then the values. E.g. something like SELECT data, timestamp from ... should become SELECT timestamp, data from ...