Microsoft Exchange Server is an email server application used by companies to handle their email, contact and calendar data from a centralized location. The entire Exchange server data gets stored in the form of EDB files that can be many GB's in size. Any unfavorable event can cause corruption of these Exchange database files. It can make Exchange Server mailboxes inaccessible to users.
Exchange EDB file is made up of server component which is based on the standard database technique. This email server system has embedded database engine, which lays out structure of disk of the Exchange Server. Major components of EDB file are as give below:
Like other database files, Exchange server EDB database is also very susceptible to any unfavorable events occurring to your system. Exchange server administrators often come across such issues which usually occur due to virus infection, improper system shutdown, application malfunction, user errors and missing database objects. There are two main types of database corruption, which require Exchange Repair to be resolved:
To overcome such Exchange server corruption situations, Exchange provides two repair tools - Eseutil and Isinteg. These utilities help you to repair, recover and restore corrupt database in minor situations. Before applying these utilities, you must create a backup of existing EDB database if it is possible as it may harm your database. In case of severe EDB corruption issues, these utilities get fail.
When the inbuilt Exchange utilities fail, you are recommended to look for the best available alternative, Exchange Server Recovery software. It is a powerful tool that repairs highly corrupt EDB files and recovers lost data. It has two modes of Exchange EDB recovery: Standard Scan & Advanced Scan. Standard scan is a fast mode and extracts user mailboxes from a corrupt EDB database, recovers mailboxes, and then saves it to MS Outlook .PST files. Advanced scan mode is slower than the first mode, but scans the severely corrupt EDB database thoroughly, recovers it and then saves it in Outlook .PST file or to a Live Exchange Server. This mode is more effective than the first mode.
Free trial version of Exchange Server Recovery tool is available which can be easily downloaded and installed on your system. It helps you to get a fair idea about the tool' s functionality and performance. This version allows you to move 25 EDB file items per folder to live Exchange Server/ PST file/ Office 36 platform.
The error mentioned may have different causes such as data connection is lost. For this, you can test your SMTP connection using telnet. For full process, see http://technet.microsoft.com/en-us/library/bb123686.aspx. Another important reason for this error could be incorrect Outlook configuration. Check your configuration.
Also, if error persists, your EDB files might have severe corruption. Run Exchange Recovery tool and fix the corruption issues.
Exchange Error 1216 'JET_errAttachedDatabaseMismatch' can take place when you modify or remove header information assessment in the database or log files. You can try eseutil to fix this error. More info is available on Microsoft sites.
There are possible chances that your antivirus application might be interfering when you are trying to connect MS Outlook to Exchange Server. To resolve such a problem, Launch MS Outlook in Safe Mode of your Windows machine. Remove all the installed add-ins in Outlook. For doing this, go to File >> Options >> Add-ins >> COM Add-ins >> Manage >> Go >> Checkbox Clear >> OK. Also, check your anti-virus settings.
There are two ways for restoring a crashed Exchange information store:
Method 1: Removal of all affected database files and mount affected store: This method is very fast for restoring services for the user and makes the previous data available easily. However, there is a chance of data loss.
Method 2: Restore fully from backup: This methods performs a full restore of data with the help of backup data. During the restore process, user will not be able to access their mailboxes as the store will not be mounted till it the restore process gets completed.
This is a small issue of exchange server while the sender is sending a message then error code 405 indicates that server is trying to identify mail address where the mail is sending but server gets failed and resend this mail back to the sender. To resolve this issue check mail address of the user who sends it.
Exchange Server gives such error when the Log File is missing some entry. It may happen when the file is not responding due to any corruption or bad modification. Manual process to correct the error is technically complex. So you should employ an expert EDB recovery tool to solve the error.
If the database shutdowns properly, move all transaction and check point files to a different folder and try mounting again. If there is problem in database shutdown (Dirty-shutdown), perform a database repair using 'Eseutil/p' and Isenteg command-line utilities.
There are many inbuilt Exchange features for EDB to PST export. But if you are not comfortable using them, try some third. Before selecting a tool do research, and go through articles from Exchange experts.
If you are busy, you should try professional tools for EDB to PST conversion. From my experience, I recommend EDB to PST tool. It’s user-friendly, and cost-effective from my point of view.