5 Frequent Errors encountered by Exchange users.

Exchange Server is one of the most recommended Server application developed by Microsoft. However there are many other Sever applications available but the supremacy of Exchange is un-challengeable. User finds Exchange extremely easy to maneuver but like other Server applications it too suffers from large number of errors and harmful events. But most of these errors are simple and can be tackled even with novice knowledge. Here in this article I will cover some of the most common and frequent error messages faced by the Exchange user.

Stop carrying-on with Error 550

Simple Mail Transfer Protocol (SMTP) is collection of communication protocol, which allows user to share information between multiple servers. Today most of the email technology is developed to utilize SMTP while sending e-mails as it is applicable for outgoing messages. The technology involved in SMTP generates a code which makes the communication between servers extremely convenient. The code is basically part of message that is differentiated into various categories which other server can easily understand. The e-mail send by the user involves information about sender/receiver, message heading and body. Considering user’s prospective, they see an interactive interface of the e-mail software. Once the message is on transmission channel, it is divided into multiple strings of text. These texts are related to each other via codes which are specifically dedicated to particular section. On the receiver end, the server software demodulates the codes and display message in a properly sequenced format.  

Ways to backup Exchange database

Microsoft Exchange Server is the most favoured server application only because of simple but effective technology used in it. It has been observed that user generally takes very less time in-order to become fluent in Exchange functionality comparing to other server side application. Basically the file system of Exchange holds two types of files. Priv.edb holds user’s mailbox data and Pub.edb keeps user’s general data. Safety is major aspect of any organisation, it has become utmost priority to secure data in today’s business environment where every transaction or information sharing has become digital. Therefore it is advisable to the user to maintain regular backup of their crucial data to counterattack emergency situation. There are various types of ways by which user can perform backup operation:

Solving Exchange Server Error – 1019 during Hard Recovery

MS Exchange Server is designed to store and serve the data to millians of users. It is quite well known that Exchange database (EDB) files often get damage and corrupted due to various reasons such as Virus attack, Dirty Shutdown, Hardware failure, abrupt application and physical damage to storage media etc. In this situations, when EDB file gets corrupt or damaged, MS Outlook restricts accessing user's emails and other items from it. To solve this issue you need Exchange Repair solution.

Microsoft has availed the users with an inbuilt utility -eseutil/p . This utility provides two modes of recovery : hard recovery and soft recovery. Soft recovery is the process in which transaction logs are replayed and database exist as offline backup. In hard recovery transaction log is replayed and the online backup of database is used.

How to Solve 'Unable to write a shadowed header for the file' Exchange Server Error?

Consider a practical working situation, when you try to carry out the hard recovery of MS Exchange Server, you might come across error -1019 on the screen. After this error message, you may find the following even ids:

Event ID: 0
Source: ESE97
Type: Error
Category: Performance
Description: (252) Unexpected Win32 error: 0x3E6
Event ID: 122
Source: ESE97 How to Solve 'Unable to write a shadowed header for the file' Exchange Server Error?

Type: Error
Category: Logging/Recovery
Description: (252) Unable to read the log. Error -1022.
Event Id: 0
Source: ESE97
Type: Error
Category: Logging/Recovery
Description: (252) error -1019

Above error message and Event IDs and indicate that the database is severely corrupted and it can not be repaired using hard recovery process. After this situation of Server, the Exchange Repair job gets terminated and the last transaction log file, which is replayed, is altered and damaged.

In order to solve this issue you need to repair corrupt exchange database file with the help of third party EDB Repair tools. These Exchange Server repair software are particulary developed with the high end scanning algorithm to retrieve all items of the exchange database file. With interactive graphical user interface and non destructive design, theses tools are completely safe to use and perform fast EDB Recovery.

Stellar Phoenix Mailbox Exchange Recovery is the best and most excellant option to sort out most of the EDB corruption, damage problems. The edb repair software is compatible with Windows 7, Vista, Server 2003, XP, and 2000. This easy to use Exchane server recovery utility supports MS Exchange Server 5.5, 2000, 2003, 2007 and 2010.

Other Related Post:

• How to Solve 'Unable to write a shadowed header for the file' Exchange Server Error? 

• How to prevent physical corruption

Troubleshooting Error 'JET_errKeyDuplicate Illegal duplicate key' in Exchange Server

The Exchange database contains all the contacts, emails, file folders and a lot of other user information. There are some corruption problems can occur in Exchange Database file due to antivirus scanning, hardware failure, log file issues, database shutdown, system dirty shutdown etc. To ensure a speedy EDB recovery and smooth functioning of the the server, You need to use Third party Exchange EDB Recovery tool.

Unable to mount MS Exchange Server 2007 database...it could be corrupt

Are you unable to mount EDB (Exchange Database) database file on the MS Exchange Server 2007 system that is being used in your organization? If yes, then there is a very prominent possibility that the EDB file is corrupt thereby disabling you from mounting it. In such cases, you should try to find out the exact cause of corruption and try to eradicate that issue. In case, nothing is succeeding then you should use a professional Exchange repair software to recover the trapped data.
Consider a similar situation in which you are unable to mount the database on MS Exchange Server 2007. The following error message is displayed:

“An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.
ID no: c1041724
Exchange System Manager”

In addition, when you check the error log the following event is logged:

“Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 486
Description: Information Store (3932) First Storage Group: An attempt to move the file "E:\Program Files\Exchsrvr\mdbdata\E00.log" to "E:\Program Files\Exchsrvr\mdbdata\E000080A.log" failed with system error 2 (0x00000002): "The system cannot find the file specified." The move file operation will fail with error -1811 (0xfffff8ed).”

Cause:

You may have run the eseutil /p command on the damaged databases. This problem has occurred because the transaction log files were not removed during the process.

Resolution:

First of all, you should check whether eseutil was run on this system at all or not by performing the following steps:
1.Click Start | Run.
2.Enter 'CMD' in the 'Run' box and press 'Enter' key. The Command Prompt window will be displayed.
3.Enter the following command:
4.c:\program files\exchsrvr\bin\eseutil /mh "c:\program files\exchsrvr\mdbdata\name of Exchange database.edb"
5.Check the repair count field. If it is 0, then the eseutil /p command was not run. For a non-zero count, eseutil /p command was run on the database.

Now, you can transfer the transaction log files to another folder if the database is in a clean shutdown state. To check this condition, you should perform the following steps:

1.Click Start | Run and enter 'cmd' in the 'Open' box and click OK.
2.To check the private information store, enter the following command in the Command Prompt:
3.c:\program files\exchsrvr\bin>eseutil /mh "drive:\program files\exchsrvr\mdbdata\priv1.edb"
4.To check the public information store, enter the following command in the Command Prompt:
5.c:\program files\exchsrvr\bin>eseutil /mh "drive:\program files\exchsrvr\mdbdata\pub1.edb"
6.Analyze the consistency check results. If the database is consistent, then all the transaction log files are moved to the information store.
7.Transfer all the log files from the directories to a backup folder.
8.Now try to mount the database. It should run fine now.


In the event of still unable to mount the database, the only way of resolving this problem is to use a third-party MS Exchange repair software. These tools are highly interactive in nature that do not damage the EDB files while scanning them.

The best Exchange repair software among all the available tools is Stellar Phoenix Exchange Server Recovery that repairs corrupted EDB files integrated in MS Exchange Server 5.5, 2000, 2003, and 2007. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this Exchange Server repair tool is able to extract individual user mailbox in the form of separated PST files.

For more visit at: http://www.ms-exchange-server-repair.com/

Restoring corrupt EDB file in MS Exchange Server 2007

MS Exchange Server is the server side of the client-server, collaborative application from Microsoft. It ably provides standard email features such as emails, contacts, notes, tasks, calendar items, etc. In addition, it provides you the option to access Exchange Server mobile devices and various web-based browsers. It may be notable that the server information is stored in an EDB (Exchange Information Store Database) file. At times the EDB file may get corrupt due to which you are unable to mount the Exchange Server database. These situations may occur due to various reasons such as abruptly exiting the Exchange Server, virus infections, corruption in the database header, hardware issues, etc. Such cases can be handled by using certain in-built methods. If you are not able to resolve the problem, then you should use an EDB Repair Software to repair the corrupted EDB file.

Consider a scenario wherein you have Microsoft Exchange Server 2007 running in your organization. When you try to mount the database that is running on the Server, you are unable to do so. An error message is displayed, that is:

“An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.
ID no: c1041724
Exchange System Manager”

Cause:

There could be the following causes for the aforementioned error message:

1. The eseutil /p command was executed on corrupted databases and the log files were not removed during the process.
2. The eseutil command was executed for an incorrect logfile base as shown in the following example:
eseutil /r three-character logfile base name

Resolution:

To resolve this problematic situation, you should perform the following methods for each of the mentioned cause:

1.Resolution for Cause 1: To do this, you should ensure two things:

A) Whether the eseutil /p command was run: This can be done by using the following command in the Command Prompt:
“c:\program files\exchsrvr\bin\eseutil /mh "c:\program files\exchsrvr\mdbdata\name of Exchange database.edb”
i. If the repair count is 1, then this command was run on this database.

B) If the database is in a clean and consistent state: To do this, you should perform the consistency check on the databases. If the database is consistent, then you should move the log files to a backup folder and then mount the databases.

2. Resolution for Cause 2: You should provide the correct parameter to run the eseutil command. For example,
“eseutil /r e00”

Once you perform the mentioned methods, try to mount the database. You will that the problem is now rectified. However, if it is not so then you should use a third-party Exchange Database Repair to extract the corrupted EDB files. Such .EDB repair tools are read-only in nature and are able to convert the EDB files to independent PST files using fast yet sophisticated scanning algorithms.

Stellar Phoenix Exchange Server Recovery is a software that performs Exchange Recovery of corrupted EDB files. It is able to perform repair edb by converting the Exchange mailboxes into equivalent PSTs for each user.

Repairing oversized corrupt EDB file in MS Exchange Server 2003

Microsoft Exchange Server is the server-side of the client-server product by Microsoft. It provides support for emailing, calendar entries and mobile- and web-based access to exchange information. All such information is stored in an EDB (Exchange Information Store Database) file. However, sometimes the EDB file can get corrupt due to which you are unable to mount the mailbox. Corruption situations can arise due to various reasons such as virus infections, human errors, database header corruption, quitting Exchange server unexpectedly, etc. In such cases, you should take appropriate corrective measures to rectify the situation. However, if you are unable to do so, then you should use a third-party Exchange Repair software to do the needful.

Consider a scenario wherein you are not able to mount Microsoft Exchange Server 2003 Standard Edition mailbox. The event ID is logged in the Application Event Log:

“Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 1112
Description: The database "Mailbox Store (Server Name)" has reached the maximum allowed size. Attempting to unmount the database.”

Cause:

The cause of this erroneous situation is that the EDB file has corrupted as its size has exceeded the permissible size of 16 GB.

Resolution:

To resolve the situation:

1. Upgrade to Exchange Server 2003 SP2 as it has got size limit of 75 GB.

2. Perform the following tasks if you are an administrator:
     a)Increase the database size limit temporarily by 1 GB.
     b)Remove the not so required database content.
     c)Defragment the database to reduce it to the permissible database size limit.

3. Mount the database in a recovery storage group by using the Recovery Storage Group feature. Then, you can use the MS Exchange Merge Wizard (Exmerge.exe) to extract the mailboxes from the database.

However, if you still are unable to resolve this issue then you should use a third-party Exchange repair software to repair the EDB file. Such tools are able to repair the EDB file without overwriting the original contents and by using fast yet sophisticated scanning algorithms.

Stellar Phoenix Mailbox Exchange Recovery is an MS Exchange repair software that enables you to repair corrupt EDB files. It scans the corrupted EDB file, repairs it, and saves it at a user-specified location. This Exchange repair software recovers different mailboxes in a separate PST files. This software supports Exchange Server 5.5, 2000, 2003, and 2007. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

Inconsistent Database Backup when Exchange Server is Running

Exchange Server databases are consisted of .edb files (database files) and .log files (database logs). All the transactions that occur for Exchange databases are first written to .log files before actually been written to database files. A database is inconsistent if all transaction log files have not been committed to the database files. But if you shut down the information service, Exchange writes all the log files to .edb files and the database comes to a completely consistent state. Thus, if you backup the database while information service is running, it will not be consistent. If your EDB files become corrupt and you try to restore from such a backup, it will give errors and the information service might fail to start. This creates an unavoidable situations of using an EDB Repair solution for your corrupted database files.

For example, consider your Exchange database files are corrupted. When you try to start Exchange Server services after restoring from a backup, you may encounter the below error in application log or on screen:


“Error -550 has occurred”

You cannot start the Exchange Server services.

Cause

You have used the backup software when Exchange Server was online. As a result, the backup is inconsistent and has failed to perform successful restore.



Solution


To prevent such errors from occurring, you are suggested to perform the database backup after stopping all the directory and information store services. Alternatively, you can look for backup solutions that are exclusively built to perform Exchange databases' backup in online state.

However, to recover the data from corrupted database files, you need to use these tools:

1. Eseutil /r command to perform soft database recovery
2. Eseutil /p command for hard repair
3. Third-party EDB Repair Tool

The hard recovery option of Exchange deletes the corrupted pages, which is not safe. Thus, you should use EDB Repair utilities if soft recovery fails. These software bring you the most effective and safe scanning algorithms for repairing damaged Exchange databases. Due to the interactive user interface they provide, these applications are easy to implement

EDB Repair Software is a feature-rich utility that employs powerful scanning algorithms to repair a damaged Exchange database. It supports Exchange Server 5.5, 2000 and 2003. It is a safe and advanced EDB Repair Tool with impressive set of features. The tool extracts user mailboxes in individual .pst file format files without affecting the original contents and view.