XADM: You Cannot Completely Track a Message with Error C1039271

Article translations Article translations
Article ID: 309776 - View products that this article applies to.
This article was previously published under Q309776
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

You may not be able to obtain a complete track of messages that generated non-delivery reports (NDRs) and you may receive the following error message during message tracking:
The log file is damaged.
Continue with the search?

ID no. c1039271
Exchange System Manager
YES / NO
If you click YES, you receive the error message again. If you click NO, the search stops.

CAUSE

This problem can occur if a log file parsing function incorrectly interprets a carriage return (CR) on a log line as a field separator. The only field separator is a TAB.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.

Properties

Article ID: 309776 - Last Review: October 24, 2013 - Revision: 1.5
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kberrmsg kbexchange2000sp2fix kbfix KB309776

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com