MTS does not support this interface

Hi

Can anyone please suggest how I can resolve the following error message which is written to the NT event log after installing new versions of VB COM components ?

Microsoft Transaction Server does not support this interface because it is a custom interface built with MIDL and has not been linked with the type info helper library.
(Package: IIS-{MyServices//Root})
(IID: {your classid here})
(Microsoft Transaction Server internals information: File: i:\viper\src\runtime\cw\cwhlpapi.cpp. Line: 318)

Thanks in advance
Nick

hi Nick, how did you install the new components?

Hi Chris

I registered my VB COM components with regsvr32 and then dragged them into an empty MTS packege using Windows Explorer.

I had used the same technique on 3 or 4 occasions before without any problems.

Should I be simply copying the components to the server and then registering them via MTS ?

I have now got the server back to a "clean" state using Norton Ghost, but am concerned about the same thing happening again for future "builds".

Any suggestions or advice would be most appreciated.

Thanks
Nick

Hey Nick. In the past, if I was making a change to my COM component I would first unregister the original (regsvr32 -u "C:\WINNT\system32\DllName.dll") and then copy the dll, exp, and lib files to the system32 folder replacing the old ones I just unregistered. At that point, I just re-registered the component. I didn't have to do anything with MTS. It sounds like you were doing the same thing. Oh yea, if you change the version on you COM component, make sure you export the MTS and install it back on your develop machine where the application calling the MTS is being written. I've gotten errors in the past because I skipped that step. If all else fails, delete the MTS component, unregister the dll, and start over.

Hi Chris

Yeah that basically what I have been doing.
I was using regsvr32 to both register and unregsiter the components and tried to be as carefull as possible.

I must admit though that I was only copying the DLLs over and not their associated lib and exp files to the system32 folder.

I think next time I will try doing everything through the MTS component wizard.("Install new components", "Add files etc") instead of registering my components with regsvr32 and then dragging them into an empty MTS package via Win Explorer.

Anyway thanks very much for your time and suggestions, it's great to "talk" to someone experienced in this field and it's much appreciated.

Usually when I get a problem like this, I can just do a search on Google or the MS knowledgebase and find the answer straight off but not this time

I did read something in the Microsoft help files recently that said Install rather than Import so maybe that's the way to go.

I have very shortly got to learn Win 2K, Commerce Server, COM+ etc so that'll be fun.

Anyway thanks again for your efforts and if you have anymore thoughts, please let me know.

I use Google quiet a bit also. Normally with any problem there was always someone else that had the same or similar...well, except for the time I was doing webclasses...but that's another story. Let me know which route you decide to take and how it works out.

As far as learning COM+ and Win2K... If you are developing for an NT machine, it makes testing a bit of a problem. I don't remember the exact problem I had but it had something to do with the Windows Installer. I think I created the export file from COM+ and another devloper (using Win98) had to upgrade the Windows Installer before he could use the component. Anyway, sorry to be so long winded...let me know which route you take and how it works out. Chris

Chris

Yes, I too have had a bad experience with WebClasses, I don't think that they were one of Microsofts better ideas and I understand that they have now dropped them completely.

When we move to COM+ it will be a complete migration, so we will be developing for Win 2K, Whistler, XP or what ever they decide to call it that week.

Regards
Nick