XADM: Cannot Find Expected Words After You Run a Full Text Index

When you enable the Full Text Indexing functionality, if you use the Advanced Find option in Microsoft Outlook to search for non-noise words after the initial full crawl has been completed, no hits are returned. This behavior may occur when you search for a word that you know is in some of the documents.

This problem can occur if the Full Text Indexing component fails to copy a schema file during Exchange 2000 Setup. If this issue occurs, you may not be warned of the error. To confirm that the schema file was copied during Setup, compare the following files:

• Setup\I386\Exchange\Bin\Srchexschema.txt on the Exchange 2000 CD-ROM
• Exchsrvr\ExchangeServer_servername\Config\schema.txt

These two files should be identical.

If the schema is wrong, you may spend days building the index, only to find that it does not work. You may experience a long diagnostic period before the wrong schema file is discovered. After you discover the problem, you must rebuild Content Indexing.

To work around this problem:

1. Copy Srchexschema.txt from the Exchange 2000 CD-ROM to Exchsrvr\ExchangeServer_servername\config.
2. Rename the file "schema.txt".
3. Delete your full text index, create a new one, and then initiate another crawl.

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

When you install Exchange 2000, a part of Setup configures the Search program. During this process, Setup copies the I386\Exchange\Bin\Srchexschema.txt file into the Search program location, and then renames this file "Schema.txt". If Setup fails to copy this file, the default search schema provided by Microsoft Search service (MSSearch) that is located in the Setup\I386\Search\Schema.txt is used.