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. Message tracking logs can't be fully indexed in Exchange Server 2016

Message tracking logs can't be fully indexed in Exchange Server 2016

View products that this article applies to.

Symptoms

Assume that you try to retrieve the message tracking logs by using Exchange admin center (EAC) or the Get-MessageTrackingLog cmdlet in Microsoft Exchange Server 2016. You could notice that the Microsoft Exchange Transport Log Search service doesn't index all the message tracking logs that are available on the server. Therefore, you can't retrieve all the message tracking logs that you defined.

↑ Back to the top

Cause

This issue occurs because the wrong prefix is returned, and then the wrong IndexPercentage is used while indexing.

↑ Back to the top

Resolution

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

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

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

↑ Back to the top

Keywords: Message tracking logs can't be fully indexed, kbexpertiseadvanced, kbsurveynew, kbqfe, kbfix, kb, CI87432, kbContentAuto

↑ Back to the top

Article Info
Article ID : 4456249
Revision : 9
Created on : 8/13/2020
Published on : 8/13/2020
Exists online : False
Views : 244