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 / .NET Framework / Component Services / January 2006

Tip: Looking for answers? Try searching our database.

Error "COM Surrogate encountered a problem..." .NET / VB6 in

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Peter Meinl - 22 Dec 2005 14:25 GMT
A multithreaded VB.NET Windows Service uses a FilesystemWatcher in each
thread.
The FilesystemWatcher event handler calls a VB6 COM+ component
"MEDAMBusiness.CMilDispatch".

After reboot of the server PC a MessageBox with the Error "COM Surrogate
encountered a problem..." pops up.
There is no entry for this error in the event log.

In the event log there is a related error:

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:
{90AF7461-8313-49AB-8971-BD9C92634B40}
Server Application Name: Medam
The serious nature of this error has caused the process to terminate.
Exception: C0000005
Address: 0x00DC8301
Call Stack:
+ 0xdc8301
MSDART!long const * const
`CLKRHashTableStats::BucketSizes(void)'::`2'::s_aBucketSizes + 0xb4
msdasql! + 0x155d
msdasql!DllGetClassObject + 0xff6
msdasql!DllGetClassObject + 0x1121
msdasql!DllGetClassObject + 0x14de
msdasql!DllGetClassObject + 0x214
msdasql!DllGetClassObject + 0x342
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 + 0x687a1
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

--
Peter Meinl
ISTEC GmbH
Peter Meinl - 23 Dec 2005 17:46 GMT
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

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.