6 Replies Latest reply: Jan 4, 2016 3:05 PM by Bill Britt RSS

    Qlikview Server Failure email without Job failing

    Riaan Du Toit

      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)