Microsoft KB Archive/820140

= XADM: Cannot Use LongtermEntryID To Open Items in a Delegate Mailbox =

Article ID: 820140

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



SYMPTOMS
When you open a delegate mailbox by using a MAPI session, the PR_LONGTERM_ENTRYID_FROM_TABLE property returns an entry identifier that is not valid. If you try to access a message by using this identifier, the following error is generated:

MAPI_E_NOT_FOUND



CAUSE
This problem occurs if the following conditions exist:
 * You access a delegate mailbox that has been moved to a different storage group on the same server.

-and-
 * You access that delegate mailbox by using Exchange 2000 MAPI.

Note This problem does not occur if you access the delegate mailbox by using Microsoft Outlook MAPI.



Cumulative Rollup Information
To resolve this problem, obtain the September 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional 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:

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

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: Information store

The English version of this fix has the file attributes (or later) 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 --  11-Jun-2003  20:34  6.0.6475.0      3,915,776  Cdoex.dll 11-Jun-2003 20:28  6.0.6475.0        827,392  Davex.dll 11-Jun-2003 20:25  6.0.6475.0        577,536  Dsaccess.dll 11-Jun-2003 19:35  6.0.6475.0        184,320  Dscmsg.dll 11-Jun-2003 19:51  6.0.6475.0        958,464  Emsmdb32.dll 11-Jun-2003 20:34  6.0.6475.0      3,575,808  Excdo.dll 11-Jun-2003 20:25  6.0.6475.0        258,048  Exmime.dll 11-Jun-2003 20:28  6.0.6475.0      2,138,112  Exoledb.dll 11-Jun-2003 20:23  6.0.6475.0         81,920  Exosal.dll 11-Jun-2003 20:28  6.0.6475.0        307,200  Exprox.dll 12-May-2003 18:40                      8,985  Frm_readnote20.js   11-Jun-2003  19:28  6.0.6475.0         49,152  Mdbevent.dll 11-Jun-2003 19:47  6.0.6475.0      2,285,568  Mdbmsg.dll 11-Jun-2003 19:30  6.0.6475.0         32,768  Mdbrole.dll 11-Jun-2003 20:26  6.0.6475.0         24,576  Mdbtask.dll 11-Jun-2003 20:24  6.0.6475.0      4,648,960  Store.exe 12-May-2003 18:40                     22,121  Util_owa20.js   11-Jun-2003  19:36  6.0.6475.0      3,735,552  Wmtemplates.dll Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional 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, do not use the PR_LONGTERM_ENTRYID_FROM_TABLE property. Instead, open each item and obtain the PR_ENTRYID property. This property gives you the long-term entry identifier. However, if you use this method, you may decrease the performance of your program.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Additional query words: kbExchange2000preSP4septbarFix

Keywords: kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB820140

-

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

© Microsoft Corporation. All rights reserved.