Look if your VBScript job is set to run detached. I think when you run it in test mode you force it to run in the foreground in the same 24x7 instance and everything is working as expected. When it's run on schedule, it runs detached in a separate instance which doesn't have access to the main 24x7 instance (scheduling engine) and that's why you don't see it changing properties of another job. Detached mode is for shielding the scheduler from potentially unstable jobs such as VBScipt jobs that tend to loose system resources. You can control detached mode using detached job property. : I have a VBScript job that when I exit and restart : changes to JALScript in the properties. I have uninstalled : and re-installed but same problem. If I run using Test Mode : it runs fine as VBScript (unless I restart) but if I : run using Normal my script runs up to Sub Main(). : Is there a number of lines limit for VBScript. There are : 1511 lines in my script.
|