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

Announcements
ALERT: QlikView server communication interruptions following Microsoft Windows Domain Controller security updates

Error The sourcedocument failed to save.. Exception=System.Runtime.InteropServices.COMException (0x80004005)

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Albert_Candelario

Error The sourcedocument failed to save.. Exception=System.Runtime.InteropServices.COMException (0x80004005)

Last Update:

Dec 20, 2021 12:31:55 PM

Updated By:

Ranganath_DR

Created date:

Sep 26, 2019 4:43:28 AM

A reload task in QlikView fails with the following error in the task log:


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)

 

This may be caused by an active virus scan locking the relevant files, or an invalid alert configured on the task.

 

Environment:
 
  • QlikView

 

Virus Scan

Ensure that QlikView file locations (.qvw, qvd, etc..) are excluded from active virus scans. See QlikView Folder And Files To Exclude From Anti-Virus Scanning .

Invalid Alerts

Remove or edit the alerts configured on the document.

Alerts can be configured in the Distribution task. To verify:

  • Open the QlikView Management Console
  • Go to Documents > Source Documents
  • Locate the failing document/task.
  • Open the document/task
  • Navigate to the Distribute tab
  • Go to the Notify tab.
  • Uncheck Send notification e-mail to recipients 
  • Make sure, there is enough disk space to save the QVW


For additional troubleshooting steps and root causes, see QlikView: Checklist For Reload/Publisher Task Failure.

Labels (1)
Comments
SweJoCa
Partner - Contributor III
Partner - Contributor III

If someone is still following this, I have the same problem which "announced itself" after an update of QlikView to sept 2025 SR1. 
I' ve followed the steps given from Albert above, to no avail. Help? 

ByrdCD
Contributor
Contributor

Same, we're on QlikView Sept 2025 SR4

Version history
Last update:
‎2021-12-20 12:31 PM
Updated by: