Using the Job or Queue Monitors always crashes 24x7 on our Window NT 4.0 servers. These options work fine on Win2000 Servers. Is this a 24x7 bug with NT 4.0? We are also accessing it via PC Anywhere (is this a factor).

I noticed another person posted this issue but saw no follow up solution.

Thanks,
Mark

Couple other people have complained that cannot use Queue Monitor on NT 4, but so far we are unable to reproduce this issue.

If you would like to help in fixing this problem please run 24x7 from command line with /DEBUG and /PBDEBUG options and then please send the produced 24x7.dbg file along with the schedule.log file to support. Please note that system might very slow in the debug mode and the output file could be very large so please zip it before sending. If possible, please create a simple job database file containing just one or two jobs before running in the debug mode. This will greatly shorten the debug time and reduce the size of the output file.

: Using the Job or Queue Monitors always crashes 24x7 on our Window NT 4.0
: servers. These options work fine on Win2000 Servers. Is this a 24x7 bug
: with NT 4.0? We are also accessing it via PC Anywhere (is this a factor).

: I noticed another person posted this issue but saw no follow up solution.

: Thanks,
: Mark

This problem still exists in 3.4.7

Ted.

: Using the Job or Queue Monitors always crashes 24x7 on our Window NT 4.0
: servers. These options work fine on Win2000 Servers. Is this a 24x7 bug
: with NT 4.0?

: I noticed another person posted this issue but saw no follow up solution.

: Thanks,
: Mark

Mark,

We know this problem for a long time, but unfortunatelly we are unable to reproduce it on our NT 4.0 systems.
We already asked several people who has the problem to provide certain debugging information that we need in order to fix it, but so far nobody returned our calls.

If you wish please run 24x7 from the command line with /DEBUG and /PBDEBUG swithes as
24x7 /DEBUG /PBDEBUG.

24x7 will run very...very slow, it might take several minutes just to start. Please let it run. When the 24x7 GUI appears click either Job Monitor or Queue Monitor buttons. After it freezes, kill the 24x7 process using Task Manager and then zip and email all .DBG and .LOG files from 24x7 Scheduler directory.

We can this this information to figure out what happens on your system. Please note the generated debug infromation is specific to 24x7 code only and it does not compromize your system in any way.

: Using the Job or Queue Monitors always crashes 24x7 on our Window NT 4.0
: servers. These options work fine on Win2000 Servers. Is this a 24x7 bug
: with NT 4.0? We are also accessing it via PC Anywhere (is this a factor).

: I noticed another person posted this issue but saw no follow up solution.

: Thanks,
: Mark

I am running 24x7 with the debug info right now, please give me the email address you would like it sent to.

Ted.

: Mark,

: We know this problem for a long time, but unfortunatelly we are unable to
: reproduce it on our NT 4.0 systems.
: We already asked several people who has the problem to provide certain
: debugging information that we need in order to fix it, but so far nobody
: returned our calls.

: If you wish please run 24x7 from the command line with /DEBUG and /PBDEBUG
: swithes as
: 24x7 /DEBUG /PBDEBUG.

: 24x7 will run very...very slow, it might take several minutes just to start.
: Please let it run. When the 24x7 GUI appears click either Job Monitor or
: Queue Monitor buttons. After it freezes, kill the 24x7 process using Task
: Manager and then zip and email all .DBG and .LOG files from 24x7 Scheduler
: directory.

: We can this this information to figure out what happens on your system.
: Please note the generated debug infromation is specific to 24x7 code only
: and it does not compromize your system in any way.

Please email your files to support@softtreetech.com

: Mark,

: We know this problem for a long time, but unfortunatelly we are unable to
: reproduce it on our NT 4.0 systems.
: We already asked several people who has the problem to provide certain
: debugging information that we need in order to fix it, but so far nobody
: returned our calls.

: If you wish please run 24x7 from the command line with /DEBUG and /PBDEBUG
: swithes as
: 24x7 /DEBUG /PBDEBUG.

: 24x7 will run very...very slow, it might take several minutes just to start.
: Please let it run. When the 24x7 GUI appears click either Job Monitor or
: Queue Monitor buttons. After it freezes, kill the 24x7 process using Task
: Manager and then zip and email all .DBG and .LOG files from 24x7 Scheduler
: directory.

: We can this this information to figure out what happens on your system.
: Please note the generated debug infromation is specific to 24x7 code only
: and it does not compromize your system in any way.

Please email your files to support@softtreetech.com

: I am running 24x7 with the debug info right now, please give me the email
: address you would like it sent to.

: Ted.