XADM: Content Indexing Crawl May Not Stop Immediately

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

Symptoms

If an administrator tries to manually stop a full-text indexing crawl, Exchange System Manager may become unresponsive. Also, the indexing process may not stop immediately, depending on the number of documents that are being indexed. It might take two minutes or longer for the indexing process to stop. This problem is more likely to occur if thousands of documents are being indexed.

To manually stop the indexing process (crawl), you need to:
  1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
  2. Click Organization, click Administrative Groups, and then click the applicable administrative group.
  3. Click Servers, click the applicable server, click Storage Group, and then click Store.
  4. Locate the store that is being indexed, and then click Stop Population.
To manually re-index all of the data, click Start Full Population.

Cause

This is synchronous behavior. When you click Stop Population, the crawl should stop immediately, but it does not.

Status

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

Microsoft is researching this problem and will post more information in this article when the information becomes available.

Properties

Article ID: 309779 - Last Review: November 2, 2013 - Revision: 2.0
Applies to
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbnofix KB309779

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