Empty status report when running as service

Hi. I have the status report turned on and pointing to a directory on C drive.

When 24x7 is running in GUI mode the reports are created correctly.

When it's running as a Windows service, the daily report (28-August-2007.htm) only includes the title and column headings--no job data at all (either from before or after switching to a service).

The jobs being run from the service are still appearing OK in scheduler.log

If I switch back to GUI mode the data re-appears.

Thoughts?

Windows 2000, 24x7 Scheduler multi-platform edition 4.1, service is running as me.

Please turn on the trace option in the Tools/Options menu; Log page. Let the service run and process at least 1 job. Check for any exceptions recorded in the debug.log file. Please let us know what you find in that file.

I can't see anything obvious...

Code:

2007-08-28 16:57:58,797 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - main(...) : start
2007-08-28 16:57:58,797 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : start
2007-08-28 16:57:58,797 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : creating business objects
2007-08-28 16:57:59,063 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : creating UI controller
2007-08-28 16:57:59,157 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : initializing business objects
2007-08-28 16:57:59,172 [main] DEBUG com.softtreetech.jscheduler.business.preferences.AbstractPrefDatabase - Creating backup for preferences file preferences.xml
2007-08-28 16:57:59,204 [main] DEBUG com.softtreetech.jscheduler.business.preferences.AbstractPrefDatabase - Preferences file has been copied to preferences.bak
2007-08-28 16:57:59,875 [main] DEBUG com.softtreetech.jscheduler.business.jobtemplates.JobTemplateSetImpl - loadDescription: path: Template/test_template.ini
2007-08-28 16:58:00,203 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : loading job db
2007-08-28 16:58:00,235 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - buildIndex(): totalRecordsNumber: 207
2007-08-28 16:58:00,235 [main] DEBUG com.softtreetech.jscheduler.db.drivers.file.FileJobDbStorage - buildIndex(): deletedRecordsNumber: 110
2007-08-28 16:58:00,516 [main] DEBUG com.softtreetech.jscheduler.JSchedulerStarter - startup() : ready to run jobs
2007-08-28 16:59:00,043 [Timer-0] DEBUG com.softtreetech.jscheduler.business.queue.JobQueue - QUEUE_UNLOCKED
2007-08-28 16:59:00,355 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - runJob(): start
2007-08-28 16:59:00,355 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - execProcess(): command line [sasbatch.bat C:\DOCUME~1\ALLUSE~1\DOCUME~1\SHARED~1\Management\sasprogs\24x7_Status_Report.sas /a] in work directory [null]
2007-08-28 16:59:00,355 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - waitForProcess(): start
2007-08-28 16:59:00,355 [Thread-10] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner$TimeoutVerifier - run(): start
2007-08-28 16:59:00,355 [Thread-10] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner$TimeoutVerifier - run(): end due to zero timeout
2007-08-28 16:59:01,886 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - waitForProcess(): end
2007-08-28 16:59:01,886 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner - isFailed(...) : exit code 0
2007-08-28 16:59:01,886 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - killProcess start
2007-08-28 16:59:01,886 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - runJob(): end
2007-08-28 16:59:02,121 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.queue.JobQueue - QUEUE_UNLOCKED
2007-08-28 17:00:00,022 [Timer-3] DEBUG com.softtreetech.jscheduler.business.queue.JobQueue - QUEUE_UNLOCKED
2007-08-28 17:00:00,257 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - runJob(): start
2007-08-28 17:00:00,257 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - execProcess(): command line [webupdate.bat hsweb] in work directory [null]
2007-08-28 17:00:00,257 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - waitForProcess(): start
2007-08-28 17:00:00,257 [Thread-92] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner$TimeoutVerifier - run(): start
2007-08-28 17:00:00,257 [Thread-92] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner$TimeoutVerifier - run(): end due to zero timeout
2007-08-28 17:10:07,570 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - waitForProcess(): end
2007-08-28 17:10:07,570 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner - isFailed(...) : exit code 0
2007-08-28 17:10:07,570 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - killProcess start
2007-08-28 17:10:07,570 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - runJob(): end
2007-08-28 17:10:07,804 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.queue.JobQueue - QUEUE_UNLOCKED
2007-08-28 17:59:00,016 [Timer-122] DEBUG com.softtreetech.jscheduler.business.queue.JobQueue - QUEUE_UNLOCKED
2007-08-28 17:59:00,251 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - runJob(): start
2007-08-28 17:59:00,251 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - execProcess(): command line [sasbatch.bat C:\DOCUME~1\ALLUSE~1\DOCUME~1\SHARED~1\Management\sasprogs\24x7_Status_Report.sas /a] in work directory [null]
2007-08-28 17:59:00,251 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - waitForProcess(): start
2007-08-28 17:59:00,251 [Thread-4698] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner$TimeoutVerifier - run(): start
2007-08-28 17:59:00,251 [Thread-4698] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner$TimeoutVerifier - run(): end due to zero timeout
2007-08-28 17:59:01,672 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - waitForProcess(): end
2007-08-28 17:59:01,672 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner - isFailed(...) : exit code 0
2007-08-28 17:59:01,672 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - killProcess start
2007-08-28 17:59:01,672 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - runJob(): end
2007-08-28 17:59:01,954 [Job #36 - 24x7_Status_Report] DEBUG com.softtreetech.jscheduler.business.queue.JobQueue - QUEUE_UNLOCKED
2007-08-28 18:00:00,027 [Timer-125] DEBUG com.softtreetech.jscheduler.business.queue.JobQueue - QUEUE_UNLOCKED
2007-08-28 18:00:00,262 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - runJob(): start
2007-08-28 18:00:00,262 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - execProcess(): command line [webupdate.bat hsweb] in work directory [null]
2007-08-28 18:00:00,262 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - waitForProcess(): start
2007-08-28 18:00:00,262 [Thread-4780] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner$TimeoutVerifier - run(): start
2007-08-28 18:00:00,262 [Thread-4780] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner$TimeoutVerifier - run(): end due to zero timeout
2007-08-28 18:10:41,040 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - waitForProcess(): end
2007-08-28 18:10:41,040 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.AbstractJobRunner - isFailed(...) : exit code 0
2007-08-28 18:10:41,040 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - killProcess start
2007-08-28 18:10:41,040 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.runner.ProgramJobRunner - runJob(): end
2007-08-28 18:10:41,275 [Job #35 - sitecopy hsweb] DEBUG com.softtreetech.jscheduler.business.queue.JobQueue - QUEUE_UNLOCKED

Here's the scheduler.log from the same period (you can see where I switched from GUI to service):

Code:

28-Aug-2007 04:57:55 PM 2 null null 24x7 Scheduler 24x7 Scheduler terminating...
28-Aug-2007 04:57:59 PM 2 null null 24x7 Scheduler 24x7 Scheduler starting...
28-Aug-2007 04:59:00 PM 2 x/y 36 24x7_Status_Report Job started.
28-Aug-2007 04:59:01 PM 2 x/y 36 24x7_Status_Report Job finished.
28-Aug-2007 05:00:00 PM 2 x/y 35 sitecopy hsweb Job started.
28-Aug-2007 05:10:07 PM 2 x/y 35 sitecopy hsweb Job finished.
28-Aug-2007 05:59:00 PM 2 x/y 36 24x7_Status_Report Job started.
28-Aug-2007 05:59:01 PM 2 x/y 36 24x7_Status_Report Job finished.
28-Aug-2007 06:00:00 PM 2 x/y 35 sitecopy hsweb Job started.
28-Aug-2007 06:10:41 PM 2 x/y 35 sitecopy hsweb Job finished.

(I've taken out the encoded text)

I don't see any exceptions recorded in the trace and don't have any explanation for this effect. Please email support for further investigation of this issue. Please attach your schedule.log so we can try to reproduce this issue in our lab.

I ran a search in the support database for HTML status report related issues and the only case I found was for reports not generated on AIX systems.

Did you get a case number for this issue "status reports in service mode" which I can track for the current status?

I found this issue in the support queue. For your referenced, Issue #000347. It is getting close to the top and will be reviewed/fixed relatively soon.