The information in this article applies to:
SYMPTOMSAfter uninstalling a newer version of the client-side package, then reinstalling a previous version of the client-side package, the client application fails to instantiate the server component running under Microsoft Transaction Server (MTS). CAUSEThe MTS package uninstall does not remove the Typelib registry key for the newer version of the component, however, it does delete the actual type library pointed to by the registry key, making the value associated with this key invalid. When a client application tries to load the most recent version of the type library, it tries to load the type library that no longer exists. RESOLUTIONA supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next Microsoft Transaction Server version
that contains this fix. http://www.microsoft.com/support/supportnet/overview/overview.asp WorkaroundInstall the hotfix on the computer where the client-side package is being exported, and then re-export the client-side packages. Use this package instead of the old ones. This hotfix removes the registry key along with the type library.STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. MORE INFORMATIONWho Should Install This Release?You should install this hotfix, if you are experiencing the symptoms described earlier.Installation Requirements:This hotfix should only be installed on systems running Microsoft Windows NT version 4.0 (Service Pack 5). It should not be installed on previous versions of Microsoft Windows NT or on Microsoft Windows 2000.How to Install:
Additional query words:
Keywords : kbMTS kbMTS200fix kbDSupport kbfix |
Last Reviewed: September 21, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |