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

ID: Q156392

The information in this article applies to:


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


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'.


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. For information on obtaining version 1.1, please see the following article the Microsoft Knowledge Base:

   ARTICLE-ID: Q168031
   TITLE     : How to Obtain Microsoft Transaction Server Version 1.1
Keywords          : kbinterop kbprg kbbug1.00 kbfix1.10 TSrvGen 
Version           : 1.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix

Last Reviewed: October 30, 1997