Article ID: 318549
This article was previously published under Q318549
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
If the access control list (ACL) contains old access control entries (ACEs) or ACEs that are not valid, the Exchange 2000 server may generate an event ID 9551 warning message for migrated Microsoft Exchange Server 5.5 mailboxes. The warning message is similar to:
If multiple ACEs that are not valid exist in a single ACL, Exchange 2000 may log an event ID 9551 warning message for only the first ACE. Exchange 2000 may stop processing the ACL when Exchange 2000 sees an ACE that is not valid. If multiple entries exist, and you remove the first ACE that is not valid, Exchange 2000 generates an event ID 9551 warning message for the next ACE that is not valid in the ACL.
Event Type: Warning
Event Source: MSExchangeIS Mailbox Store
Event Category: (6)
Event ID: 9551
Time: 1:00:00 AM
Description: An error occurred while upgrading the ACL on folder [MBX:User1]/Calendar located on database "Server1\Mailbox Store 1 (server)". The Information Store was unable to convert the security for /O=ORGANIZATION/OU=SITE/CN=RECIPIENTS/CN=123456 into an NT Security Identifier. It is possible that this is caused by latency in the Active Directory Service, if so, wait until the user record is replicated to the Active Directory and attempt to access the folder (it will be upgraded in place). If the specified object does NOT get replicated to the Active Directory, use the Microsoft Exchange System Manager or the Exchange Client to update the ACL on the folder manually. The access rights in the ACE for this DN were 0x401.
The ACEs are entries that originate from Microsoft Windows NT security for Exchange Server 5.5 disabled accounts. This problem may occur if the Exchange Server 5.5 mailboxes (or public folders) were migrated to Exchange 2000 and the DS/IS consistency adjuster was not used on the Exchange Server 5.5 store to remove these entries from the ACL.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
The recommended resolution is to run the DS/IS consistency checker against the information store before migration. All information store migrations (both private and public) should run the DS/IS consistency checker to prevent this problem. The following workaround of applying the new build and installing the registry settings and the Deadlist.txt file are supported for situations where the migration has occurred and the server cannot be restored to a pre-migration state, and therefore, performing the DS/IS consistency check is not a possibility. The creation of the Deadlist.txt file can be a tedious and time-consuming activity. This workaround is not meant to be a replacement for running the DS/IS consistency checker before the migration.
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 the Microsoft Knowledge Base:
301378The English version of this fix should have the following file attributes or later:
(http://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Component: Information store
Collapse this tableExpand this table
After you apply this fix, to implement it, you must create a text file that includes the distinguished names that you are getting warning messages for. To implement the fix, you must also use Registry Editor.
To implement the fix:
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.