Event 1009 frequently occurs in application logs for lagged database copies in Exchange Server 2016

Applies to: Exchange Server 2016

Symptoms


In Microsoft Exchange Server 2016, the Event 1009 warning message frequently occurs in your application logs for each of the lagged database copies. This issue causes SCOM to constantly report an error on the servers that have a lagged copy. Therefore, the application logs are filled up with those warning messages.

Cause


The Event 1009 warning is raised because the FeedingSkippedException is thrown when the server starts SearchFeedingController for a lagged copy. This exception is thrown if content-index state of database copy isn't healthy. Content indexing is auto suspended for lagged copies by design. This is done to reduce the load on the mailbox server. But currently, there isn't any check to disable the SearchFeedingController for lagged copies.

Resolution


To fix this issue, install the Cumulative Update 14 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016.

References


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