Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Good Day
We are currently having issues with a job failing intermittently on SAP for a specific Qlik view request. All the jobs seems to run fin accept for one that fails intermittently. The failure on SAP side is:
Timeout reached while waiting for clearance of shared buffer.
We checked in the worker processes logs but there is no error listed in them.
There is however errors on the side of Qlik view and this is the following:
(2021-12-11 02:58:05) Information: Memory Allocation Delta for this file=121.25 Mb. Available PhysicalMemory Before Reload=62590.30 Mb. Available Physical Memory After Reload=61400.76 Mb. Total Physical Memory=61400.76 Mb.
(2021-12-11 02:58:06) Error: The Source Document was NOT reloaded successfully. DocumentPath=D:\QLIKVIEW\30. EXTRACTORS\SAP Extractors\Stock\2022 Stock Movement Extractor.qvw.
(2021-12-11 02:58:06) Information: Closing the document.
(2021-12-11 02:58:06) Information: Closed the QlikView Engine successfully. ProcessID=25892
(2021-12-11 02:58:06) Error: The task "Extractors/SAP Extractors/Stock/2022 Stock Movement Extractor.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=D:\QLIKVIEW\30. EXTRACTORS\SAP Extractors\Stock\2022 Stock Movement Extractor.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)
(2021-12-11 02:58:06) Information: Task Execute Duration=00:28:06.1650472
(2021-12-11 02:58:06) Information: Sending Alert mail
(2021-12-11 02:58:06) Error: Failed to send mail. Exception=System.FormatException: An invalid character was found in the mail header: ';'. || at System.Net.Mail.MailAddressParser.ParseLocalPart(String data, Int32& index, Boolean expectAngleBracket, Boolean expectMultipleAddresses) || at System.Net.Mail.MailAddressParser.ParseAddress(String data, Boolean expectMultipleAddresses, Int32& index) || at System.Net.Mail.MailAddress..ctor(String address, String displayName, Encoding displayNameEncoding) || at QDSMain.SMTPServerResource.SendMail(ILogBucket logBucket, MailMessage i_MailMessage, Boolean validateMailAddress)
Does this suggest there is a bottle neck on the memory from the Qlik view server?
Kind Regards
Fran
Hello @Francois1 ,
Thanks for posting.
Would be interesting to see the errors on the script/document log instead of the Task one. Here we can also see your SMPT is complaining when sending an email as the task has failed.
Nevertheless, this seems a secondary issue, so I would suggest to have a look at such look and search on our Community afterwards.
Cheers!
Hello,
did you ever find the cause? We are seeing the same problem.
Hi @fzalexanderjohn,
Do you have the same error in the task log Error: The Source Document was NOT reloaded successfully? If so, then check the document log of the QVW associated with the failed task. Also check the SAP Conncetor logs for any errors. Please post back here and let us know what you find. Thanks!
Best Regards
Hello Chip,
sadly we already have an open case with our Qlik Support for months now without any progress despite sending all kinds of logs. Find people who have had the same problem and found the solution seems to be the best course of action for me now.