XCON: Content Indexing Crawls Are Unsuccessful After You Change the Primary SMTP Domain Address

This article was previously published under Q309769
This article has been archived. It is offered "as is" and will no longer be updated.
In Exchange 2000 Server, if you change the primary Simple Mail Transport Protocol (SMTP) domain address, Content Indexing crawls may not succeed and your indexed information may not be updated. Unless you examine logs, you may not discover this behavior for some time after the SMTP change.
This behavior can occur because Exchange 2000 Server cannot automatically update the affected indexes. Exoledb does not discover the SMTP domain address change until the information store restarts.

Note that the Universal Resource Locators (URLs) of messages depend on the SMTP domain that the administrator has chosen for the Exchange site. Therefore, if you change the SMTP domain, Exchange must again crawl all documents that have been crawled for full text indexing.
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
To work around this behavior, delete the affected indexes and then recreate them by initiating a fresh full crawl. To initiate a fresh full crawl, stop and then restart the Information Store service on all Exchange 2000 Servers that host affected mailboxes.
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.

Article ID: 309769 - Last Review: 10/24/2013 08:01:09 - Revision: 1.4

  • Microsoft Exchange 2000 Server Standard Edition
  • kbnosurvey kbarchive kbbug kbexchange2000sp2fix kbfix KB309769