Problem with COM+ component in VB (&H80004005 )

[Anders Englund]

I've got a problem with some COM+ components during development. I'm using VB6 (SP5) under WinXP (SP1).

Ok, here's how to make the problem appear:
1) Create a new project (EXE)
2) Add another program (ActiveX DLL)
3) Set the MTSTransactionMode for Class1 to anything but NotAnMTSObject.

Run the project group in VB. Wham! "System Error (&H80004005)" before the project even starts up. Compiling seems to work fine, and the compiled components also seem to work when registering them in COM+.

I've checked MSDN with no luck. Have anyone else seen this? In any case, is there a proper procedure to report this problem to MS?

--Anders

[deja]

this is very obvious.
when u set MTSTransactionMode property other then NotAnMTSObject u r actually "telling" VB that u want to run the object under some context in MTS (or COM+).
when u start running application under VB IDE, vb create this application (DLL or EXE) under it's own context, but he cannot run an MTS object under it's own context beacuse he don't have the appropriate sevices to support to that application (or object).

if u want to run this project u must compile it and install it under COM+ application.

u should read more about COM+, Context, Activities etc.

[Anders Englund]

Actually, it's not that obvious. I've been working with this project for a few years now, and never had a problem with this.
I can also verify that this works fine under both NT4and Win2k. Yes, you do get a warning that the project should be run under MTS, but you can still run it.
Also, in order to debug a COM+/MTS object you should compile it, install it in COM+ and then be able to run it in debug mode. But this doesn't solve the problem.

From MSDN:

Specifies the transactional behavior of a class. This property is only used by components running in the Microsoft Transaction Server, and has no effect if the component is run outside of the Transaction Server.

--Anders

[deja]

ok,
so u do agree that debugging this project will be in VB context, not COM+.
and u right about the ability to run the project from VB, and yes u will get a warning about this issue.
i have no problem to run the project in that case, and i am getting warning message from vb.
i think u should check service pack for vb and for win2k.

[Anders Englund]

I'm not running Win2k. It's not a problem when I try it in Win2k. I'm running Windows XP Pro.

--Anders

[deja]

so check the service pack for xp

[Anders Englund]

Been there, done that. Won't work either way.

--Anders

[mattiasf]

I sometimes have the same problem with my projectgroup, not always. I'm running against a VSS (Visual Source Safe) database on a remote server in a different domain. When I disconnect from the remote VSS database the error dissapears. Then I can reconnect to VSS and debug the application again. I don't know why.

[Hack]

By VSS do you mean Visual Source Safe?

[sergioman]

Hi guys,
I had the exact same problem trying to debug my ActiveX app. I began after I switched from one domain to another with my company. If found the link below but did not need to follow all the items listed. Instead I used the vbs script to disable the directory service lookup and started my VB6 ActiveX project to debug. Once I was sure that I was not going to get the “System Error &H80004005 Unspecified error" error, I reran the vbs script and re-enable the service lookup. So far I’ve not had any problems. Good luck.



http://www.talkaboutsoftware.com/gro...ges/10784.html