XADM: Access Violation When You Move a Mailbox Programmatically by Using Cdoexm.dll

View products that this article applies to.

This article was previously published under Q296862

Symptoms

If you move a mailbox programmatically by using the move mailbox method in Exchange 2000, an access violation may occur in the application that calls the move mailbox method.

↑ Back to the top

Cause

This problem occurs because Cdoexm.dll loads Mapi32.dll explicitly from the Exchsrvr\Bin folder, to avoid conflict with the Mapi32.dll file that is included with Outlook. However, if the application calls the MAPIInitialize function, Mapi32.dll is loaded from the Winnt\System32 folder. Because of this, two Mapi32.dll files are loaded in the application address space, which causes the access violation.

↑ Back to the top

Resolution

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later:

Component: Move Mailbox

Collapse this tableExpand this table

File name	Version
Cdoexm.dll	6.0.4418.98

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

↑ Back to the top

More information

The following information from the Microsoft Developer Network (MSDN) describes how to explicitly map Messaging Application Programming Interface (MAPI) calls to MAPI DLLs:

Explicitly Mapping MAPI Calls to MAPI DLLs

In some cases, MAPI calls made from a particular DLL or executable file need to be routed to the system MAPI DLL (called Mapi32x.dll) or another custom MAPI DLL even though the default mail client supports the call. Such DLLs or executables files can be listed as string registry values in the HKLM\Software\Microsoft\Windows Messaging Subsystem\MSMapiApps key. The registry value for these keys can be empty or identify a mail client key that resides under HKLM\Software\Clients\Mail.

When the stub library resolves a MAPI call, it first enumerates the DLL and executable files listed under the HKLM\Software\Microsoft\Windows Messaging Subsystem\MSMapiApps key checking to see if the DLL or executable file is currently in process. If there is a match, the stub library gets the string value. If the value is the empty string, the stub library routes the call to the system MAPI DLL, Mapi32x.dll. If the string is not empty, the stub uses the string value to find the key below HKLM\Software\Clients\Mail where it can find the appropriate registry value to dispatch the call, one of DLLPath, DLLPathEx, or MSIComponentID values. For example:

HKLM\Software\Microsoft\Windows Messaging Subsystem\MSMapiApps::exchng32.exe = "" (route call directly to Mapi32x.dll)

HKLM\Software\Microsoft\Windows Messaging Subsystem\MSMapiApps::msspc32.dll = "Microsoft Outlook" (route call using Microsoft Outlook key under HKLM\Software\Clients\Mail)

↑ Back to the top