Last post Oct 16, 2007 07:14 PM by jfdiazb
Sep 07, 2004 06:01 AM|imranghani|LINK
Sep 07, 2004 08:58 AM|tomasr|LINK
Sep 07, 2004 09:41 AM|imranghani|LINK
Sep 07, 2004 01:52 PM|teststand|LINK
Sep 08, 2004 03:32 AM|imranghani|LINK
Sep 08, 2004 09:46 AM|BruceJohnson|LINK
Sep 08, 2004 11:18 AM|teststand|LINK
Dec 19, 2006 10:16 AM|sgoncu|LINK
Seems like I also have some similar problem.
We have an old legacy VB6.0 COM component which we needed to update.
We made the change, recompiled and tested on 2 different WinXP machines, (one is the development and the other is a clean machine) works fine.
But when we deploy it on W2003 Server production machine, the component stops working, giving us the above mentioned exception.
Reverting back to old dll, works fine. Unregister old and register new, asp.net page crashes.
Why this can be?
Oct 16, 2007 07:14 PM|jfdiazb|LINK
I have a similar problem
I have a Activex component made in VB 6.0.
When I Register the component on the server (Win 2003) some times ,the first time the application run very well.
But after that, the application crashes.To correct the problem i have to register the component again.
I have 1000 servers but in 100 servers happens this error.
On 5 servers the solution no works.
Im Using a application made in C# with Asp with framework .net 1.1
Some idea for correct this problem??????