Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Mailbox that has a bad move request can't be cleaned up from destination mailbox database in Exchange Server 2019 and 2016


View products that this article applies to.

Symptoms

In Microsoft Exchange Server 2019 or Exchange Server 2016, if an error occurs in a move request or you cancel the move request before the move is complete, the mailbox can't be deleted from the destination database. After the retention period that you defined by using Set-MailboxDatabase cmdlet has already passed, you can still see it in Get-MailboxStatistics cmdlet's result. This issue may consume lots of disk space in Exchange Server. 

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 

↑ Back to the top


Resolution

To fix this issue, install one of the following updates:
For Exchange Server 2019, install the Cumulative Update 1 for Exchange Server 2019 or a later cumulative update for Exchange Server 2019.
For Exchange Server 2016, install the Cumulative Update 12 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016.

↑ Back to the top


References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: if an error occurs in a move request, if you cancel a move request before it complete, kb, kbfix, kbqfe, Mailbox can't be cleaned up from destination mailbox database, kbHotfixAuto, CI97349

↑ Back to the top

Article Info
Article ID : 4488264
Revision : 13
Created on : 2/12/2019
Published on : 2/12/2019
Exists online : False
Views : 266