FIX: Catalog Doesn't Recognize Visual Basic Hex Typelib Versions

• Microsoft Transaction Server, versions 1.0, 1.1

SYMPTOMS

Transaction Server may be unable to load some components built with Visual Basic, even components it was previously able to load.

CAUSE

Visual Basic uses hexadecimal notation to track version information in type libraries. Transaction Server expects to read decimal notation. Thus, the problem only occurs if the version information contains the hexadecimal digits "A" through "F".

STATUS

Microsoft has confirmed this to be a problem in Microsoft Transaction Server version 1.0. This problem was corrected in Microsoft Transaction Server version 1.1.

REFERENCES

For information on obtaining version 1.1, please see the following article the Microsoft Knowledge Base:

Q168031 How to Obtain Microsoft Transaction Server Version 1.1

Additional query words:

Keywords : kbinterop kbprg kbMTS kbMTS100bug kbMTS110fix kbGrpCom kbDSupport kbBug
Version : winnt:1.0,1.1
Platform : winnt
Issue type : kbbug