Microsoft KB Archive/156392

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

Article ID: 156392

Article Last Modified on 3/16/2005

-

APPLIES TO


 * Microsoft Transaction Services 1.0

-



This article was previously published under Q156392



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 or version 2.0, please see the following articles in the Microsoft Knowledge Base:

168031 HOWTO: Obtain Microsoft Transaction Server Version 1.1

185174 Latest Version of Microsoft Transaction Server

Keywords: kbbug kbfix kbmts110fix KB156392

-

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

© Microsoft Corporation. All rights reserved.