Easily Repair Public Folder Database of Exchange 2016, 2013, 2010, 2007, 2003

  author
Written By Ashwani Tiwari
Anuraag Singh
Approved By Anuraag Singh
Published On August 23rd, 2022
Reading Time 7 Minutes Reading

In this write-up, we are going to discuss a manual and advanced solution that will help to Repair Public folder database of Exchange 2013, 2010, 2007, 2003 in an absolute way.

Exchange Server contains an agile Extensible Storage Engine (ESE) and store secure Information to facilitate effective email communication. Moreover, the Exchange Information store comprises STM and EDB files where the original mailbox data resides.

Both files, i.e., STM and EDB are divided into two categories like Private (Priv1.edb) and Public (Priv1.stm) helps the server to identify the default mailbox database storage, while Public files save all information associated with a default public store.

It simply means, the Public EDB and STM files where all actions will take place. They keep all emails, contacts, notes, attachments, etc. safe and any damage to these files will lead to data loss.

Usually, the Pub1.edb is a file which can store important email attachments and MAPI email messages. Thus, in order for some users to protect their work data, this is a file that needs to be secured from threats by repairing Corrupt Public Folder Database.

All Possible Threats Occurred in Pub1.edb

There are many of things that can damage the Public EDB or Pub1.edb file. The most common ones are listed below:

  • An unexpected power outage due to unavailability of the power supply
  • An incapable shutdown procedure during mail restoration process
  • A spontaneous hard disk sector error can lead to corrupt Pub1.edb file
  • Malicious programs such as viruses, malware or Trojans attack

Due to all above issues, MS Exchange server may be unable to perform the standard shutdown procedure quitting the database indirty shutdown or an inconsistent state. In such situations, the database is not able to isolate itself from the transaction log streams that may impact the consistency and integrity of database too. At that point, if users can restart the server, it shows the missing log files out of data which, if lost, renders the Exchange server may corrupt.

Another reason of Exchange problems includes the Jet Engine. Jet engine errors arise due to some hardware or software issues which can damage a server database at various levels including the Information Store, Exchange Server file system, Jet Database Engine, etc. According to this case, the EDB files end up has become corrupted or damaged.

Steps to Repair Public folder database of Exchange 2016, 2013, 2010, 2007, 2003

Go through the below steps that will help to restore or Repair Corrupt Public Folder Database. Let us have a look:

  • First, you should stop the Exchange Information Store services
  • Go to the Bin folder using command line interface with the following command:
eseutil /mh ..\mdbdata\priv1.edb at the command line path: C:\exchsrvr\bin>
  • After that, Press Enter key
  • Next, check if the state of database is clean or not. If users will find any type of issues, they need to perform the soft recovery after switching the folder to the desired place where log files are saved.
  • Then, run this script at the command line path
C:\Program Files\exchsrvr\MDBDATA> “C:\Program Files\exchsrvr\BIN\eseutil" /r E0
  • Again, you must check the state. If all things are still same, you must execute the hard recovery process. In the command line path C:\Program Files\exchsrvr\MDBDATA>, type the below command:
C:\Program Files\exchsrvr\BIN\eseutil" /p pub1.edb
  • Navigate to Mbdata folder and discard both files like *.chk and Temp.edb along with the log files
  • Now, mount and then dismount the database of Exchange Server and cut off the Exchange information store services.
  • Eventually, you should try to defragment Public EDB mailboxes by running the below command:
C:\Program Files\exchsrvr\BIN>eseutil /d "C:\Program Files\exchsrvr\MDBDATA\pub1.edb"
  • After that, perform the Isinteg.exe fix by typing the below command:
C:\Program Files\exchsrvr\BIN>isinteg -s (servername) -fix -test alltests
  • Exit the command prompt, and now restart the Exchange Server services to reinstall the recovery of corrupt or damaged Pub1.edb files.

However, these steps are capable to restore the Public file in most situations of damage, but, in case of severe corruption, the process may fail to public folder database.edb file. In addition, it requires a lot of technical knowledge to execute since it contains multiple command prompts. Therefore, a better solution to Repair Corrupt Public Folder Database is by employing an efficient and reliable tool.

A Feasible Approach to Restore Public Folder Database.edb

If the above-stated method does work properly, users can opt for a reliable third-party tool named as Exchange Recovery tool. It is designed in such a way to recover or repair emails from Exchange Mailboxes without any data loss. Moreover, it enables to recover Exchange Private (Priv.edb), and Public Folders (Pub.edb) and STM Files. It has an easy-to-use interface that even a novice user can understand its layout without taking external help.

Download purchase

The software support public folders and private offline/dismounted Exchange database file. It provides scan mode option that recover and repair Exchange mailbox & EDB file from corruption. The quick scan option removes minor corruption and for highly corrupted .edb file select the advance scan option.

This utility recover deleted mailbox after retention period. The advance scan mode easily recovers hard deleted Exchange EDB mailboxes and data items from loaded Exchange database file. User can use this option and recover deleted mailboxes in Exchange 2013 with no loss of data.

It supports various types of Exchange mailbox’s such as: legacy, user, archive, shared, disconnected and data items like – journals, calendars, mails, tasks, notes, contacts & export directly to Live Exchange, Office 365, and different file formats. You can also migrate public folders to Office 365 with all items.

Users can multiple and selectively migrate Microsoft Exchange emails and various data items with all mailboxes to PST, EML, MSG, EML, PDF, MBOX, HTML file formats. The tool automatically creates the export report which saves the success and fail count of exported Exchange data.

Key Features Of Professional Software

  1. Recover & Repair corrupted public and private EDB file
  2. Preview recovered MS Exchange EDB mailbox data items before conversion
  3. Maintain on-disk hierarchy and keep metadata intact of user mailboxes
  4. Provide option to remove encryption from Exchange mailbox (SMIME/OpenPGP) in batch
  5. Selectively convert Exchange EDB mailbox data using category and date filter option
  6. Support all Exchange Server, MS Outlook, and Microsoft Windows OS versions

Stepwise Method to Repair Public Folder Database Of Exchange 2016/2013/2010/2007/2003

Step 1: Download the automated wizard in your system, Install and Run it

download software

Step 2: Select the Add File button from home screen > Load corrupt offline public folder EDB file

select add file

Step 3: Click on Advance scanning mode > Click on the Add button

select advance scan

Step 4: Preview recovered & repaired EDB public folder > Click export

preview recovered corrupt edb file

Step 5: Select the Exchange Public folder > Click on the Export option > Select the browse button to set target file location > Click on the export button

click export

The Exchange EDB public folder are successfully repaired and exported to the select export option

Final Words

At certain times, the crucial data may be lost and normal users are unable to recover them back. Therefore, in this blog, we have discussed both manual and automated solution that will help to Repair Public folder database of Exchange 2013, 2010, 2007, 2003 in detail. So, users can use any approach as per their need for recovering the corrupt public folder database.edb in an efficient way.

  author

By Ashwani Tiwari

Being a Chief Technical Analyst, I am aware of the technicalities faced by the user while working with multiple technologies. So, through my blogs and articles, I love to help all the users who face various challenges while dealing with technology.