Running jobs manually using remote control asynchronously

I have 24x7 running as a windows service on Machine A. I am trying to run few jobs manually using 24x7 remote control on installed on server B. Once I connect from server B using 24x7 Remote control, I am able to start the job on remote only if I choose to wait for its completion (run synchronously). If I uncheck the job for "Wait for job to complete" and then click Remote button, the job does not gets started.

At fist I thought it had something to do with job process setting as "Asynchronous Process" but I tried to run both kinds of jobs, Asynchronous Process and synchronous Process and I am getting same result.

Can some one please let me know what am I missing?

I tried to search the forum for similar issue but was unable to do so, if there is similar previous thread, please point me to that!

Thanks!

Goldie.

Please verify the legacy "asynchronous operations "option is not checked in the Remote Host Profile properties. This option can cause conflicts with asynchronous job runs.

Also try reconnecting to the host or just refreshing the logs to see what appears in the log for a remote asynchronous job. In other words if a "Job starting" message is recorded in the job log. If yes, the job starts and immediately aborts, which in turn would indicate a communication issue. If there is no such message, then it is something on the Remote Control side, and need to know more details about the job setup; and also know which versions of 24x7 you are running on the remote and local hosts.

I believe i figured it out. I was trying to start a job that was disabled. Once i enabled the job, it ran find with "Wait for job to complete" box unchecked!

little off topic, but i also found that if a disabled job is started the way i described in my previous post, it will not notify any other jobs that needs to be started on its completion either.

Thx for your prompt response!!!

Goldie.

Please keep in mind those running jobs this way is not the same as running them normally on schedule. From the remote control you are basically sending a job for remote execution, not triggering it on the scheduler side. It is not logically connected/linked to any other job and the scheduler is not going to chain them as you are might be expecting.

Windows based 24x7 Remote Control is not designed for that. The primary purpose of the Remote Control is job management, development and monitoring. 24x7 Web-based console can be used to trigger job in remote schedulers. It can also do virtually everything that a Windows based Remote control can do.