we also know this problem.
It seems to appear if the applicaton get opened by another person or another computer. The other effect is if your account uses morer than 2 licenses (e.g on a desktop, on a laptop and on a server). You only can own two licences at the time.
Always run is to open QlikView, open document.
Kristoffer, thanks for your reply.
I do have a local developer license for Desktop installed on the server that hosts Qlikview.
I have continued to play around with this problem today and after some testing, have found a workaround that, although far from ideal, appears to work.
My suspicion is that because the vbscript runs asynchronously (i.e. it doesn't wait for one line to finish before it starts on the next), the error probably pops up when lines 1 and 2 of the script are executed simultaneously. The fact that sometimes it works and sometimes it doesn't would support this theory, particularly as it tends to fail on the first load, the works on the second (the first load is typically slower).
By inserting wscript.sleep 3000 after line 1, this gives the application 3 seconds to load before then assigning the document to the object and opening the document. Having run the script 20 times just now, I have not had any errors so far, so fingers crossed this has done the trick.
Not sure whether I would class this as a Qlikview bug, or a limitation of using an asychronous script to launch the application, (or both!). To be absolutely safe, going forward, I might make it my practise to insert a sleep command of a couple of seconds in between every command so the script doesn't get ahead of itself.
Interested in your thoughts.