Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Contact
Find Answers
Join Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Get Support
Have a Question?
Search Qlik's Support knowledge database or request assisted support for your highly complex issues.
Submit a Case
Talk with a Representative
Critical Issues
Experiencing a business critical issue? Please Contact us by phone. Click here to view phone numbers by region.
Contact UsWelcome Guest
Installed Qlik Products
My Environments
Log your environments to ensure faster and more targeted troubleshooting.
View Available Licenses
My Licenses
Understand your licenses to help you maximize your experience.
- ALERT: Qlik Product Download Page Click here
- ALERT: Support Alert Click here
Knowledge
How to collect ODBC logs
Article Number: 000055332 | Last Modified: 2019/07/16Description
1. ODBC Connector logs:
2. Driver debug logs:
- Modify C:\Program Files\Common Files\Qlik\Custom Data\QvODBCConnector\QvODBCConnector.exe.config and change log level to ALL
- Re-run the test above and collect the logs from C:\ProgramData\Qlik\Custom Data\QvODBCConnector\Log
2. Driver debug logs:
- Open Registry Editor (Start->Search for “regedit”)
- Create the following entries under HKEY_LOCAL_MACHINE\SOFTWARE\Qlik\Qlik SQL Server ODBC Driver\Driver
- LogFileCount 50
- LogFileSize 20971520
- LogLevel 6
- LogPath A valid path on disk (e.g., C:\ProgramData\Qlik\Driver)
- Note that in older Sense versions the path in registry is called "HKEY_LOCAL_MACHINE\SOFTWARE\Simba\Simba SQL Server ODBC Driver\Driver" and new Sense versions have the path under ""HKEY_LOCAL_MACHINE\SOFTWARE\Qlik\Qlik SQL Server ODBC Driver\Driver""
- Note that these instructions are written for MSSQL and if you need to generate the debug Simba logs for other data sources, these entries have to be placed their respective data sources.
- Enable ODBC tracing on OS level and attach the logs (please attach all logs again - ODBC Connector, driver log as above and this ODBC trace log). The directions are here
- https://docs.microsoft.com/en-us/sql/odbc/admin/setting-tracing-options
- https://docs.oracle.com/cd/E17952_01/connector-odbc-en/connector-odbc-configuration-trace-windows.html
Get Answers
Find Answers
Get Support
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a case
Talk with a Representative
Critical Issues
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.