After migrating our VB6/ASP/COM+/SQLServer 2000 solution
to Windows 2003 Servers we get the following errors in the
event log and the intranet site stops responding (COM+
application needs to be shut down). The problem occurs a
few times per day (under development/test load).

On our Windows 2000 Server based production situation the
problem does not occur.

=======
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: {A32A836F-115A-4606-9AB7-
A4001A464A0E}
Server Application Instance ID:
{25FF35FD-5423-4D83-9733-87B8F0E558A5}
Server Application Name: Business
Exception: C0000005
Address: 0x0159503F
Call Stack:
sqloledb!DllMain + 0x255df
sqloledb!DllMain + 0x1c358
sqloledb!DllMain + 0xc1d6
msado15!DllCanUnloadNow + 0x6ab5
msado15!DllGetClassObject + 0x2f28
=======

Please help, since this problem stops us from moving to
Windows 2003 Server for our production systems.

Thanks in advance.

Eric.

[Keviv Nahom]

Hi Eric,

I am facing the very same error and on look out for a solution. We recently migrated our ASP website from Win 2000 to a 2003 server. The website uses COM+ components, the DLLs of which are used to create Word documents and converts them to PDF. The application simply hangs without any error messages displayed on the UI. When I check the system event log, I see a similar error message as above.

Any knowledge sharing or tips on this problem is greatly appreciated.

Thanks,
Keviv