I am testing 24x7 as an NT Service. If I try to stop the service I get the following error message:

Could not stop the 24x7 scheduler service on Local Computer.
Error 997: Overlapped I/O operation is in progress.

The service then appears to stop though. What does this mean and how do I avoid it. Also, can you tell me what the advantages are of running 24x7 as an NT service? I don't seem to see any clear benefit.

Thanks,
Jeff Inouye

You are running Win2000 or XP, right?
These Windows versions detect that the 24x7 Service Control Manager performs somme operations on another process when it gets the stop service request. Indeed, it terminates the Job Engine, which is running as a separate process. Ohter than the message this does not cause any other side effects or problems, so you can simply disregard it.

Also, not that this message doesn't appear with 24x7 v3.0.4 and later.

: I am testing 24x7 as an NT Service. If I try to stop the service I get the
: following error message: Could not stop the 24x7 scheduler service on
: Local Computer.
: Error 997: Overlapped I/O operation is in progress.

: The service then appears to stop though. What does this mean and how do I
: avoid it. Also, can you tell me what the advantages are of running 24x7 as
: an NT service? I don't seem to see any clear benefit.

: Thanks,
: Jeff Inouye

Thanks for the response...how about my question about advantages of using 24x7 as an NT service? Why would you want to run it this way?

: You are running Win2000 or XP, right?
: These Windows versions detect that the 24x7 Service Control Manager performs
: somme operations on another process when it gets the stop service request.
: Indeed, it terminates the Job Engine, which is running as a separate
: process. Ohter than the message this does not cause any other side effects
: or problems, so you can simply disregard it.

: Also, not that this message doesn't appear with 24x7 v3.0.4 and later.

I believe the main reason why some people setup 24x7 to run as a service is because they want it to start automatically when their computer starts but before anyone logs on to the system. If you just use a shortcut in the StartUp folder, it will not start until the logon.

Some people also like that it runs invisible (and all launched batch and graphical programs as well) and this makes it more difficult for other users to interact with the batch processing.

Services can be remotelly stoped and started.

On other hand, services have many limitations, such as limited access to network resources, that could be a sticking point if your bsuness rules require accessing network files, database, etc...

Batch files and graphical programs can be also started invisible if you setup them to run in a hidden window.

That's why you should carefully consider if it is worth to run 24x7 as a service.

: Thanks for the response...how about my question about advantages of using
: 24x7 as an NT service? Why would you want to run it this way?