BUG: Type Mismatch Error Using CDO in MS Transaction Server

ID: Q195928

The information in this article applies to:

Collaboration Data Objects (CDO), versions 1.1, 1.2, 1.21

SYMPTOMS

When you use two CDO components under Microsoft Transaction Server control, the application hangs or returns a "Type Mismatch" error.

CAUSE

MAPI does not support multiple DCOM sessions.

RESOLUTION

Modify the context where you create the second Microsoft Transaction Server component. If you create the second Microsoft Transaction Server component (inside the first Microsoft Transaction Server component) in the following manner:

    Set objObject = New Object.Class

Modify the code as follows:

   Set objObject = GetObjectContext.CreateInstance("Object.Class")

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

Using two CDO components under Microsoft Transaction Server control fails because MAPI does not support multiple DCOM sessions. By using the GetObjectContext, you obtain a reference to the ObjectContext that is associated with the current Microsoft Transaction Server object.

To use the GetObjectContext function, you must set a reference to Microsoft Transaction Server Type Library (that is, mtxas.dll).

Additional query words:

Keywords          : kbole kbCDO110bug kbCDO120bug kbCDO121bug kbMsg kbMTS 
Issue type        : kbbug
Solution Type     : kbpending

Last Reviewed: November 18, 1998