Windows Service did not start in a timely fashion...

[=?Utf-8?B?Sm9obiBTLg==?=]

I developed a Windows Service application written in vb.net and have
successfully installed it on many workstations (over 25 PCs). All
workstations have Windows XP SP2 installed. There are two workstations
located at separate customers that have an issue during installation. I
receive the error “The service did not respond to the start or control
request in a timely fashion.� The service properties Log On is set to use
the Local System account, could there be an issue with some permissions
rights here?

[Tom Shelton]

On Jun 11, 4:57 pm, John S. <John [e-mail]>
wrote:

I developed a Windows Service application written in vb.net and have
successfully installed it on many workstations (over 25 PCs). All
workstations have Windows XP SP2 installed. There are two workstations
located at separate customers that have an issue during installation. I
receive the error "The service did not respond to the start or control
request in a timely fashion." The service properties Log On is set to use
the Local System account, could there be an issue with some permissions
rights here?

Without seeing the code - my guess is that you are doing to much in
the OnStart method. I would limit this method to simply starting a
thread on which you actually do your login and your service work. The
problem is that if your onstart method takes to long to complete,
windows will kill it.

--
Tom Shelton

[Mr. Arnold]

"John S." <John [e-mail] in message
news:4E**********************************@microsof t.com...

>I developed a Windows Service application written in vb.net and have
successfully installed it on many workstations (over 25 PCs). All
workstations have Windows XP SP2 installed. There are two workstations
located at separate customers that have an issue during installation. I
receive the error “The service did not respond to the start or control
request in a timely fashion.� The service properties Log On is set to use
the Local System account, could there be an issue with some permissions
rights here?

The only time I have seen that happen, and I have forced it to happen as
well during the start-up of a .NET Service application, is an exception is
being thrown, which is causing the Start-up to time out.

You should review your code on the Onstart event to see what is happening.
One way I have done things to pin point it is dump messages into the event
log to see where the program was at when it went down on the start-up.

Another way I have done it to see where it was at in the Service program was
using the NET Send command sending messages locally to the machine, nothing
like those pop-up NET Send (OK Message boxes) to track things down.