I am experiencing some ETL documents that are freezing at the end of completion. They run through the full length of code, but do not shut down after the last line of code finishes. The entire QV.EXE instance has to be forcibly shut down. The script will hang when run normally, and also when stepped through via the debugger.
Also, the documents on the server have been getting similar types of error messages.
(2013-05-15 08:57:49) Information: Closing the document.
(2013-05-15 08:58:14) Error: Could not close the SourceDocument. Exception=The currently executing operation was aborted.
(2013-05-15 08:58:15) Warning: The QlikView Engine isn't responding to close command, it will be killed (Please ignore logged errors about the kill).
(2013-05-15 08:58:15) Information: Killing the QlikView Engine. ProcessID=5940
(2013-05-15 08:58:15) Information: Closed the QlikView Engine successfully. ProcessID=5940
(2013-05-15 08:58:15) Error: The task "Reload MostActiveScriptReload" failed. Exception:
This seems to lead me to the idea one of our newest progress inhibitors is something that is getting a handle on the QlikView termination functions and blocking them. Any ideas on what this latest and greatest monkey wrench is?
