Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

QV Server Reload never keeps running... ODBC/Permission issue?

My application connects to an iSeries/AS400 through ODBC.   I have set up a System DSN through the QV 32-bit Administrator from the Tools Menu on the Script Editor.

I can run this reload manually from Qlikview.

When I run this from the ReloadEngine/Scheduler - the task just keeps running.  

My QVServer Services run under a local administrator account, but the server is a Domain Member Server.    Even though I set up a System DSN, could there be an issue because I am not running my QV Server with domain credentials?

I am on most current - 11.2 SR10

3 Replies
Not applicable
Author

3/2/2015 6:29:53 PM Error Document open threw an exception. Exception=The currently executing operation was aborted.
3/2/2015 6:29:53 PM Error The sourcedocument failed to open.. Exception=System.Runtime.InteropServices.COMException (0x80010108): The object invoked has disconnected from its clients. (Exception from HRESULT: 0x80010108 (RPC_E_DISCONNECTED)) at QlikView.IUserPreferences.set_SMTPServer(String _SMTPServer) at QVBWrapper.Document.Load(ILogBucket i_LogBucket, Boolean withData)
3/2/2015 6:29:53 PM Error The document failed to open.
3/2/2015 6:29:54 PM Error The task "QVDLoad.qvw" failed. Exception: QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> System.Threading.ThreadAbortException: Thread was being aborted. at QVBWrapper.DocumentPool.Checkout(ILogBucket logBucket, eCheckoutMode checkoutMode, String fileName, Boolean clearAll, Boolean clearLocks, Boolean clearOneAndOnlyOnes, Boolean reduce, String variableName, String variableValue, AbortCallbackCheck abortCallbackCheck, String sectionAccessUsername, String sectionAccessPassword, DocumentRestoreMode documentRestoreMode, Boolean withData, Boolean forceQvbAllocation) at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) --- End of inner exception stack trace --- at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) --- End of inner exception stack trace --- at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult)
3/2/2015 6:29:54 PM Error Task failed with exception
3/2/2015 6:29:54 PM Error Exception=The currently executing operation was aborted.

Not applicable
Author

In the ODBC Driver config (on the server), have you enabled Query Timeout ?

I've had this before, I had to open the application up on the server client install, and reload.  Threw up a connection error which I could fix.

Check as well that the destination database allows the QV (or whatever user you're using) user and that there aren't other queries hitting the db at the same time.

Not applicable
Author

I am not sure if it is correct protocol since I set up all my services with a local admin user to the server, but I changed only the Distribution Service to the domain admin account, restarted the service and now the loads are working fine.

Prior to doing so, I added the local qlik account to have permissions to the document folder.   Before I did that, the reload failed immediately.   Once I added the proper permissions to the Qlik document folder the load would start hang until it timed out.   This is why I guess that the local Qlik user did not have permissions to the ODBC configuration.   Not sure there is any way around this other than to run the Distribution Service as the user who created the ODBC