
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Qlik Sense Tasks are failing with the error "The application has failed to start because its side-by-side configuration is incorrect"
Dec 19, 2023 8:50:29 AM
Dec 19, 2023 8:50:29 AM
All the Qlik Sense Tasks associated with the ODBC Data connection fail with the below error on a Multi-node environment:
The application has failed to start because its side-by-side configuration is incorrect
The Task status in the Qlik Sense Management Console states:
This issue can be identified by reviewing the Qlik Sense Script logs (How to find the Script (Reload) logs in Qlik Sense Enterprise on Windows). They will read:
20231206T205455.165+0800 Error: Failed to start connector: QvOdbcConnectorPackage.exe (System error: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.)
20231206T205455.166+0800 Execution Failed
20231206T205455.166+0800 Execution finished.
Resolution
Option One
The Microsoft tool Sxstrace tool can be used to identify the root cause:
- Run an administrative Command prompt
- Enable tracing by executing the below command:
sxstrace trace -logfile:sxstrace.etl - Reproduce the issue by restarting all the Qlik Sense services and re-running a Failed task.
- Go back to the Command prompt and press Enter to end the tracing.
- Convert the tracing into a human-readable format with
sxstrace parse -logfile:sxstrace.etl -outfile:sxstrace.txt - Analyze the resulting sxstrace.txt file and check for the errors with your IT team.
By default sxstrace.etc and sxstrace.txt files are saved in "C:\Windows\System32\" path
Option Two
- Login to all the Qlik Sense Windows machine
- Go to "C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\" path
- Compare the "qvodbcconnectorpackage.exe.config" files
Configuration files must be same across the environment.
Cause
- ODBC Config files can be corrupted or modified
- DLL files can be corrupted
Environment