 |
SoftTree Technologies
Technical Support Forums
|
|
| Author |
Message |
cslomka
Joined: 02 Oct 2007
Posts: 17
|
|
 Runnig jobs with 24x7.exe / JOBS |
 |
We have 24x7 running as a service and it was suggested here to run using the above command. When I use the command the a new instance of the scheduler launches and I get a message that indicates that there is already an instance of the scheduler running so the schedule is not actived. Then no job launches.
We do not have remote acess set up and we are not running in distributed mode.
|
|
| Wed Oct 03, 2007 12:18 pm |
  |
 |
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7951
|
|
| |
|
The command line parameter is actually JOB not JOBS, and it must be following by an name or unique ID of the job to launch, for example,
24x7.exe /JOB 125
Hope this helps.
|
|
| Wed Oct 03, 2007 12:26 pm |
|
|
cslomka
Joined: 02 Oct 2007
Posts: 17
|
|
| |
|
Sorry typo I was usings the job/jobname <number>
|
|
| Wed Oct 03, 2007 12:30 pm |
|
|
cslomka
Joined: 02 Oct 2007
Posts: 17
|
|
| |
|
I ran as you indicate above and now get a message indicating job does not exist. I am entering the job number listed on the properties page. Is this correct?
|
|
| Wed Oct 03, 2007 12:42 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7951
|
|
| |
|
Yes, this is correct and it should work if you enter a valid number. Try some other job and see if it works for you.
|
|
| Wed Oct 03, 2007 12:46 pm |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
