Category Archives: Exchange server

Steps to Recover Corrupt PRIV, PRIV1, Pub & Pub1 edb and stm database files

As we know Exchange Database files are nothing more than the exact replica of user’s mailbox on MS Outlook. Moreover, this MS Exchange Server works in properly way with MS Outlook in exchange emails. And, each and every single email that is received or sent at the user’s end is primarily saved at server. Now, exchange server firstly save these emails at Exchange Database files that prove very helpful when you require dealing with accidental deletion of user mailbox.

It is very important that you manage your exchange server database properly. As an IT administrator you need to maintain a proper check upon your Information Store and at the same time validate its consistency. Now, every single storage group in an Exchange server normally includes one or more Mailbox and Public Folder stores. During installation, by default just one storage group gets created. With Exchange Server 2000 and 2003, every Mailbox store comprises a database set consisting of two files: ‘Priv1.edb’ and ‘Priv1.stm’.


Click to Enlarge the Image

The ‘Priv1.edb’ file is more like a rich-text database that primarily includes email messages, headers and text attachments corresponding to the messages. Moreover, this file also has streaming file ‘Priv.stm’ that majorly stores multi-media data like video, audio, images and other internet content files that is formatted as MIME data. The real issue with ‘Priv.edb’ file is its size keeps on increasing, which ultimately makes it susceptible of getting corrupt. In addition, Hard disk corruption and header corruption are other key causes accountable for corrupting the ‘Priv1.edb’ file. However, you don’t have to worry as there is a manual method to recover the corrupt Priv1.edb file.


Method: Recover Exchange EDB Files Manually
1.    First of all start the information store service and make a note of all the errors.
2.    Stop the information store service and then run the following commands from the ‘Bin’ folder:

“c:\exchsrvr\bin>eseutil /mh ..\mdbdata\priv1.edb”

    3.   Now, you got to verify the ‘State’ line in the output. Just ensure that all the files are consistent. In case, you find any of the files inconsistent, conduct soft recovery. And, to perform such recovery, you just got to switch to the folder where the database and log files are located. After this, just ensure you run the following at the command prompt:

‘C:\Program Files\exchsrvr\MDBDATA>”C:\Program Files\exchsrvr\BIN\eseutil” /r E00’image003

4.   Once again, it is important that you ensure the consistency of both the public information store and the private information store.
5.   If they are consistent, then skip the next step.

If you found the databases to be inconsistent, then it is important for you to do a hard repair. To do this, run the following commands:

‘C:\Program Files\exchsrvr\MDBDATA>”C:\Program Files\exchsrvr\BIN\eseutil” /p priv1.edb’image004

‘C:\Program Files\exchsrvr\MDBDATA>”C:\Program Files\exchsrvr\BIN\eseutil” /p pub1.edb’

6.   Now, it is important that you remove the log files from the ‘Mdbdata’ folder.
7.   Delete the ‘.chk’ file and the ‘Temp.edb’ file.
8.   Now, mount the databases and then, dismount them instantaneously.
9.   Finally, you got to stop the information store service and then defragment the public and private store databases as follows:

For Priv.edb:
C:\Program Files\exchsrvr\BIN>eseutil /d
C:\Program Files\exchsrvr\MDBDATA\priv1.edb image005

For Pub.edb:
C:\Program Files\exchsrvr\BIN>eseutil /d
C:\Program Files\exchsrvr\MDBDATA\pub1.edb

10.   Run the ‘Isinteg.exe’ utility just to ensure that each database is consistent.

‘C:\Program Files\exchsrvr\BIN>isinteg -s (servername) -fix -test alltests’image006
Restart the information store service.

However, after performing the manual process if you are not able to mount the database and access your precious emails, then you don’t have to worry. By taking help of a proficient third party exchange database recovery tool you can fix the issue very effectively. The application is very appropriate in repairing corrupt Exchange server database files, i.e. ‘Priv1.edb’ and ‘Pub1.edb’, and can help you retrieve the valuable user mailbox data. The competent tool can effectively restore emails, contacts, appointments, and other mailbox items. The software recreates the entire EDB database which can be mounted easily. There is no technical skill required to access this software, you just follow the instruction given by the software. Go through free version to recover emails from corrupt exchange edb file.

You can download this software from here:       images

Tagged , , , , , , , , , , , , ,

Steps to Convert Exchange EDB Mailbox to Outlook PST File Manually

Many a time I have already posted on my blog to Convert emails from one format to another by manual method. There is no doubt it required some technical skills to perform such operation, that’s way I am offering a alternative option also to do such tasks with the help of third party applications which is having a creditability in the market.  images

Now I am explaining the step by step guide to Convert or Export Exchange EDB Mailbox to Outook PST File :-

Sometimes users needs to convert edb file to pst file format to access these emails on MS Outlook Platform. MS Outlook does not understand the edb format, to Open these edb emails to MS Outlook you need to convert edb file to pst file. You cannot import the EDB files to Outlook directly as it may harm your files or you may lose you data.

Here is an free utility, called ExMerge.exe, provided by Microsoft to handle errors and issues which take place in MS Exchange Server database. This application is specially design to repair corrupt EDB file of MS Exchange server and allow you to save them into MS Outlook PST format.

Benefits of ExMerge utility are:

  • It can be used for single mailbox, multiple (selected) or all the mailboxes which are stored in the Exchange Server.
  • It can be used for exporting Exchange server data to pst file.
  • This tool prevent duclicacy of messages from exporting the same contents of a mailbox twice to the same PST file.
  • It can be used as a “brick-level backup” solution that backs up a single mailbox instead of an entire database.

How to install ExMerge utility on your system?

To install ExMerge utility on your system, you must assure your system have MS Exchange Server installed along with the admin tools of Exchange server.

First download the ExMerge.exe from the Internet. Click on ExMerge icon shown below to go to the download page:

On the download page, click on the Download button to start downloading the exe. Once the exe is downloaded successfully, install it by running it as administrator and then configure it. Once it is configured on your system, log in to your Exchange Server account with Exchange Administrator rights.

Things you need to know before using ExMerge utility:

  • Make sure you must have full permissions on all the selected mailboxes to be merged.
  • Besides this, make sure that the computer in which you are going to run ExMerge.exe, has Microsoft Outlook Client and Microsoft Exchange Administrator programs installed. As Microsoft does not support installing for Exchange Server components and Outlook on the same computer, you should not install Outlook on the Exchange Server.
  • If you are using Exchange Server 2003, being an Exchange administrator, you would have no rights to open the mailboxes. To overcome this issue, go to the Security tab of the mounted mailbox store in the recovery storage group. You will find the Exchange Administrators Group with explicit deny rights for “send as” and “receive as”. Overwrite it to give them full access and inherit the rights down to each mailbox itself.

Once the ExMerge utility is installed and configured, you are ready to run it. Start ExMerge, log on to your Exchange server and follow the steps shown below:

  1. In the Microsoft Exchange Mailbox Merge Wizard, select the procedure you would like to perform.

Click on Extract or Import (Two Step Procedure) and click on Next to continue.

  1. Now select the step you would like to perform.

Click on Step 1: Extract data from an Exchange Server Mailbox and click on Next to continue.

  1. In the Data Selection Criteria dialog box, click on Import Procedure tab.

Click on Archive data to target store and click on OK to continue.

  1. In the same dialog box, click on Message Details tab.

Enter the required things asked there and click on OK to continue.

  1. Now it is the time for Mailbox Selection. All the mailboxes which are available on the selected server, will be listed here.

Select the mailboxes and click on Next to continue.

  1. Select a folder where you want to save the Personal Folder (.PST) files.

Click on Change Folder button to select a location. Click on Next to start the process.

  1. The Process Status will be shown in this window.

Once the operation is completed successfully, click on Finish button to finish the process.

If you are using MS Exchange Server 2007, you cannot run ExMerge utility directly on the Exchange Server machine which can easily be done in the earlier versions. Besides this, it may take enough time to be completed and you would require performing many steps.

If you are unable to perform such operation and face some difficulty, I would genuinely recommend you to download the Free trial version of this application. User can perform all operation in Free version rather than to save data. Good thing is that you can see your recovered data in Free version, If you are completely sure your mailbox is recover then go for a full version license.


Tagged , , , , , , , , ,

Step by Step Guide to Import or Export Outlook PST File Manually

Normally, MS Outlook automatically stores the data such as emails messages, appointments, contacts, journal entries, tasks, and notes in these two locations:

In a personal storage folder, which is known as .pst file.

In a mailbox located on the server. Usually, mailbox is placed on a server in case you utilize Outlook with Microsoft Exchange Server.

when you access without Microsoft Exchange Server, MS Outlook 2013 stores the data that simultaneously includes all default and custom folders in a personal folder. And another important thing is that you also need to note that when MS Outlook 2013 is used with Exchange, your mailbox, data resides on the server rather than on your computer. At the time when you open MS Outlook, the program contacts the server and within a matter of a few minutes display your data.

Unless your only email account is on an Exchange Server, Outlook 2013 creates a local data file for you when you set up your profile. Depending upon the requirement, it is necessary to create a new PST file and then add or remove folders to it. When Exchange Server is the only account, Outlook stores all items in your Exchange Server mailbox.

But, you need to remember that you have to clean up all old tasks or messages that get pile up. Outlook 2013 provides an AutoArchive feature allow the user to specify how often Outlook should clean out old items, which emails items to move, and so on. If you choose to archive items rather than delete them, Outlook places them in a PST file of your choosing. Nevertheless, it is possible to restore them back easily. Manually, you got to open that set of folders and successfully copy the items back to your regular folders. In fact, the more relevant option you can opt is the usage of the import feature in Outlook to import from the archive file.

If you already have to remove your account profile and no longer have access to previously archived folders, you need to import the file back into Outlook to gain access to the files again.

Click the File drop-down menu. Navigate to the Open & Export sub-menu, and then click Import/Export.

By default Import from another program or file, get selected. If it doesn’t get selected then click Next.


Select Outlook Data File (.pst), and then click Next.


Click Browse, and then choose the PST file you want to import.
Click Open and then click Next.
If a password was assigned to the Outlook Data File (.pst), you are prompted to enter the password, and then click OK.
Set the options for importing items. The default settings usually don’t need to be changed.

The top folder — usually Personal Folders, Outlook Data File, or your email address — is selected automatically.

Include sub folders is selected by default. All folders under the folder selected will be imported.

The default selection of Import items into the same folder in matches the folders from the imported file to the folders in Outlook. If a folder doesn’t exist in Outlook, it will be created.

Select the Folder you want to import and Click Finish. You’re done!

Although you might be doing much of your work in Outlook 2013, but rarely there are occasions when you want to move data into Outlook from other programs or might even require exporting data from Outlook to another program. Just by following the steps mentioned above you could easily import and export item.

This process is little complex, minor mistake can create problem. If you want to skip all this process and save time, I would recommend a third party application, lots of available in the market. Some of available with free trial version with full features. Here is the one which you can download from here.


If you want to skip all this process and perform such task easy, accurately and fast then go for a third party application. This application surely help you. You can download this application from here:  images

Tagged , ,

Steps to Repair Corrupt Exchange Server Database

The Information Store is vital part of MS Exchange Server. It is specifically used to store crucial data in both Mailbox and Public folder. The Information Store can be looked a database of Exchange Server as it uses database files to manage the stored data efficiently. It must be quite understandable that Information Store holds users important data. Although the files kept in Information Store is always prone to number of threats. Which can severly damage the data that can result in corruption or permanent loss.

However the positive side of using Exchange Server is that, these errors can be easily tackled using various recovery techniques. For the convenience of normal and novice users, who does not possess in-depth knowledge of about Exchange Server third party recovery tools are available. Such recovery tools performs all the recovery steps on their own, the user is just required to follow the instructions on the interface. Let us discuss some of the major issues related with Information Store.

  • Fail to start Information Store.
  • Unable to stop the Information Store service and other dependent services.
  • Information Store does not respond even by using resources completely.
  • The user fails to send and receive the emails.
  • The error message can be experienced when user tries to mount the mailbox.
Possible solutions:
  • If user has clean and updated backup files then he can easily restore the data at earlier best condition.
  • In-order to repair corrupt database files user can opt for free utility provided by Microsoft known as ESEUTIL and ISINTEG. The former application is used to rebuild and repair malfunctioned backup files. The later application is used to fix the errors occurred in Information Store.
  • Go for reliable third party recovery tool.
Free utility (ESEUTIL/P) is used to perform database repair, but it removes those files which it fails to understand, there are possibilities of data loss. The only best and recommended solution for the above mentioned issue is to go for third party recovery tool. There are large numbers of recovery tools available in the market. But it is very important to choose reliable and professional tool.
Exchange Database Recovery is one such highly professional application that successfully repairs and recoups all data from damaged Exchange Server in only three simple steps. The tool has very simple and self explanatory interface which facilitates the user greatly. The free demo version of the tool can be downloaded from the respective website.
If you want to skip all this process and perform such task easy, accurately and fast then go for a third party application. This application surely help you. You can download this application from here:  images
Tagged , , , , , ,

Steps to Move Exchange Server Mailbox to Higher Version

Exchange mailbox migration becomes significant and certain to manage growing mailbox storage needs of an organization. Microsoft Exchange Server connects all user mailboxes of an organization with a domain. However, every MS Exchange Server version has its own mailbox storage capacity and therefore becomes unstable or slow after crossing the permissible limit. Microsoft has been continuously expanding email storage capacity of MS Exchange Server in the updated version. Putting Exchange mailboxes of an old Exchange Server on the upgraded Exchange version is best option for organizations to get additional storage space and ensure email security compliance.

Suppose, if your organization is using MS Exchange Server 2007 for email communication. By migrating Exchange mailboxes into higher version such as Exchange Server 2013, you can easily accommodate new users plus protect your crucial business emails from hackers and intruders. All administrative tasks on the Exchange Server 2007 including mailbox migration are performed by Exchange Management Shell. Exchange Management Shell is a part of Exchange Server 2007 Management Console that comprises of a set of Powershell scripts or cmdlets. Using move-mailbox cmdlet, you can export Exchange 2007 mailboxes over different domains of a network.

But following conditions must be fulfilled before you can move Exchange Server 2007 mailboxes into Exchange Server 2013:

1. Both Exchange Server 2007 and Exchange Server 2013 must be part of your network

2. You must possess administrative role on both source and target servers

3. You must have access rights of local administrative group of the target server

4. Both source and destination Exchange Servers are listed in the Active Directory list

5. Both source and destination Exchange Servers are running in online mode

Exchange management cmdlet to move mailbox into another server is:

get-mailbox –database <old database> | move-mailbox –targetdatabase <new database> -configurationonly:$true

You can also set the mailbox database size limit in the set-mailbox cmdlet for Exchange migration and other tasks. The powershell script line to restrict mailbox database size is:

Set-Mailbox <UserID> -ProhibitSendQuota <Value> -ProhibitSendReceiveQuota <Value> -IssueWarningQuota <Value>

Suppose you specify send limit of the mailbox database to 15 GB in the set-mailbox cmdlet then Exchange mailboxes above 15 GB will not be accessed by users and will show warning messages. You can use set-mailbox and move-mailbox cmdlets in combination also. With set-mailbox cmdlet, you shall be able to export only specific mailboxes of your Exchange Server 2007 organization. However, Exchange mailbox migration with Exchange cmdlets takes considerable time and therefore, it is not suitable for large scale migration.

Exchange Server software caters the bulk mailbox migration requirements of organizations. This Exchange mailbox migration tool lets organization to move mailboxes into lower or higher Exchange Server. It also export Exchange Server mailboxes to cloud. This Exchange mailbox migration tool also proves beneficial in moving public EDB databases of one forest into the new MS Exchange domain.


If you want to skip all this process and perform such task easy, accurately and fast then go for a third party application. This application surely help you. You can download this application from here:   images

Tagged , , , ,

How to Solve when Exchange Database Fails to Mount with (hr=0x80004005, ec=-528) Error?

Transaction log files record all the modifications to an Exchange Server database and are crucial for the proper functioning of Exchange. If you remove a log file that has not been written to the associated database, it can bring several issues, the most common being that the database may fail to mount. You can solve this problem by removing all the log files, but you first need to check the database consistency. If it exists in inconsistent state, the solution is to restore from backup or apply an EDB Repair technique.

For instance, consider a scenario in Exchange Server. You try to mount a mailbox store, but the operation fails with the below error message:

“Exchange is unable to mount the database thay you specified. Specified database: Servername\First Storage Group\Mailbox Database; Error code: mapiExceptionCallFailed: Unabble to mount database. (hr=0x80004005, ec=-528)”

The error occurs each time when you try to mount the store. As a result, all the clients connected to server are disconnected.


The above error can occur if you remove a (or more) log file, which has not been committed to the database yet.


To solve this issue, you need to move the transaction log files to a different folder. For this, follow the steps mentioned underneath:

1. Stop Information Store and all databases in the storage group

2. Verify the integrity of database by running esesutil /mh command, followed by database name (for example, for Mailbox Store1 database, name is Mailbox Store1.edb). Examine the ‘State’ value under its header information

3. If the database is in Clean Shutdown (Consistent) state, you can safely remove all the transaction log file and save them to a different folder. Make sure you don’t remove the current transaction log file

4. If the database is in Dirty Shutdown (Inconsistent) state, restore from the last online backup. In case backup is invalid, run eseutil /r command for soft recovery.

If this fails, you can run eseutil /p command for hard recovery or use an Exchange repair software. The former option (hard recovery) causes data loss as it deletes the corrupted pages. An EDB Repair utility can safely repair a corrupted Exchange database and provides secure data restoration.

Exchange Server Recovery is a powerful EDB Repair Tool that repairs and restores Exchange database created with Exchange Server 5.5, 2000, 2003, 2007, 2010, 2013 and 2016. The advanced EDB Repair Software extracts all user mailboxes into individual *.pst files and provides option for selective mailbox recovery. The tool is compatible with Windows 7, Vista, XP, 2003, and 2000.

If you want to skip all this process and perform such task easy, accurately and fast then go for a third party application. This application surely help you. You can download this application from here:  images

Tagged , , , , , , , , , , ,