We are running version 10 of QV Server, and we are coordinating the load of a QVW from several QVD's with an ETL load of an Oracle data warehouse database.
The load is started from Tidal, via it's remote agent on the QV server, using a .BAT file. The .BAT file runs perfectly when run manually, or if it's scheduled via Windows Task Scheduler.
However, when starting it via a Tidal job, QV.EXE starts (you can see it in Task Manager) but never does anything, and just sits there like it's waiting for something. You have to hit 'End Process' to kill it.
I temporarily revived our old QV ver 9 server and tried the same task - it works from Tidal just fine - loads that QVW up like a champ.
I can run any other program (XCOPY.EXE, Excel, etc) on this ver 10 server via Tidal/.BAT with no problem.
The only thing I can think of is that maybe QV.EXE is waiting for the GUI progress box to open up, but since Tidal runs it's jobs in a console, and not on the desktop, it has no windowing layer to open the box in...
Has anybody else experienced this? Is there a way to have ver. 10 QV.EXE run in a TRULY silent mode (yes, I tried "SET ErrorMode=0;") with nothing showing on the desktop?
I don't have experience with your environment, but have you tried running a *.vbs file with vbscript to do the reload instead of the batch file? Search the forum for examples and use the doreload() function.
It seems you are leasing license for the batch user. This is what causing you problem.
You need to buy a QVLC (Local Client) and put it on the server. It should run fine then.
When running via batch file, the batch is trying to lease more than 2 times, and then it's hanging as it cannot handle the license popup in the backgroud. Just buy one license of QVLC and put the key in the user session you are running batch under. This way, it will run batch processes with local licenses and will not try to lease it from the server.
Hope this helps, and if it does, please provide feedback.
Not sure that's it - I'm using the same user ID for the batch file as I am when I do development on this same server.
That also doesn't explain why the same setup works fine on the old ver.9 server.
I am almost sure, that's the issue. I have gone through exact same issue and resolved it. Somehow when you run as dialog user it leases license just fine, but with batch it causes issues.
Try getting a temporary key from QlikTech for few days to test it out. Or you can convert one Named CAL to QVLC to try this out.
OK, at this point I'm willing - is there something I need to do to convert the Named CAL to a QVLC? I've never heard of a QVLC license before in my conversations with QlikTech...
Talk to your QlikView salesman / partner. It's called QlikView Local Client license. It used to be called QlikView Developer or Standalone client license. I am pretty sure you can convert one Named CAL to QVLC, but it may depend on your particular contract situation. Give it a try, or worst case you would need to buy one license. I believe cost is same as Named CAL, but again you need to confirm this with your QlikView person / partner.
I'm interested to know whether you gave the proposed solution a go, and what the result was. I'm experiencing a similar problem, but with the difference that Windows scheduler is used to initiate the jobs.