WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk.
To resolve this problem, use the steps in the section titled
Rebuilding an Exchange 2000 Server with Full-Text Indexing to rebuild your Exchange server following the disaster. If the Exchange server has already been rebuilt, and Full-Text Indexing fails to function properly, follow the steps in the section
Repairing Full-Text Indexing on a rebuilt Exchange 2000 Server.
Rebuilding an Exchange 2000 Server with Full-Text Indexing
To rebuild an Exchange 2000 Server that makes use of Full-Text Indexing following a disaster, use the following steps. Detailed information on how to rebuild an Exchange 2000 Server can be found in the Exchange 2000 Disaster Recovery White Paper located at http://www.microsoft.com/Exchange.
- The Administrator must have current, valid backup sets made of the Exchange Information Stores and the Microsoft Windows 2000 Server Operating System. The Windows backup set should consist at a minimum of the entire boot partition (containing the Windows 2000 boot files), the entire system partition (containing the Windows 2000 installation folder) and the System State data (the registry, IIS Metabase, and other items) which were all backed up in the same backup job using the Windows 2000 Backup utility.
- Replace any damaged hardware in the Exchange server following the disaster. Ensure if possible that all replacement hardware in the server you are rebuilding is identical to the hardware that existed in the server that experienced the disaster.
- If you cannot boot into the Windows operating system of your Exchange 2000 server following the disaster, you may need to re-install Windows before being able to restore your Windows backup set.
- Restore all the items in your Windows backup set in one restore job.
- Install any Windows 2000 service packs and software updates that were running on the damaged server to the server you are rebuilding and any other applications (other than Exchange 2000) and dynamic data that existed on the Exchange server prior to the disaster.
- Start Registry Editor (Regedt32.exe). Locate and delete the following keys in the registry:
HKEY_LOCAL_Machine\Software\Microsoft\Search\Install
HKEY_LOCAL_Machine\Software\Microsoft\Search\1.0\Applications\ExchangeServer_instance
HKEY_LOCAL_Machine\Software\Microsoft\Search\1.0\CagalogNames\ ExchangeServer_instance
HKEY_LOCAL_Machine\Software\Microsoft\Search\1.0\Databases\ ExchangeServer_instance
HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1.0\Gather\ ExchangeServer_instance
HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1.0\Gathering Manager\Applications\ExchangeServer_instance
HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1.0\Indexer\ ExchangeServer_instance
- Quit Registry Editor.
- Run Exchange 2000 setup in Disaster Recovery mode. When Exchange 2000 setup appears, it will have the action of �Disaster Recovery� set for all previously installed components on the Exchange 2000 server being recovered. In order to insure the Microsoft Search files get reinstalled with the Disaster Recovery setup, you must first set the Microsoft Exchange 2000 component to the action of �None� and then re-set it back to �Disaster Recovery�. Once you have done this you can click on the Next button to proceed with the Disaster Recovery setup process. During the setup process you should overwrite any files that have a newer file date than the ones being copied.
- Install any Exchange 2000 hotfixes that were running on the damaged server to the rebuilt server.
- Install any Exchange 2000 service packs in Disaster Recovery mode that were running previously on the damaged server to the server you are rebuilding.
- If the drives containing the Exchange database files and log files were also lost in the disaster, restore the Exchange 2000 databases that existed on the damaged server to the server you are rebuilding.
- Reboot the rebuilt Exchange 2000 server and then recreate your Full-Text Indexes for the Exchange Information Stores that use them.
Repairing Full-Text Indexing on a rebuilt Exchange 2000 Server
If the Exchange 2000 Server damaged in a disaster has already been rebuilt using different steps than the ones listed in this article and although the Exchange databases can be mounted, Full-Text Indexing still fails to function on the rebuilt Exchange 2000 server, perform the following steps.
- Delete any current Full-Text Indexes. To do so, click Start, point to Programs, point to Microsoft Exchange, and then click System Manager. In Exchange System Manager, in the console tree, double-click Administrative Groups, and then double-click the administrative group that contains the server that has storage groups of the full-text indexes you want to remove. Under the server that has storage groups that contain the mailbox stores or public stores for which you want to remove full text indexes, right-click each storage group, and then click Delete Full-Text Index for each storage group. Close Exchange System Manager.
- Start Registry Editor (Regedt32.exe). Locate the following key in the registry:
HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\Search\1.0\Databases
- Under Databases, click ExchangeServer_instance, where instance is the server from which you want to delete full-text indexes. In the details pane, view the following string values: FileName and LogPath. FileName points to the property store used by full-text indexing. LogPath points to the folder that contains the log files and checkpoint files for the property store. Next to Log Path, under Data, locate the folder where the property store and log files are kept. Record the path to this folder, as you need it for the next step. By default, the folder is:
C:\Program Files\Exchsrvr\ExchangeServer_instance
where C:\ is the drive where Microsoft Exchange 2000 was installed and instance is the name of your server running Exchange. - In Windows Explorer, or from a command prompt, go to the folder that you recorded in the previous step.
Caution Because you are going to delete files from this folder, consider copying the contents of this folder to a safe location save the folder information in the event an error occurs while deleting the files.
Under the ExchangeServer_instance folder, delete all the contents of the Projects and GatherLogs subfolders, insuring that you do not delete the Projects and GatherLogs subfolders themselves. View the contents of the Projects and GatherLogs folders to ensure the required files are deleted. Then close Windows Explorer or the command prompt. - Locate and delete the following keys in the registry:
HKEY_LOCAL_Machine\Software\Microsoft\Search\Install
HKEY_LOCAL_Machine\Software\Microsoft\Search\1.0\Applications\ExchangeServer_instance
HKEY_LOCAL_Machine\Software\Microsoft\Search\1.0\CagalogNames\ ExchangeServer_instance
HKEY_LOCAL_Machine\Software\Microsoft\Search\1.0\Databases\ ExchangeServer_instance
HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1.0\Gather\ ExchangeServer_instance
HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1.0\Gathering Manager\Applications\ExchangeServer_instance
HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1.0\Indexer\ ExchangeServer_instance
- Quit Registry Editor.
- Run Exchange 2000 setup. When Exchange 2000 setup appears you must set the Microsoft Exchange 2000 component to the action of �Reinstall�. Once you have done this you can click on the Next button to proceed with the Reinstall setup process. During the setup process you should overwrite any files that have a newer file date than the ones being copied.
- Install any Exchange 2000 hotfixes that were running on the server previously.
- Install any Exchange 2000 service packs that were running on the Exchange server previously.
- Reboot the rebuilt Exchange 2000 server and then recreate your Full-Text Indexes for the Exchange Information Stores that use them.