topic Re: qlikview document could not be opened in QlikView

qlikview document could not be opened

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

Hello we've got a qlikview document with script to read from QVD files

the document doesn't have SECTION ACCESS at all but we are getting the below error as per the log file:

(2019-11-14 11:27:08) Information: Starting task '1-Prod CES - Case Management Mart - PEGA @ 10774 (Case_Management_Mart_Pega)'. Id:1376d7c9-6f66-4a57-82f8-a75848078936. Triggered by 'TaskCompletedTrigger'. Id:25c0f3e6-0efc-4458-a7ea-642f7751aa1d

(2019-11-14 11:27:08) Information: Entering Task Execution.

(2019-11-14 11:27:08) Information: ClusterID=1

(2019-11-14 11:27:08) Information: QDSID=e415609b-fd99-e261-9f5b-850ac17792b2

(2019-11-14 11:27:08) Information: TaskID=1376d7c9-6f66-4a57-82f8-a75848078936

(2019-11-14 11:27:08) Information: MaxRunTime=1.00:00:00

(2019-11-14 11:27:08) Information: MachineName=QLIKMMPRD

(2019-11-14 11:27:08) Information: Max attempts:1

(2019-11-14 11:27:08) Information: Current Attempt=0

(2019-11-14 11:27:08) Information: Task Dependencies are OK

(2019-11-14 11:27:08) Information: Document is marked to be Reloaded with fresh data. Initializing Reload for Distribution.

(2019-11-14 11:27:08) Information: Opening "\\qlikprd\Source Documents\1-PROD\Customer Case Analysis Dashboard\QVWT\Case_Management_Mart_PEGA.qvw"

(2019-11-14 11:27:08) Information: Allocating new QlikView Engine. Current usage count=0 of 4 (of type non-reader).

(2019-11-14 11:27:08) Information: Max retries:5

(2019-11-14 11:27:08) Information: Attempt:01

(2019-11-14 11:27:09) Information: Opened the QlikView Engine successfully. ProcessID=7912

(2019-11-14 11:27:09) Information: Allocated QlikView Engine successfully. Current usage count=1 of 4 (of type non-reader). Ticket number=1276.

(2019-11-14 11:27:09) Information: Loading document "\\qlikprd\Source Documents\1-PROD\Customer Case Analysis Dashboard\QVWT\Case_Management_Mart_PEGA.qvw" (487.50 Mb)

(2019-11-14 11:27:10) Information: Loading. LoadTime=00:00:01.0073117

(2019-11-14 11:27:11) Error: Document open call failed. The document might require username and password.

(2019-11-14 11:27:11) Information: Attempted to load the document without data.

(2019-11-14 11:27:11) Error: The document failed to open.

(2019-11-14 11:27:12) Information: Closed the QlikView Engine successfully. ProcessID=7912

(2019-11-14 11:27:12) Error: Document could not be opened

(2019-11-14 11:27:12) Information: Closed the QlikView Engine successfully. ProcessID=7912

(2019-11-14 11:27:12) Information: Failed to check in document: \\qlikprd\Source Documents\1-PROD\Customer Case Analysis Dashboard\QVWT\Case_Management_Mart_PEGA.qvw

(2019-11-14 11:27:12) Error: The task "1-Prod CES - Case Management Mart - PEGA @ 10774 (Case_Management_Mart_Pega)" 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: \\qlikprd\Source Documents\1-PROD\Customer Case Analysis Dashboard\QVWT\Case_Management_Mart_PEGA.qvw || 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)

(2019-11-14 11:27:12) Information: Task Execute Duration=00:00:03.6997027

(2019-11-14 11:27:12) Information: TaskResult.status=Finished

(2019-11-14 11:27:12) Information: Notifying all triggers of new state:FinishedWithErrors

(2019-11-14 11:27:12) Information: Notifying all triggers of new state:FinishedWithErrors - completed

(2019-11-14 11:27:12) Information: Saving Task Result

we've got another server machine that has QlikView server installed and the task runs successfully but on the current machine that we are working on it is giving the above error

Kindly advise on what to do to fix this issue

Re: qlikview document could not be opened

Josh_Berg_Support — Thu, 14 Nov 2019 15:26:03 GMT

That error is a bit of a tricky one as it can be caused by a few issues. I took a look through our Knowledgebase and found the following article regarding this error:

https://support.qlik.com/articles/000003243

If you re-run the task at another time, will it complete without error or does it fail with the same error in the task log? You said you have another Qlikview Server that's able to run this task successfully, is the QVS that's failing to run the task a new install or has this ever worked properly on this server? Has anything recently changed in your Qlikview environment that could be related to this error?

Thanks,
Josh
Qlik Support

Re: qlikview document could not be opened

ali_hijazi — Tue, 19 Nov 2019 08:38:52 GMT

Hello we increased the memory on the new server but still getting the same error

is there something we should check?
kindly advise

Re: qlikview document could not be opened

Brett_Bleess — Tue, 19 Nov 2019 13:42:59 GMT

Ali, do you guys have the Desktop Client installed on the server as well? If so, can you login as the service account and open/license the Desktop (you can do a license lease if you can assign the service account a Named CAL from the QVS), and see if things open properly that way? The only other thing of which I can think is Anti-Virus or some other active scanning utility you have running on the server is screwing up our ability to open the file with the exclusive lock such that we can save the file post reload... Shout back when you can with info but hopefully this may help you move things forward a bit more.

Regards,
Brett

Re: qlikview document could not be opened

ali_hijazi — Tue, 19 Nov 2019 14:49:23 GMT

Hello, yes I can open the document with QlikView desktop and I can reload the document successfully
only the task fails to open the document
knowing that the distribution service is run by a domain administrator
I will ask admins to disable anti-virus and will get back to you
thank you for your prompt reply

Re: qlikview document could not be opened

Brett_Bleess — Tue, 19 Nov 2019 14:57:42 GMT

Ali, yeah, see if the AV team and do exceptions on our folders, that should ensure you do not have any issues related to active scanning. If they want some proof, hopefully their logs will show them grabbing things while we are trying to open etc. If not, only thing I can suggest would be running Sys Internals Process Monitor utility on the folder to see what other process may be getting hold of the file we are trying to open. Hopefully that may catch things for you. Keep us posted, but that is the best hunch I have at the moment and by the way, you do not need a domain admin running things, a domain user set up a s local admin on the server should be fine! 🙂 I cannot imagine you have a security issue in this case!

Cheers,
Brett

Re: qlikview document could not be opened

ali_hijazi — Tue, 19 Nov 2019 16:57:46 GMT

Hello
one thing to add; the tasks run successfully if the qvw file doesn't have data and the reload simply saves data as qvd and deletes tables
so the tasks only fail when the qvw file has data i.e. a complete dashboard

Re: qlikview document could not be opened

Brett_Bleess — Tue, 19 Nov 2019 22:14:05 GMT

Ok, I suspect your data model may be the issue in that case, any chance you can do a limited load of a few records so we can have a look at what the data model ends up looking like? I would suspect you have a Cartesian of some sort in the data model etc. that is likely causing things to balloon in size when the app is opened with data. The only easy workaround is to drop your tables at the end of the script in the meantime. Thanks for the extra info that was very helpful, hopefully this makes sense as well.

Regards,
Brett

Re: qlikview document could not be opened

Arthur_Fong — Wed, 20 Nov 2019 03:53:17 GMT

Is this qvw binaried from another qvw?

To check this, go to the first line in the script and look for any binary load in it.

If there is, check the qvw of the binary source and see if there is section access in it.

Re: qlikview document could not be opened

ali_hijazi — Wed, 20 Nov 2019 07:00:49 GMT

yes it binary loads from another document and that other document doesn't have section access

Re: qlikview document could not be opened

ali_hijazi — Wed, 20 Nov 2019 07:02:05 GMT

but opens and reloads successfully without any issue from Desktop

Re: qlikview document could not be opened

ali_hijazi — Wed, 20 Nov 2019 07:05:21 GMT

I emptied the document from data (File->reduce->remove all values) saved the document then ran the task same error

as I told you before it runs successfully (the reload I mean) from the desktop

Re: qlikview document could not be opened

Brett_Bleess — Wed, 20 Nov 2019 13:19:42 GMT

Ali, is there any Script/Document log being created when you run things via the Task in QMC? That is the next step on this one, as if you are getting that log, if you can attach, that should help us figure out where things are getting hung up. If there is no log, check the Settings\Document Properties\General tab\Generate logfile setting there to be sure that is checked on the source doc, as otherwise it will not create things. Not sure what version you are running either, since things are failing, if the logging is set correctly, you may need to go to the QlikViewBatch folder in ProgramData\QlikTech in order to find the partial script/doc log there, just FYI.

Regards,
Brett

Re: qlikview document could not be opened

ali_hijazi — Thu, 21 Nov 2019 08:10:29 GMT

Attached is the log file generated by the task
but now I changed the user account running the distribution service and the task ran successfully but now ran into another problem!!!
So the file what was failing to open by the task was open with the new user account and task finished successfully
Now we come to the dashboard file which binary loads from another file;
if I open the dashboard in Desktop it reloads successfully in 10 seconds
but if I run the task as per the log it reloads successfully but when it tries to save the file it took like 17 hours and didn't save so I had to manually stop the task and get the following error:

(11/20/2019 2:32:34 PM) Information: Start saving document

(11/21/2019 7:44:07 AM) Information: DistributeTask[c2a6761b-5814-483d-ab49-b49a56f9ca20] ("1-Prod CES: Customer Case Analysis Dashboard - PEGA @ 9441"): TryAbort. Triggered by 'ManualAbortTrigger'. Id:00000001-0002-0003-0405-0607080c0b0a. ExecID:d429c43a-a94f-47d2-a30d-25dd3312aaf4
and when I stopped the task the following error was logged:

(11/21/2019 7:44:07 AM) Information: Check in document: \\qlikprd\Source Documents\1-PROD\Customer Case Analysis Dashboard\QVW\Customer Case Analysis Dashboard - PEGA.qvw

(11/21/2019 7:44:07 AM) Information: Closing the document.

(11/21/2019 7:44:07 AM) Error: The sourcedocument failed to save.. Exception=System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component. || at QlikView.Doc.SaveAs(String _FileName, Int16 _Format) || at QVBWrapper.Document.Save(ILogBucket i_LogBucket, String i_SaveAsFileName)

(11/21/2019 7:44:07 AM) Information: Closed the QlikView Engine successfully. ProcessID=10608

(11/21/2019 7:44:07 AM) Error: The task "1-Prod CES: Customer Case Analysis Dashboard - PEGA @ 9441" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.LogBucketErrorException: The sourcedocument failed to save.. Exception=System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component. || at QlikView.Doc.SaveAs(String _FileName, Int16 _Format) || at QVBWrapper.Document.Save(ILogBucket i_LogBucket, String i_SaveAsFileName) || 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)

(11/21/2019 7:44:07 AM) Information: Task Execute Duration=17:11:47.7897989

knowing that the location at which the document is saved is excluded from AntiVirus scan

Re: qlikview document could not be opened

Brett_Bleess — Thu, 21 Nov 2019 18:49:15 GMT

Ali, have a look at the following article link, I would say you need to try increasing the Desktop Heap size and see if that does the trick here or not.

Desktop Memory Heap & QVB Engines

Regards,
Brett

Re: qlikview document could not be opened

ali_hijazi — Mon, 25 Nov 2019 15:54:56 GMT

Today we noticed a weird behavior
we ran ProcMon to monitor what might be going wrong during saving the document
and the tasks run successfully
whereas when we turned off this monitoring tool the tasks fail

we repeated this several times and the result is that whenever we run the monitoring took the tasks won't fail whereas when we turn off this monitoring tool the tasks fail

Any clue?

Re: qlikview document could not be opened

Brett_Bleess — Tue, 03 Dec 2019 19:49:20 GMT

Ali, I would have to say there must be some other process getting hold of the QVW file such that the QDS/QVB no longer has the exclusive lock, and when you run ProcMon that is preventing that process from doing so, but I would think ProcMon should likely catch the other process trying to get hold of things. The only other thing that comes to mind is something network related to where it would almost seem something is going to sleep and is not waking up in a timely manner and thus timing something out on our side, as ProcMon constantly touching things may be keeping that channel open? Best theories of which I can think at the moment.

Regards,
Brett