Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Event 1009 frequently occurs in application logs for lagged database copies in Exchange Server 2016

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

View products that this article applies to.

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.

↑ Back to the top

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.

↑ Back to the top

Resolution

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

↑ Back to the top

References

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

↑ Back to the top

Keywords: Event 1009 in app logs for lagged database copies, kb, kbfix, kbqfe, kbHotfixAuto, CI105500

↑ Back to the top

Article Info
Article ID : 4515254
Revision : 5
Created on : 9/17/2019
Published on : 9/17/2019
Exists online : False
Views : 242