Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
hi,
we have few documents and reload tasks.
we have recently upgraded our server form QV 11.2 SR13 to QV 12 November 2017 SR2
all worked but all of a sudden, last night, some tasks (only some, not all) has started to fail over and over.
at the failing scripts we get the same unknown error:
2018-03-04 09:55:52 0015 LOAD id,
2018-03-04 09:55:52 0016 account_id,
...........
2018-03-04 09:55:52 0085 FROM some_file.qvd (qvd)
2018-03-04 09:55:52 70 fields found: id, account_id, ...
2018-03-04 09:55:52 -128 =
2018-03-04 09:55:52 Execution Failed
2018-03-04 09:55:52 Execution finished.
the task doesn't reload from DB so it's not a connection.
there is no other process writing into that QVD in parallel
the task error is:
(04/03/2018 09:55:52) Information: The Source Document is being reloaded. DocumentPath=D:\QLIK....qvw
(04/03/2018 09:55:52) Error: The sourcedocument failed to reload..
Exception=System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component. ||
at QlikView.Doc.DoReload(Int32 _Mode, Boolean _Partial, Boolean _Debug) ||
at QVBWrapper.Document.Reload(ILogBucket i_LogBucket, Boolean i_MonitorQVBCPUUsage, Boolean i_Partial, Boolean i_ReadDocumentLog)
(04/03/2018 09:55:52) Information: Closing the document.
(04/03/2018 09:55:53) Information: Closed the QlikView Engine successfully. ProcessID=9256
(04/03/2018 09:55:53) Error: The task "some task" failed. Exception:
|| QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow.
---> QDSMain.Exceptions.ReloadFailedException: Reload failed
---> QDSMain.Exceptions.LogBucketErrorException: The sourcedocument failed to reload..
Exception=System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component. ||
at QlikView.Doc.DoReload(Int32 _Mode, Boolean _Partial, Boolean _Debug) ||
at QVBWrapper.Document.Reload(ILogBucket i_LogBucket, Boolean i_MonitorQVBCPUUsage, Boolean i_Partial, Boolean i_ReadDocumentLog) ||
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)
(04/03/2018 09:55:53) Information: Task Execute Duration=00:00:07.5940641
also in TaskResult:
<?xml version="1.0" encoding="utf-8"?>
<Root TaskID="0d5e026c-4c76-42b7-ab6e-6053352afbb5" OwnedByClusterID="1" RunID="aaa5fd1f-d280-49dd-ad34-dc86db44f313" TaskManuallyAborted="False" PreviousRunHadErrors="True" InternalError="True" LastExecution="04/03/2018 09:55:45" LastExecutedOn="DIL-QLP" QueuedAt="04/03/2018 03:05:26" QueuedByTriggerId="3adddab1-88d7-4ec4-ae72-72a2f6262d18" RunningOn="" StartedAt="04/03/2018 09:55:45" FinishedAt="04/03/2018 09:55:56" MaxRunTime="00:15:00" StartCount="33956" HasWarnings="False" Status="Finished" Modified="2018-03-04T07:55:56.7278640Z">
<LogFinalEntries>
<LogFinalEntry Type="Error" Date="04/03/2018 09:55:52" Text="The sourcedocument failed to reload..
Exception=System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.

at QlikView.Doc.DoReload(Int32 _Mode, Boolean _Partial, Boolean _Debug)
 at QVBWrapper.Document.Reload(ILogBucket i_LogBucket, Boolean i_MonitorQVBCPUUsage, Boolean i_Partial, Boolean i_ReadDocumentLog)" />
<LogFinalEntry Type="Error" Date="04/03/2018 09:55:53" Text="The task "some file.qvw" failed. Exception:
QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exceptions.LogBucketErrorException: The sourcedocument failed to reload..Exception=System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.

at QlikView.Doc.DoReload(Int32 _Mode, Boolean _Partial, Boolean _Debug)

at QVBWrapper.Document.Reload(ILogBucket i_LogBucket, Boolean i_MonitorQVBCPUUsage, Boolean i_Partial, Boolean i_ReadDocumentLog)

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)" />
</LogFinalEntries>
</Root>
GD shows nothing.
any idea?
The -128 is curious. Any chance you have Unicode characters in the qvd?
Are you able to load that QVD (in its entirety) in a test document? Just a QVW with a single LOAD statement... And by preference on the original QVD in the original location. Anything funny happening during that test load?
Can you provide the full QDS task log and the document log of the QVW associated with this task for review?
I had this problem recently when joining 3 files of type qvd.
In my case, I expected the 3 files to have the same columns and same data types. But, I noticed analyzing the headers of each qvd that there was a file that had a column like <Type> UNKNOWN </ Type> while the same column in the second qvd was <Type> REAL </ Type>. It seems that qlikview was having problems mixing both types of data.
My solution was to take the first qvd and save it as CSV (txt) and concatenate it with the second in qvd format. Since CSV does not have those data type headers. A conversion process for the header would have been better, but this worked.
I wanted to leave this here as a reference in case you have the same problem error -128, maybe it will be useful.
I ran into a this as well today with QlikView Nov 2017 SR6. I have had the same script running for a few years and all of a sudden it failed but my log file from the script had a"-129" in it. I pinpointed the problem but can't figure out the "why" behind it. For some reason my script no longer likes an Autonumberhash256 based field that was build and then later used in a resident load. When it gets to that resident load, the script just hangs for an hour or so and then finally fails. And for whatever reason, when my publish task with that code was in that "hanging" mode, it also caused one other publish task to fail and caused a second publish task to never even begin when it was scheduled to do so, so I can only assume that it caused a bottleneck of some sort in Qlik and the QMC halted and prevented other publish tasks from properly executing. So my work around was to replace my Autonumberhash256 with just something like this... Field1 & Field2 (instead of Autonumberhash256(Field1, Field2)).
We have a number of resources available in our knowledge database around this particular message. While they might not have captured all possible root causes yet, they might be a place to start.
Example: Error -129 or -128 when reloading app
If the issue is specifically related to an App, and can be consistently reproduced, it might be worth raising a support ticket and providing the app for testing.
Hi,
Is the issue resolved? We are getting the same error in our environment. Could you please let us know if you have resolved this?
Thanks in advance