Version 1.33 Reports Aren't Running (and service "stopped")

[Brent Pirolli]

I have upgraded from 1.24 or something old to 1.33. I followed all of the update instructions and the program seems to work great other than one fatal flaw... the daily reports are set to run at 6am and they don't run at all! If I go in and manually run a set of "all" reports, they come through fine.

Upon further analysis, I've looked at the "service" button to find it says the service is installed but stopped. If I open the serivces.msc I can see the ESAT service is installed but is STARTED!

I can click stop in services.msc and it stops, and I go to ESAT and click uninstall and it disappears from the services.msc. I can then click "install" and it installs into the services.msc in a STARTED state.... but again ESAT shows it as stopped. Clicking "Start" does nothing in the ESAT program if the service is already started in services.msc (ESAT's readout sits at "stopped"). If the service is stopped in services.msc and I click start in ESAT, the service moves to a started state in services.msc but remains in the "stopped" state in ESAT.

I'd have to imagine these two behaviors (no reports and service oddities) are related. Something like it thinks the service is stopped so it won't run the reports at the 6am setting...

Thoughts on how to fix this or troubleshoot it further??? Any help is greatly appreciated.

Windows Server 2003 Standard
Exchange 2003

[Peter Banz]

It's important that the service is stopped and uninstalled before upgrading. If you forgot that, I recommend to redo the entire update process.

Also if there is a problem with the ESAT scheduler service make sure the agent service is a login service. Specially with the newer OS's and service packs. Also if nothing else you can use the MS scheduler. The instructions and examples are in the manual.