Windows service timeout

[Cubaman]

Hello everybody. I'm currently developing a windows service. In OnStart
a launch two threads that carry on some work while the service is
running. My problem comes from the fact that once the service is
installed, it just time out at system startup and don't start. But i'm
able to start it manually once i'm logged in. I read in a page
something about signed assemblyes, saying that clr have to verify the
executable at startup, causing the delay. I just unsigned the assembly
and still face the same problem. I also notice that some compilation of
the solution start at system starup, and othes does not, with out
aparent reason, because there is no code change. Any sugestion? Thanks
in advance.

[Peter Bromberg [C# MVP]]

Cubaman,
You don't show any sample code for what is happening in the OnStart method.
OnStart basically gives you a 30 second SCM Timeout.
So if you are kicking off 2 threads, they should be background threads and
the Start methods must return within the startup timeout period.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Cubaman" wrote:

Hello everybody. I'm currently developing a windows service. In OnStart
a launch two threads that carry on some work while the service is
running. My problem comes from the fact that once the service is
installed, it just time out at system startup and don't start. But i'm
able to start it manually once i'm logged in. I read in a page
something about signed assemblyes, saying that clr have to verify the
executable at startup, causing the delay. I just unsigned the assembly
and still face the same problem. I also notice that some compilation of
the solution start at system starup, and othes does not, with out
aparent reason, because there is no code change. Any sugestion? Thanks
in advance.

[Cubaman]

Hello Peter, and thanks for your answer. Here is the code i'm executing
in OnStart method:

/// <summary>
/// Method launched on service start.
/// </summary>
/// <param name="args">non e</param>
protected override void OnStart(string[] args) {
ThreadPool.Queu eUserWorkItem(n ew WaitCallback(Jo bWs),
null);
ThreadPool.Queu eUserWorkItem(n ew
WaitCallback(Jo bManteinance), null);
//// Write info to eventlog, so controler detects the
service start.
eventLog.WriteE ntry("Service started",
EventLogEntryTy pe.Information) ;
}

JobWs and JobManteinance are two functions that do all the work.
What do you mean by background thread? A thread with a low priority?
Thank you, best regards.

Oscar Acosta
Peter wrote:

Cubaman,
You don't show any sample code for what is happening in the OnStart method.
OnStart basically gives you a 30 second SCM Timeout.
So if you are kicking off 2 threads, they should be background threads and
the Start methods must return within the startup timeout period.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Cubaman" wrote:

Hello everybody. I'm currently developing a windows service. In OnStart
a launch two threads that carry on some work while the service is
running. My problem comes from the fact that once the service is
installed, it just time out at system startup and don't start. But i'm
able to start it manually once i'm logged in. I read in a page
something about signed assemblyes, saying that clr have to verify the
executable at startup, causing the delay. I just unsigned the assembly
and still face the same problem. I also notice that some compilation of
the solution start at system starup, and othes does not, with out
aparent reason, because there is no code change. Any sugestion? Thanks
in advance.