My Qlikview applications are sometime failing. The apps are scheduled to reload every 15 mins and it fails atleast 10-15 times a day. After failing it generally fixes itself in the next reload. I guess the Qlikview services are not responding Intermittently, but have no ideas how to fix this.
The follow is the log that appears during the failure of reload.
Logs:
--------
2013-04-04 21:05:00) Information: Task Dependencies are OK
(2013-04-04 21:06:01) Error: The task "BatchDashboard/Batch Dashboard_Loader.qvw" failed. Exception:
(2013-04-04 21:06:01) Error: QDSMain.Exceptions.DistributionFailedException: Distribute failed with errors to follow. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
(2013-04-04 21:06:01) Error: at QlikTech.NetClient.QvClient.GetMessageDataFromSocket(Byte[] buffer, Double timeout)
(2013-04-04 21:06:01) Error: at QlikTech.NetClient.QvClient.GetMessageSizeFromSocket(Double timeout)
(2013-04-04 21:06:01) Error: at QlikTech.NetClient.QvClient.Execute(Byte[] request)
(2013-04-04 21:06:01) Error: at QlikTech.NetClient.QvClient.Execute(String request)
(2013-04-04 21:06:01) Error: at Wrappers.QVSWrapper.Ask(String question)
(2013-04-04 21:06:01) Error: at Wrappers.QVSWrapper.GetPhysicalPath(String documentName)
(2013-04-04 21:06:01) Error: at QDSMain.DistributeTask.GetFileName(String path)
(2013-04-04 21:06:01) Error: at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult)
(2013-04-04 21:06:01) Error: --- End of inner exception stack trace ---
(2013-04-04 21:06:01) Error: at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult)
(2013-04-04 21:06:01) Error: at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult)
Check application log also in your main folder where application is kept , log file having all the details of failure of reload.
Vikas
Hope this resolve your issue. If the issue is solved please mark the answer with Accept as Solution & like it. If you want to go quickly, go alone. If you want to go far, go together.
The application log does not reflect anything related to this reload failure. This reload failure occurs even before the actual reload of document starts and application log does not record this failure details.
