I found additional information in the EventLog pointing to MS OleDb Provider
for ODBC.
We use
Windows 2003 Server SP1
MS OleDb Provider for ODBC
MS ODBC Driver for Oracle
Oralce 9.2.0.1
XA Transactions
The problem occurs under stress testing.
Event Type: Information
Event Source: Application Error
Event Category: (100)
Event ID: 1004
Date: 23.12.2005
Time: 18:10:21
User: N/A
Computer: PONTIUS
Description:
Reporting queued error: faulting application dllhost.exe, version
5.2.3790.0, faulting module msdasql.dll, version 2.82.1830.0, fault address
0x0003a356.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 64 6c 6c ure dll
0018: 68 6f 73 74 2e 65 78 65 host.exe
0020: 20 35 2e 32 2e 33 37 39 5.2.379
0028: 30 2e 30 20 69 6e 20 6d 0.0 in m
0030: 73 64 61 73 71 6c 2e 64 sdasql.d
0038: 6c 6c 20 32 2e 38 32 2e ll 2.82.
0040: 31 38 33 30 2e 30 20 61 1830.0 a
0048: 74 20 6f 66 66 73 65 74 t offset
0050: 20 30 30 30 33 61 33 35 0003a35
0058: 36 6
Peter Meinl - 23 Jan 2006 10:15 GMT
Shalen,
I did not get much useful feedback too.
I our case it seems to happen under heavy load only.
To prevent trace information written to a database trace table from being
rolled back with application data we had marked our trace class with
"requires new transaction". I changed this to "Not supported" which
massively reduces the number of transactions. This seems to have solved our
problem.
BTW: "COM Surrogate" refers to the DLLHost process.
>I found additional information in the EventLog pointing to MS OleDb
>Provider
[quoted text clipped - 38 lines]
> 0050: 20 30 30 30 33 61 33 35 0003a35
> 0058: 36 6