The best place to start troubleshooting this issue is to read through the job log that check what happened before it freezes. In particular look for runaway job(s) that start before that. If you don't have access to the graphical interface use any text editor even notepad.exe to read schedule.log file. Also check in the Windows Event Viewer for all messages reported in Application Event log around that time. Please let us know what you find there. : Hello, : We are having a weird situation - and I'm sorry that : I have very little information to go on, but this is : all we have at the moment. : At some point in time, something happens to the 24x7 : service and it stops executing jobs that have been : scheduled - but the process remains active and the : the service remains registered as runnning and active. : In order for 24x7 to function properly again the : the service must be stopped and restarted. : I've included a link to a screenshot of the error in : the Event Viewer. : Again, I appreciate this is pretty flimsy, but what : I hope for is that this is something that you've : seen before and can immediately carve out a solution : rather than assuming this is enough to puzzle it out : right off. Additionally I am twice removed from the : actual problem site so for me to collect any more : information I'd have to ask someone to ask someone : else. : Cheers : TJ
|