We have version 3.4.26.0 installed on a Windows 2003 server running as
a service.
Periodically, the service stops and we get a message box pn the desktop
that says 24x7.exe has encountered a problem and has terminated.

The detail option says it failed in PBVM70.DLL.

24x7 was stable on our old NT4.0 server. We have been having
this problem since moving to Win2003 2 weeks ago.

Did you move/copy scheduler settings from the old installation (I mean settings from the Tools/Options menu)?
Did you configure jb queues the same way or diffferently?
What is happening before that error? Are there any jobs running? If yes, what are they doing?
do you use MAPI or SMTP email interface?

: We have version 3.4.26.0 installed on a Windows 2003 server running as
: a service.
: Periodically, the service stops and we get a message box pn the desktop
: that says 24x7.exe has encountered a problem and has terminated.

: The detail option says it failed in PBVM70.DLL.

: 24x7 was stable on our old NT4.0 server. We have been having
: this problem since moving to Win2003 2 weeks ago.

We built the scheduler from scratch on the Win2003 box
but we set it using the same options and job parameters as the NT 4.0 box.
We used the most recent version of 24x7. The NT 4.0 version was at least
4 years old.

Job queues are the same.

Jobs are running normally went it crashes. These detached jobs
that are running batch files.

the SMTP interface is configures on the tools/option dialog.
However, there is no alerts / notifications set up so it shouldn't be
sending anything.

: Did you move/copy scheduler settings from the old installation (I mean
: settings from the Tools/Options menu)?
: Did you configure jb queues the same way or diffferently?
: What is happening before that error? Are there any jobs running? If yes, what
: are they doing?
: do you use MAPI or SMTP email interface?

: Jobs are running normally went it crashes. These detached jobs
: that are running batch files.

So there are some jobs running at the time of the popup. Right? Can you providem ore infor about these jobs?
Are there any file-watch jobs looking for network files?

: So there are some jobs running at the time of the popup. Right? Can you
: providem ore infor about these jobs?
: Are there any file-watch jobs looking for network files?

There are jobs that start based on a trigger file.
The folder for these trigger files is on a different
server. The 24x7 server is started using a local user
who is a member of the local admin group.

Theyre really isn't one job that is running at the time it crashes.
It seems to be a different job each time. However all jobs are pretty much
the same. These are jobs execute a batch file that
contains a start /w prgm.exe command. What other info would
you like for me to supply?

I have another customer who is running the same application
(on Win2003) and their scheduler has never crashed.

There are jobs that start based on a trigger file.
The folder for these trigger files is on a different
server. The 24x7 server is started using a local user
who is a member of the local admin group.

Theyre really isn't one job that is running at the time it crashes.
It seems to be a different job each time. However all jobs are pretty much
the same. These are jobs execute a batch file that
contains a start /w prgm.exe command. What other info would
you like for me to supply?

I have another customer who is running the same application
(on Win2003) and their scheduler has never crashed.

One other thing, that I just found. In the event log there is an
Error type event. Category SNMP, description
24x7 SNMP extension agent : Timeout occurred while waiting for trap
data.

I don't think network permissions is a concern here.
Can you compare settings for these 2 scheduler instances? Are they the same?
Do you have by any change "Show Job Status Display" option enabled?

Does the other scheduler also check for network files?

: There are jobs that start based on a trigger file.
: The folder for these trigger files is on a different
: server. The 24x7 server is started using a local user
: who is a member of the local admin group.

: Theyre really isn't one job that is running at the time it crashes.
: It seems to be a different job each time. However all jobs are pretty much
: the same. These are jobs execute a batch file that
: contains a start /w prgm.exe command. What other info would
: you like for me to supply?

: I have another customer who is running the same application
: (on Win2003) and their scheduler has never crashed.

: One other thing, that I just found. In the event log there is an
: Error type event. Category SNMP, description
: 24x7 SNMP extension agent : Timeout occurred while waiting for trap
: data.

Show job status display is not checked.
I'm not sure the other scheduler is still around, but I'll
check.
The other scheduler was accessing the trigger files across
the network in the same manner.

: I don't think network permissions is a concern here.
: Can you compare settings for these 2 scheduler instances? Are they the same?
: Do you have by any change "Show Job Status Display" option enabled?

: Does the other scheduler also check for network files?

Do you use any programmatic interfaces to the scheduler?
Do you use 24x7 Remote Control or 24x7 web-based interface?
Do you run the scheduler as a standalone server or as a service? Do you start directly on the server or using Windows Remote Desktop or some other "remote" feature?
Are there any other error or warning messages in Windows Application or System Event Log predeceasing 24x7.exe faults?
Have you checked for network address conflicts or outages that occurring during file checks?

: Show job status display is not checked.
: I'm not sure the other scheduler is still around, but I'll
: check.
: The other scheduler was accessing the trigger files across
: the network in the same manner.

programmatic interfaces : No.
24x7 Remove control : No . Web interface : No
Running as a service.
The services is started thru remote desktop
not using any remote features at all.

I documented the Event log error in a previous post:
That is we get the following message before it crashes

Error type event. Category SNMP, description
24x7 SNMP extension agent : Timeout occurred while waiting for trap
data.

I'll instruct them to look for network conflicts etc.

: Do you use any programmatic interfaces to the scheduler?
: Do you use 24x7 Remote Control or 24x7 web-based interface?
: Do you run the scheduler as a standalone server or as a service? Do you start
: directly on the server or using Windows Remote Desktop or some other
: "remote" feature?
: Are there any other error or warning messages in Windows Application or
: System Event Log predeceasing 24x7.exe faults?
: Have you checked for network address conflicts or outages that occurring
: during file checks?

Let's try to dig in 24x7 SNMP direction. Please try stopping SNMP service on the system and check if it will stop the crashing Also please check if any job has SNMP notification action set.

: programmatic interfaces : No.
: 24x7 Remove control : No . Web interface : No
: Running as a service.
: The services is started thru remote desktop
: not using any remote features at all.

: I documented the Event log error in a previous post: That is we get the
: following message before it crashes

: Error type event. Category SNMP, description
: 24x7 SNMP extension agent : Timeout occurred while waiting for trap
: data.

: I'll instruct them to look for network conflicts etc.

Thanks for your help so far.
There is no job with SNMP notification set.
The users will schedule a stop of the SNMP service
tomorrow to see if this error stops.
I'll report back then. Thanks again.

: Let's try to dig in 24x7 SNMP direction. Please try stopping SNMP service on
: the system and check if it will stop the crashing Also please check if any
: job has SNMP notification action set.

We finally got an opportunity to try what you suggested.
The event log errors STOPPED when we stopped the
SNMP service.
We cannot permanently stop SNMP because it is used for
hardware monitoring etc .

With the SNMP service running we were getting the
SNMP Trap message every 2 hours like clockwork.

: Thanks for your help so far.
: There is no job with SNMP notification set.
: The users will schedule a stop of the SNMP service
: tomorrow to see if this error stops.
: I'll report back then. Thanks again.

In that case simply rename 24x7snmp.dll to 24x7snmp.dll_bak while the service is stopped and then restart the service.

: We finally got an opportunity to try what you suggested.
: The event log errors STOPPED when we stopped the
: SNMP service.
: We cannot permanently stop SNMP because it is used for
: hardware monitoring etc .

: With the SNMP service running we were getting the
: SNMP Trap message every 2 hours like clockwork.

Thanks again for the recommendation. We will
try that and let you know the outcome.

: In that case simply rename 24x7snmp.dll to 24x7snmp.dll_bak while the service
: is stopped and then restart the service.