Event ID 4017 MSExchangeIS every 15 minutes for one database

Sara Rojas 0

We are migrating mailboxes with -SuspendWhenReadyToComplete from Exchange 2016 to a new databases in Exchange 2019 CU14

No mailboxes migrated at 100% yet

Only ONE database for each node of the new DAG in Exchange 2019 generate the event ID 4017 every 15 minutes

The Timed Events Processing is delayed for database XXXXX (Oldest event: 10/23/2024 10:08:00 AM, Skipped Events: 1, Skipped mailboxes: 1)

1 answer

Jake Zhang-MSFT 6,930 Reputation points Microsoft Vendor

2024-11-04T02:51:08.2133333+00:00
Hi @Sara Rojas ,

Welcome to the Microsoft Q&A platform!

Based on your description, you are experiencing timed event processing issues during mailbox migration. Event ID 4017 indicates a processing delay, which can be due to a number of reasons. Here are a few steps you can take to troubleshoot and resolve this issue:

Make sure your Exchange server has enough resources (CPU, memory, disk I/O) to handle the migration process. Resource limitations can cause processing delays.

Verify the health of the databases involved. Use the Get-MailboxDatabaseCopyStatus cmdlet to check the status of database copies and make sure they are running properly.

Large or highly active mailboxes can sometimes cause delays. Consider temporarily reducing the load by staggering the migration of larger mailboxes.

You can try pausing and then resuming the migration batch to see if that eliminates the delay.

Please feel free to contact me for any updates. And if this helps, don't forget to mark it as an answer.

Best,

Jake Zhang
Please sign in to rate this answer.
Sara Rojas 0 Reputation points

2024-11-12T03:25:47.8833333+00:00

Hi Jake,

Thank for your help, list next my comments for each point:

1.- The new servers show in HealthChecker report acceptable resouces

2.- The output of Get-MailboxDatabaseCopyStatus indicate that everything is ok, mounted an healthy databases

3.- All move-request in each database have movestatus= autosuspended, no more mailbox are migrating or with movestatus= inprogress.

4.- My doubt is if there are solution, something else to check, before resume the batch. There is no risk if I resume the batch?

Regards

SR

Jake Zhang-MSFT 6,930 Reputation points Microsoft Vendor

2024-11-14T09:21:46.3733333+00:00

Hi @Sara Rojas ,

Thanks for the details. Based on your comments, your environment seems to be in good shape. Before you resume a batch, consider the following points:

Sometimes, specific events or mailboxes can cause delays. You can use the Get-MailboxStatistics cmdlet to identify any mailboxes with unusually high activity or large sizes that could be causing problems.

Carefully review the Application and System logs for any warnings or errors that you might have missed initially. In particular, look for any events related to mailbox moves or database operations.

Make sure that regular maintenance tasks, such as defragmentation and index rebuilds, are not interfering with the migration process. You can check the maintenance schedule using the Get-MailboxDatabase cmdlet.

Verify that there are no network issues between the Exchange servers that could cause delays. High latency or packet loss can affect the migration process.

If everything is OK and you decide to resume the batch, it should be safe to do so. The -SuspendWhenReadyToComplete parameter is designed to pause the migration at a safe point, so resuming does not pose a risk. However, monitor the process closely after resuming to ensure that there are no unexpected issues.

Please feel free to contact me for any updates. And if this helps, don't forget to mark it as an answer.

Best,

Jake Zhang

Amit Singh 4,986 Reputation points

2024-11-18T05:45:47.5166667+00:00

At this stage, as suggested by Jake, Double-check the Application and System logs for any warnings or errors related to mailbox moves or database operations. It’s important to ensure there are no hidden issues affecting the migration. If everything checks out, resuming the batch should be safe.

Jake Zhang-MSFT 6,930 Reputation points Microsoft Vendor

2024-11-19T02:16:44.13+00:00

Hi @Sara Rojas ,

Please kindly consider this comment as a warm follow up, I want to know if your problem has been solved. If you still have any other questions, please feel free to comment here and I'm glad to provide further support.If the above info is helpful to this question, you can click "Accept Answer". Have a nice day!

Best,

Jake Zhang
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Event ID 4017 MSExchangeIS every 15 minutes for one database

1 answer

Your answer