XFOR: MSExchangeDX Fails to Start Due to Corrupted Index After Upgrading NT to SP4

ID: Q224991

The information in this article applies to:

Microsoft Exchange Server, version 5.5
Microsoft Windows NT Server version 4.0 SP4

SYMPTOMS

After you upgrade a computer running Windows NT 4.0 Service Pack 3 (SP3) that was running Microsoft Exchange Synchronization (DXA) service to SP4, the following errors appear in the Windows NT Application Event Log and DXA service fails to start:

Event ID: 249
Source: MSExchangeDX
Description: Error -1201 occurred while trying to create a new database.

-and-

Event ID: 172
Source: ese97
Description: MSExchangeDX ((276)) The database engine is initiating index cleanup of database 'd:\exchsrvr\DXADATA\XDIR.EDB' as a result of an NT version upgrade from 4.0.1381 SP3 to 4.0.1381 SP4.

-and-

Event ID: 177
Source: ese97
Description: MSExchangeDX ((276)) Database 'd:\exchsrvr\DXADATA\XDIR.EDB': The secondary index 'DisplayName_index' of table 'MapTable' is corrupt. Please defragment the database to rebuild the index.

CAUSE

After you apply Windows NT 4.0 SP4, you need to rebuild the indexes of the DXA database to start the DXA service, because the UNICODE sort order is changed in Windows NT 4.0 SP4. This symptom happens because the DXA doesn't rebuild indexes of DXA database automatically when the DXA service is started after upgrading the Windows NT version.

RESOLUTION

If you defragment the DXA database, indexes will be rebuilt and the DXA will start successfully.

Additional query words:


Keywords          : 
Version           : winnt:4.0 SP4,5.5
Platform          : winnt 
Issue type        : kbprb

Last Reviewed: May 13, 1999