I am running 24x7 automation suite 3.2.4 and everytime I attempt to reboot my Windows 2000 Pro workstation, I get a Dr. Watson error. Any suggestions?

Do you mean Dr.Watson error in 24x7?
Does it run any jobs while the machine is being rebooted?

: I am running 24x7 automation suite 3.2.4 and everytime I attempt to reboot my
: Windows 2000 Pro workstation, I get a Dr. Watson error. Any suggestions?

: Do you mean Dr.Watson error in 24x7?
: Does it run any jobs while the machine is being rebooted?

Actually, I mean that as 24x7 is shutting down, it will throw up a Dr. Watson error.
It is not running a scheduled job as it is quitting. Also, I have it running in the
run key, not running as a service.

Do you have any jobs scheduled for logout or shutdown events?
Try setting the job that reboots the machine as asynchronous and detached.

: Actually, I mean that as 24x7 is shutting down, it will throw up a Dr. Watson
: error.
: It is not running a scheduled job as it is quitting. Also, I have it running
: in the
: run key, not running as a service.

: Do you have any jobs scheduled for logout or shutdown events?
: Try setting the job that reboots the machine as asynchronous and detached.
OK, I think I have confused you. It is not a 24x7 scheduled
job that causes the Dr. Watson. It occurs when the scheduler
is loaded and on the SYSTRAY and the user shuts down
their workstation. There is not a job that reboots or
that is running when the Dr. Watson occurs. The scheduler
is merely loaded and the workstation is being shut down.

But still, are there any jobs scheduled for system "logout" or "shutdown" events? If yes, please check what these jobs are doing in these events.

What do you get as the last or 3 records in the job log? Are there any indications of what could cause this problem?

Are you running 24x7 in the server mode (see Tools/Options menu; Network tab if you want to verify it)? If yes, are there any active connections at the time of shutdown?

: OK, I think I have confused you. It is not a 24x7 scheduled
: job that causes the Dr. Watson. It occurs when the scheduler
: is loaded and on the SYSTRAY and the user shuts down
: their workstation. There is not a job that reboots or
: that is running when the Dr. Watson occurs. The scheduler
: is merely loaded and the workstation is being shut down.

: But still, are there any jobs scheduled for system "logout" or
: "shutdown" events? If yes, please check what these jobs are
: doing in these events.

: What do you get as the last or 3 records in the job log? Are there any
: indications of what could cause this problem?

: Are you running 24x7 in the server mode (see Tools/Options menu; Network tab
: if you want to verify it)? If yes, are there any active connections at the
: time of shutdown?

No jobs are scheduled for shutdown events. However, we may be attributing
something that might be causing the problem. We are referencing a .dat file
for 24x7 to use. Occassionally, we have an update to that file. We stop all
instances (processes) by process id which unloads 24x7. Then, we replace the
.dat file and reload 24x7. Usually, this must occur in order for us to get
the Dr. Watson.

The last record indicates that 24x7 is shutting down.

No, server mode is not enabled.

How do you "stop" all instances?

: No jobs are scheduled for shutdown events. However, we may be attributing
: something that might be causing the problem. We are referencing a .dat file
: for 24x7 to use. Occassionally, we have an update to that file. We stop all
: instances (processes) by process id which unloads 24x7. Then, we replace the
: .dat file and reload 24x7. Usually, this must occur in order for us to get
: the Dr. Watson.

: The last record indicates that 24x7 is shutting down.

: No, server mode is not enabled.

: How do you "stop" all instances?
We determine the process id and run a Kill "PROCESS ID".