When Exchange Server database won’t mount, users cannot access mailbox data and mail-flow gets interrupted.
Quick Solution
EdbMails for EDB to PST Converter is an free tool to convert online & offline corrupt and healthy EDB Files to PST, Live Exchange and Office 365.
This blog introduces common issues appearing while mounting databases and solution to fix those issues:
- Database reaches 16 GB limit:This logs Event IDs 1112 and 445. When mailbox store size of Exchange reaches 16 GB limit (Exchange 2003), Recovery Storage New group feature suggests mounting the database to a recovery storage group. You can get mailboxes by using Exchange Server 2003 version of the Microsoft Exchange Merge Wizard.
- Database is corrupted:This logs an Event ID 474, shows the presence of checksum error. You can export to new Server. You can repair and recover it with eseutil/p, eseutil /d and isinteg –fix, and also using EdbMails EDB Recovery
- The transaction log files gets deleted or modified by anti-virus software: Antivirus software is very important to maintain security of the Exchange Server. Ensure that folders contains Some folders on the server, like the folder containing the transaction logs, that should never be scanned.Event IDs 455 and 9518 will be logged in this situation. Incoming mails in the exchange server are written in a folder of exchange server transactional logs. Antivirus may regonize some of the mails as virus and purge them. This leads to Exchange server crash and data loss. Ensure that Exchange server transactional log folders are excluded from antivirus scanning.
- Exchange Server needs SeSecurityPrivilege rights that Group Policy does not have This logs an event with ids 2102, 9004, 1005, 1002, 9519, 1029, 9074, 1121, 125The SeSecurityPrivilege permission and rights is must to support Exchange security functions, including the ability to report which Windows accounts are being used to gain access to mailboxes. Ensure that you have SeSecurityPrivilege rights.
- Service pack version on a Exchange clustered Server is wrong:A service pack installation may also fail on mounting Exchange database. If your server is Exchange 2000 running in your environment, it’s a common error that occurs on clustered Exchange server. To overcome this, Ensure service pack is installed on all notes of cluster. Use rolling upgrades for service pack upgrades installation as suggested by Microsoft.
- There is no space in Exchange hard drive:In this situation Event IDs 9519, 9559, 482, 1003 will be logged.This problem can be resolved by making free disk space and mount the Exchange database. If there only exchange related files are on the disk, then you need perform defragmentation of the database file to reduce the size of the database. Check the transactional log files, if you have many transactional log files, try to free the space by deleting the logs.
You can choose EdbMails Exchange server EDB Recovery Tool which can smoothly repair damaged or corrupted Exchange Database files and restore emails, attachments, contacts, calendars, tasks, deleted items etc. having features like:
- Migrate multiple mailboxes from Exchange EDB, OST, PST to Live Exchange Server
- Mapping Mailboxes / folders from EDB file to Live Exchange Server mailbox for Exchange Server Migration
- Export all the Mailbox items such as Email, Contacts, Calendars, Tasks, Notes etc.
- Recover Exchange EDB, OST, PST File of any size
- Recover all the Mailboxes from your Exchange EDB, OST, PST file to Live Exchange Server
- Perform EDB, OST, PST to Live Exchange Migration without installing Outlook on your computer.
Quick Solution
EdbMails for EDB to PST Converter is an free tool to convert online & offline corrupt and healthy EDB Files to PST, Live Exchange and Office 365.