Enterprise Messaging System Application Microsoft Exchange Repair

An organization's local area network uses Microsoft Exchange Server 5.5 English as the intranet information collaboration platform, with the Microsoft WINNT4.0 (installed SP6a patch) as the operating system. Exchange server stores personal mailboxes for everyone and office information for each office from 98 to the present, and clients receive and view personal mail and public information through Microsoft Outlook 2000. This server is connected to UPS, set to automatically 7:30am on every day, 9:00pm shutdown.

One day, the user reports that Microsoft Outlook 2000 is not in, checked, and the network condition is normal, and the Microsoft Exchange Directory Service and its associated services on the server are on the Web Store, Microsoft Exchange message Transfer Agent, and Microsoft Exchange Event Service are not started. Try to start these services manually, can not start, reported the Winnt internal error. After inspection and analysis, excluding the event log full, hard disk space, permission settings change, etc. may cause this fault, that may be chsrvrdsadata under the Dir.edb database incomplete or fragmented too much, so decided to use the Eseutil command tool to repair. After executing the ESEUTIL/R command, the Dir.edb database was found to be incomplete (inconsistancy), then the ESEUTIL/D command was executed to defragment the database, but the database was prompted for an error. Also, Microsoft Exchange Administrator Manager cannot connect to Exchange Server, so you cannot use directory Export to pour or pour data from recipient containers. The entire Exchange Server service is completely unusable, and the data information on the Exchange Server server is extremely important to the user unit, and many important office information is on the Exchange Server server's database.

To repair the database and save a large amount of important data saved on the Exchange Server server, I have carefully analyzed the relevant event log records based on the field symptoms, consulted a large amount of relevant information using the Microsoft online Knowledge Base, and consulted an experienced expert on Exchange server, Very carefully step-by-step implementation of fault detection and repair, after two days of struggle, finally fixed the Exchange Server service, and all the directory and data information are fully restored. The specific repair steps are as follows: