We are still in the 30 day trial period
and are trying to get the unattended
"Master" 24x7 server to automaticlly
startup up as Windows 2000 service.
Going in thru Tool>Options>Service Tab
creates an entry in the Services table
but the service does not start on re-boot.
Trying to start the service manually
causes Window's Error 1058, something
about the service being disabled or there
being no enabled devices with it.

Any suggestions?

Thanks,
Don

Intro: The only limitation of the trial version is that the service must run under LocalSystem account with "Allow service to interact with the Desktop" option checked. This is needed for the service to display "Evaluation Reminder" screen on the service startup. The LocalSysem is the only account that supports that option.

I guess you are trying to setup it under some other user account or don’t use the "interact" option. As a result the service cannot start. Unfortunately the LocalSystem account cannot be used for the Master/Standby because LocalSystem has no network access. I suggest that you don’t try the Fail-over mode while running it as service until you get a licensed copy of the software. The Fail-over mode can be easily tested in the non-service mode.

: We are still in the 30 day trial period
: and are trying to get the unattended
: "Master" 24x7 server to automaticlly
: startup up as Windows 2000 service.
: Going in thru Tool>Options>Service Tab
: creates an entry in the Services table
: but the service does not start on re-boot.
: Trying to start the service manually
: causes Window's Error 1058, something
: about the service being disabled or there
: being no enabled devices with it.

: Any suggestions?

: Thanks,
: Don

Thanks, I think that was the root of my problem. Not being much of a Window's person, I was looking for the "Interact with the Desktop" checkbox in your application. I was trying to setup one server as the "Master" and use "Remote Control" to submit jobs to it. I had been having some success but was just not able to get the service to start automatically.

The only other thing I noticed was that when a job was scheduled and ran, the Monitor showed the correct Start Time but the Finish Time and Duration were off. The job would only take about 3 minutes to run but the Start Time and the Finish Time were the same and the Duration was 0. But the timestamp on the jobs output file showed that the job had run about 3 minutes. Should I expect to see 3 under the Duration heading?

Thanks,
Don

: Intro: The only limitation of the trial version is that the service must run
: under LocalSystem account with "Allow service to interact with the
: Desktop" option checked. This is needed for the service to display
: "Evaluation Reminder" screen on the service startup. The
: LocalSysem is the only account that supports that option.

: I guess you are trying to setup it under some other user account or don’t use
: the "interact" option. As a result the service cannot start.
: Unfortunately the LocalSystem account cannot be used for the
: Master/Standby because LocalSystem has no network access. I suggest that
: you don’t try the Fail-over mode while running it as service until you get
: a licensed copy of the software. The Fail-over mode can be easily tested
: in the non-service mode.

Here is what happens when set a program type job to run asynchronous: when the time comes 24x7 kicks of the job and considers the job done. If you set the job to run synchronous it will kick of the job and monitor it waiting for the job to complete before starting anything else in the same job queue. In this case the job is done when the stem process terminates or 24x7 aborts after user-specified timeout. The "finish" time that you in the log is the logical "done" time. On contrary the job monitor utility acts both as a job monitor and as a system task monitor. It displays time of the system process so you can see if the job is still running. This is especially helpful when remotely monitoring jobs using the 24x7 remote control.

In case if you need to know real job e time and/or build sequential or dependent jobs always use synchronous job run-time mode.

: Thanks, I think that was the root of my problem. Not being much of a Window's
: person, I was looking for the "Interact with the Desktop"
: checkbox in your application. I was trying to setup one server as the
: "Master" and use "Remote Control" to submit jobs to
: it. I had been having some success but was just not able to get the
: service to start automatically.

: The only other thing I noticed was that when a job was scheduled and ran, the
: Monitor showed the correct Start Time but the Finish Time and Duration
: were off. The job would only take about 3 minutes to run but the Start
: Time and the Finish Time were the same and the Duration was 0. But the
: timestamp on the jobs output file showed that the job had run about 3
: minutes. Should I expect to see 3 under the Duration heading?

: Thanks,
: Don