Microsoft KB Archive/887161

= Full-text indexes do not work after you rename your domain in Exchange Server 2003 =

Article ID: 887161

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition

-





SUMMARY
''After you rename your domain in Microsoft Exchange Server 2003, the content indexing service may not update your full-text indexes. This issue occurs because the registry entries that are associated with the full-text indexes are not updated when the domain name is changed.

To resolve this issue, you must use the Exchange Server MSSearch Administration tool to locate the full-text indexes and to fix the indexes that do not work.''



SYMPTOMS
Full-text indexes do not work after you rename your domain in Exchange 2003. Additionally, the following event may be logged in the Application log: Event ID : 3036

Source : Microsoft Search

Category : Gatherer

Type : Warning

Description : The crawl seed \\.\BackOfficeStorage\servername.domain.com\Public Folders in project  cannot be accessed. Error: 80150804 – A description for this error could not be found.



CAUSE
When the content indexing service is started for the first time, the distinguished name of the database is stored in the registry. If you change the domain name, the distinguished name of the database changes. However, the registry value is not updated. Therefore, content indexing no longer works.



RESOLUTION
To resolve this issue, use the Exchange Server MSSearch Administration tool to search for full-text indexes, isolate the indexes that have problems, and then fix these indexes by programmatically modifying the registry key for the start page of the index searches.

To do this, follow these steps.

Step 1: Download and install the Exchange Server MSSearch Administration tool
 Download the Exchange Server MSSearch Administration tool.

The following file is available for download from the Microsoft Download Center:

Download the MSSearch_Admin.exe package now. Open the folder where you downloaded the MSSearch_Admin.exe file, and then double-click the MSSearch_Admin.exe file. In the Choose Directory for Extracted files box, type C:\, and then click OK. An MSSearch_Admin folder is created under C:\. The extracted files are stored in this folder.

Step 2: Download and register the ads.dll file
To use the Exchange Server MSSearch Administration tool, you must register the ads.dll file. This file comes bundled with the files that are used for Variant Conversion Functions, namely the ArrayConvert.exe file.  Download the ArrayConvert.exe file.

The following file is available for download from the Microsoft Download Center:

Download the arrayconvert.exe package now.</li> Open the folder where you downloaded the ArrayConvert.exe file, and then double-click the ArrayConvert.exe file.</li> In the Unzip to folder box, type C:\ArrayConvert, and then click Unzip.</li> Click OK, and then click Close.</li> Click Start, click Run, type regsvr32 C:\ArrayConvert\ads.dll, and then press ENTER.</li> Click OK.</li></ol>

Step 3: Identify the Exchange servers that have full-text indexes
 Click Start, click Run, type cmd, and then press ENTER.</li> Change to the folder where you installed the Exchange Server MSSearch Administration tool files.</li> Type mssearch_admin /action:list /outputfile:list.xml, and then press ENTER. This will create a file named list.xml in the current working folder.</li> In Microsoft Internet Explorer, open the list.xml file that you created in step 3c. You should see a list of all Exchange computers that have full-text indexes created on them. This list includes all Exchange computers in all administrative groups in the organization. Either keep this file open, or note the Exchange computers that are listed.</li></ol>

Step 4: Fix the non-working full-text indexes on the individual Exchange computers
 At the command prompt, change to the folder where you installed the Exchange Server MSSearch Administration tool files.</li> Type mssearch_admin /action:status /exserver: /outputfile: _Status.xml, and then press ENTER.

Note  is one of the computer names from the list.xml file.</li> Open the _Status.xml output file in Internet Explorer. Header information appears under the Application Name: ExchangeServer  heading. Find the Total Error Count row. If the value for this header is not zero, the full-text indexes that have errors are listed in red under the header information.

If the value for the Total Error Count label is more than zero, go to step 4d. If the value for the Total Error Count label is equal to zero, go to step 4f.</li> At the command prompt, type mssearch_admin /action:fixup /exserver: /outputfile: _Fixup.xml, and then press ENTER.

Note  is the name of the computer that you identified in step 4c as having index errors.</li> Open the _Fixup.xml output file in Internet Explorer. Header information appears under the Application Name: ExchangeServer  heading. Find the Total Error Count and Total Errors Fixed rows. The values of these two rows should be equal. The full-text indexes that were fixed are listed in green under the header information.</li> <li>Repeat steps 4a through 4c for each Exchange computer that you noted in step 3.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
Besides performing administrative tasks, the Exchange Server MSSearch Administration tool will detect and repair one or more of the following configurations that are incorrect for a full-text index:
 * The full-text index location that is stored in Active Directory directory service is incorrect. This can occur if you move the full-text index from its default location.
 * The original index start address for the full-text index is no longer correct. This can occur if either of the following occurs after the full-text index is created:
 * The domain is renamed.
 * The primary Simple Mail Transfer Protocol (SMTP) address for the default recipient policy has changed.

<div class="references_section">