Shulou(Shulou.com)06/02 Report--

Environment:

Exchange 2013 CU19

Problem description:

The user runs the New-MailboxImportRequest command through the EMS Management Shell, imports the .pst file to the target mailbox, and the import status is always "in queue". As shown in the figure:

Cause analysis:

First, we recommend that users run the Get-MailboxImportRequestStatistics command to query mailbox import status information and export the results to reports.txt:

Get-MailboxImportRequest | Get-MailboxImportRequestStatistics-IncludeReport | fl > c:\ reports.txt

In the export report, the following error was found:

"Job pickup failed. Invalid job-Orphaned could not find the requested valid index entry."

According to the error content, we understand that the content indexing function of the imported target mailbox database may be abnormal, so it is recommended that users try the following steps to rebuild the index:

1. Pause the Microsoft Exchange search and Microsoft exchange search host controller services on the Exchange server side.

two。 Open the mailbox database that imported the target mailbox (the default path in Exchange 2013 is C:\ Program Files\ Microsoft\ Exchange Server\ V15\ Mailbox\), and rename or move to. The GUID folder at the end of single to another location. This folder is used to store indexes.

3. Restart the two services paused in step 1.

Run the following command to see if the mailbox database index status is "healthy". Please note that it may take some time to rebuild the index.

Get-MailboxDatabaseCopyStatus | ft-AutoSize

After the index is rebuilt successfully, execute the import command New-MailboxImportRequest again. However, it is still unsuccessful and the import status is displayed as "failed".

Use the command mentioned above again to check the import information, this time with the following error:

"error: unable to save the change item to the store. MapiExceptionShutoffQuotaExceeded: Unable to save changes."

This error means that the size of the imported file exceeds the quota for the target mailbox, so it is recommended that users run the following command in EMS to view this setting:

Get-Mailbox "username" | fl-Property MaxReceiveSize, MaxSendSize, ProhibitSendQuota, ProhibitSendReceiveQuota, IssueWarningQuota

The results are as follows:

As can be seen from the returned results, the maximum receive quota set by the user's mailbox is less than the actual size of the. pst file to be imported (85MB).

After finding the cause of the error, run the following command to change the limit quota for the mailbox.

Get-MailBox "username" | Set-MailBox-IssueWarningQuota unlimited-ProhibitSendQuota unlimited-ProhibitSendReceiveQuota unlimited-MaxReceiveSize unlimited-MaxSendSize unlimited

Wait a while after the change, or restart the Microsoft Exchange Information Store service to take effect immediately. Finally, execute the file import instruction again, and the import is successful.

Note: restarting the Microsoft Exchange Information Store service will unmount and remount all databases on the Mailbox server, which will temporarily disrupt mail flow and client connections.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.