The description of the event ID 9646 message includes a GUID instead of a recipient name

The following event ID message is logged on a server that is running Microsoft Exchange Server 2003:

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9646
Description: Mapi session "a3acaee7-cb14-4466-83ce-1dd117b546dc" exceeded the maximum of 250 objects of type "objtMessage".

You expect the description of the event ID 9646 message to include a recipient name that is in the following format: However, the description of the event ID 9646 message includes a GUID instead of a recipient name.

This issue occurs if the Exchange Store.exe process cannot resolve the GUID to an msExchMailboxGuid attribute or to an objectGUID attribute. The Store.exe process may not be able to resolve the GUID if sibling domains exist in the same forest. A sibling domain is another domain that exists at the same level in the forest. When the Store.exe process tries to resolve the GUID, the Store.exe process sets the BaseDN parameter of the Lightweight Directory Access Protocol (LDAP) query to a value that is equal to the domain naming context of the user. If the Exchange server is in a sibling domain, the LDAP query returns no results.

To work around this issue, change the format of the GUID to a format that you can use in an LDAP query. Then, use the LDP utility (Ldp.exe) to search for the recipient name that maps to the GUID that appears in the description of the event ID 9646 message. The following sections describe these steps in detail.

Step 1: Change the format of the GUID to a format that you can use in an LDAP query

Note The GUID is composed of five sections. Each section is separated by a hyphen (-). This procedure uses the following GUID as an example:

1. Use a backslash (\) to separate each pair of numbers in the GUID.
   
   After you complete this step, the GUID is in the following format:
   \a3\ac\ae\e7-\cb\14-\44\66-\83\ce-\1d\d1\17\b5\46\dc
2. Reverse the pairs in the first section, the second section, and the third section. Do not change the fourth section or the fifth section.
   
   After you complete this step, the GUID is in the following format:
   \e7\ae\ac\a3-\14\cb-\66\44-\83\ce-\1d\d1\17\b5\46\dc
3. Remove the hyphens.
   
   After you complete this step, the GUID is in the following format:
   \e7\ae\ac\a3\14\cb\66\44\83\ce\1d\d1\17\b5\46\dc
   Use this GUID in the LDAP query.

Step 2: Use LDP.exe to search all domains for the recipient name that maps to the GUID

Warning If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.

Note Ldp.exe is included with the Microsoft Windows Support Tools. To install the Windows Support Tools in Microsoft Windows 2000 Server, double-click Setup.exe in the Support\Tools folder on the Windows 2000 Server CD. To install the Windows Support Tools in Microsoft Windows Server 2003, double-click Suptools.msi in the Support\Tools folder on the Windows Server 2003 CD.

1. Start Ldp.exe.
2. Click Connection, and then click Connect.
3. In the Server box, type the name of a domain controller that is in the root domain of the forest.
4. In the Port box, confirm that the port number is set to 3268.
5. Click OK.
6. Click Connection, and then click Bind.
7. Type a user name, a domain, and a password for an account that has Enterprise Administrator permissions, and then click OK.
8. On the View menu, click Tree.
9. Delete the text in the BaseDN box, and then click OK.
10. In the left pane, right-click the first object, and then click Search.
11. In the Search window, type the following text in the Filter box:
    (&(objectclass=*)(msExchMailboxGuid=\e7\ae\ac\a3\14\cb\66\44\83\ce\1d\d1\17\b5\46\dc))
12. Under Scope, click Subtree.
13. Click Run.

For more information about how to use Ldp.exe to search for LDAP strings, click the following article number to view the article in the Microsoft Knowledge Base: