Searching...
Friday, 17 August 2018

How to Export Exchange 2003 Mailbox to PST Over 2GB


MS Exchange 2003 server amongst its many compatibility features, allows Exchange Administrators to export Exchange database files to a new server or newer file formats. However, while performing the Exchange database migration, they often come across issues like “mailbox over 2 GB” when they run Microsoft suggested Exchange utility Exmerge.exe. The reason is that inbuilt programming Algorithms do not support Export Exchange 2003 EDB to PST for more than 2 GB and shows an error. To handle this gap the best feasible option is to deploy Stellar EDB to PST Converter and migrate mailboxes irrespective of their file size.

Exmerge.exe is an exchange utility used by Admins for Exchange 2003 to migrate mailboxes to PST and other file formats. However, before exporting mailbox, users need to verify the following points:

S.No.
Verify that

Outcome if not verified
1
You have necessary permissions.
If the necessary permissions are not available, then Exchange Administrator cannot apply utilities on the server
2
What is Ex-merge and how it is used?
Knowledge about the utility and its usage helps in easy and fast application

3
Pre-configure Exchange 2003 server-dependent services

Prepares Exchange server for data transfer, else migration is not successful
4
Check size of the mailbox.
If mailbox size is small, then Exchange utility concludes the export-job, smartly.

5
Verify that the mailbox is not in offline mode.
Exchange utility is not meant for data transfer for mailboxes in offline mode


Before starting with export Exchange 2003 EDB to PST, it is better to understand the Roles of Exmerge.exe utility. Following are the Roles of Exmerge:

  1. Exports Exchange 2003 server mailbox to PST
  2. Provides Graphical mode for extraction
  3. Requires several permissions and pre-configuration
  4. Server dependent utility and provides Exchange professionals with necessary Import-Export functions.

     Once you have verified and configured Exchange, execute the following steps:

  • Install and Run ExMerge.exe utility and click on Next button
  • Choose the option “Export or Import” and again click on Next button
  • An option displays stating “Select Data from Exchange Server Mailbox”. Click on the displayed message followed by Next
  •  Enter the name of server where the mailbox is to be extracted
  •  Select the location for mailbox database and checkbox for single or multiple mailboxes to export and click on Next button
  • Go to Location Selection page and click on Next button. Choose the desired destination to save PST file
  •  PST file is saved at selected location. Confirm completion of the process by confirming creation of corresponding PST file

Sometimes mailbox is not converted into PST file, due to the limitations of Ex-merge utility. Export Exchange 2003 EDB to PST process faces following limitations:

  1. PST file size restricted to 2GB. Ex-Merge utility restricts Exchange 2003 export mailbox to PST over 2 GB
  2. Cannot extract Unmounted or offline mailboxes
  3. Dependency on Live-production environment and pre-configured services
  4. Works with server’s pre-set internal configurations to run services and to set permissions
Ex-merge Exchange Utility generates the following errors when it faces either of the above mentioned limitations:
  1. Exmerge does not have required permissions to migrate selected mailboxes
  2. PST cannot be saved. Insufficient hard disk space
  3. Unmounted or corrupted Information Store
  4. Unable to mount mailboxes with corrupted emails

What is the best solution? 

Exchange Administrators always have a backup plan ready to combat any unforeseen state of affairs. One of these backup plans includes opting for a reliable software like Stellar EDB to PST Converter which can convert EDB to PST without any size-limitations. 

How does the software work?

  • Launch Stellar EDB to PST Converter Software
  • Select the EDB file from Exchange database. Alternately, Find EDB if the location is not known
  • Click on Start button and the software starts scanning of EDB file or mailbox. A progress bar shows that the scanning is in progress
  • Verify file components as the software displays a preview of all the recoverable items. All the converted mailboxes available in the EDB file are listed in the preview pane
  • Click the mailbox to export to PST
  • Go to the main menu and click on Save button and Stellar EDB to PST Saving options are displayed.
  •  Checkmark for PST, browse the destination path to save the converted PST file and click Ok button
  • Specified mailbox is converted to PST file with no restriction on file size and the process of Exchange 2003 export mailbox to PST over 2GB is successfully achieved. 

      Conclusion

Stellar EDB to PST Converter software can easily export Exchange 2003 Mailbox to PST. However, there are other features also which classifies this software as unique. The software recovers accidentally deleted offline mailboxes and supports conversion of Unicode EDB files. Software also facilitates selective conversion to save user time and effort. Save and Load scan feature allows users to save the converted file after a time gap without repeated scanning. Implementing the right tool at the right time always ensures business continuity.
Wednesday, 27 June 2018

How to Resolve "ESEUTIL failed with jet error -1811"?

While using ESEUTIL, users can sometimes face unexpected errors which can lead to complete mailbox inaccessibility. Resolving such errors is an uphill task especially since the information that appears along with the error message can be very cryptic. Stellar Phoenix Mailbox Exchange Recovery software acts as a one-stop solution for dealing with Exchange ESEUTIL errors and can play an instrumental role in bringing the Exchange server back online in such scenarios.

ESEUTIL is an easily accessible command-line utility for performing various complex tasks for the Exchange server. This inbuilt tool proves to be extremely helpful when it comes to fixing corrupted Exchange databases, defragmenting them, reducing their size, or checking their integrity. But sadly, ESEUTIL sometimes faces errors which cause it to terminate without completing its action which can cause damage to Exchange files and leave users in a soup with no access to their mailboxes and failure in executing other commands.

In such cases where ESEUTIL command fails to perform, reliable and competent software applications like Stellar Phoenix Mailbox Exchange Recovery come to the rescue and help users in overcoming their Exchange troubles. This post demonstrates this fact by describing a scenario where ESEUTIL fails with Jet error 1811 and Stellar Mailbox Recovery fixes the same quickly.

Problem Scenario – Exchange Jet Error 1811

When working with the Exchange server, initiating defragmentation procedures is a common thing. The defragmentation option makes used storage contiguous, eliminates unused storage, and reduces the database's size by compacting it. The command used for this purpose is eseutil /d.

Usually, the above mentioned command executes flawlessly and delivers what it promises. However, in rare situations, it fails with the error “Access to the source database. ‘…mdbdata\priv2.edb’ failed with jet error 1811”. This error is typical in Exchange versions 2003, 2007, 2010, and 2013. Evidently, decrypting this error message can be very difficult especially for a user with limited Exchange error handling experience. Still, there are a few things that can be done to attempt resolving Jet Error 1811.

Exchange Jet Error 1811 – Causes & Common Solutions
A quick look across Exchange forums reveals that the primary causes for Jet Error 1811 are:
  • A mismatch between Exchange log file signature and log generation number file
  • System malfunctions like interrupted installation or un-installation of an application
  • Virus / Malware infection to Exchange system files
  • Accidental Deletion of essential system files or registry information
  • Sudden shutdown of the machine due to power failure leading to corruption in the database
  • EDB file corruption owing to sundry reasons
Since the reasons behind this error can expand over such vast proportions, decoding exactly what caused it in your case can become tough. Hence, try out the hit-and-trial solutions listed below one by one to attempt resolving it.
  • Disable your anti-virus program and try mounting the Exchange database. If it works, add an exception in your anti-virus application for Exchange service files.
  • Take a backup of all Exchange log files and then move the original log files to a different folder. Thereafter, rename the file E00*.log to E00.log and perform a full restore of the Exchange database by replaying log files.
  • Restore Exchange database from a previous backed up. Thereafter, restart the Information Service
  • Look for ‘EDB*.LOG’ files in the MDBDATA directory and search for a non-broken sequential string of all the file names, numbered in hexadecimal, for example, EDB0001a.LOG to EDB0003f.LOG and EDB.LOG. If all of the files are accounted for, there might be chances that your EDB.CHK file is damaged. Locate this file and move it to some another directory. Then restart the Information Service.
  • If a particular log file is missing, all the log files that are numbered lower than the missing one will have to be deleted along with edb.log and edb.chk. After this, repair commands (eseutil /p) will need to be executed on the Exchange server. If they execute fine, next step will have to be recovery procedure using command eseutil /r.
There might be a high chance that even after you try out all the above fixes, Jet Error 1811 still exists. Such a condition is indicative of severe corruption in Exchange database files which can be fixed with the best Exchange server remedy, Stellar Phoenix Mailbox Exchange Recovery.

What to do if manual techniques fail?

If manual tricks don’t work the magic, place your trust in an application that is more accurate and proficient. Stellar Phoenix Mailbox Exchange Recovery will help you overcome Jet error 1811 and a majority of other Exchange Jet engine errors smoothly. Ranked as one of the most recommended software by MVPs, this product repairs corrupt Exchange Database (EDB) files and restores mailbox content which can be directly exported to Live Exchange or Office 365. You can also save individual email messages recovered from EDB files in a variety of formats like PST, MSG, EML, HTML, RTF, and PDF.

Through a simple 3-step procedure – select EDB file, scan-and-preview, and repair-and-recover – this software allows you to overcome the drawbacks of manual Exchange repair techniques and stay ahead of nasty issues. Equipped with a convenient GUI, this product saves your time and effort while helping you ensure that Exchange server stays problem-free. Read more about the product here: Stellar Phoenix Mailbox Exchange Recovery.

Wrapping it up

We hope that at this point you’re much more aware of Jet Error 1811, its prime causes, and ways to fix it at your end. As a general rule, keep your Exchange EDB files backed up and server software updated. Also, maintain an uninterrupted power supply to the Exchange server and add an exception for Exchange services in your anti-virus application and firewall. Lastly, keep Stellar Phoenix Mailbox Exchange Recovery handy since it is the best alternative to manual Exchange repair techniques and helps you bring Exchange back online regardless of how grave an error seems to be.
Tuesday, 8 May 2018

How to Solve Exchange Information Store Error 1053 on Startup

The Exchange Information Store is a critical server component which, if facing issues, can put the entire lot of server activities on hold. Errors like 1053 on startup can be especially problematic since they can lead to complete inaccessibility of user mailboxes and public folder databases which are parts of the Information Store. Stellar Phoenix Mailbox Exchange Recovery software is a product that can prove to be a worthy asset when trying to combat errors like this.

Introduced in Exchange 2000, the Information Store is primarily composed of mailbox and public folder databases. Exchange Information Store (IS) is a storage platform that is used to manage different types of information within Exchange server. Storage Groups are a critical component of the IS and are comprised of multiple public and private stores. It is in these public and private stores that the actual Exchange databases reside. Depending upon their type, various database components are saved within EDB and STM files. The rich text MAPI database gets saved in EDB file while STM files store streaming data along with the content that arrives from the SMTP source.

Since the health of the IS directly impacts how Exchange server works, even minor issues within it can lead to disasters. Citing the case of one of our clients here, following an Exchange server system update, they constantly faced issues where the IS would not start like it should automatically but instead, it kept throwing various error codes like Exchange server error 451, Exchange server error 452, and Exchange server error 471.
Since the IS wasn’t starting and they weren’t able to gather much information about the error from the event log, the client couldn’t proceed with their regular server activities and badly needed a quick fix. Read on to find out exactly how we helped them to overcome this issue.

Finding the real cause behind IS Error 1053

Understanding why an error happens is crucial in determining its resolution. Here are some probable causes of the Information Store error 1053:

  1. ·    Incompatible .NET Framework installation against the service pack for Exchange Server
  2. ·    Inability of Exchange System Attendant in finding any of its default containers: Exchange Enterprise Servers, Exchange Services, and Exchange Domain Servers
  3. ·      Missing or corrupt jcb.dll file in callback library
  4. ·      Unexpected system shutdown
  5. ·      Incorrectly writing data to the disk

Depending upon what the exact cause for the error is, the next section contains a list of solutions you can try out to fix it.

Solutions to Exchange IS error 1053

Note: The following fixes work to solve Exchange server error 451, Exchange server error 452, and Exchange server error 471. Try the below mentioned solutions one at a time. Move to the next fix if the previous one doesn’t work.

  • ·         Ensure that the latest updated .NET Framework is installed for Exchange
  • ·         Ensure the Exchange Storage Group exists in one of its default containers
  • ·         Copy jcb.dll file from Exchange 2003 SP2 installation disc to “Exchsrvr/bin” folder
·          Follow the below mentioned steps:

1.    Open Windows NT Event Viewer and verify the log for following services:
§  EDB file
§  MSExchangeIS
§  MSExchangePriv
§  MSExchangePub
Note: If the event log shows any other error apart from “Out of the disk” or one that suggests using “isinteg-patch” command, proceed further. Else skip to the sure-shot remedy discussed in the last section.
2.    Shut down all running Exchange services and reboot the server. Restart the server to automatically restart the IS; when that happens the IS will automatically try to restore the database into consistent state.
3.    Make a full online backup of Exchange IS database (including all EDB, STM, and LOG files)
4.    Now initiate a full restore of the backup and ensure that the “Start Services after Restore” option isn’t enabled. When the IS starts, it replays the existing log files bringing the information store to functional state and if this step is processed successfully, you can be sure that no data will be lost.
5.    Go to event log and check the log files for the EDB file. If they contain any message indicating that there was problem while replaying the log files, then open the Mdbdata folder and remove corrupt log files that. Once this is done, restart the IS.
6.    If step5 doesn’t work, initiate a full online backup. Enable “Start Service after Restore” option and select “Erase all Existing data”. This will restore data to the point when backup was last taken.
7.    Note: This step will involve the erasing of existing data in the IS. Hence proceed with caution. If you cannot afford any loss of data, skip to the sure-shot remedy discussed in the last section.
8.    Now start “Exchange Server Administrator” program, click on “Advanced” tab and run “DS/IS Consistency Adjuster”.
9.    If these steps fail to eradicate the error, then the last resort is to wipe the Information Store. To wipe out stores, backup database and delete EDB, CHK, LOG, and STM files.
Note: The process to wipe private and public IS will result in irrecoverable deletion of mailbox data and public folders. To revive the IS without any loss of data, skip to the sure-shot remedy discussed in the next section.

Sure-shot Remedy to Exchange IS error 1053

If none of the above methods work or you wish to avoid any data loss, repair Exchange EDB file using Stellar Phoenix Mailbox Exchange Recovery software. This advanced tool is undoubtedly the most sure-shot way of getting rid of problems like Exchange server error 451, Exchange server error 452, and Exchange server error 471 which stem from Information Store issues like the error 1053. Backed by powerful scanning and repair algorithms, this product helps users repair even the severest of damage and corruption in Exchange EDB files and recover the data saved within them. Find all there is to know about this product here: https://www.stellarinfo.com/edb-exchange-server-recovery.htm

Final Words
If the solutions discussed above don’t work, use Stellar Phoenix Mailbox Exchange Recovery to recover the Information Store data. Once the database has been recovered, reset the IS to give things a clean start.
Monday, 24 July 2017

How to Export large Exchange mailboxes to PST

Exchange server plays home to user mailboxes for an entire organization. With hundreds of incoming and outgoing emails per day, the size of Exchange mailboxes is bound to exceed its limits. Exporting large mailboxes to PST format is the only way to protect them from inevitable corruption. Stellar EDB to PST Converter is the ideal choice for exporting large Exchange mailboxes to PST format.

For any organization, its database is priceless. All business documents, user mailboxes, and hundreds of other entities reside within it. Thus, every possible measure is taken to safeguard it from damage. But with so much data piling up within the database for years, the size of the Exchange database file (EDB) is sure to exceed safe limits. Lest it turns corrupt, some actions must be taken to reduce the EDB file size. One of the best ways to do it is by converting the EDB file to PST format.

The difficulties of exporting large mailboxes to PST

It sounds simple in theory but exporting data from large EDB files to PST format is practically tricky. There are a lot of methods to do it but the problem lies in the large file size that needs to be converted. Usual methods that work with mailbox export fail when the size of the mailboxes exceeds a certain limit. For example:
  • Microsoft Outlook freezes while trying to export
  • Finding the correct parameter to export using New-MailboxExportRequest is challenging
  • Trying to export mailboxes larger than 5GB with the New-MailboxExportRequest command results in error 0x80040115
Thus, to accomplish the export, some workarounds need to be adopted.

Solutions to the problem

There are several ways to solve the issue:
  • Manual folder-by-folder export through Outlook
  • Exporting to separate PST files for each Exchange folder. However you should take care that each individual PST shouldn’t exceed a size of 20GB
  • Using parameters like “ContentFilter” in conjunction with “IncludeFolders” when executing the New-MailboxExportRequest command
  • Export using an all-in-one (CAS+HUB+MBX) server. For this you’ll first need to move the target mailbox on this server. Thereafter, follow these steps:
  •          a.    Create a share on CAS server
  •          b.    Use PowerShell command New-MailboxExportRequest with the MRS service running on the CAS server to translate information to PST and store it on a UNC path.
  • Split the mailbox using date ranges with the help of Search-Mailbox command and then export each smaller mailbox
  • Use a third-party product to split PST and spawn a new one when the set limit is reached. For example, when the first PST reaches 20GB, spawn a new incrementing PST and start exporting data to it.
 Recommend Third-Party Software

If none of the other techniques work and you need to go with a third-party tool to complete the job, we recommend that you use Stellar EDB to PST Converter. This professional tool extracts all vital Exchange mailbox data such as emails, contacts, attachments, etc. from online as well as offline EDB files and converts it into equivalent Outlook PST format. This handy tool can help you shed some load off old EDB files by converting them to PST format and moving them to local machines. Also, since it supports conversion of online EDB file, you won’t have to dismount the database during the process. It can thus save you from hours of server downtime and loss of productivity.

The Final Word

To avoid EDB files and mailboxes from growing extra-large in size, here’s a suggestion – instead of splitting the mailbox when it gets large, create a new journaling mailbox as the "current one" grows to 10GB.  This way, you won't need to split the mailbox later. Also, you may wish to consider using a separate journaling server and host the journaled mailboxes on it.  In any case, now you know how you can handle “export large mailboxes” problem through reliable third-party software.
Sunday, 14 May 2017

How to recover Exchange Database with log files

Developed by Microsoft, Exchange Server is one of the most widely used mail as well as a calendaring server. This popular messaging platform offers scheduling, emails, and tools for both messaging service and custom collaboration applications. With hands on this renowned application, a user can manage as well as create all communication effortlessly, be it in on the mobile device or at the workplace.
 
In the Exchange Server, one thing that plays a vital role is Transaction Log Files. It manages the complete changes record that are made in the Exchange Server. All the information i.e. to be inserted into mailbox database is first written in the Exchange Server database. If in case, any detail is missing from the log file, it results in an operation failure issue. And, as a result, a user cannot access mailbox database from EDB files. In short, log files are essential for proper functioning of the Exchange Database.
 
Let’s now look at how log files help in Exchange Database Recovery - 
 
How to Recover Exchange Database with Log Files
 
Prior to executing the Exchange mailbox database recovery, a user needs to examine whether the state of the database is healthy or is in a dirty shutdown. To run this, the user needs to use the following Eseutil/mh command:
c:\program files\exchsrvr\bin>eseutil\mh “drive: \program files\exchsrvr\mdbdata\priv1.edb”

Two Approaches to Recover Exchange Database
 
•    Soft Recovery
•    Hard Recovery
 
Soft Recovery
 
Soft Recovery is the procedure of replaying the transaction log files in a scenario when the database is re-mounted on the server that is suffering from an unanticipated halt.
During this circumstance, the soft recovery process is auto-executed by the Exchange Server through the entire pending transaction log file just by reading the checkpoint file. If in case, this auto process does not work, Eseutil commands are being used.
 
ESEUTIL / r enn/ L [path to log files] / s[ path to checkpoint file] /d [ Path to database file]/ i
 
Here r stands for recovery mode, enn for log file name prefix, /l specify path to log file, and /d specify the path to database file (it does not includes the name of the file itself). 
 
Steps are as follows:
 
•    Execute Eseutil /mh command.
•    Now, check the health of the database
•    If the state is clean shutdown, then from Transaction logs folder location, migrate all the log files and mount the stores; In case it is in a dirty shutdown state, ensure whether Logs required log files is available or not.
•    Next, check whether the required log files are in a clean state or not. To confirm this, execute Eseutil /ml “Path of the log files\log prefix”.
•    Now, if log files are healthy, use Eseutil /r <Log Prefix> /l “Path of the log files” /d “Path of the database” command and execute soft recovery— eseutil/r.
•    On successful completion of all the commands, mount the stores.

If in case, an error is generated—“Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outstanding database attachment has been detected at the start or end of recovery, but the database is missing or does not match attachment info) after n seconds”.  Then just run soft recovery using “/i” switch. This action will override the EDB-STM mismatch and resolve the error. ¬¬

Hard Recovery

 
Hard Recovery procedure uses online backup to replay log files. If, in any circumstance, the “Last Backup Set” option is set on, then the recovery process can be executed automatically. In this recovery process, there is no need of a checkpoint file as database recovery is performed using restore.env file. Adding more, in the scenario, when “Last Backup Set” option is not enabled, hard recovery is to be executed manually using Eseutil command.

Syntax to execute Hard Recovery:
 
C:\Program Files\ Exchsrvr\bin.eseutil /cc “ C:\Temp\First Storage Group “_

Here, C:\Program Files\ Exchsrvr\bin.eseutil / indicated Eseutil installed location, C:\Temp\First Storage Group “_ indicates restore.env folder location.

Note: This recovery process will only work on the restored databases from the valid backup. No other Exchange server EDB files can be recovered using it.

Steps are as follows:
 
•    Go to C:\Temp
•    Check the log restore location
•    Now, open the folder and check for the Restore.env location
•    Now,  use the copy of Restore.env location as well as logs to execute Hard Recovery
•    Go to command prompt
•    Run the Hard recovery from Bin folder using Eseutil /cc “Path of the restore.env containing folder” command
•    After a successful completion, the Restore.env folder will be empty
•    Now, stores are ready to mount

Inevitably, with hands on this manual process, an individual can recover Exchange Database with log files. However, this recovery process is a bit lengthy and is not free from manual intervention. Therefore, it becomes prone to risks. To overcome this, a third-party recovery solution would serve the purpose as it is fully automated and free from manual interference.

Based on experienced and skilled professionals, if a suggestion is to be made then, Stellar Phoenix Mailbox Exchange Recovery is a sure-shot. It is tried, tested, and an approved software solution.

About Stellar Phoenix Mailbox Exchange Recovery
 
Stellar Phoenix Mailbox Exchange Recovery is an ultimate utility designed to repair corrupt Exchange Server Database Files. This professional solution works in almost all scenarios of data loss, be it corruption, crash, damage, etc. With hands on this software, an individual can quickly repair EDB Files as well as mailbox content such as Calendars, Journals, Contacts, Emails, Attachments, Tasks, To Do List, and much more.

The overall functionality of this EDB Files Recovery tool is simple; three intuitive steps—Select, Scan, and Save. It is fast, easy, reliable, and secure. This do-it-yourself software is highly demands its impressive option sets, improved features, and amazing look & feel. Adding more, it offers you with the flexibility to save the recovered data into varying formats such as HTML, PST, RTF, EML, MSG, and PDF.

This ultimate Mailbox Exchange Recovery software supports PUB.EDB files repairing, Windows 10, 8.1, 8, 7, Vista and Windows Server 12 and 8. Additionally, it is compatible with the MS Exchange Server 2016, 2013, 2010, 2007, 2003, and 2000.

The Way Forward
 
Nowadays, Exchange is one of the most popular mail servers. This Server is used at a gigantic scale for scheduling, tools, emails, etc. Thereby, it is necessary to ensure proper functioning of the same for increased productivity as well as management. However, just like other utilities, it is also prone to getting corrupt or damaged. Here, Exchange Recovery becomes imperative.