This article was previously published under Q288668
This article has been archived. It is offered "as is" and will no longer be updated.
If you stop a Content Index service crawl by using Exchange System Manager, a "Catastrophic failure" error message that is similar to following is logged in the Gatherer log:
4/13/2000 5:42:34 PM File:\\.\BackOfficeStorage\cig.extest.microsoft.com\MBX\username\Inbox\RE%3A DOGFOOD%3A Selfhost has been postponed..EML Add Error fetching URL, (8000ffff - Catastrophic failure)
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 theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
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 1.
This is not actually a catastrophic error. The wording of the text in the Gatherer log is incorrect.
After you apply Exchange 2000 Server Service Pack 1 (SP1), the message text in the Gatherer log reads correctly if you stop a Content Index service crawl by using Exchange System Manager:
File:\\.\BackOfficeStorage\kup1Dom.extest.microsoft.com\nonmapi\test\776.txt Add Error fetching URL, (80040d54 - The filtering has been aborted because of a user action, such as stopping the crawl.)
When your server is running Exchange 2000 and Windows Clustering, if you shut down the Mssearch service (the Content Indexing service) before you shut down the Clussvc service (the Windows Clustering service), you may also receive an inaccurate catastrophic failure error message.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
264624 XADM: Content Indexing Logs Catastrophic Error When Shutting Down
270058 XADM: Using the Gthrlog.vbs Utility to View Gather Logs