How to Fix Exchange Server 2019 StalledDueToTarget_BigFunnel Error

Learn what causes the Exchange Server 2019 StalledDueToTarget_BigFunnel error and how to resolve it with some simple steps.

If you are migrating mailboxes from Exchange Server 2013 to Exchange Server 2019, you may encounter an error that says “Informational: The request has been temporarily postponed because Search is not up to date.” This error indicates that the migration is stalled due to a problem with the content indexing on the target server.

In this article, we will explain what causes this error, how to troubleshoot it, and how to fix it.

What is StalledDueToTarget_BigFunnel Error?

The StalledDueToTarget_BigFunnel error is a common issue that occurs when migrating mailboxes to Exchange Server 2019. Exchange Server 2019 uses a new architecture for content indexing called Big Funnel, which is based on Bing technology. Big Funnel improves the performance and reliability of search and indexing operations, but it also requires more resources and synchronization between the mailbox database and the search index.

Sometimes, the content indexing operations may experience a temporary interruption or a lag, which causes the migration to stall until the index is up to date. This can happen due to various reasons, such as:

• High CPU or disk utilization on the target server
• Network latency or bandwidth issues
• Database availability or replication issues
• Antivirus or firewall interference
• Corrupted or missing index files

How to Troubleshoot StalledDueToTarget_BigFunnel Error?

To troubleshoot the StalledDueToTarget_BigFunnel error, you need to check the status of the migration and the content indexing on the target server. You can use the following PowerShell commands to do so:

• To get the migration status, use the Get-MoveRequestStatistics cmdlet with the -IncludeReport parameter. This will show you the detailed report of the migration, including the stall reason and duration.
• To get the content indexing status, use the Get-MailboxDatabaseCopyStatus cmdlet with the -ContentIndexState parameter. This will show you the health of the content index for each database copy on the target server.

If the migration status shows that the stall reason is StalledDueToTarget_BigFunnel, and the content indexing status shows that the index state is Failed, FailedAndSuspended, or Crawling, then you need to fix the content indexing issue before resuming the migration.

How to Fix StalledDueToTarget_BigFunnel Error?

There are two possible ways to fix the StalledDueToTarget_BigFunnel error, depending on the cause of the content indexing issue:

• If the content indexing issue is caused by high resource utilization, network latency, or antivirus or firewall interference, you can try to resolve it by performing the following steps:
  • Reduce the load on the target server by suspending or rescheduling other tasks that consume CPU or disk resources, such as backups, maintenance, or other migrations.
  • Optimize the network performance by checking the bandwidth, latency, and firewall settings between the source and target servers.
  • Disable or configure the antivirus or firewall software on the target server to exclude the Exchange folders and processes from scanning or blocking.
  • Restart the Microsoft Exchange Search and Microsoft Exchange Search Host Controller services on the target server.
  • Resume the migration and monitor the progress and the content indexing status.
• If the content indexing issue is caused by database availability or replication issues, or corrupted or missing index files, you can try to resolve it by performing the following steps:
  • Check the health and status of the database availability group (DAG) and the database copies on the target server. If there are any errors or warnings, fix them accordingly.
  • Rebuild the content index for the affected database copies by using the Update-MailboxDatabaseCopy cmdlet with the -CatalogOnly parameter. This will delete the existing index files and create new ones from scratch.
  • Resume the migration and monitor the progress and the content indexing status.

Frequently Asked Questions (FAQs)

Question: How long does it take to rebuild the content index?

Answer: The time it takes to rebuild the content index depends on the size of the database, the number of items, and the available resources. It can take from a few minutes to several hours. You can check the progress of the index rebuild by using the Get-MailboxDatabaseCopyStatus cmdlet with the -ContentIndexState parameter.

Question: How can I prevent the StalledDueToTarget_BigFunnel error from happening again?

Answer: To prevent the StalledDueToTarget_BigFunnel error from happening again, you can follow some best practices, such as:

• Plan your migration carefully and schedule it during off-peak hours or weekends to avoid resource contention and network congestion.
• Monitor the performance and health of the source and target servers before, during, and after the migration. Use tools like Performance Monitor, Resource Monitor, Event Viewer, and Exchange Troubleshooting Assistant to identify and resolve any issues.
• Keep your Exchange servers updated with the latest cumulative updates and security patches. This will ensure that you have the most recent fixes and improvements for the Big Funnel technology.

Summary

The StalledDueToTarget_BigFunnel error is a common issue that occurs when migrating mailboxes to Exchange Server 2019. It indicates that the content indexing on the target server is not up to date and the migration is postponed until it is. To fix this error, you need to troubleshoot and resolve the content indexing issue, either by optimizing the resources and network, or by rebuilding the index files. By following the steps and tips in this article, you should be able to resume your migration and avoid this error in the future.

Disclaimer: This article is for informational purposes only and does not constitute professional advice. The author and the publisher are not liable for any damages or losses that may result from following the instructions or recommendations in this article. Always consult a qualified IT professional before making any changes to your Exchange environment.