Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
dutoitr
Partner - Contributor II
Partner - Contributor II

Qlikview Server Failure email without Job failing

So, the Qlikview server at one client recently started sending me job failed alerts every morning after the scheduled time but the job ran successfully.

Anyone else had an issue like this where the server sends out false failure alerts and how did you trace or fix the issue?

I already tried:

  • Ran a repair on the installation
  • Deleted the reload schedule and recreated it
  • Checked that the email settings are still valid.
  • Deleted the email entries on the Server Alert page and added them back.

Server:

  • Windows Server 2012 Standard 64bit
  • Qlikview Server 11.20 SR10
  • All in one installation using Qlikview web server

Failure email:

The task "FUNCTIONAL/VIP/VIP Data.qvw" failed. Part of the log file follows:

2015-12-29 05:06:12 AM  Error   The Source Document was NOT reloaded successfully. DocumentPath=E:\QLIKVIEW\FUNCTIONALLAYER\VIP\VIP Data.qvw.
2015-12-29 05:06:13 AM  Error   The task "FUNCTIONAL/VIP/VIP Data.qvw" 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=E:\QLIKVIEW\FUNCTIONALLAYER\VIP\VIP Data.qvw.
at QDSMain.ReloadTask.VerifyConditions(TaskResult taskResult)
at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage)
--- End of inner exception stack trace ---
at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage)
at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult)
--- End of inner exception stack trace ---
at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult)
at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult)

7 Replies
Peter_Cammaert
Partner - Champion III
Partner - Champion III

How do you know that the task ran successfully, when everything points to a failed reload? No trace of a failure in the TaskLog on the server? The message appears in the email only?

p_verkooijen
Partner - Specialist
Partner - Specialist

Do you use retry ? (only available with publisher license)

Also like pcammaert typed, what is the task status in QMC?

Paste the full logfiles from C:\ProgramData\Qliktech\DistributionService\1\Log\yyyymmdd\taskname

dutoitr
Partner - Contributor II
Partner - Contributor II
Author

I know because the task log shows a success and the model when opened shows the updated information.

dutoitr
Partner - Contributor II
Partner - Contributor II
Author

I seem to get the failure email every day at the same time. Every day at 05:06am :

I tested this by changing the reload time from 05:00am to 05:05am (5 minutes later)

I still got this failure email at this time. So, the failure email was sent when the reload job was still busy. As today's job finished at 05:08am.

Seems then maybe there is something stuck in the alert email queue that does not clear out and keeps generating an alert email every morning.

Is something like that possible?


I checked the Task and Document logs and all of them says success.

p_verkooijen
Partner - Specialist
Partner - Specialist

Not quite sure but it could be a leftover from an old task, could be a missing source file.

Check the Tasklogfiles

C:\ProgramData\QlikTech\DistributionService\2\Log\20151231\......\TaskLog.txt

Check the Root and Workorder logfiles

C:\ProgramData\QlikTech\DistributionService\nr\Log\Root_20151231.txt

  • C:\ProgramData\QlikTech\DistributionService\nr\Log\Workorder_20151231.txt


Try to identify the task guid and check the Tasks directory

C:\ProgramData\QlikTech\DistributionService\Tasks


Bill_Britt
Former Employee
Former Employee

Hi,

In the QMC how many reload engines do you have setup and how many processors does the server have? I am thinking you are trying to run more than 9 reload engines and you have not increase the Desktop Heap

Bill

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
ruchitsharma
Contributor
Contributor

Hi! I am having the same issue, did you find a solution for it? It is happening for all jobs run on a timed schedule but not for jobs run via EDX. Any help is appreciated.