Microsoft KB Archive/202630

= PRB: MTS and COM+ Do Not Always Install Typelibs on Client Computers =

Article ID: 202630

Article Last Modified on 12/5/2007

-

APPLIES TO


 * Microsoft Transaction Services 1.0
 * Microsoft Transaction Services 2.0
 * Microsoft COM+ 1.0
 * Microsoft COM+ 1.5

-



This article was previously published under Q202630



SYMPTOMS
Microsoft Transaction Server (MTS) client install .exe files and COM+ application proxy .msi files do not always install component type libraries (typelibs) on client computers. As a result, if a client application uses the interfaces that those type libraries support, the application may fail.

For example, for Microsoft Visual Basic applications, early binding with one of these objects does not work and may result in a "Type mismatch" error. Microsoft Visual C++ applications that try to obtain one of these interfaces may receive an REGDB_E_IIDNOTREG error.

This problem does not occur with late binding (that is, the use of the IDispatch interface).



CAUSE
This problem occurs if you use the Import component(s) that are already registered option to install components into an MTS package or COM+ application, MTS and COM+ do not attempt to work with the type library for objects that are installed with this option. By default, MTS client install .exe files or COM+ application proxies do not include the typelibs for these objects.



RESOLUTION
For your applications to work as expected, use the Install new component(s) option to install components in MTS and COM+. The typelibs for your components are then installed on client computers when you use client install .exe files or application proxies.

Additional query words: executables installer

Keywords: kbmtsexplorer kbprb KB202630

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.