Click here to Skip to main content
11,574,503 members (56,396 online)
Rate this: bad
good
Please Sign up or sign in to vote.
See more: service
All of a sudden (!) my Windows Service wont start. When I try to start it, it
returns immediately with the error in the subject line. The event data is as follows:

Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: tcptunercollector.exe
P2: 1.0.0.0
P3: 4e3a9d71
P4: System.Configuration
P5: 2.0.0.0
P6: 4a275e0d
P7: 1a6
P8: 15a
P9: IOIBMURHYNRXKW0ZXKYRVFN0BOYYUFOW
P10:
Attached files:
C:\Windows\Temp\WER93D4.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WER93D5.tmp.hdmp
C:\Windows\Temp\WERA7AC.tmp.mdmp
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_tcptunercollecto_2237e423646d0acc8ebaff0aa4bce62dbc1192_cab_88c1a885
Analysis symbol:
Rechecking for solution: 0
Report Id: 9a729c80-bea3-11e0-9d85-005056ba0076
Report Status: 4



At the same time, the Windows System log says that "The service did not respond to the start or control request in a timely fashion". It also says "A timeout was reached (30000 milliseconds) while waiting for the SDV collector to connect".

This is NOT true. It returns immediately, and an event log write in my OnStart method never gets executed.

This is running on Windows Server 2008 R2.

Also, this runs fine on my Windows XP development box.

I have searched for these errors, but most assume that the service is really simply not responding.

This error happens immediately when I try to start the service.

If this wasn't a server, I would try rebooting it, but for now I would rather
try and understand the problem.

Thanks in advance for any suggestions.
Posted 4-Aug-11 5:27am

1 solution

Rate this: bad
good
Please Sign up or sign in to vote.

Solution 1

I cannot help you much on the cause of your failure but can help you with the timeout report.

Whenever a service is in startup and throws an exception, you will always get that error message. Service startup does not care if you failed to respond due to a loop or an exception, it just cares as to whether or not you are completing startup successfully. When you return from your OnStart command the base class returns the code that indicates you started up successfully.

What I usually do is pull up a trace monitor (like from SysTools) and throw in trace.WriteLine commands as I progress thru the code. That helps to tell me where I blew up.

However...looking at what you displayed, the signature for you class is different from what it was when it was registered. Did you make a new version and just copy it onto the server? I believe for my services I always did an uninstall and install to ensure the signature matched what is being put out on the server.
  Permalink  
Comments
mitchmcc at 4-Aug-11 14:19pm
   
Michael, thanks for your help. It did help me figure out the problem. Believe it or not, it appeared that there was some type of invalid character in my .config file, and this was (I believe) causing the service to essentially crash before it really even got started. This meshes with what I saw!

Thanks again, and my advice to everyone is to check your .config file!

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS


Advertise | Privacy | Mobile
Web04 | 2.8.150624.2 | Last Updated 4 Aug 2011
Copyright © CodeProject, 1999-2015
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100