Skip to main content

Qlik

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
balajibc64
Creator III
Creator III
‎2023-08-27 03:46 PM

Qlik View Task Issue

Hi, we are using latest Qlik View version (MAY 2023) and licensed one.  Our business created dashboard and schedule a reload task to run frequently.  Whenever reload task rans, sometime we are getting failure for the few jobs.  Below is the error we are getting, not sure why its happening.  Could you please suggest on this ? 

(8/27/2023 6:20:44 AM) Information: The Source Document reload complete. DocumentPath=\\cfwdod5sq001\QLIK\QlikviewPRD\SourceDocs\IC\2.QVDGen\QVDGen_Daily_4706SO.qvw

(8/27/2023 6:20:44 AM) Information: Memory Allocation Delta for this file=44.69 Mb. Available Physical Memory Before Reload=24471.55 Mb. Available Physical Memory After Reload=23427.25 Mb.

(8/27/2023 6:20:44 AM) Error: The Source Document was NOT reloaded successfully.

  Error: The task "QVDGen_Daily_4706SO" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exceptions.LogBucketErrorException: The Source Document was NOT reloaded successfully. DocumentPath=\\cfwdohd5sqls001\QLIK\QlikviewPRD\SourceDocs\IOC\2.QVDGen\QVDGen_Daily_4706SO.qvw.  ||    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)

 

Labels (3)
Labels
985 Views
0 Likes
2 Solutions

Accepted Solutions
Chip_Matejowsky
Support
Support
‎2023-08-29 06:41 AM

In response to balajibc64

@balajibc64,

The last action of the load script right before the reload fails is the STORE statement. First, as Marcus suggested, review your reload schedule to ensure there's no other tasks trying to write/read this QVD at the time of it being stored.

If there aren't any other tasks reading/writing concurrently to this QVD, an option is to add a SLEEP statement (e.g. SLEEP 10000) after the store statement. This is to give the reload a bit of a breather, since at this point, Windows has to write the data to disk. The number is in milliseconds and can be tweaked as needed. It might be trying to do the Store, finishes and then errors out right after. Hopefully the Sleep would give it a chance to catch up.

If the reload is still failing after adding a STORE statement, another option if we know this happens with certain reloads, is to set up MS Sysinternals Process Monitor scan on those QVDs to see if anything else is touching it that might cause the error.

Best Regards 

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

View solution in original post

849 Views
0 Likes
marcus_sommer
MVP
MVP
‎2023-08-30 09:57 AM

In response to balajibc64

A sleep-statement could be added between the statements - means before a load / store starts or after it ends - just to give the various I/O operations on the outside of Qlik a certain extra time to finish their threads.

In your case you are loading from the qvd by concatenating the historic data with the current ones and storing it again in the same file. Such approach worked usually very well without such lock-issues but by a heavy workload on the storage/network it may react too slowly. Therefore you may try a sleep-statement before the store-statement.

Beside this there is further a possibility that any other process locked the file in the meanwhile. Therefore it might be helpful to move the task to start a few minutes earlier or later.

View solution in original post

832 Views
0 Likes
19 Replies
marcus_sommer
MVP
MVP
‎2023-08-28 04:15 AM

If the task failed then take a look on the document-log.

567 Views
0 Likes
Chip_Matejowsky
Support
Support
‎2023-08-28 07:05 AM

Hi @balajibc64,

As @marcus_sommer indicated, you'll want to review the document log of the QVW /QVF file associated with the failed task. Refer to Qlik Support KB article The Source Document was NOT reloaded successfully for more details.

 

Best Regards 

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!
565 Views
0 Likes
balajibc64
Creator III
Creator III
‎2023-08-28 08:02 AM
Author

Yes. but it is failing occasionally.  For example, every 10 mins one task running means, if task failed, again it will be success in the other run. Even If I tried to reload the task manually, then immediately its working fine. 

Also need clarity on the statement 

Memory Allocation Delta for this file=44.69 Mb. Available Physical Memory Before Reload=24471.55 Mb. Available Physical Memory After Reload=23427.25 Mb.

This is anything related to memory space? please clarify 

561 Views
0 Likes
Chip_Matejowsky
Support
Support
‎2023-08-28 08:24 AM

In response to balajibc64

@balajibc64,

So what is the exact error returned in the document log when the task fails? That will help us help you.

 

Best Regards

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!
557 Views
0 Likes
marcus_sommer
MVP
MVP
‎2023-08-28 08:37 AM

In response to balajibc64

I think it has nothing to do with the RAM and also not with the task else it's very likely that the document-reload failed because any of the sources/targets is locked or temporary unavailable.

Regardless if a task is successful or failing - if you want to know more about what happens you will at first to need to look on the document-log.

554 Views
balajibc64
Creator III
Creator III
‎2023-08-28 09:41 AM
Author

@Chip_Matejowsky @marcus_sommer  I checked the document log. But in that folder I can able to see only TASK log there is no document log for that particular failure time. 

Also for crosscheck could you please help me for the location. 

 

548 Views
0 Likes
marcus_sommer
MVP
MVP
‎2023-08-28 09:50 AM

In response to balajibc64

The origin document-log is within the folder in which the qvw resides and a copy within the program data of QlikTech by the distribution service probaby ...1\log\YYYYMMDD.

Important is of course to enable this logging within the document-properties in tab general of the qvw. IMO this should be the default-setting.

545 Views
0 Likes
balajibc64
Creator III
Creator III
‎2023-08-28 10:02 AM
Author

@marcus_sommer @Chip_Matejowsky  Yes right, I'm checking the correct file. But when I looked that folder I can able to see task log, document log as well as distribution report for the success run. But for failure task I can see only task log only. 

542 Views
0 Likes
marcus_sommer
MVP
MVP
‎2023-08-28 10:15 AM

In response to balajibc64

This is already a hint that not the task itself is causing the issue else the reload. To get a document-log even if the reload breaks with any error you need to enable the user-setting to write immediately into the log. It's within the user-properties in the tab general and if I'm not mistaken it results in:

EnableFlushLog=1

within the settings.ini.

Take a look within the file from the server and change this setting appropriately. Before this make a BACKUP of the settings.ini and stop the qvs.exe to get a write-access to the file.

538 Views