Re: Problem in running .Net Service on a Quad Processor

Thanks Willy,
But what baffles me is that on my machine it does not give this timeout
This is my system configuration:
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
OS Manufacturer Microsoft Corporation
System Name USER_XP
System Manufacturer Dell Inc.
System Model OptiPlex GX620
System Type X86-based PC
Processor x86 Family 15 Model 6 Stepping 4 GenuineIntel ~3391 Mhz
Processor x86 Family 15 Model 6 Stepping 4 GenuineIntel ~3391 Mhz
BIOS Version/Date Dell Inc. A07, 31/03/2006
SMBIOS Version 2.3
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.2180
(xpsp_sp2_rtm.040803-2158)"
Total Physical Memory 2,048.00 MB
Available Physical Memory 1.52 GB
Total Virtual Memory 2.00 GB
Available Virtual Memory 1.96 GB
Page File Space 3.85 GB
Page File C:\pagefile.sys

Is this something got to also do with OS? In fact shouldn't my service
be faster on a QuadProc machine?
Also when I compiled the service and debugmode it ran on the
QuadProcessor machine without any errors.
I need to answer these questions before I advice my peers any changes.
Please help.

Thanks a lot.

Many regards
Sunil

Willy Denoyette [MVP] wrote:
<sunil@xxxxxxxxxxxxxxx> wrote in message
news:1168338382.130590.151880@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dear All,
I have created a .Net service in 2.0 and running it on a machine that
has a Quad Processor.
It is failing with the following error.
"Error 1053: The service did not respond to the start or control
request in a timely fashion"
This is what I saw in event Viewer.
Timeout (30000 milliseconds) waiting for the MyService Server service
to connect.

This is because your OnStart method did not return in a timely fashion, once the Onstart is
called the SCM waits for a maximum of 30 seconds for it to return, if OnStart doesn't return
within this 30 secs., then the SCM considers the service has failed to start, logs a message
and kill the service.
So, you have to investigate your OnStart and try to find out why it takes longer than 30
seconds to return.

Willy.

.

Relevant Pages

  • Re: Problem in running .Net Service on a Quad Processor
    ... It is failing with the following error. ... This is because your OnStart method did not return in a timely fashion, once the Onstart is called the SCM waits for a maximum of 30 seconds for it to return, if OnStart doesn't return within this 30 secs., then the SCM considers the service has failed to start, logs a message and kill the service. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: .NET Windows Service OnStart hangs on Process.ProcessName
    ... don't run this in OnStart. ... service variables and kick-off a service thread to run the real service ... // This line will hang long enough to prevent ... | the service from starting for timeout reason. ...
    (microsoft.public.dotnet.framework)
  • Re: Probleme mit Windows Dienst
    ... im OnStart-Ereignis einen Timer starten zu ... aber dann bekam ich immer ein Timeout beim Starten des Dienstes. ... Ein Timeout beim Starten bekommst du nur dann, wenn der Code im OnStart zu ...
    (microsoft.public.de.german.entwickler.dotnet.vb)
  • Re: C# Service Terminating Itself
    ... > In SDK terms, ... > RegisterServiceCtrlHandlerEx() to register a callback for communication ... > with the SCM. ... When OnStart returns normally, "StartSuccessful" is written to the EventLog, ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Problem in running .Net Service on a Quad Processor
    ... stringargs) ... typeof(ServiceRuntime).Assembly.GetName.FullName, ... It looks like you don't run this "Start" in another thread, that means that OnStart only returns to the SCM when Start returns. ... Now, if you DB activity takes more than 30 seconds, the SCM will get nervous and kill the "OnStart" thread and bail out. ...
    (microsoft.public.dotnet.languages.csharp)
Loading