Batch file reload process stalls

[#1]

I am running a batch file to reload 6 documents (using "c:\program files\qlikview\qv.exe" /r "document.qvw"). 5 of the 6 documents reload fine but one stalls after the reload process is completed. It doesn't matter where in the sequence of reloads, this same document will always stall and leave the windows cmd window on screen and qv.exe still loaded as a Windows process.

I have removed PostReload macros to eliminate this. The document actually saves after the reload. It reloads fine in QlikView - only a problem when running in a batch file.

Running QV9 SR3. Any ideas on how to isloate the problem?

Thanks, Kevin

[#2]

Further to this post ...

I have created a brand new document, copied the script from the problem document to the new one and exported the layout from the problem document to the new one.

This still does not resolve the issue and the document still stalls after a successful reload.

Can anyone offer any suggestions as to why this might be happening?

Thanks, Kevin

[#3]

Hi

I'd like to repost this problem in case someone might have some ideas that can resolve this.

Thanks, Kevin

[disqr_rm]

Can you turn on the "Generate log" checkbox under document properties, for the problematic document, and run the sequence again? Then check if you see anything in the log file generated in the same directory as qvw file.

Also you may want to run that one document in a separate batch file and see if that works or not.

Seems to be something wrong with the document - marco, triggers, etc., and not with the batch file itself.

Rakesh

[#5]

Thanks for the reply Rakesh

In order to resolve this problem I created a completely new document, manually copied the script, all the objects and macros, recreated all the groups and variables. Now the scheduled reload process works successfully. I'm assuming that some corruption existed within the document somewhere. I had previously tried exporting the entire layout and importing into a new docoument but this did not resolve the problem.

Frustrating and time consuming but at least the process works now.

Cheers, Kevin