I did a clean install of 24x7 version 3.4.24 and then a clean install of version 3.4.25e on a server running WINDOWS 2003.

After about 45 minutes on both versions 24x7 stopped running... see the event view application log below.

I am running 24x7 as an application not a service.
The machine has 3 gig of memory and plenty of disk storage free.
I tried this running my production schedule database and your examples schedule database with no jobs scheduled. Both had the same results.

I don't have this problem on a WINDOWS 2000 server environment.

Here is the event log for both 24x7 versions is:

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 6/29/2005
Time: 11:19:05 PM
User: N/A
Computer: SPGDBSCHED1
Description:
Faulting application 24X7.EXE, version 3.4.21.0, faulting module PBVM70.DLL, version 7.0.3.10095, fault address 0x001a30fe.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 32 34 58 ure 24X
0018: 37 2e 45 58 45 20 33 2e 7.EXE 3.
0020: 34 2e 32 31 2e 30 20 69 4.21.0 i
0028: 6e 20 50 42 56 4d 37 30 n PBVM70
0030: 2e 44 4c 4c 20 37 2e 30 .DLL 7.0
0038: 2e 33 2e 31 30 30 39 35 .3.10095
0040: 20 61 74 20 6f 66 66 73 at offs
0048: 65 74 20 30 30 31 61 33 et 001a3
0050: 30 66 65 0fe

Any jobs running at that time? You can check the job log to find out which jobs started before the crash. If yes, what were they doing?
Do you have tracing option enabled?

: I did a clean install of 24x7 version 3.4.24 and then a clean install of
: version 3.4.25e on a server running WINDOWS 2003.

: After about 45 minutes on both versions 24x7 stopped running... see the event
: view application log below.

: I am running 24x7 as an application not a service.
: The machine has 3 gig of memory and plenty of disk storage free.
: I tried this running my production schedule database and your examples
: schedule database with no jobs scheduled. Both had the same results.

: I don't have this problem on a WINDOWS 2000 server environment.

: Here is the event log for both 24x7 versions is: Event Type: Error
: Event Source: Application Error
: Event Category: (100)
: Event ID: 1000
: Date: 6/29/2005
: Time: 11:19:05 PM
: User: N/A
: Computer: SPGDBSCHED1
: Description: Faulting application 24X7.EXE, version 3.4.21.0, faulting module
: PBVM70.DLL, version 7.0.3.10095, fault address 0x001a30fe.

: For more information, see Help and Support Center at
: http://go.microsoft.com/fwlink/events.asp .
: Data: 0000: 41 70 70 6c 69 63 61 74 Applicat
: 0008: 69 6f 6e 20 46 61 69 6c ion Fail
: 0010: 75 72 65 20 20 32 34 58 ure 24X
: 0018: 37 2e 45 58 45 20 33 2e 7.EXE 3.
: 0020: 34 2e 32 31 2e 30 20 69 4.21.0 i
: 0028: 6e 20 50 42 56 4d 37 30 n PBVM70
: 0030: 2e 44 4c 4c 20 37 2e 30 .DLL 7.0
: 0038: 2e 33 2e 31 30 30 39 35 .3.10095
: 0040: 20 61 74 20 6f 66 66 73 at offs
: 0048: 65 74 20 30 30 31 61 33 et 001a3
: 0050: 30 66 65 0fe

Trace is not enabled and no jobs were scheduled. I am just running your examples schedules database with no jobs scheduled to run.

It just happened again...

Here is part of the 24x7 log showing the startup at 8:19:14 and when I started it up again at 8:54:22.

Also below is the event view application log showing the error at 8:39:22 which is shortly after it started at 8:19:24.

6/30/2005 08:19:14 0 0 0 24x7 Scheduler 24x7 Scheduler starting...
6/30/2005 08:54:22 0 0 0 24x7 Scheduler 24x7 Scheduler starting...

Here is the latest application event log:

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 6/30/2005
Time: 8:39:22 AM
User: N/A
Computer: SPGDBSCHED1
Description:
Faulting application 24X7.EXE, version 3.4.21.0, faulting module PBVM70.DLL, version 7.0.3.10095, fault address 0x001551c9.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 32 34 58 ure 24X
0018: 37 2e 45 58 45 20 33 2e 7.EXE 3.
0020: 34 2e 32 31 2e 30 20 69 4.21.0 i
0028: 6e 20 50 42 56 4d 37 30 n PBVM70
0030: 2e 44 4c 4c 20 37 2e 30 .DLL 7.0
0038: 2e 33 2e 31 30 30 39 35 .3.10095
0040: 20 61 74 20 6f 66 66 73 at offs
0048: 65 74 20 30 30 31 35 35 et 00155
0050: 31 63 39 1c9

It must be doing something before it crashes. Please try creating a new empty job database and check if it happens again. To create a new job database file use File/New/Job Database menu.
PS. Unfortunately the information in the event log record you are referenced is totally useless. It does not provide any meaningful details on what caused the crash, it simply states which DLL crashed.

: Trace is not enabled and no jobs were scheduled. I am just running your
: examples schedules database with no jobs scheduled to run.

: It just happened again...

: Here is part of the 24x7 log showing the startup at 8:19:14 and when I
: started it up again at 8:54:22.

: Also below is the event view application log showing the error at 8:39:22
: which is shortly after it started at 8:19:24.

: 6/30/2005 08:19:14 0 0 0 24x7 Scheduler 24x7 Scheduler starting...
: 6/30/2005 08:54:22 0 0 0 24x7 Scheduler 24x7 Scheduler starting...

: Here is the latest application event log: Event Type: Error
: Event Source: Application Error
: Event Category: (100)
: Event ID: 1000
: Date: 6/30/2005
: Time: 8:39:22 AM
: User: N/A
: Computer: SPGDBSCHED1
: Description: Faulting application 24X7.EXE, version 3.4.21.0, faulting module
: PBVM70.DLL, version 7.0.3.10095, fault address 0x001551c9.

: For more information, see Help and Support Center at
: http://go.microsoft.com/fwlink/events.asp .
: Data: 0000: 41 70 70 6c 69 63 61 74 Applicat
: 0008: 69 6f 6e 20 46 61 69 6c ion Fail
: 0010: 75 72 65 20 20 32 34 58 ure 24X
: 0018: 37 2e 45 58 45 20 33 2e 7.EXE 3.
: 0020: 34 2e 32 31 2e 30 20 69 4.21.0 i
: 0028: 6e 20 50 42 56 4d 37 30 n PBVM70
: 0030: 2e 44 4c 4c 20 37 2e 30 .DLL 7.0
: 0038: 2e 33 2e 31 30 30 39 35 .3.10095
: 0040: 20 61 74 20 6f 66 66 73 at offs
: 0048: 65 74 20 30 30 31 35 35 et 00155
: 0050: 31 63 39 1c9

I created an empty job database. I started 24x7 up as an application not a service. It took a while but it finally stopped with the same error as before. I did get a trace on this.

Note that I did have another 24x7 master scheduler on another server (Windows 2000) monitoring my problem server (Windows 2003) continuously at 10 minute interval using the AGENTTEST JAL statement.

The Event Viewer Error is the same as in previous messages.

Since I don't know how to send you the trace file as an attachment... here are the last few lines of the trace log:

SMI Release SMI_CONNECTION(009FEA48) refCount(2)
DPB Release DPB_SESSION_SERVICE(1BDBC398) refCount(1)
SMI Release SMI_TRACE(009FEC20) refCount(4)
SMI Release SMI_CONNECTION(009FEA48) refCount(1)
DPB56 Memory Proc Common : count(9107), total(757760), alloc(683499), free(59649)
DPB Release DPB_SESSION_SERVICE(1BDBC398) refCount(0)
DPB Release DPB_Connection(1BDBC4A0) refCount(0)
SMI Release SMI_CONNECTION(009FEA48) refCount(0)
SMI Release SMI_TRACE(009FEC20) refCount(3)
SMI Release SMI_LISTENER(009FEC68) refCount(1)
SMI Release SMI_TRACE(009FEC20) refCount(2)
SMI AddRef SMI_LISTENER(009FEC68) refCount(2)
SMI AddRef SMI_TRACE(009FEC20) refCount(3)
WSD04 AddRef: RefCount for connection object = 1
SMI AddRef SMI_TRACE(009FEC20) refCount(4)
SMI AddRef SMI_TRACE(009FEC20) refCount(5)
SMI AddRef SMI_LISTENER(009FEC68) refCount(3)
SMI Release SMI_LISTENER(009FEC68) refCount(2)
SMI AddRef SMI_CONNECTION(009FEA48) refCount(3)
SMI Release SMI_CONNECTION(009FEA48) refCount(2)
SMI12 Listener (009FEC68): Open Connection: (009FEA48). numConnections(103), SUCCEEDED (00000000)
WSD04 AddRef: RefCount for connection object = 2
WSD07 ReadHeader: Proto = 24576, Len = 142
SMI01 Connection(009FEA48): Create Message: (1BDBCC18), initial size 142 bytes
DPB AddRef DPB_SESSION_SERVICE(1BDBC2B0) refCount(2)
DPB40 SessionId (00000000): Handle Request: CREATE_SESSION(1), streamVer(0). SUCCEEDED (00000000)
DPB20 Connection(009FEA48): ClientConnect : dbadmin(GJOHNSON1) userId(dbadmin), connectString(), sessionId(FFFFFFFF). ... (00000000)
SMI AddRef SMI_LISTENER(009FEC68) refCount(3)
SMI16 Listener (009FEC68): Create Session: (1BDBC398). SUCCEEDED (00000000)
DPB41 : Use Session : sessionId(467387288). SUCCEEDED (00000000)
SMI Release SMI_LISTENER(009FEC68) refCount(2)
SMI AddRef SMI_CONNECTION(009FEA48) refCount(3)
DPB AddRef DPB_Connection(009FEB18) refCount(1)
DPB AddRef DPB_SESSION_SERVICE(1BDBC2B0) refCount(3)
DPB20 Connection(009FEA48): ClientConnect : dbadmin(GJOHNSON1) userId(dbadmin), connectString(), sessionId(1BDBC398). SUCCEEDED (00000000)
SMI01 Connection(009FEA48): Create Message: (1BDBDF50), initial size 0 bytes
DPB Release DPB_SESSION_SERVICE(1BDBC2B0) refCount(2)
SMI03 Connection(009FEA48): Send Reply Message: (1BDBDF50) sequenceNumber(475246) Asynchronous. ... (00000000)
SMI06 Connection(009FEA48): Process request Message: (1BDBCC18) serviceId(0), sequenceNumber(475246). SUCCEEDED (00000000)
WSD08 Send: result = 0
WSD07 ReadHeader: Proto = 24576, Len = 83
SMI03 Connection(009FEA48): Send Reply Message: (1BDBDF50) sequenceNumber(475246) Asynchronous. SUCCEEDED (00000000)
SMI01 Connection(009FEA48): Create Message: (1BDBDF90), initial size 83 bytes
DPB55 Memory Session : (1BDBC2B0) count(959), total(352256), alloc(208080), free(134536)
DPB AddRef DPB_SESSION_SERVICE(1BDBC2B0) refCount(3)
DPB56 Memory Proc Common : count(9112), total(757760), alloc(683877), free(59269)
DPB40 SessionId (1BDBC398): Handle Request: DISCONNECT(2), streamVer(0). SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(1BDBC2B0) refCount(2)
DPB AddRef DPB_SESSION_SERVICE(1BDBC2B0) refCount(3)
DPB21 Connection(1BDBC2B0): ClientDisconnect: userId(dbadmin), connectString(), sessionId(1BDBC398). ... (00000000)
DPB Release DPB_SESSION_SERVICE(1BDBC2B0) refCount(2)
DPB21 Connection(1BDBC2B0): ClientDisconnect: userId(dbadmin), connectString(), sessionId(1BDBC398). SUCCEEDED (00000000)
SMI06 Connection(009FEA48): Process request Message: (1BDBDF90) serviceId(0), sequenceNumber(475248). SUCCEEDED (00042137)
SMI01 Connection(009FEA48): Create Message: (1BDBE290), initial size 0 bytes
SMI03 Connection(009FEA48): Send Reply Message: (1BDBE290) sequenceNumber(475248) Asynchronous. ... (00000000)
WSD08 Send: result = 0
SMI03 Connection(009FEA48): Send Reply Message: (1BDBE290) sequenceNumber(475248) Asynchronous. SUCCEEDED (00000000)
SMI08 Connection(009FEA48): Disconnect: ... (00000000)
WSD09 SendDisconnect: result = 0
WSD04 Release: RefCount for connection object = 2
WSD06 ReadHeader: Received disconnect code = FF
SMI08 Connection(009FEA48): Disconnect: SUCCEEDED (00000000)
WSD04 Release: RefCount for connection object = 1
DPB Release DPB_SESSION_SERVICE(1BDBC2B0) refCount(1)
SMI Release SMI_CONNECTION(009FEA48) refCount(2)
SMI Release SMI_CONNECTION(009FEA48) refCount(1)
SMI Release SMI_TRACE(009FEC20) refCount(4)
DPB56 Memory Proc Common : count(9108), total(757760), alloc(683825), free(59321)
DPB Release DPB_SESSION_SERVICE(1BDBC2B0) refCount(0)
DPB Release DPB_Connection(009FEB18) refCount(0)
SMI Release SMI_CONNECTION(009FEA48) refCount(0)
SMI Release SMI_TRACE(009FEC20) refCount(3)
SMI Release SMI_LISTENER(009FEC68) refCount(1)
SMI Release SMI_TRACE(009FEC20) refCount(2)

: It must be doing something before it crashes. Please try creating a new empty
: job database and check if it happens again. To create a new job database
: file use File/New/Job Database menu.
: PS. Unfortunately the information in the event log record you are referenced
: is totally useless. It does not provide any meaningful details on what
: caused the crash, it simply states which DLL crashed.

Check in the Task Manager the following counters on the Processes tab page:
Number of Threads
Numbers of Handles
Memory Usage

You may need to customize the view (View/Columns) if not all of these columns are visible on the processes tab.

If the any of these keeps growing with time and never drops back you are probably experiencing resource leakage issues. If they just float up and down, it is something else. In that case please email to support all .LOG files from 24x7 home directory and also all files from the Performance Data subdirectory. It is a good idea to zip them into 1 archive all before sending.

: I created an empty job database. I started 24x7 up as an application not a
: service. It took a while but it finally stopped with the same error as
: before. I did get a trace on this.

: Note that I did have another 24x7 master scheduler on another server (Windows
: 2000) monitoring my problem server (Windows 2003) continuously at 10
: minute interval using the AGENTTEST JAL statement.

: The Event Viewer Error is the same as in previous messages.

: Since I don't know how to send you the trace file as an attachment... here
: are the last few lines of the trace log: SMI Release
: SMI_CONNECTION(009FEA48) refCount(2)
: DPB Release DPB_SESSION_SERVICE(1BDBC398) refCount(1)
: SMI Release SMI_TRACE(009FEC20) refCount(4)
: SMI Release SMI_CONNECTION(009FEA48) refCount(1)
: DPB56 Memory Proc Common : count(9107), total(757760), alloc(683499),
: free(59649)
: DPB Release DPB_SESSION_SERVICE(1BDBC398) refCount(0)
: DPB Release DPB_Connection(1BDBC4A0) refCount(0)
: SMI Release SMI_CONNECTION(009FEA48) refCount(0)
: SMI Release SMI_TRACE(009FEC20) refCount(3)
: SMI Release SMI_LISTENER(009FEC68) refCount(1)
: SMI Release SMI_TRACE(009FEC20) refCount(2)
: SMI AddRef SMI_LISTENER(009FEC68) refCount(2)
: SMI AddRef SMI_TRACE(009FEC20) refCount(3)
: WSD04 AddRef: RefCount for connection object = 1
: SMI AddRef SMI_TRACE(009FEC20) refCount(4)
: SMI AddRef SMI_TRACE(009FEC20) refCount(5)
: SMI AddRef SMI_LISTENER(009FEC68) refCount(3)
: SMI Release SMI_LISTENER(009FEC68) refCount(2)
: SMI AddRef SMI_CONNECTION(009FEA48) refCount(3)
: SMI Release SMI_CONNECTION(009FEA48) refCount(2)
: SMI12 Listener (009FEC68): Open Connection: (009FEA48). numConnections(103),
: SUCCEEDED (00000000)
: WSD04 AddRef: RefCount for connection object = 2
: WSD07 ReadHeader: Proto = 24576, Len = 142
: SMI01 Connection(009FEA48): Create Message: (1BDBCC18), initial size 142
: bytes
: DPB AddRef DPB_SESSION_SERVICE(1BDBC2B0) refCount(2)
: DPB40 SessionId (00000000): Handle Request: CREATE_SESSION(1), streamVer(0).
: SUCCEEDED (00000000)
: DPB20 Connection(009FEA48): ClientConnect : dbadmin(GJOHNSON1)
: userId(dbadmin), connectString(), sessionId(FFFFFFFF). ... (00000000)
: SMI AddRef SMI_LISTENER(009FEC68) refCount(3)
: SMI16 Listener (009FEC68): Create Session: (1BDBC398). SUCCEEDED (00000000)
: DPB41 : Use Session : sessionId(467387288). SUCCEEDED (00000000)
: SMI Release SMI_LISTENER(009FEC68) refCount(2)
: SMI AddRef SMI_CONNECTION(009FEA48) refCount(3)
: DPB AddRef DPB_Connection(009FEB18) refCount(1)
: DPB AddRef DPB_SESSION_SERVICE(1BDBC2B0) refCount(3)
: DPB20 Connection(009FEA48): ClientConnect : dbadmin(GJOHNSON1)
: userId(dbadmin), connectString(), sessionId(1BDBC398). SUCCEEDED
: (00000000)
: SMI01 Connection(009FEA48): Create Message: (1BDBDF50), initial size 0 bytes
: DPB Release DPB_SESSION_SERVICE(1BDBC2B0) refCount(2)
: SMI03 Connection(009FEA48): Send Reply Message: (1BDBDF50)
: sequenceNumber(475246) Asynchronous. ... (00000000)
: SMI06 Connection(009FEA48): Process request Message: (1BDBCC18) serviceId(0),
: sequenceNumber(475246). SUCCEEDED (00000000)
: WSD08 Send: result = 0
: WSD07 ReadHeader: Proto = 24576, Len = 83
: SMI03 Connection(009FEA48): Send Reply Message: (1BDBDF50)
: sequenceNumber(475246) Asynchronous. SUCCEEDED (00000000)
: SMI01 Connection(009FEA48): Create Message: (1BDBDF90), initial size 83 bytes
: DPB55 Memory Session : (1BDBC2B0) count(959), total(352256), alloc(208080),
: free(134536)
: DPB AddRef DPB_SESSION_SERVICE(1BDBC2B0) refCount(3)
: DPB56 Memory Proc Common : count(9112), total(757760), alloc(683877),
: free(59269)
: DPB40 SessionId (1BDBC398): Handle Request: DISCONNECT(2), streamVer(0).
: SUCCEEDED (00000000)
: DPB Release DPB_SESSION_SERVICE(1BDBC2B0) refCount(2)
: DPB AddRef DPB_SESSION_SERVICE(1BDBC2B0) refCount(3)
: DPB21 Connection(1BDBC2B0): ClientDisconnect: userId(dbadmin),
: connectString(), sessionId(1BDBC398). ... (00000000)
: DPB Release DPB_SESSION_SERVICE(1BDBC2B0) refCount(2)
: DPB21 Connection(1BDBC2B0): ClientDisconnect: userId(dbadmin),
: connectString(), sessionId(1BDBC398). SUCCEEDED (00000000)
: SMI06 Connection(009FEA48): Process request Message: (1BDBDF90) serviceId(0),
: sequenceNumber(475248). SUCCEEDED (00042137)
: SMI01 Connection(009FEA48): Create Message: (1BDBE290), initial size 0 bytes
: SMI03 Connection(009FEA48): Send Reply Message: (1BDBE290)
: sequenceNumber(475248) Asynchronous. ... (00000000)
: WSD08 Send: result = 0
: SMI03 Connection(009FEA48): Send Reply Message: (1BDBE290)
: sequenceNumber(475248) Asynchronous. SUCCEEDED (00000000)
: SMI08 Connection(009FEA48): Disconnect: ... (00000000)
: WSD09 SendDisconnect: result = 0
: WSD04 Release: RefCount for connection object = 2
: WSD06 ReadHeader: Received disconnect code = FF
: SMI08 Connection(009FEA48): Disconnect: SUCCEEDED (00000000)
: WSD04 Release: RefCount for connection object = 1
: DPB Release DPB_SESSION_SERVICE(1BDBC2B0) refCount(1)
: SMI Release SMI_CONNECTION(009FEA48) refCount(2)
: SMI Release SMI_CONNECTION(009FEA48) refCount(1)
: SMI Release SMI_TRACE(009FEC20) refCount(4)
: DPB56 Memory Proc Common : count(9108), total(757760), alloc(683825),
: free(59321)
: DPB Release DPB_SESSION_SERVICE(1BDBC2B0) refCount(0)
: DPB Release DPB_Connection(009FEB18) refCount(0)
: SMI Release SMI_CONNECTION(009FEA48) refCount(0)
: SMI Release SMI_TRACE(009FEC20) refCount(3)
: SMI Release SMI_LISTENER(009FEC68) refCount(1)
: SMI Release SMI_TRACE(009FEC20) refCount(2)

Are you guys running 24x7 on a server with Windows 2003? Could this be a Win 2003 configuration issue perhaps. Nothing special was done to our server.

Still had the problem with an empty job schedule. The performance logs did not pick up any unusual activity.

I am sending all logs and files I have collected to support in a zip file.

: Check in the Task Manager the following counters on the Processes tab page:
: Number of Threads
: Numbers of Handles
: Memory Usage

: You may need to customize the view (View/Columns) if not all of these columns
: are visible on the processes tab.

: If the any of these keeps growing with time and never drops back you are
: probably experiencing resource leakage issues. If they just float up and
: down, it is something else. In that case please email to support all .LOG
: files from 24x7 home directory and also all files from the Performance
: Data subdirectory. It is a good idea to zip them into 1 archive all before
: sending.