paul
Mon Nov 27 03:47:38 CST 2006
Hi,
thanks for your reply.
I already know which ActiveX object is causing the problem. It is OO4O
from Oracle. The error occurs on our production system irregularly.
Since it is the production system, I cannot hook up the debugger to it.
The real issue here is that IIS is not returning the native OO4O error
message to me, instead it is returning a generic error mesage which is
of no use in locating the problem. All I really need here is a way to
force IIS 6.x to return native component errors.
Is that possible?
Regards
Paul
David Wang schrieb:
> It no longer exists, but the issue is just as straight forward to
> diagnose.
>
> IIS versions prior to 6.0 had a bad practice of catching exceptions and
> then trying to handle them and continue onward when the correct thing
> is to let the exception halt processing. This is exactly what IIS 6.0
> does.
>
> You are getting a crash on a Server.CreateObject call. This can be
> trapped with a debugger attached onto the worker process, which will
> identify the offending DLL (and you can reverse engineer which
> Component it is).
>
> I realize that to you, it seems that IIS6 lost a "feature" to figure
> out the component that is crashing, but in reality, the feature is
> still there. We just got rid of the good intentioned but badly
> implemented feature in favor of a well implemented but not obvious
> feature.
>
> We'd rather you take the effort to find the right solution, instead of
> leaving you an obvious but incorrect solution.
>
>
> //David
>
http://w3-4u.blogspot.com
>
http://blogs.msdn.com/David.Wang
> //
>
>
>
> paul wrote:
> > Hello,
> >
> > in IIS 5.x it is possible to configure IIS to return the native error
> > message when an error occurs due to a Server.CreateObject call. This is
> > done via the check box "Enable Debug Exception Handling" on the tab
> > Home Directory/Configuration/Process Options.
> >
> > I cannot find the equivalent in IIS 6. I have tried searching the web
> > and reading the help files but cannot find anything relevant. Does this
> > feature still exist?
> >
> > The problem I am trying to solve is that when Server.CreateObject is
> > called I get the standard ASP error message " ...Unexpected error. A
> > trappable error (C0000005) occurred in an external object. The script
> > cannot continue running. ..." rather that the more useful component
> > message.
> >
> > Any help or ideas appreciated.
> >
> >
> >
> > Regards
> > Paul