Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / C# / August 2006

Tip: Looking for answers? Try searching our database.

Windows Service won't start when referenced assemblies are in the GAC

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
loretta.stokes@gmail.com - 10 Aug 2006 22:30 GMT
I was wondering if anyone else has experienced this problem. On certain
machines we get the standard error when starting the service manually
(or on reboot):

"Error 1503: The service did not respond to the start or control
request in a timely fashion"
and
"Timeout(3000 milliseconds) waiting for the <MyServiceName> to connect"

I added code to the constructor of the service to write a message to
the event log and it was not getting called. So no hidden message boxes
or errors. I changed the service to log on as the admin account instead
of local system and that did not work. The only thing that would work
was to rebuild the service and the referenced assemblies without strong
naming them. The service references 3 assemblies, all of which are
installed to the GAC. I re-versioned the assebles and removed the
strong naming. It works, but why? We have tested this on several
machines without any issues.The machine in which the error occurs is
fast enough. I has more that 1 GB of ram and 3Ghz processor.Also, I am
not sure what actually causes this scenario.I would appreciate any help
or suggestions.
Vadym Stetsyak - 11 Aug 2006 08:13 GMT
Hello, loretta.stokes@gmail.com!

You can use fuslogvw tool for further investigation of
binding issue with strong named assemblies.

Generally windows services based on ServiceBase write exceptions
to the event log, or if you're on .NET 2.0 - CLR will add exception desc to
event log.

--
Regards, Vadym Stetsyak
www: http://vadmyst.blogspot.com
loretta.stokes@gmail.com - 21 Aug 2006 14:59 GMT
It was written in VS 2003 so .NET 1.1. The only error that I get in the
event log is the timeout error that I mentioned. "Timeout (3000
milliseconds) waiting for the <ServiceName> to connect. I will try the
tool that you mentioned. Thanks for the recommendation. What doesn't
make sense is that we have regular windows apps that reference the same
assemblies and they start without any errors.

> Hello, loretta.stokes@gmail.com!
>
[quoted text clipped - 8 lines]
> Regards, Vadym Stetsyak
> www: http://vadmyst.blogspot.com

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.