Get-MailboxExportRequest status not updated, but request completed

Question

question

ilianko-6627 asked Jan 8, '21 ilianko-6627 commented May 31, '22

Get-MailboxExportRequest status not updated, but request completed

Recently I upgraded from Exchange 2013 to exchange 2019 and now my script that exports mailboxes does not work properly

I found the following problem:

get-MailboxExportRequest is updated very slowly ( 1 hour to one day) ... The status shows that export is queued, but the export is already finished, and the pst file is without errors. ( My database configuration is DAG with two servers on different sites)

Get-MailBoxExportRequest:

RunspaceId : d38cdd90-9892-455e-a617-4ce43ad298c5
FilePath : \\admins\y_x_20210108.pst
Mailbox : domain/xxx yyy
Name : x_y_20210108
RequestGuid : e10c8560-1cec-42a2-9272-21db0c3d0e55
RequestQueue : DB-01
Flags : IntraOrg, Push
BatchName : admin
Status : Queued
Protect : False
Suspend : False
Direction : Push
RequestStyle : IntraOrg
OrganizationId :
WhenChanged : 1/8/2021 10:05:35 AM
WhenCreated : 1/8/2021 10:00:52 AM
WhenChangedUTC : 1/8/2021 8:05:35 AM
WhenCreatedUTC : 1/8/2021 8:00:52 AM
Identity : domain/xxx yyy\y_x_20210108
IsValid : True
ObjectState : New

If I check the status with get-MailboExportRequeStstatistic everything is OK:
RunspaceId : d38cdd90-9892-455e-a617-4ce43ad298c5
Name : y_x_20210108
Status : Completed
StatusDetail : Completed
SyncStage : SyncFinished
Flags : IntraOrg, Push
RequestStyle : IntraOrg
Direction : Push
Protect : False
Priority : Normal
WorkloadType : Local
Suspend : False
FilePath : \\admins\y_x_20210108.pst
ComplianceStorePath :
PreferredMessageFormat : Default
SourceAlias : y_x
SourceIsArchive : False
SourceExchangeGuid : 0837e85a-7cc9-440d-b390-fa411590ce2b
SourceRootFolder :
RecipientTypeDetails : UserMailbox
SourceVersion : Version 15.2 (Build 721.0)
SourceMailboxIdentity : domain/yyy_xxx
LargeItemsEncountered : 0
QueuedTimestamp : 1/8/2021 10:00:51 AM
StartTimestamp : 1/8/2021 10:00:57 AM
LastUpdateTimestamp : 1/8/2021 10:03:46 AM
LastSuccessfulSyncTimestamp : 1/8/2021 10:03:45 AM
InitialSeedingCompletedTimestamp : 1/8/2021 10:03:46 AM
CompletionTimestamp : 1/8/2021 10:03:46 AM
SuspendedTimestamp :
OverallDuration : 00:02:54.8590619
TotalSuspendedDuration : 00:00:00
TotalFailedDuration : 00:00:00

office-exchange-server-administration

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ilianko-6627 · May 31 at 06:30 AM

After 2019 CU12 upgrade the problem is gone :)

0 ·

Answer 1 · 2021-01-11T06:36:16.787Z

LucasLiu-MSFT answered Jan 11, '21 LucasLiu-MSFT commented Jan 19, '21

Hi @ilianko-6627 ,
Does exporting all mailboxes have this issue?
"PST file is without errors" means that you can import the .pst file to mailbox and get the complete mailbox data?
Please try to following steps:
1.Please try to restart the Microsoft Exchange Mailbox Replication service.
2.Please try to run the following command to view the health and status information about mailbox database copies.

 Get-MailboxDatabaseCopyStatus

3.Please run the following commands to remove all mailbox export request then create an export request to export only one mailbox, then check the status again. If the status is normal, please check whether the script you are using supports Exchange 2019.

 Get-MailboxExportRequest -Status Completed | Remove-MailboxExportRequest
 New-MailboxExportRequest -Mailbox <> -FilePath <>

In addition, according to my test to export the mailboxes in Exchange 2019 and running the " Get-MailBoxExportRequest" and " Get-MailboxExportRequestStatistics" command lines, the results obtained are normal.

If the response is helpful, please click "Accept Answer" and upvote it.
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.

3.png (54.6 KiB)

· 2

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LucasLiu-MSFT · Jan 14, 2021 at 10:01 AM

Hi @ilianko-6627 ,
Do suggestions above help? If the issue has been resolved, please click “Accept as answer” to mark helpful reply as an answer, this will make answer searching in the forum easier and be beneficial to other community members as well.

Thanks for your understanding.

If the response is helpful, please click "Accept Answer" and upvote it.
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 ·

LucasLiu-MSFT · Jan 19, 2021 at 06:33 AM

Hi @ilianko-6627 ,
I am writing here to confirm with you how thing going now? If the above suggestion helps, please click “Accept as answer” to mark helpful reply as an answer.Your action would be helpful to other users who encounter the same issue and read this thread.
Thanks for your understanding.

If the response is helpful, please click "Accept Answer" and upvote it.
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 ·

Answer 2 · 2022-01-24T16:47:49.98Z

Joachim-3513 answered Jan 24, '22

I can confirm that this is a problem with Exchange 2019 on premise too.

Randomly a MailboxExportRequest is shown as "Queued" while it's already writing data or is even finished.
Most times the correct status "InProgress" and "Complete" can be retrieved, but sometimes it's stuck with "Queued" while it is NOT queueing. There is nothing in the posts above that can help resolve the situation. The problem is the server not reporting a correct status with get-MailboxExportRequest

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

question