Exchange Server Discussion Forum

Learn How to Convert EDB to PST File Using Free Utility Pledge Arlen . 16th Sep 2016 . 3 Reply

Exchange Server users are often required to access their mailboxes on MS Outlook platform. However, since Exchange Server saves the mailbox data components in EDB file format, which is not supported by MS Outlook, so the task becomes complicated. The only solution to access EDB files in Outlook environment is to convert them in Outlook PST format.

For this purpose, the best solution suggested by experts is third-party EDB to PST converter but user can also try free utility ExMerge.exe by Microsoft to get the task done. Benefits of using this utility are:

  1. Provides facility to convert single as well as multiple Exchange Server mailboxes
  2. Avails options for moving data from PST files to Exchange Server
  3. Avoid exporting the duplicate content by restricting the transfer of similar contents of a mailbox to the PST file
  4. Allows user to restore individual mailboxes instead of complete database

Steps to install and utilize ExMerge.exe:

  1.     Browse and download ExMerge.exe
  2.     Install and run the utility as administrator to configure it on your system
  3.     Log in to the Exchange account as Exchange Administrator
  4.     Open the ExMerge.exe utility on the local server
  5.     When Microsoft Exchange Mailbox Merge Wizard,, then click the Next button to initiate the conversion process.
  6.     Select the two step process between one step process and two step process
  7.     Choose Extract data option to Exchange database from Exchange Server mailbox and click Next button
  8.     Povide the name of the required Microsoft Exchange Server to extract data
  9.     Complete the process prerequisites and click Next to continue ahead
  10.     Select the database EDB files that you want to access on MS Outlook and click continue
  11.     Choose the destination PST file folder and mailbox where you want to restore converted files and click Next
  12.     The process will display a successful completion message, click on Finish button to close up the process

The above-discussed process enables user to access required EDB files on MS Outlook easily. The location and availability of ExMerge.exe utility varies from Exchange Server version to version. Here is a list of process requirements, user should consider before starting the conversion process with ExMerge.exe:

  1. User must have full access or permission to access required Exchange Server mailboxes
  2. User must possess Microsoft Outlook Client on the hosting system along with Microsoft Exchange Administrator

The process of EDB to PST conversion through ExMerge.exe is quite time consuming and involves lot of steps and precautions. Therefore, experts advise the use of third party Edb to PST converter like Kernel for Exchange Server to get the conversion done quickly and accurately. The latest version of the software possesses enhanced features than any traditional EDB converter program. It allows user to export converted files to various cloud email platforms and Servers and even allows user to transport files to on -premises locations and archive folders. User can also try the trial version of the software to assess its capabilities, before making the purchase. Read more here:


Algernon Bearded . 16th Sep 2016

Physical corruption can cause serious effect on an organization running on Exchange Server. It may corrupt total database information, and halt the ongoing organizational activities. Therefore, we have listed some indications below, which may alarm the user in advance about forthcoming disaster. Identifying and preventing Exchange Server corruption on an early stage may save database from huge loss.

How to Identify Physical Database Corruption?

  • Jet engine errors show early signs of physical corruption
  • Try creating online backup, it will verify complete database and will spot corrupted file if there is any
  • Try using inbuilt utility Esefile.exe to spot errors in database files. If the corruption is minor, then this tool can resolve it and prevent damage
  • Try another inbuilt utility Isinteg.exe to check major corruption issues in the Exchange Server database

Prevention of Physical Database Corruption

  • Use fine quality hardware components to prevent corruption issue
  •  Keep a regular check on Exchange Server configuration
  •  Verify the settings of the hardware components time to time
  • Try not to use antivirus program on administrative Exchange Server computer
  • Turn off write-back caching

These above steps would help user to keep the corruption issues away from Exchange Server.  Though these steps are capable of evading physical corruption issues but there are no sure shot chances that corruption will never ever occur, as sometimes reason of physical data corruption remains unknown. If similar case happens then user is required to fix physical data corruption issues as soon as possible to save the database from permanent damage.

Resolution to Physical Database Corruption

  • If backup Exchange Server database is regularly created, then try to restore data from there
  • Utilize native utilities Esefile.exe and Isinteg.exe to fix different level of corruption issues
  •  Use certified third party Exchange recovery software to fix the corruption issue

Best Recovery Solution

Kernel for Exchange Server recovery is the best physical corruption resolution so far, according to Exchange recovery experts. This software works instantly on any kind of issue and provides desired results in the shortest span of time. It is completely user-friendly and offers understandable interface to be utilized without requiring any external assistance. Though it follows a simple procedure but its recovery process is power packed with advanced algorithms. The software has solution for every business type, be it a large organization or a small business holding few Exchange Servers. Have a gist about its latest functions enlisted as follows:

  • Resolve EDB file error caused from physical corruption and repairs it with intact content and properties of the file
  • Facilitates the user view data by using preview feature of the software
  • Enables user to extract particular files form recovered batch of EDB files
  • Provides unlimited saving formats and options to restore the recovered EDB files
  • Fixes damaged EDB files using two different recovery modes, standard mode and advanced scan mode
  • Multiple recovered EDB file migration options to relocate files such as Office 365 and Archive mailboxes
  • Available in free version for user’s feasibility
  • Free technical assistance round the clock

To checkout more information visit here:

David Jones . 24th Jun 2016

In Exchange Server 2016, users can take the help of Recovery Database (RDB) to mount a replica of a regular mailbox database on an Exchange Server. Recovery database, which is an exclusive mailbox database allowing you to mount a restored mailbox database in order to retrieve the mailbox items as a part of the recovery operation. RDB is pretty helpful in restoring the individual items or mailboxes directly, from the available copy or backup of database. Most importantly, without making any alterations to the current data. 

Although, only the administrators have the access to this recovery database, to smoothly perform the process of restoring mailboxes using backup. Unfortunately, the end users are restricted to create new mailboxes, from Outlook or any other device or email client. During the entire process, the recovery database will not disturb the original copy of mailbox database, which is running currently. 

The complete data mounting process for Exchange Server 2016 follows a four-step procedure:  

Step1: Create the database on Exchange 2016 server
Step2: Save a database backup copy in the recovery database
Step3: Execute one or more mailbox restore requests
Step4: Eliminate the recovery database when it is no more required

Though it is a four-step procedure, but each step is still time consuming. IT experts suggests to use third party EDB file extractor to save time and money, spent over such a lengthy procedure. Exchange Recovery Tool is one of the most popular EDB file extractors among IT professionals. This software recovers the corrupted and lost Exchange database then extracts EDB file data from them effectively. It provides extensive options to extract and export EDB files data such as export data to Live Exchange Server and export data to Office 365. Moreover, the software maintains the integrity of the data and its structure during the migration process. It extracts data from EDB files and exports them to various destinations in few simple steps:

Step1: Launch Kernel for Exchange Server on your computer system. A pop-up window will appear to mention the source of exchange database
Step2: Select the required file and click next
Step3: Choose the recovery mode in between Standard scan and Advance scan in case you doubt the file to be corrupted and click Finish
Step4: After scanning process, EDB files will appear in hierarchical manner.
Step5: View the required data files using Preview option.
Step6: Choose the saving format for your EDB files and provide the destination to export them.
Step7: After choosing the saving destination, click on Finish.

So, using the third party tool is much easier and faster to extract EDB file data from Exchange Server 2016, instead of lengthy manual method. Checkout more info visit at:

Henry Polards . 9th Feb 2016
How to Resolve Database Dismounted in Exchange Server? Silvano Redarko . 7th Jan 2016 . 2 Reply

There are many business organizations that make sue of Exchange server regarding email communication. It is an advance and user-friendly email server application.

MS Exchange store all information of the users' mailboxes in exchange server database .edb files. These files allow the server to analysis the exchange EDB database.

If exchange server is corrupted or damaged due to hardware failure, jet errors, improper shutdown, file size errors, virus attacks, human errors, etc. simultaneously the EDB files get inaccessible. In fact, EDB file corruption makes it difficult for an individual to read emails, calendar, contacts and other data. If you are facing this situation, then use inbuilt ESEUTIL/repair cmdlets to repair corrupt exchange server EDB. It is an effective utility to repair your exchange database files and works with an Extensible Storage Engine. This utility is located in the EXCHSRVRBIN directory.

Use Eseutil repair utility to repair a corrupt or harmed exchange server database before repairing exchange server database takes backup of entire exchange server databases including log files, priv1, pub folder and STM files to a secure location on the system. With the help of ESEUTIL utility, you can read the header information database file in exchange server.

It is capable to fix following error like exchange server error code – 550 JET¬_errdatabasedirtyshutdown state, error code – 528 unable to mount, dirty shutdown state, etc. You can resolve physical or logical corruption and recover exchange server database mailbox items instantly.

If Eseutil utility and other manual methods fail to repair exchange database, then use third party software such Kernel for exchange recovery software to repair corrupt or damaged or inaccessible database and restore mailbox items like Inbox, Outbox, Tasks, Sent Items, Deleted Items, Draft, Journals, Calendars, Notes, Contacts, etc. The software is capable to convert EDB to PST files with all email properties like to, cc, BCC, subjects, from and time etc.

For more help visit

Silvano Redarko . 7th Jan 2016
How to repair corrupt exchange server database edb files? Estorm Andeno . 7th Dec 2015 . 3 Reply

Microsoft Exchange Server is used by many organizations as a mail server application to email communication. The exchange server provides you with a reliable and effective messaging platform for creating distribution lists, sending email messages etc.

The exchange server save every email sent or receive data on the server. The server store these emails and other data as EDB files which are useful in dealing with different corruptions of user mailbox. The EDB file is really important for operating exchange server properly. The EDB file stores rich text data like headers, text attachments and email messages of Exchange Server and each EDB file has a corresponding STM file.

Reason of EDB file corruption issues in Exchange server are:

  • JET engine errors
  • Virus attacks
  • Error Code 528
  • Hardware Failure
  • Server Crash
  • Header Corruption
  • Log Files error
  • Dirty Shutdown
  • Logical corruption
  • Human Errors

In case edb file gets corrupted due following issue, then edb files generate few error messages such as:

  • ‘The database engine found a bad page’.
  • ‘The system cannot find the path specified’.
  • ‘Error opening Message Store’.
  • ‘JET_errRecordNotFound, the key was not found’, ‘JET_errRecordDeleted’
  • ‘Unable to initialize DAO/JET DB Engine’.
  • ‘Unable to initialize Microsoft Exchange Information Store service’.
  • ‘The system cannot find the path specified’.

When an EDB file gets corrupted and become inaccessible, then you need to repair edb files with inbuilt utilities like Eseutil.exe and Isinteg.exe. This utility is capable to repair corrupted edb files and rebuild exchange server database but in situations when Eseutil and Isinteg does not offer repairing exchange server database, then you need to third party EDB repair tool to repair corrupt or inaccessible exchange server database file perfectly.

Kernel for exchange server is the trusted EDB File repair software to repair database accurately. EDB to PST converter tool is capable to repair corrupt exchange server database edb files and at the same time it even recovers deleted or lost mailbox items, Inbox, Outbox, Sent Items, Deleted Items, Draft, Journals, Tasks, Calendars, Notes etc. The software easily works on exchange server version 2016, 2013, 2010, 2007, 2003, 2000, 5.5 and 5.0, and also compatible with MS Outlook 97, 98, 2000, 2003, 2007, 2010, 2013 and 2016 versions. Read more

Resmor Amina . 7th Dec 2015
How to convert edb to pst files in exchange server? Robert Desilva . 19th Nov 2015 . 1 Reply

Microsoft Exchange database repair utility is a popular tool which offers you to repair some assistance with corrupting EDB file from harm exchange server and also migrate exchange repair software in safe mode. Exchange repair software has incredible features to migrate exchange server edb files and restore lost mailbox data. Exchange repair tool apply the best technique for inaccessible database recovery and move Exchange EDB files to PST file even client save their EDB file in Pub1.EDB or Priv1.EDB folders.

Through getting this exchange repair tool you can easily extract emails from inaccessible EDB file and migrate EDB mailbox to PST mailboxes including – Notes, Contacts, Calendars, Tasks, Journals, Attachments, Reminders, Inbox, Outbox, Sent items, Draft etc. If your exchange server database is corrupted due to server shutdown, power issues, JET errors, drive errors, corrupt header errors, server down issues, server crash incidents etc then it is capable to resolve this issue instantly.  The software smoothly runs on such MS Exchange server versions- 2016, 2013, 2010, 2007, 2003, 2000, 5.5 and 5.0.

Powerful key-features of Exchange repair tool –

  • Repair corrupt or inaccessible exchange server database
  • Convert EDB files from inaccessible EDB database into outlook PST files format.
  • Export EDB to PST with all email properties like To, Cc, Bcc, Subject etc.
  • Exchange repair tool supports ms outlook versions-  MS Outlook 2016, 2013, 2010, 2007, 2003, 2000, 98, 97.
  • The tool recover EDB mailbox data including - Notes, Contacts, Calendars, Tasks, Journals, Massages, Inbox, Outbox, Sent items, Draft, Deleted folders etc.
  • The software save edb files in other format like RTF, MSG (Unicode/ANSI), HTML, EML, Text etc
  • The software provides easy Graphical User Interface to edb files repair
  • Easily install and uninstall option is available
  • Migrate exchange repair tool by getting EDB to PST tool at reasonable cost.
  • Two important recovery mode is available like Standard Scan and Advanced Scan
  • The software supports exchange server version 2016, 2013, 2010, 2007, 2003, 2000, 5.5 & 5

For more help read -

Estorm Andeno . 19th Nov 2015
EDB to PST Converter Yanjack Son . 30th Oct 2015 . 1 Reply
How can I fix Exchange database errors? Resmor Amina . 15th Oct 2015 . 3 Reply

Exchange server database may get corrupted due to many reason like improper server shutdown, power issues, JET errors, drive errors, corrupt header errors, server down issues, and server crash incidents etc.

In case of the corruption in exchange server database massage shown.

Three most common errors:

1018 JET_errReadVerifyFailure

1019 JET_errPageNotInitialized

1022 JET_errDiskIO

You can see three type level of error in exchange sever Database.

JET database engine - database level error.

file system - page level error.

Exchange information store - Application level error.

You can perform Exchange Recovery by using Eseutil.exe utility to find and repair database level error. It can easily resolve this error in few second. Eseutil.exe is inbuilt utility of exchange server to repair corrupt database.

Page level error file system error and you can also fix it by Eseutil.exe without hassle.

If you are facing Application level error in exchange server database then use another utility named is Isinteg.exe. To check and to fix the information store databases. It can easily fix Priv.edb and Pub.edb folder.

In case Eseutil and Isinteg exe fails to repair exchange server error then try third party tool to instantly repair. Read more

Resmor Amina . 15th Oct 2015
How to repair Exchange edb file? Kenny Madden . 7th Oct 2015 . 7 Reply

To repair corrupt exchange server you should use the ESEUTIL command-line utility. In case ESEUTIL command failed due to any reason then use EDB repair tool to fix exchange server, it is sophisticated utilities and it has more capability to restore deleted or lost mailbox items.

Henri Walgor . 14th Oct 2015