Job does not run

Hi
This is first time I am using 24X7 scheduler. I have scheduled
several jobs. When I check it shows time and date log when it run but in
reality none of the job run. Can someone help me what I might be doing wrong.
I am using Win 2003 server. Also, I do not see any time or date in Next Run and Last Run column
of JOBS Tab.

My scheduler is closed all the time and i checked 24X7 Services is in STARTED mode in Windows
2003 SERVICE Panel.

You are not trying to run a trial version in service mode? Are you?

: Hi
: This is first time I am using 24X7 scheduler. I have scheduled
: several jobs. When I check it shows time and date log when it run but in
: reality none of the job run. Can someone help me what I might be doing wrong.
: I am using Win 2003 server. Also, I do not see any time or date in Next Run
: and Last Run column
: of JOBS Tab.

: My scheduler is closed all the time and i checked 24X7 Services is in STARTED
: mode in Windows
: 2003 SERVICE Panel.

>>You are not trying to run a trial version in service mode? Are you?

I have the same problem.
It's not possible to run jobs via service mode in the trial version?

The trial version can only run under LocalSystem account because it needs access to the interactive user desktop., and that's why when you enable the service mode it sets the service to run under LocalSystem account.

FYI: Registered version can run under any account provided that account has sufficient privileged to execute the scheduled jobs and access the required resources.

Is this true of the multi-platform edition as well?

I installed the service under my account using 24x7srv.exe

Over the last 3 nights:

- only a few of the expected jobs ran
- everything ran OK
- only some of the jobs ran; some ran once I started the 24x7 GUI, and one sent an e-mail but there's nothing in the log; also a number of semaphore files are missing

I think it only applies to the Windows version. In the trial mode, on startup it displays the Evaluation Reminder dialog waiting for the user to acknowledge this by clicking the Continue button. Whether it is setup to run as a service or not, it still needs to have access to the user Desktop. In Windows, only LocalService account can access the Desktop fro ma service. If you pick any other account, the service is going to display the dialog somewhere on the hidden services desktop, but you cannot see it. As a result, the service isn't going to load and jobs aren't going to run. As you see, this is the only trial version limitation, apart from the default 30-day trial period.

The multi-platform version doesn't display anything when running as a service, regardless of the trial or non-trial mode.

Thanks for the prompt reply. So it appears the issues I've seen were caused by something else? (I can start a new thread if that's the case)

If this is still an issue, please start a new thread.

If some jobs run, but not all, that obviously means that the service is running. If jobs that the scheduler says in the log have been run, but you don't see any results of these jobs, you should add custom loging to these jobs or simply redirect their output to a log file. I am pretty sure you will find in the output the cause of the problem.

Just in case… one common mistake that many people make is the assumption that jobs started from a service like 24x7 would run the same way as jobs started manually from command line or from 24x7 running in graphical mode. Wrong. Windows services have lots of limitations, for example, they cannot access network files using mapped network shares, they must use UNC path instead, they cannot access certain local and network resources and generally affected by different security settings. Any job started from a service including child processes created by that job fall under the same umbrella. Please note that this is not specific to 24x7 service. it is a general Windows design.