Follow me on Twitter at
FYI, I'm blogging most of my stuff over at More Wally now.
You might want to add my rss feed to your reader at:
Need Assistance - 0x8000ffff catastrophic error when debugging VB6 COM+ objects - Wallace B. McClure

Wallace B. McClure

All About Wally McClure - The musings of Wallym on Web, HTML5, Mobile, Xamarin.iOS, Xamarin.Android, and Windows Azure.


Visual Studio Magazine Column Personal Blog


Book Authors




Georgia Tech Bloggers



Need Assistance - 0x8000ffff catastrophic error when debugging VB6 COM+ objects

Hi all. I am trying to debug some Vb6 COM+ components under Win2k3 server. I have inherited this code from someone else. I have loaded the components into a COM+ application. I have the com+ app running as the interactive user. When I run the components through the debugger and call them through the web browser, I get an 0x8000ffff catastrphic error. When I don't run the components within the debugger, everything runs normally. I can compile the components fine. The compiled components work properly when called directly,
the problem is when running underneath the debugger.

I am running Win2k3 server, vb6 with sp5, and sql2k with sp3.

Anyone have any thoughts as to how to resolve this issue and to debug the components properly? I have searched the MS knowledgebase and google (sites and groups) with little result. I think that this is a security issue in that some user does not have appropiate access to something, but I am running as the local administrator and everything is configured to run as the Interactive User.



Mathew Nolton said:

do you have it set to "Binary Compatability"?
If in debug mode, try turning compatibility to "No Compatibility"

-Mathew Nolton
# November 17, 2003 1:11 PM

Wallym said:

"binary Compatability" to "No Compatibility" no worky........
# November 17, 2003 1:23 PM

Mathew Nolton said:

I read that somewhere a while ago. Since you were grasping at straws, I thought I'd throw one into the pile.
-Mathew Nolton
# November 17, 2003 1:27 PM

Glenn G said:

We have just encountered the exact issue since applying Vis Studio sp5... Have you found a solution yet?
# January 23, 2004 4:28 PM