faulting module msdasql.dll Error, COM+ XA transactions

We get the below errors in VB6 COM+ Components when stress testing.

We use
Windows 2003 Server SP1
MS OleDb Provider for ODBC
MS ODBC Driver for Oracle
Oralce 9.2.0.1
XA Transactions

Error 1
--------

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 23.12.2005
Time: 16:57:09
User: N/A
Computer: PONTIUS
Description:
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

Error 2
---------

Event Type: Error
Event Source: COM+
Event Category: Unknown
Event ID: 4786
Date: 23.12.2005
Time: 16:57:09
User: N/A
Computer: PONTIUS
Description:
The system has called a custom component and that component has failed and
generated an exception. This indicates a problem with the custom component.
Notify the developer of this component that a failure has occurred and
provide them with the information below.
Component Prog ID:
Server Application ID: {828CF9EB-6234-41F5-BB2E-64F9E6AB4987}
Server Application Instance ID:
{71F7448D-1684-4703-A64A-A644FBF5C2A2}
Server Application Name: Medam
The serious nature of this error has caused the process to terminate.
Exception: C0000005
Address: 0x4BFEA356
Call Stack:
msdasql!DllRegisterServer + 0x1a80f
msdasql!DllMain + 0x8b96
msdasql!DllGetClassObject + 0xdd3
msdasql!DllGetClassObject + 0x3a7
msado15! + 0x2a37
msado15!DllGetClassObject + 0x4c23
msado15! + 0x2a1d
MedamTracerMTS!DllCanUnloadNow + 0x2005
RPCRT4!NdrServerInitialize + 0x462
RPCRT4!NdrStubCall2 + 0x217
RPCRT4!NdrCStdStubBuffer2_Release + 0xd4
OLEAUT32!VariantTimeToDosDateTime + 0x1827
ole32!WdtpInterfacePointer_UserMarshal + 0x13fa
ole32!CoQueryAuthenticationServices + 0x473a
RPCRT4!NdrProxySendReceive + 0x40
RPCRT4!NdrProxyInitialize + 0xb0
RPCRT4!I_RpcProxyNewConnection + 0x128c9
RPCRT4!NdrUserMarshalFree + 0xa1
MedamBusiness!DllCanUnloadNow + 0x8897d
MedamBusiness!DllCanUnloadNow + 0x7d0f7
RPCRT4!NdrServerInitialize + 0x462
RPCRT4!NdrStubCall2 + 0x217
RPCRT4!NdrCStdStubBuffer2_Release + 0xd4
OLEAUT32!VariantTimeToDosDateTime + 0x1827
ole32!WdtpInterfacePointer_UserMarshal + 0x13fa
ole32!CoQueryAuthenticationServices + 0x473a
RPCRT4!NdrProxySendReceive + 0x40
RPCRT4!NdrProxyInitialize + 0xb0
RPCRT4!I_RpcProxyNewConnection + 0x128c9
RPCRT4!NdrUserMarshalFree + 0xa1
MedamBusiness!DllCanUnloadNow + 0x69704
MedamBusiness!DllCanUnloadNow + 0x68a4b
RPCRT4!NdrServerInitialize + 0x462
RPCRT4!NdrStubCall2 + 0x217
RPCRT4!NdrCStdStubBuffer2_Release + 0xd4
OLEAUT32!VariantTimeToDosDateTime + 0x1827
ole32!WdtpInterfacePointer_UserMarshal + 0x13fa
ole32!WdtpInterfacePointer_UserMarshal + 0x13ad
ole32!ProgIDFromCLSID + 0x1fcf
ole32!ProgIDFromCLSID + 0x1dcd
ole32!DcomChannelSetHResult + 0x85d
ole32!WdtpInterfacePointer_UserMarshal + 0x12db
ole32!WdtpInterfacePointer_UserMarshal + 0x116c
ole32!WdtpInterfacePointer_UserMarshal + 0x15ec
ole32!DcomChannelSetHResult + 0x7d6
ole32!DcomChannelSetHResult + 0x5fa
USER32!EnableMenuItem + 0x4cd4
USER32!EnableMenuItem + 0x4da1
USER32!GetWindowLongW + 0x183
USER32!DispatchMessageW + 0xf
COMSVCS!CoCreateActivity + 0x572b
COMSVCS!CoCreateActivity + 0x562f
COMSVCS!CoCreateActivity + 0x5fc8
COMSVCS!CoCreateActivity + 0x6414
msvcrt!_endthreadex + 0xa3
kernel32!GetModuleFileNameA + 0xeb


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.




.

Relevant Pages