Skip to main content
Announcements
Talend Data Catalog 8.0 End of Support: December 31, 2024 Get Details

Qlik Sense Tasks are failing with the error "The application has failed to start because its side-by-side configuration is incorrect"

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Rakesh_HB
Support
Support

Qlik Sense Tasks are failing with the error "The application has failed to start because its side-by-side configuration is incorrect"

Last Update:

Dec 19, 2023 8:50:29 AM

Updated By:

Sonja_Bauernfeind

Created date:

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:

Message from ReloadProvider: Reload failed in Engine. Check engine or script logs.
Changing task state from Triggered to Started
Trying to start task. Sending task to slave scheduler QlikServer1.Domain.local
Changing task state to Triggered
 

ODBC Connection Error 2.png

 

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:

  1. Run an administrative Command prompt
  2. Enable tracing by executing the below command:
    sxstrace trace -logfile:sxstrace.etl
  3. Reproduce the issue by restarting all the Qlik Sense services and re-running a Failed task.
  4. Go back to the Command prompt and press Enter to end the tracing.
  5. Convert the tracing into a human-readable format with
    sxstrace parse -logfile:sxstrace.etl -outfile:sxstrace.txt
  6. 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

  1. Login to all the Qlik Sense Windows machine
  2. Go to "C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\" path
  3. 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

 

Labels (2)
Version history
Last update:
‎2023-12-19 08:50 AM
Updated by: