Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
ngpham
Contributor
Contributor

QMC reload task database connection "Request Aborted" error

We are installing the Qlik Sense Server Jun 2019. In QMC, we configured a reload task for my main App to run hourly.

When starting, load script will connect to MSSQL DB to read data from the database in Data Connection 'Analytics' with Connection String: CUSTOM CONNECT TO "provider=QvOdbcConnectorPackage.exe;driver=mssql;host=111.111.11.11;database=myDatabase;integrated security=False;Encrypt=false;TrustServerCertificate=false;Trusted_Connection=false;EnableQuotedIdentifiers=1;ReturnSpecificTypeAsOdbcType=yes;".
 
After setting up everything, we tried starting reload task manually. It returned SUCCESS. However, after some times running at scheduled time, it turns to Failed.
 
Checking the log file, we found:
    2019-09-05 12:33:32      Reload Executed By            UserDirectory=INTERNAL; UserId=sa_scheduler
    2019-09-05 12:33:32      Process Executing             Qlik Sense Server
    2019-09-05 12:33:32      Process ID                    4232
    2019-09-05 12:33:32      Grpc version                  5.0.0
    2019-09-05 12:33:32      Protobuf version              3.4.0
    2019-09-05 12:33:32 0026 LIB CONNECT TO 'Analytics'
    2019-09-05 12:33:45      Error: Request Aborted.
    2019-09-05 12:33:45      Execution Failed
    2019-09-05 12:33:45      Execution finished.
 

Then we try to manually start the reload task many times, it still FAILed, although connection to DB server is smooth. Running the load script from the Script Editor shows that the Data Connection 'Analytics' connected and success.

 
We also found that 2 reload tasks of Apps: "License Monitor" and "Operations Monitor" also FAILED with message: "Status Message    Connector reply error: ***"
 
 
Could you advise us how and where to check why the task failed?
 
Note: no Section Access is being used in this app.
2 Replies
shaun_lombard
Creator II
Creator II

Is there a reason why you chose to use ODBC? Have you tried the OLEDB connector?
Are you in a multi-node environment?
shaun_lombard
Creator II
Creator II

Sample OLEDB connection string:
OLEDB CONNECT TO [Provider=SQLOLEDB;Integrated Security=SSPI;Data Source=111.111.11.11;Initial Catalog=myDatabase;]