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:
The first step is to open the Control Panel/service and stop the Microsoft Exchange System Attendant service that is started and its associated Exchange Server service.

The second step is to replicate the Exchsrvrmdbdata Pub.edb, Priv.edb, Edb*.log, Res*.log, and Edb.chk to other places (such as F:mdbdataback).

Step three, run the setup.exe on the Microsoft Exchange Server 5.5 CD, select Remove all, uninstall the Exchange server completely, and restart the computer after uninstalling.

Step fourth, run the Setup.exe on the Microsoft Exchange Server 5.5 CD again, reload Exchange server, and when you set the organization name and Site name name during Setup, Be sure to set the same name as the Sing Woo original. After installation, you need to install the same patches as the original. When the installation is complete, open the Control Panel/service and view the services, at which time the Exchange Server-related services (Microsoft Exchange information Store, Microsoft Exchange message The Transfer Agent, Microsoft Exchange Event Service, has been started, stating that the Exchange server server is installed properly.

Step fifth, open the Control Panel/service and stop the Microsoft Exchange System Attendant service and its associated Exchange Server services.

The sixth step is to move the Pub.edb, Priv.edb, Edb*.log, Res*.log and Edb.chk in the newly installed Exchsrvrmdbdata directory to other places (such as F:newmdbtemp), to back up the Pub.edb in the second step, Priv.edb, Edb*.log, Res*.log and Edb.chk files are copied to the newly installed Exchsrvrmdbdata directory.

Step seventh, restart your computer, open the Control Panel/service, and discover that Microsoft Exchange System Attendant, Microsoft Exchange Directory Services, Microsoft Exchange The Message Transfer Agent service is started, but the Microsoft Exchange information Store and Microsoft Exchange Event Service services are not able to start. Switch to MS-DOS, and after switching to the Exchsrvrbin directory, execute the isinteg-patch command to generate a unique GUIDs (globally unique Identifiers) under the newly installed directory. You can then start the Microsoft Exchange information Store and Microsoft Exchange Event Service manually. At this point, the related services for the Exchange Server server have started normally, but after entering Microsoft Exchange Server Administrator manager, there are no Exchange Server users in containers.

Step eighth, run Microsoft Exchange Server Administrator Manager, open the menu file→new other→recipients containter, and recreate the same directory name (directory Name) of the recipient Containter.

Step nineth, select any of the service objects (such as organization, Site, configuration, and so on) in the left panel of the Microsoft Exchange Server Administrator Manager window. Then open the menu file→properties, select the Advanced tab, click the Ds/is Consistency Adjustment button, select all inconsistencies, click Adjust. Then look at the containers, when all the Exchange Server users are already displayed in their respective containers.

Step Tenth, select the user's mailbox in recipients, then open file→properties, click Primary Windows NT account, and select the appropriate Windows NT accounts from the Add User OR Group list. Now that the Exchange Server service is repaired, Microsoft Exchange clients can log on to the Exchange Server server and use the appropriate directory and information services.

During this Exchange Server server failover process, I have the following experience: First, be sure to do a backup, in case the repair is unsuccessful, can be restored; second, to make full use of event log records to analyze the possible causes of failure, and find solutions; third, Take full advantage of Microsoft's online Knowledge Base (http://support.microsoft.com/search/) to search out and issue-related articles to find out how to solve the problem.