Ok, its publisher that runs the job (i guess that Publisher has no problem running other "non vbs" tasks, like a reload of the James.qvw file.).
What i meant was that if you had some sort of vbs triggered by a control on a webpage the vbs script will mostly be run by the netservice account (or what ever the heck it's called . And this user has most likely not been using Qlikview. So, when a user opens qlikview first time he is given the choise of running as analyzer, evaluation or enter license key.
I think Blaise is right on the money. Easy way to check is to log on to the machine using the account you use to run the QV services and start QlikView manually to see if you get stuck on the registration popup that appears the first time running the standalone.