Article ID: 815475
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
SYMPTOMS
When you run a program that calls the Extended MAPI GetProps function and passes a NULL property tag array to obtain all the properties of an attachment, you may receive a MAPI_E_CALL_FAILED failure code result for some messages.
You may not be able to use Collaboration Data Objects (CDO) to programmatically process message attachments because CDO requires the GetProps call with a NULL property tag array to be successful.
CAUSE
This problem may occur if all the following conditions are true:
- You configure a Post Office Protocol version 3 (POP3) client on a Microsoft Exchange Server 5.5 computer to send a message that contains an attachment, where you have enabled voting buttons, to a recipient whose mailbox is stored on an Exchange 2000 computer.
- The Exchange Server computer is configured to both forward the message to the Exchange 2000 computer and send that mail by using Microsoft Exchange Rich Text Formatting.
- Your program calls the Extended MAPI GetProps function and passes a NULL property tag array to obtain all the properties of the message attachment after the message has been received by the Exchange 2000 computer.
This problem occurs because the server returns the PR_MAPPING_SIGNATURE MAPI property to the client. Because the client does not expect to receive this client-side-only property from the server, the routines that process the server results before passing them back to the caller fail, and the MAPI_E_CALL_FAILED code is returned.
RESOLUTION
Cumulative Patch Information
To resolve this problem, obtain the September 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824282 September 2003 Exchange 2000 Server post-Service Pack 3 rollup
Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange 2000 Server service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Component: Emsmdb32.dll
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ------------------------------------------------------------ 07-Mar-2003 19:05 6.0.6433.0 3,915,776 Cdoex.dll 07-Mar-2003 18:56 6.0.6433.0 827,392 Davex.dll 07-Mar-2003 19:05 6.0.6433.0 3,571,712 Excdo.dll 07-Mar-2003 18:53 6.0.6433.0 258,048 Exmime.dll 07-Mar-2003 18:56 6.0.6433.0 2,138,112 Exoledb.dll 07-Mar-2003 18:50 6.0.6433.0 81,920 Exosal.dll 07-Mar-2003 18:56 6.0.6433.0 303,104 Exprox.dll 07-Mar-2003 18:16 6.0.6433.0 2,285,568 Mdbmsg.dll 07-Mar-2003 17:50 6.0.6433.0 32,768 Mdbrole.dll 07-Mar-2003 18:52 6.0.6433.0 4,644,864 Store.exe
Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 How to obtain the latest Exchange 2000 Server service pack
WORKAROUND
To work around this problem in your program, make sure that the program calls GetProps with a property tag array that specifies the properties that you want.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
Additional query words: kbExchange2000preSP4septbarFix XADM
Keywords: kbhotfixserver kbqfe kbfix kbexchange2000presp4fix kbbug KB815475
