Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem debugging COM+ component in VB 6 IDE

Status
Not open for further replies.

ashvn

Programmer
Mar 21, 2001
33
MU
Hi everyone,

I have a component (say A) which is normally instantiated from within another component (say B), itself called from an ASP page. I used to be able to debug component A without any problems with the ASP page running, but then don't know what happenned, I could no longer debug, and the only workaround I found was to set the MTSTransactionMode of the classes to debug to 0. I have WIN XP SP2. Been looking around on different sites, and this looks like a prob with COM+, but haven't been able to resolve it. Any ideas most welcome.

Thanks a lot!

 
It's not a problem, it's a feature....

As I recall, Microsoft doesn't support debugging of COM+ component transaction behavior. You can debug the component, but not its MTS Context.

Bob
 
Well, thanks for the answer, but that still keeps me wondering why it used to work before.. The system actually logs errors in the event viewer, and if I do not change the MTSTransaction mode of the class to debug to 0, then I get this error: VB(-2147417851) Method '~' of object '~' failed. Any ideas on this?

Thanks!
 
Well, we all hate that error! It usually means that a Microsoft program attempted to do something that it wasn't authorized to do. The reasons for it are vastly varied: I just spent four days tracking down such an error (well, the vendors tracked it down, and I reinstalled everything), and it turned out to be that we had copied a folder from a source ftp site. When we redid the installation with a hand-created folder, the program worked.

Sorry, but you don't have an easy answer that I can think of.

Bob
 
Well, one thing is that I can debug the component if I remove visual studio and re-install it. But if I put in SP4(or higher; haven't tried any older SPs though), then it stops working again... Meaning, something must have been brought in by the SPs that has caused the debugging to stop working...
 
Sigh....whatever happened to the good old days when a line of code was a line of code?

Good luck,

Bob
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top