Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Sasiwaran
Contributor
Contributor

Qlikview QMC Task get struck when saving

Hi,

We have an issue where some of our QMC tasks get struck when saving. The reload finishes successfully but gets struck when saving and the task doesn't complete. It has to be manually aborted and when restarted it runs without issues.

Below is the error we gets in the Logs

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.

 

If anybody has faced the issue, feel free to provide more info. 

Thanks in Advance.

4 Replies
rubenmarin

Hi, usually document log, wich is enabled opening the document with desktop version, checking the option in document properties -> Genreal -> Generate log file, gives more information about the steps of the reload.

In any case the issue looks related to the save step, maybe the account that runs QV services doesn't have write access to the document. You can check this login as this user and trying to edit the file or just executing a manual reload from desktop and try to save.

Other options can be lack of resources, blocked by antivirus software, conflicts whit other process...
Daniele_Purrone
Support
Support

Hi! There might be some causes for this:

1) if you don't have enough space on disk to save the reloaded source document

2) we had a bug on the 12.20 track when this issue was happening if the document contains many document bookmarks. The bug was solved in 12.20 SR6. Can you verify if you are in that scenario?

Daniele - Principal Technical Support Engineer & SaaS Support Coordinator at Qlik
If a post helps to resolve your issue, please accept it as a Solution.
Chip_Matejowsky
Support
Support

In addition to what @Daniele_Purrone stated, I have seen this error on single node QlikView/Reload Engine environments when RAM was scarce, and also if the QVW associated with the task was corrupt.

Is the issue intermittent or constant? If intermittent, does the reload typically succeed after a server reboot or restarting of QV services?

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!
Chip_Matejowsky
Support
Support

@Sasiwaran 

Just wanted to follow up here as I have experienced this same issue again recently. The issue was resolved by increasing the Windows Desktop Memory Heap as outlined in the Qlik Support article "How many reload engines (QVB) to allow in an environment" under the Windows limitation heading. So this is something you would definitely want to consider if the other suggestions didn't work for you.

 

-Chip

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!