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

Last reviewed: October 29, 1997
Article ID: Q156392

The information in this article applies to:

Microsoft Transaction Server, version 1.0

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. 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 kbbug1.00 kbfix1.00.sp2
Version           : 1.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.