Defeat Exchange errors with Exchange Recovery Tool

Microsoft Exchange Server, the most reliable, advanced and secure award winning server. Still many times it reflects some superfluous errors and these errors further lead to Exchange EDB mailbox corruption.  These pop up error messages interrupt the process of email communication and halt all server related functions. These errors even don’t allow the user to restart the Server easily.

Famous Exchange Server Errors with EDB Recovery

We all Exchange Server users know that there are some errors that come often while we work on Server machine. Here we are going to discuss some Exchange error codes with their possible cause and their solution also. Some of them are as follows:-

"Operation terminated with error -1003

0xFFFFFC15 JET_errInvalidParameter Invalid API parameter 4294966293"

Main reason behind the occurrence of this error is when any damage or corruption happens in Exchange server then the database becomes inaccessible and above error is reported. In such conditions you are allowed neither to access mailbox nor send or receive emails from Exchange database. To overcome this situation you need Exchange Server repair.

Exchange Database Recovery prevents data loss due to mortiferous Exchange Server Errors

Power failures are ineluctable both for a novel and connoisseur Exchange Server user. Like a bolt from the blue, abrupt power failures, also termed as dirty shutdown affect the Information Store causing exchange database corruption. Abnormal termination causes the Information Store to crash and is one of the key factors responsible for Exchange database (EDB file) corruption.

Information Store Service is the pivotal element of Microsoft Exchange Server whose damage or corruption eliminates the entire accessibility of the user mailbox data stored on the server. Though this fact is indubitable that emails hold inestimable value for its owner but when the Exchange Infomation Store is affected rendering the user mailbox data inaccessible, a user also looses his contacts, calendars, tasks, journals, notes, schedules and appointments which can drastically play havoc in the life of a corporate guy.

But, for every problem there exists a solution as well. A lucid solution is to restore the Exchange Server database using an updated backup. Nonetheless, a backup may not be available in certain cases, or while trying to restore the database, using the backup file, certain error messages might forestall the process.

If any of the above scenario alludes you, then the perfect solution is third party Exchange Database Recovery tool. An efficacious solution “Stellar Phoenix Mailbox Exchange Server Recovery” from a leading data recovery company joins the league of dexterous software that recover exchange database from the corrupt or damaged EDB file, owing to multifarious Microsoft Exchange Server errors.

Whether it the Information Store corruption, JET engine errors, buffer manager errors, Exchange database corruption due to a virus attack or Trojan malfunction, this adroit tool is highly compatible and supports MS Exchange Server 2010, 2007, 2003, 2000 and 5.5. Since, the software is crafted on the grounds of user-friendliness it can be used efficiently by a tech savvy and a novice user alike. Using advanced algorithms adept at recovering all the data such as, emails, contacts, attachments, journals, To-do lits, tasks, calendar items, this exchange database recovery software supports selective recovery as well. Knowing the ropes to repair Exchange Server, this utility comes with a complete user guide and a free downloadable demo version to test its efficacy.

Repairing of Exchange Server is the best option for corrupt Exchange Server

Behind corruption of MS-Exchange Server, faulty hardware is one of the major factors. Corruption in Exchange Server occurs shortly. In order to get rid of this issue, soft recovery can be used. Soft recovery is an automatic replay process of transaction log files that take place when a database is mounted again after an unexpected stop. Soft recovery employs the checkpoint file to check which transaction log file to start with it when transactions are replayed into databases sequentially. This is how; process of soft recovery helps you to make the databases up to date with all recorded transactions.

Discussed below is an event ID that is observed in the log file at a time of performing soft recovery. That, event ID appears to be like this:

“Product Name: Exchange

Product Version: 14.0 (Exchange 2010)

Event ID: 465

Event Source: ESE

Category: KHI

Alert Type: Error

Rule Path: Microsoft Exchange Server/Exchange 2010/Common Components/Extensible Storage Engine

Rule Name: Corruption was detected during soft recovery in the log file. The log file is damaged and is unusable. This may be caused by faulty hardware.”

Same error message disturbs every time while performing soft recovery. Recovery cannot be carried out smoothly.

Cause:

Reason for the occurrence of above error message is the detection of corruption in the log file while carrying out soft recovery.

Solution:

For solving the above erroneous situation, follow one or more of the below stated measures:

1) Try to perform restoration of the log file from a backup copy, perform the same if the log file defined is the current log file in use.

2) Make use of the Exchange Server database tool also known as Eseutil.exe with the /R and /A switches to recoup a database through missing log files.

However, if no proper results get found, then a third party Exchange Server Repair tool is a best solution. Several tools are easily available on Internet that is enough capable to recover Exchange Server objects, such as contacts, attachments, appointments, journal, tasks, events, etc. 

It is advised to be extra careful while doing selection of a third party tool. Same is advised because now days, a lot of third party tools are available that make fake commitments for their promotion. These tools prove harmful rather than beneficial. Stellar Phoenix Exchange Server Recovery is one of the reliable tools on which you can trust blindly.

Solving Exchange 2010 Server error “Mailbox exceeded the maximum number of corrupted items ..” ?

Microsoft Exchange server is an important application for millions of businesses around the worldwide. Exchange 2010 server is the latest features rich version of Microsoft Exchange Server and most of the users are trying to migrate from old version to Exchange Server 2010. But, sometimes when you try to move your mailboxes from a previous version to Exchange 2010 server, it shows some error messages. The reason behind these errors could be corruption of Exchange Mailbox. In this situation, you need to opt for Exchange Server Repair to get repaired and moved your mailboxes.

How to Perform Exchange Server Recovery for inaccessible data ?

Exchange Server is a popular e-mail communication server. These days, almost all big organizations are implementing it as their main mail server. When any problem occurs in Exchange Server, it logs the troubled event IDs in the application log along with their system diagnosis. In general, the reason behind most of the error messages, is the corruption of Exchange Server database and this corruption leads to the inaccessibility of Exchange Server database. Well, data loss can be overcome, if you have the latest backup of your data. However, if backup is not available, then you need to go for a third party Exchange Server recovery software.

In respect of the above issue, let us consider a practical case. Suppose, your Microsoft Exchange 2003 server has got locked for no reason. And, when you rebooted the Server, you failed to start that up. On viewing the application event log, you saw the following event IDs on the screen:

“Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9518
Date: 6/7/2005
Time: 5:56:43 PM
User: N/A
Computer: CRC2K3
Description:
Error Log file is corrupt starting Storage Group
/DC=local/DC=cr/CN=Configuration/CN=Services/CN=Microsoft
Exchange/CN=CityRealtyMail/CN=Administrative Groups/CN=First Administrative
Group/CN=Servers/CN=CRC2K3/CN=InformationStore/CN=First Storage Group on the
Microsoft Exchange Information Store.
Storage Group - Initialization of Jet failed.

Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event ID: 9175
Date: 6/7/2005
Time: 6:07:09 PM
User: N/A
Computer: CRC2K3
Description:
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are
network problems or the Microsoft Exchange Server computer is down for
maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000

Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 454
Date: 6/7/2005
Time: 5:56:43 PM
User: N/A
Computer: CRC2K3
Description:
Information Store (448) First Storage Group: Database recovery/restore
failed with unexpected error -501.”

And, when an attempt was made to mount the public folder, an error message written as below appeared on the screen:

“The database files in this store are corrupted”

Reason: The primary cause, which is responsible for the occurrence of above error message is the corruption of the Exchange Server database. Corruption occurs because of unexpected system shutdown, operating system failure, human error, application malfunction etc.

How to solve ? : In order to solve the above problem you need to apply soft repair method first. Follow the following steps to perform the soft repair process:

1) Run the following commands to check the consistency of database:
   eseutil /mh ..\mdbdata\priv.edb > mypriv.txt
   eseutil /mh ..\mdbdatapub.edb > mypub.txt

2) If any of the databases are found to be inconsistent, use the following commands to carry out the soft repair solution:

eseutil /r /ispriv
eseutil /r /ispub

3) Now use the steps listed in the MS KB article:
"How to recover from information store corruption"
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q272570

But sometimes, execution of 'ESEUTIL' utility results data loss in Exchange Server. For good results, it is better to opt for a third party Exchange Server Recovery tool. These tools have been developed to overcome the problems that occur because of corrupt Exchange Server database. It is the best alternative, when you need to perform EDB recovery for getting your lost email objects back.

Stellar Phoenix Mailbox Exchange Recovery is a self-explanatory tool that is used to perform quite efficiently. The Exchange Server recovery tool restores all your seemingly lost e-mail objects, such as contacts, attachments, e-mails, appointments, tasks, journal, events and more. The application restores the RTF and HTML messages in their original format and shows compatibility with Windows 7, Vista, Server 2003, XP and 2000. Visit Tool  http://exchange.stellarservertools.com/

How to Solve Exchange database Error -327

Exchange Database corruption is a common and major problem of Microsoft Exchange Server. There are many issues which lead to corruption in Exchange database like, database dirty shutdown, human error, hardware issues, virus infection, EDB file header corruption and network issues. In case of EDB file corruption, you are unable to mount the Exchange Server. In such situation, you should try to search the main cause of corruption and perform appropriate action to repair corrupt database.

When a Exchange Server database is corrupt or damaged, you should use your backup (if backup is available) to restore such corrupted database or run ESEUTIL utility to repair it. eseutil is a command line utility and located in the C:\Program Files\Exchsrvr\Bin folder.

Now suppose you run the ESEUTIL /D utility to defragment your Exchange database, the process fails and you might find the following error message in Application Event Log file:

“Operation terminated with error -327 (JET_errBadPageLink, Database corrupted) after seconds”.

At this moment, you might also notice that you are unable to perform any normal operation on the database and your Server being unresponsive.

Cause

The JET_errBadPageLink error generally indicates the logical corruption in database. This error might be the consequence of incorrect internal database structure.

Solution

In order to get rid of this error, you should use these methods:

* If you have the complete backup, restore your infeasible database.

* Transfer users' mailboxes to a healthy Exchange Server through 'Move Mailbox' features in Administrator tool.

* Execute ESEUTIL /P against the damaged database and check database for consistency by using the ESEUTIL /K command.

In case, the above method does not work well and problem still persists, it is suggested to use a third party Exchange database repair tool to efficiently handle the situation.

Stellar Phoenix Mailbox Exchange recovery software is a safe application that can handle all corruption scenarios including logically crashed Exchange database. Moreover, it can recover deleted user mailboxes from corrupt or damaged and inaccessible Exchange Server database. The free demo version is also available to analyze the software working and features. It supports MS Exchange Server 5.5, 2000, 2003, 2007 and 2010.

How to recover mailbox store database through Microsoft Exchange recovery tool

Logical corruption of Exchange Server database makes the saved data of Exchange Server totally inaccessible. Exchange Server objects contain data of contacts, e-mail messages, attachments, appointments, journal, tasks, events, and similar more. Exchange Server database gets corrupt or damaged because of faulty hardware, sudden system shutdown, and loss of power supply. In such data loss situation, backup helps you to restore data. If backup is unavailable or falls short to recover the database, then in such situations a third party Exchange Server Recovery tools can be used.

For further clarification of above issue. Let us consider a practical scenario. Suppose, you make a try to mount a mailbox store in a MS-Exchange 2000 server, but fails to mount it. In addition to this, you receive an error message that is:

''The database files in this storage are inconsistent
Id no: c1041739''

In addition to this, whenever you try to mount the database the following events are viewed in the application event log:

“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 465
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description: Information Store (2224) C:\Program Files\Exchsrvr\mdbdata\E00.log. Corruption was detected during soft recovery in logfile 4092:203. The failing checksum record is located at position 4117. Data not matching the log-file fill pattern first appeared in sector %6. This logfile has been damaged and is unusable”

“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 477
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description: Information Store (2224) C:\Program Files\Exchsrvr\mdbdata\E00.log. The log range read from the file "2095104 (0x00000000001ff800)" at offset 12800 (0x00003200) for -501 (0xfffffe0b) bytes failed verification due to a range checksum mismatch. The read operation will fail with error %7. If this condition persists then please restore the logfile from a previous backup.”

Cause:
Above error message is caused because of inconsistent state of the mailbox store database and public store database.

Solution:
For solving above error message, and to access data of the mailbox store database. You have to follow the below steps:

Confirm the database state by below steps:
1.Open command prompt.
2.Transfer to the Drive:\Program Files\Exchsrvr\Bin folder. This location is the default location for installation of Exchange 2000 server program files.
3.Enter the following command:
“eseutil /mh "drive:\program files\exchsrvr\mdbdata\database_name.edb"
4. Check the output to verify the database state. If the database is not in a consistent state, then you
will receive the below text in the Output:
State: Dirty Shutdown

If the database is in inconsistent state, then you can repair the database by following steps:

• Use a command prompt.
• Transfer the Drive:\Program Files\Exchsrvr\Bin folder.
• Enter the following command:
• eseutil /p "drive:\program files\exchsrvr\mdbdata\database_file_name.edb"
• Defragment and rebuild the database so that the database can be used in a production environment. To do the same, you have to enter the below command:
• eseutil /d /t:x "drive:\program files\exchsrvr\mdbdata\database_file_name.edb
• Check the database status is consistent or not by typing the following command, and can check the output:
• eseutil /mh "drive:\program files\exchsrvr\mdbdata\database_file_name.edb"

If the database is consistent, then the below text will appear in the output

• State: Clean Shutdown
• To repair the Exchange Server database, you have to execute Isinteg.exe utility. For doing the same, you have to enter the following command:
• Isinteg –s exchange_server_name –fix –test alltests
• Perform the steps 3 to 6 again for each database.
• Mount the databases.
• After the databases are mounted, perform storage group online backup.

If still the backup remains in an inconsistent state, then it is better to go for a third party Exchange Recovery tools. Several third party tools are available in the market that performs Microsoft Exchange recovery instantly. These tools have read-only and are non-destructive conduct.

Stellar Phoenix Exchange Server Recovery is an authentic edb repair tool that performs the Microsoft Exchange recovery and makes the Exchange Server database corruption free, even if it is logically corrupt. It shows compatibility with Windows 7, Vista, Server 2003, XP, and 2000. The interface of the tool is available in English language.

Troubleshooting the situation when the EDB file gets beyond 16 GB size in MS Exchange Server SP1

If you are using MS Exchange Server 2003 Service Pack 1 in your organization, then you should be mindful about its size and keep archiving the data. Because if you fail to do so, then the EDB (Exchange Database) file may soon cross its 16 GB limit, thereby making it unmountable and, also, corrupt. The Messaging Database (MDB) automatically stops functioning, and becomes unable to mount, when the mailbox reaches this 16 GB limit. But you need not worry as there are several methods that you can perform for Exchange recovery. But when these do not work, then you should surely use a third-party Exchange recovery software.

Consider a scenario in which you are unable to mount MS Exchange Server SP 1. When you check the event log, the following event IDs are logged in it:

“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.
Event Type: Warning
Event Source: ESE
Event Category: Space Management
Event ID: 445
Description: Information Store (3160) The database D:\Program Files\Exchsrvr\MDBDATA\priv1.edb has reached its maximum size of 16383 MB. If the database cannot be restarted, an offline defragmentation may be performed to reduce its size.”

Cause:

The most probable cause of this issue is that the size of the mailbox has increased 16 GB.

Resolution:

To resolve this issue, there are following methods that you can use to perform Exchange Server recovery and get the Exchange Server back on track:

You should try to upgrade to MS Exchange Server 2003 Service Pack 2 by downloading and installing the Service Pack 2. Restart the system after installing it.

If you are the system administrator in your organization, then you can employ the following steps:

 i.Increase the size limit of the database by 1 GB although temporarily.
 ii.Remove the content that you do not need or take a backup of such items.
 iii.Then, defragment the database to compact it to such an extent that it is under the specified limits of the database size.

You can use the Recovery Storage Group feature to mount the database in the recovery storage group. After that, use the Exmerge.exe tool to retrieve the inaccessible user mailboxes from the database.

If you are still unable to mount the system, then you ought to take desperate measures to recover the Exchange Server. For such cases, a third-party Microsoft Exchange recovery software proves to be the most handy resolution. Such Exchange recovery tools are so efficient and reliable that the databases remain untouched during the Exchange Server recovery.

The most trusted and recommended tool in this respect is Stellar Phoenix Exchange Server Recovery that extracts user mailboxes in the form of separate PST files from damaged EDB files. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this Exchange recovery software works on EDB files created for MS Exchange Server 5.5, 2000, 2003, and 2007.

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