COM+

[Mikesc]

Another Win 2000 problem...

In Win 2000 COM and MTS have been integrated.
Packages in Win2000 are called applications.

I have a DLL with all the proper settings, compiled with Binary Compatibility, and ObjectContext/Transaction code.

I then added the DLL to an Application (package). I believe all the settings for the application are correct (mostly default + requires transaction).

When I run a an exe that uses the DLL I get a "No such interface supported" error message.

I referenced both the DLL and the COM+ library in the project.

Is this a problem between COM+ and vb6?

Anybody know anything about this?

Is the component installed correctly on your client machine? I'm guessing that your dcom settings or CLIDs have not been updated which is why it can't find the interface. You will also have to recompile your EXE after you update your config.

[Mikesc]

Thank you for your reply. I'm pretty sure the components are installed correctly and the ID is OK, I've installed/uninstalled, registered/unregistered numerous times. The exe is actually a VB project running in the development environment and therefore not yet compiled but I did change the reference to no avail. The component worked fine before adding it to an application(package). Now I just get errors. I even tried adding the ObjectControl interface to the component and using its Activate method to instantiate it but no luck.
If only the error was a little more descriptive...

[Mikesc]

Apparently VB won't accept the 'requires transaction' option from a component in COM+. When I switched to 'supports transactions' the error message went away and everything runs peachy keen. I hope they fixed this in the release version of Win2000.