.NET Runtime 2.0 error on service
We have a custom service that writes to the DB (SQL 2005). It is a complete 64-bit environment (DB Service, .NET). We run one of our servers every morning when we have a spike in our data volume. We work fine on the other server. The only differences I could notice between the two machines is that one of them crashed and had .NET 3.5 installed.
Has anyone else seen this type of behavior?
Here is the event log entry from today's crash:
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event
ID : 1000 Date: 6/11/2008
Time: 09:35:03
User: N / A
Computer: RDDARWIN02
Description:
Servicehost application malfunction. exe, version 2.0.6.6, stamp 48eb7b7a, error module kernel32.dll, version 5.2.3790.4062, brand 462643a7, debug? 0, error address 0x0000000000027d8d.
For more information, see the Help and Support Center at http://go.microsoft.com/fwlink /events.asp.
Data:
0000: 41 00 70 00 70 00 6c 00 Appl
0008: 69 00 63 00 61 00 74 00 icat
0010: 69 00 6f 00 6e 00 20 00 io.
0018: 46 00 61 00 69 00 6c 00 Fail
0020: 75 00 72 00 65 00 20 00 ure.
0028: 20 00 73 00 65 00 72 00.sr
0030: 76 00 69 00 63 00 65 00 vice
0038: 68 00 6f 00 73 00 74 00 host
0040: 2e 00 65 00 78 00 65 00..exe
0048: 20 00 32 00 2e 00 30 00.2 ... 0.
0050: 2e 00 36 00 2e 00 36 00..6 ... 6.
0058: 20 00 34 00 38 00 65 00.4.8.e.
0060: 62 00 37 00 62 00 37 00 b.7.b.7.
0068: 61 00 20 00 69 00 6e 00 a..in
0070: 20 00 6b 00 65 00 72 00.ker
0078: 6e 00 65 00 6c 00 33 00 nel3.
0080: 32 00 2e 00 64 00 6c 00 2 ... dl
0088: 6c 00 20 00 35 00 2e 00 l. 0.5 ...
0090: 32 00 2e 00 33 00 37 00 2 ... 3.7.
0098: 39 00 30 00 2e 00 34 00 9.0 ... 4.
00a0: 30 00 36 00 32 00 20 00 0.6.2 ..
00a8: 34 00 36 00 32 00 36 00 4.6.2.6.
00b0: 34 00 33 00 61 00 37 00 4.3.a.7.
00b8: 20 00 66 00 44 00 65 00.fDe
00c0: 62 00 75 00 67 00 20 00 bug.
00c8: 30 00 20 00 61 00 74 00 0..at
00d0: 20 00 6f 00 66 00 66 00.off
00d8: 73 00 65 00 74 00 20 00 set.
00e0: 30 00 30 00 30 00 30 00 0.0.0.0.
00e8: 30 00 30 00 30 00 30 00 0.0.0.0.
00f0: 30 00 30 00 30 00 32 00 0.0.0.2.
00f8: 37 00 64 00 38 00 64 00 7.d.8.d.
0100: 0d 00 0a 00 ....
source to share
Have you tried a debugger attaché to run your code before crashing? Maybe you can track where the problem is.
You can also use adplus to get a process dump and then use that dump in windbg to help pinpoint the problem. Something like this should give you the dump file you are looking for:
adplus -crash -pn servicehost.exe
source to share