Microsoft KB Archive/235558

= PRB: Importing Components in MTS 2.0 Ignores Transaction Attributes =

Article ID: 235558

Article Last Modified on 6/12/2001

-

APPLIES TO


 * Microsoft Transaction Services 2.0

-



This article was previously published under Q235558



SYMPTOMS
When importing a component into Microsoft Transaction Server (MTS) 2.0 by using the Import component(s) that are already registered in the MTS Component Import Wizard, the configuration or attributes this component has for its transaction mode are ignored and the component appears as "Does not support transactions."



CAUSE
The .dll registration information that MTS reads and modifies to register a component in its run-time environment does not include the transaction attribute information. Therefore the transaction attributes stored in the .dll file are ignored.



RESOLUTION
Do not add components by using the Import component(s) that are already registered option. Instead, import them by either dragging the .dll file into the MTS components pane or by using Install new component(s) in the MTS Component Wizard. If the .dll file is not currently registered, MTS will register it as needed.



STATUS
Microsoft is aware of the problems the lack of a warning may cause. We will keep you updated on this issue through MSDN, TechNet, and other information resources.



Steps to Reproduce Behavior

 * 1) Create a new ActiveX DLL in Visual Basic 6.0. Give the project a name such as ImportTestDLL.
 * 2) Rename the default Class1 as ImportTest.
 * 3) Set the MTSTransactionMode attribute in the Properties pane to 2 - Requires Transaction.
 * 4) Compile the DLL.
 * 5) Create a new empty package in the MTS Explorer snap-in.
 * 6) Right-click the Components folder under the package icon and click New and then select Component.
 * 7) When the Component Wizard appears, click Import component(s) that are already registered.
 * 8) In the Choose Components to Import pane, click Refresh list and select your new ImportTestDLL.ImportTest object. You should now have the green globe representing your object in the components folder for the package.
 * 9) Right-click the object and select Properties. On the Transaction tab, the item Does not support transactions will be selected. However, the setting used in the Visual Basic project should set this value to Requires a transaction.

NOTE: You might want to delete the package and unregister and delete your DLL after reproducing the error.

Additional query words: MTS packages components transactions import registering MTSTransactionMode

Keywords: kbsysadmin kbprb KB235558

-

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

© Microsoft Corporation. All rights reserved.