Troubleshooting connections to data sources may require tracing data traffic to reveal the communication patterns and details between a client and the database server.
We advise to first narrow down the issue as much as possible. If the load script of the .qvw / .qvf contains a lot of statements it helps a lot if a smaller document can be created, one which contains only the problem statements.
For steps on enabling ODBC Tracing, see the following:
Setting Tracing Options
Enabling ODBC Tracing on Windows
In addition, enable QVConnect logging:
Troubleshooting Qlik products: QVConnect logging
Related Content
Troubleshooting Data Connections in Qlik Cloud and Qlik Sense Enterprise on Windows
Troubleshooting Qlik products: QVConnect logging
Troubleshooting Qlik products: How to generate OLEDB tracing
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
