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

[Albert_Candelario]

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.

[SweJoCa]

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]

Same, we're on QlikView Sept 2025 SR4

[patrickbe]

Same issue on sept 2025 SR1, (very) large document will not save. Huge disc write requests on C disk (and not on D where it should be saved). After a while the 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.". Ram is fine, only 194GB in use (31%) and CPU also good.over the 24 cores. This is new environment and on the old one (May 2023) it works just fine.

[patrickbe]

My case was explained. The Environment Variables %TEMP% for service account pointed to C:\Users\[sa_user]\AppData\Local\Temp folder. Temp file was too large for disk space, so crashed.