Re: Custom Service Terminates Unexpectedly
- From: "Dave Patrick" <DSPatrick@xxxxxxxxxxxxxxxx>
- Date: Thu, 26 Mar 2009 21:00:18 -0600
If the service can't handle any abnormal conditions (eg exceptions) then it may be impossible to know.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
"JMZ" wrote:
A custom .Net service terminated unexpectedly with an entry in the System
Event log under Service Control Manager, error 7034. There were no other
entries in any event log. It appears from the files it was processing at the
time that all the threads it started were terminated immediately. The service
itself was not able to handle any exceptions, and I know that when it did
terminate, it was right in the middle of an XSLT transform call. The file was
created, but it was empty. The XSLT is good. We have used it without any
problems for years. When I reprocessed the original file, it processed fine.
It appears that some external event caused the service to terminate in this
way, but the only thing we can do is wait for it to do the same thing again,
alert us when it does, and run sc query against the service. Although, I
don't think it's guaranteed to retrieve the cause of the termination. I have
a utility that will log the sc query result to a log file if it happens again.
What else can we look at to find the cause of this? When this happens, the
files are left in an inconsistent state, which also have to be reprocessed.
Thank you in advance.
.
- Follow-Ups:
- References:
- Custom Service Terminates Unexpectedly
- From: JMZ
- Custom Service Terminates Unexpectedly
- Prev by Date: Re: Multiple rundll32.exe appearing under processes
- Next by Date: Re: can I use schtasks on 2003 sever to run a task on a 2008 server
- Previous by thread: Custom Service Terminates Unexpectedly
- Next by thread: Re: Custom Service Terminates Unexpectedly
- Index(es):
Relevant Pages
|
