Has anybody experienced problems with corrupted database files? We recently had an incident where the scheduler stopped running jobs. We have 24x7 running as an NT service. We stopped the service and then started 24x7 and stepped through running each job manually. We came to a specific job that, when we attempted to run, caused 24x7 to exit abnormally upon exit. We restored the job database from a 2-day old backup and the jobs started running normally again. This has happened several times, approximately twice per week.

Just thought I'd add as a followup, we are receiving an "Overlapped I/O Process" message when we stop the 24x7 service. This occurs even when active jobs are not running.

: Has anybody experienced problems with corrupted database files? We recently
: had an incident where the scheduler stopped running jobs. We have 24x7
: running as an NT service. We stopped the service and then started 24x7 and
: stepped through running each job manually. We came to a specific job that,
: when we attempted to run, caused 24x7 to exit abnormally upon exit. We
: restored the job database from a 2-day old backup and the jobs started
: running normally again. This has happened several times, approximately
: twice per week.

Please upgrade. This warning doesn't appear in the recent 24x7 versions.

Here is the brief description of the issue:

24x7 Service consists of two processes: the service control and the job engine. When you stop the service the service control process stops the job engine. Windows NT doesn't care about it, but 2000 and XP detect this processing and display "Overlapped I/O Process" warning. Ignore this warning as not important.

: Just thought I'd add as a followup, we are receiving an "Overlapped I/O
: Process" message when we stop the 24x7 service. This occurs even when
: active jobs are not running.

Which 24x7 version are you running?
Any changes done in that job and the way it was done?
Do you use other programs that create or modify jobs in 24x7 programmatically?

: Has anybody experienced problems with corrupted database files? We recently
: had an incident where the scheduler stopped running jobs. We have 24x7
: running as an NT service. We stopped the service and then started 24x7 and
: stepped through running each job manually. We came to a specific job that,
: when we attempted to run, caused 24x7 to exit abnormally upon exit. We
: restored the job database from a 2-day old backup and the jobs started
: running normally again. This has happened several times, approximately
: twice per week.