Darren Larner wrote on 2010-09-17: > > Hi Guys > > I have written an application that will process varying tasks at > scheduled times. The application runs fine as a standalone application. > I want this to run as a Windows Service on the fileserver so that the > program is always running 24/7. I can add my application as a service > using srvany as per Calvin Hsia's weblog. The application runs fine as > a service and processes my tasks as I expect. The problem is when the > application crashed or a problem is encounter, the error handler in my > application is not fired. The application just stops working (although > still running as service) and there is not indication as to what the > error is that has been encountered. How I would like it to work is > that an error log is produced by my error handler. Then the > application shutsdown (using my ON SHUTDOWN methid) and then the > service can be resumed. Is this feasible and if so how do I go about > this as I cannot figure out how to do this. > > Any help would be much appreciated. > > Thanks > Darren > >
Darren, Are you using SYS(2335)? And read up on SYS(2334) while you're there. These may help prevent unexpected hangs. Tracy Pearson PowerChurch Software _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/000101cb58fe$4601c650$d20552...@com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
