topic Re: Suggestions for QMC task fail resolving in QlikView

Suggestions for QMC task fail resolving

vindhya_giri — Mon, 26 Jan 2026 18:19:17 GMT

Hello,

We have upgraded from QV 11.2 SR10 to QV 12.10 SR1.

After the upgrade, from our first daily cycle there were 3 tasks that failed on QMC.

1. The task log says : Document could not be opened

When looked at the application log, it says reload completed successfully.

What could be the reason for the task to fail even though the reload was completed successfully?

2. The app itself was not opened/reloaded.

Thus there is no application log available

Task log says: Document could not be opened

On manual reload, the reload was completed normally

3. The task log says: The Source Document was NOT reloaded successfully

The application log says: OLEDB connection failed.

On manual reload, the reload was completed normally

We have a common connection defined in a qvs file and the same qvs is used in all the qvw's.

All the other tasks in the cycle completed successfully.

Next two days of daily cycle completed normally without any issue

On the 4th day of the daily cycle after the upgrade, the issues reappeared. Two tasks failed on QMC.

1. Task# 2 from above failed again

The app itself was not opened/reloaded.

Thus there is no application log available

Task log says: Document could not be opened

On manual reload, the reload was completed normally

2. There is one more different task which failed for the first time.

The task log says: The Source Document was NOT reloaded successfully

The application log says: OLEDB connection failed.

On manual reload, the reload was completed normally

I have gone through few posts on the community but still not sure which area to look at. Please advise me on this

Thank you!

Re: Suggestions for QMC task fail resolving

vishsaggi — Thu, 16 Feb 2017 15:39:13 GMT

Are these dependent tasks or individual tasks. Did you check your document log for this task in QDS-1-Log-There will be date folders. Can you check the document log from this folder for that specific dashboard?

Re: Suggestions for QMC task fail resolving

vindhya_giri — Thu, 16 Feb 2017 16:12:45 GMT

Hi Vishwarath

These are dependent on other jobs.

Went to the document log in the location you mentioned and see the same as what I have mentioned as application log in my original post.

Thank you

Vindhya

Re: Suggestions for QMC task fail resolving

vindhya_giri — Thu, 16 Feb 2017 16:44:18 GMT

pcammaert‌ : Please provide your inputs on this.

Thanks

Vindhya

Re: Suggestions for QMC task fail resolving

Peter_Cammaert — Fri, 17 Feb 2017 07:56:10 GMT

Please post all relevant log files, or at least those parts that mention the failure and the 100 lines before.

(The Document Log isn't needed)

Re: Suggestions for QMC task fail resolving

avinashelite — Fri, 17 Feb 2017 07:59:57 GMT

It could you for couple if reasons

*Access issue

*Files dependent task conditions

*Connectivity issue

Please share the specific log files so that it will help us to suggest

Re: Suggestions for QMC task fail resolving

vindhya_giri — Fri, 17 Feb 2017 14:41:19 GMT

Task log for task 2 from the first day of failure:

(The app itself was not opened/reloaded.

Thus there is no application log available

Task log says: Document could not be opened)

(2/11/2017 12:47:56 AM) Information: DistributeTask[a712810f-1bde-4e3a-b541-a872c342a3b8] ("TASK_NAME"): TryStart - Starting task. Triggered by 'TaskCompletedTrigger'. Id:1a467d32-3982-4ed4-8beb-13fa9038f1c3. ExecID:996da4a2-96a4-402b-aa91-3b69c5933d08

(2/11/2017 12:47:56 AM) Information: Entering Task Execution.

(2/11/2017 12:47:56 AM) Information: ClusterID=1

(2/11/2017 12:47:56 AM) Information: QDSID=ea5ce2aa-54f5-7b64-a854-73f3022856e7

(2/11/2017 12:47:56 AM) Information: TaskID=a712810f-1bde-4e3a-b541-a872c342a3b8

(2/11/2017 12:47:56 AM) Information: ExecID=996da4a2-96a4-402b-aa91-3b69c5933d08

(2/11/2017 12:47:56 AM) Information: MaxRunTime=1.00:00:00

(2/11/2017 12:47:56 AM) Information: MachineName=XXXXX

(2/11/2017 12:47:56 AM) Information: Task execution max attempts=1

(2/11/2017 12:47:56 AM) Information: Task execution current attempt=1

(2/11/2017 12:47:56 AM) Information: Task Dependencies are OK

(2/11/2017 12:47:56 AM) Information: The task "TASK_NAME" is starting

(2/11/2017 12:47:56 AM) Information: Document is marked to be Reloaded with fresh data. Initializing Reload for Distribution.

(2/11/2017 12:47:56 AM) Information: Opening "D:\QlikViewProjects\Claims\generators\File.qvw"

(2/11/2017 12:47:58 AM) Information: Allocating new QlikView Engine. Current usage count=7 of 8 (of type non-reader).

(2/11/2017 12:47:58 AM) Information: Max retries:5

(2/11/2017 12:47:58 AM) Information: Attempt:01

(2/11/2017 12:47:59 AM) Information: Opened the QlikView Engine successfully. ProcessID=10460

(2/11/2017 12:47:59 AM) Information: Allocated QlikView Engine successfully. Current usage count=8 of 8 (of type non-reader). Ticket number=13.

(2/11/2017 12:47:59 AM) Information: Loading document "D:\QlikViewProjects\Claims\generators\File.qvw" (0.38 Mb)

(2/11/2017 12:48:00 AM) Information: Loading. LoadTime=00:00:01.0000781

(2/11/2017 12:48:01 AM) Error: Document open call failed. The document might require username and password.

(2/11/2017 12:48:01 AM) Information: Attempted to load the document without data.

(2/11/2017 12:48:01 AM) Error: The document failed to open.

(2/11/2017 12:48:02 AM) Information: Closed the QlikView Engine successfully. ProcessID=10460

(2/11/2017 12:48:02 AM) Error: Document could not be opened

(2/11/2017 12:48:02 AM) Information: Failed to check in document: D:\QlikViewProjects\Claims\generators\File.qvw

(2/11/2017 12:48:02 AM) Error: The task "TASK_NAME" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exceptions.FailedDocumentCheckoutException: Failed to check out document with path: D:\QlikViewProjects\Claims\generators\File.qvw || at QDSMain.AbstractReloadTask.Reload(String fileName, IExecutingTaskResult executingTaskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || --- End of inner exception stack trace --- || at QDSMain.AbstractReloadTask.Reload(String fileName, IExecutingTaskResult executingTaskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || at QDSMain.DistributeTask.PerformExecute(IExecutingTaskResult executingTaskResult) || --- End of inner exception stack trace --- || at QDSMain.DistributeTask.PerformExecute(IExecutingTaskResult executingTaskResult) || at QDSMain.Task.AbstractTask.TaskExecution(CurrentExecutionArgs args)

(2/11/2017 12:48:02 AM) Information: Task Execute Duration=00:00:05.4324270

(2/11/2017 12:48:02 AM) Information: Sending Alert mail

(2/11/2017 12:48:05 AM) Information: TaskResult.status=Finished

(2/11/2017 12:48:05 AM) Information: Notifying all triggers of new state: "FinishedWithErrors"...

(2/11/2017 12:48:05 AM) Information: Notifying all triggers of new state: "FinishedWithErrors" - Completed

Re: Suggestions for QMC task fail resolving

vindhya_giri — Fri, 17 Feb 2017 14:43:49 GMT

Task log from first day , task 3: (The task log says: The Source Document was NOT reloaded successfully

The application log says: OLEDB connection failed.

On manual reload, the reload was completed normally

We have a common connection defined in a qvs file and the same qvs is used in all the qvw's):

(2/11/2017 12:47:56 AM) Information: Document is marked to be Reloaded with fresh data. Initializing Reload for Distribution.

(2/11/2017 12:47:56 AM) Information: Opening "D:\QlikViewProjects\Claims\generators\file.qvw"

(2/11/2017 12:47:59 AM) Information: Failed to allocate new QlikView Engine. Retrying! Max usage reached. Current usage count=8 of 8 (of type non-reader).

(2/11/2017 12:48:02 AM) Information: Allocating new QlikView Engine. Current usage count=6 of 8 (of type non-reader).

(2/11/2017 12:48:02 AM) Information: Max retries:5

(2/11/2017 12:48:02 AM) Information: Attempt:01

(2/11/2017 12:48:03 AM) Information: Opened the QlikView Engine successfully. ProcessID=11068

(2/11/2017 12:48:03 AM) Information: Allocated QlikView Engine successfully. Current usage count=7 of 8 (of type non-reader). Ticket number=14.

(2/11/2017 12:48:03 AM) Information: Loading document "D:\QlikViewProjects\Claims\generators\file.qvw" (0.22 Mb)

(2/11/2017 12:48:03 AM) Information: Physical FileSize=0.22 Mb. Memory Allocation Delta for this file=4.14 Mb. Available Physical Memory Before Open=253592.16 Mb. Available Physical Memory After Open=253590.19 Mb. Total Physical Memory=262050.34 Mb.

(2/11/2017 12:48:03 AM) Information: Attempted to load the document without data.

(2/11/2017 12:48:03 AM) Information: The document was loaded successfully.

(2/11/2017 12:48:03 AM) Information: Document was opened successfully

(2/11/2017 12:48:04 AM) Information: Starting reload

(2/11/2017 12:48:04 AM) Information: The Source Document is being reloaded. DocumentPath=D:\QlikViewProjects\Claims\generators\file.qvw

(2/11/2017 12:48:05 AM) Information: Reloading.

(2/11/2017 12:48:05 AM) Information: The Source Document reload complete. DocumentPath=D:\QlikViewProjects\Claims\generators\file.qvw

(2/11/2017 12:48:05 AM) Information: Memory Allocation Delta for this file=34.55 Mb. Available Physical Memory Before Reload=253588.84 Mb. Available Physical Memory After Reload=253573.59 Mb. Total Physical Memory=253573.59 Mb.

(2/11/2017 12:48:06 AM) Error: The Source Document was NOT reloaded successfully. DocumentPath=D:\QlikViewProjects\Claims\generators\file.qvw.

(2/11/2017 12:48:06 AM) Information: QlikView->Settings->Document Peferences->Generate Logfile in document is set. Enabling Log Copier.

(2/11/2017 12:48:06 AM) Information: Looking for the document log "D:\QlikViewProjects\Claims\generators\file.qvw" to become available.

(2/11/2017 12:48:06 AM) Information: Found a document log. FileName=D:\QlikViewProjects\Claims\generators\file.qvw.log

(2/11/2017 12:48:06 AM) Information: Writing documentLog to C:\ProgramData\QlikTech\DistributionService\1\Log\20170211\004756 - TASK_NAME\DocumentLog.txt

(2/11/2017 12:48:06 AM) Information: Closing the document.

(2/11/2017 12:48:06 AM) Information: Closed the QlikView Engine successfully. ProcessID=11068

(2/11/2017 12:48:06 AM) Error: The task "TASK_NAME" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exceptions.LogBucketErrorException: The Source Document was NOT reloaded successfully. DocumentPath=D:\QlikViewProjects\Claims\generators\File.qvw. || at QDSMain.AbstractReloadTask.VerifyConditions(IExecutingTaskResult executingTaskResult) || at QDSMain.AbstractReloadTask.Reload(String fileName, IExecutingTaskResult executingTaskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || --- End of inner exception stack trace --- || at QDSMain.AbstractReloadTask.Reload(String fileName, IExecutingTaskResult executingTaskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || at QDSMain.DistributeTask.PerformExecute(IExecutingTaskResult executingTaskResult) || --- End of inner exception stack trace --- || at QDSMain.DistributeTask.PerformExecute(IExecutingTaskResult executingTaskResult) || at QDSMain.Task.AbstractTask.TaskExecution(CurrentExecutionArgs args)

(2/11/2017 12:48:06 AM) Information: Task Execute Duration=00:00:10.1196704

(2/11/2017 12:48:06 AM) Information: Sending Alert mail

(2/11/2017 12:48:10 AM) Information: TaskResult.status=Finished

(2/11/2017 12:48:10 AM) Information: Notifying all triggers of new state: "FinishedWithErrors"...

(2/11/2017 12:48:10 AM) Information: Notifying all triggers of new state: "FinishedWithErrors" - Completed

Re: Suggestions for QMC task fail resolving

vindhya_giri — Fri, 17 Feb 2017 14:49:44 GMT

Hi Avinash,

Can you please suggest of any specific area where to look at for the first two points you mentioned?

Sometimes tasks completes normally and sometimes they fail. So not sure if would be an access issue.

Thanks!

Re: Suggestions for QMC task fail resolving

stabben23 — Fri, 17 Feb 2017 14:51:55 GMT

What is D:? is it a local disc on the same server as C: or a mapped network drive?

Re: Suggestions for QMC task fail resolving

vindhya_giri — Fri, 17 Feb 2017 14:57:46 GMT

Hi Staffan

It is a local disc on the same server as C:

Re: Suggestions for QMC task fail resolving

avinashelite — Fri, 17 Feb 2017 15:08:34 GMT

could you share the specific QVW files log ?? that's what we need to help you

Re: Suggestions for QMC task fail resolving

Peter_Cammaert — Fri, 17 Feb 2017 17:58:21 GMT

The reload engine has trouble accessing this document. Possible causes:

during upgrade, the service account has changed and the document NTFS rights do not permit the service account to open this document
document has section access (indeed, very unusual for a QVD generator, but anyway) and the service account isn't listed in the section access table
a virus scanner (or another process) has this document open and QDS wants exclusive write access. Big clash

First check file the permissions for this document. Is there a virus scanner active on this server?

Re: Suggestions for QMC task fail resolving

Peter_Cammaert — Fri, 17 Feb 2017 18:00:00 GMT

If this failure is caused by an OLEDB connection problem, that may also point to wrong privileges. What kind of OLEDB connection are you using? Does it utilize Windows security?

Re: Suggestions for QMC task fail resolving

vindhya_giri — Fri, 17 Feb 2017 18:24:06 GMT

OLEDB 64bit connection (Oracle db)

Yes, it utilizes Windows security.

Re: Suggestions for QMC task fail resolving

vindhya_giri — Wed, 22 Feb 2017 16:26:17 GMT

Hi Peter,

Sorry for the late reply. I missed your post

Our cycle has been going on well since then. Did not make any changes. Will keep monitoring it though.

Yes, the virus scanner is active on the server.

Thanks