windows service terminated unexpectedly

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a .NET windows service written in C# that runs fine on my XP Pro dev
box with a P4 and hyperthreading. But when I run it on a Windows Server 2003
box, I get an "unexpected termination" with the following sc query:

C:\>sc query slabserver

SERVICE_NAME: slabserver
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
(NOT_STOPPABLE, NOT_PAUSABLE,
IGNORES_SHUTDOWN))

WIN32_EXIT_CODE : 1067 (0x42b)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

I have everything I can think of wrapped in in try..catch sections with
exception logging. No exceptions are logged. The service is just shut down.

Any ideas?

Thanks,

-Tyler
 
What did you use to define the account that is used to login to the
system?

I was having the same problem some time back and it was fixed by adding
this line to my project installer class:

processInstaller.Account = ServiceAccount.LocalSystem;


Full class:

[RunInstallerAttribute(true)]
public class ProjectInstaller : Installer
{
private ServiceInstaller serviceInstaller;
private ServiceProcessInstaller processInstaller;

public ProjectInstaller()
{
serviceInstaller = new ServiceInstaller();
serviceInstaller.StartType = ServiceStartMode.Automatic;
serviceInstaller.ServiceName = "ServiceName";
serviceInstaller.DisplayName = "ServiceDisplayName";


processInstaller = new ServiceProcessInstaller();
processInstaller.Account = ServiceAccount.LocalSystem;

Installers.Add(serviceInstaller);
Installers.Add(processInstaller);
}
}

Not sure if that will help, but just incase it's not something you have
done yet.
 
Thanks, Jose. I've tried different user contexts, including local system. I
may have found the issue. A susequent crash left an event trail with "The
exception generated was 80000003 at address 0000000078EF3320
(ntdll!DbgBreakPoint)" which upon further research seems to be a flaw in the
ntdll.dll. I'm not making a call to it directly, but perhaps a component I'm
using is or perhaps the runtime is.

Not sure.
 
Hi Tyler,

Based on my understanding, there is no error logged in the Event Log in
Application,Security and System.
If I misunderstood, please feel free to post here.
Because this error is a very general one "The process terminated
unexpectedly.", it is hard to track the issue so far.
Also I think you may try to isolate the problem by comment out your code
block one by one until there is not error.
So that we can narrow down the issue.

Best regards,

Peter Huang

Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Thanks, Peter.

Sorry I wasn't clear before. There was an entry in the Event Log (at least
on one of the meltdowns):

Event Type: Information
Event Source: DrWatson
Event Category: None
Event ID: 4097
Date: 4/8/2006
Time: 9:07:23 AM
User: N/A
Computer: PLDEV
Description:
The application, c:\searchlab\slabserver\slab.server.exe, generated an
application error The error occurred on 04/08/2006 @ 09:07:22.732 The
exception generated was 80000003 at address 0000000078EF3320
(ntdll!DbgBreakPoint)

I have now split my service into three services where the most likely
culprit rests in one, the second most likely in another, and the most stable
in the third and I'm using IPC remoting channel to communicate between the
two.

I'll report back here with the result.

Thanks,
 
Hi Tyler,

Thanks for your information.
If the isolated process did not work for you.
It seems that there was a crash on your machine which can not be catch.
For dump anaylysis, I think you may try to contact MSPSS directly.
http://support.microsoft.com

Thanks for your understanding!

Best regards,

Peter Huang

Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top