XADM: Rootfolder Does Not Work If the mailNickname Attribute Value Does Not Match Any Proxy Addresses

This article was previously published under Q321934
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
IMailbox::Rootfolder does not work and returns error code 80040e19 if there is no proxy address for the user in the following format
name@domain
where name is the value in the user's mailNickname attribute and domain is derived from the value in the user's homeMDB attribute.

The error message for error code 80040e19 is:
No key matching the described characteristics could be found within the current range
CAUSE
Rootfolder builds the URL based on information it reads from the user's mailNickname attribute in Active Directory. Before Rootfolder returns the URL, Rootfolder tries to bind to the URL to validate it. The Bind operation validates a URL by searching for users who have matching proxy addresses. Because the information contained in the mailNickname attribute is not guaranteed to match a user's proxy address, this search may not work. If this search does not work, Rootfolder returns error 80040e19.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Rootfolder has been changed to build the URL based on information from the mail attribute instead of the mailNickname attribute. This guarantees that the search performed in the Bind operation will succeed.The English version of this fix should have the following file attributes or later:

Component: CDOEX

File nameVersion
Cdoex.dll6.0.5771.3

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.
WORKAROUND
Add a proxy address to the user for which Rootfolder fails that matches the name in the mailNickname attribute.
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.
-2147217895 80040e19
Properties

Article ID: 321934 - Last Review: 10/24/2013 11:40:20 - Revision: 1.4

Microsoft Exchange 2000 Server Standard Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB321934
Feedback