Getting Event 5001 MSExchangeIS after migration to Exchange 2016 server

Bart Grootveld 1 Reputation point

Since deinstalling another mailserver we are getting the 5001 event a lot in our event logs, if we ask the corresponding users they do not notice any problems, although there seems to be quite a bit problem since a lot of these errors are generated.

Microsoft Exchange Information Store service encountered a corrupt AD object with ID (<hash>). Error text is (Mailbox Database attribute is null mailbox location type MainArchive for recipient <hash>
LID: 57912
Correlation ID: 00000000-0000-0000-0000-000000000000
Build Number: 15.1.2308.21
Database GUID: <hash>
Database Hash: <hash>
Mailbox GUID: <hash>
Mailbox Number: 0
Operation source: Mapi
Client Type: MoMT
Hash Code: 634626396
Logged on User Identity: 00000000-0000-0000-0000-000000000000
Logged on User SID: S-1-5<hash>

Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,524 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,323 questions
{count} votes

3 answers

Sort by: Most helpful
  1. KyleXu-MSFT 26,206 Reputation points

    @Bart Grootveld

    Here is a similar question: Error in the Exchange 2013 Server event Viewer (under application log) after user is migrated to exchange online

    You could ignore those event ID, that op also gets this error message when migrate mailboxes. So, I would suggest you tell related users to recreate Outlook profile, then watch for a while to see whether the Event ID is gone.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Limitless Technology 39,331 Reputation points


    did you already tried to see if the mailboxes were provisioned correctly?

    Verify that the cloud-based archive mailbox is created

    According to Microsoft :
    This Error event indicates that Microsoft Exchange was unable to initialize the Microsoft Exchange Information Store service because the disk is full.

    1.If the database transaction log files are on the same disk, it is possible that too many log files have accumulated. This situation can be caused by excessive database usage during a mailbox move or other operation, or it can be caused by incorrectly performing backups. The correct method to remove database transaction log files is to perform an online backup. An online backup commits all the log files to the database, and then removes the log files from the disk.
    2.If the database has become too large for the disk, consider moving the database to a new disk.
    3.If there are other files on the disk, consider deleting or moving those files.
    4.If there are other Exchange databases on the disk, consider moving those databases.
    5.Reclaim disk space in the Exchange database by using the Exchange Server Database Utilities (Eseutil.exe).

    --If the reply is helpful, please Upvote and Accept as answer--

    0 comments No comments

  3. Bart Grootveld 1 Reputation point

    Thank you for your answers, but in this specific case there is no Exchange online involved.