Antidote for Exchange Server Error 8197

Microsoft Exchange Servers are deployed in establishments in copious numbers across the globe. One of the trusted solutions for handling business emails, MS Exchange Servers are the backbone of enterprises that manage vital emails and act as a repository for user mailbox and its data.

Exchange Servers succumb to corruption on the grounds of virus attack, software or hardware malfunction, abnormal termination of the Information Store Service, dirty shutdown due to power failure etc. These multifarious reasons play a major role in the corruption of Exchange Server database file (EDB).

A common error message encountered by the Exchange Server users is:

“Event Type: Error
Event Source: MSExchangeFBPublish
Event Category: General
Event ID: 8197
Date: MM/DD/YY
Time: XX:XX:XX AM
User: N/A
Computer: Server Name
Description:
Error initializing session for virtual machine Server Name. The error number is 0x80040111. Make sure Microsoft Exchange Store is running. Also, make sure that there is a valid public folder database on the Exchange server.”

The aforementioned error message appears in the application log every 25 minutes irking the Exchange User time and again by hampering his work. This error message appears due to the unbinding of the Global Catalog Server by the background tasks of the free/busy folder to process updates. The free/busy task in Exchange Server deploys Windows's Operating System's referral mechanism to locate the Global Catalog Servers, contrary to the other tasks that rely on DSACCESS mechanism. These two processes have different algorithms that results in the occurence of the Exchange Event ID 8197.

To resolve this error, find out the Global Catalog Server that is not binding here:

HKEY_USERS\.DEFAULT\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\ExchangeAdmin

The registry key should be different from this:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider\DS

By using the general connectivity troubleshooting steps for the Global Catalog Server that is unbinding, the above problem can be resolved. For more detail information about this error, you may see: http://blogs.technet.com/b/exchange/archive/2005/07/29/408394.aspx

However, if the above problem still persists, you may use a dexterous third party tool.

A trusted tool for Exchange Server repair is “Stellar Phoenix Mailbox Exchange Server Recovery”. This software supports MS Exchange Server 5.5, 2000, 2003, 2007 and 2010. Offering a clear preview of the recoverable EDB file components, this .edb repair software can be tested for its competency in the demo version. A step by step, easy to understand user guide comes with the software. This powerful tool uses extensive mechanism to perform effective recovery of vital data in cases of severe EDB file corruption. This utility also facilitates selective recovery.

How to solve Exchange Event 9175 ?

Exchange Mailbox Store is a very important component of the server and essential to proper functioning of an Exchange server. Each Exchange mailbox store is constituted of two important files named Priv.edb and Priv.stm. The EDB file is an ESE database file and also known as MAPI based database. It stores all MAPI messages, e-mail attachments and other important data. The STM file, known as streaming file, is also an ESE database file and stores primal internet content. When Microsoft Exchange Server is started, ESE determines the state of database whether it is in Consistent or Inconsistent. If ESE finds any inconsistency in Exchange database, it performs soft recovery. However, when a severe corruption occurs in a mailbox store, you will no longer be able to work with Exchange database smoothly and when you attempt to mount the database, you may get some error messages.

For example, consider a scenario wherein you are using Exchange server 2000 or 2003 and you encounter some corruption problem in your database. When you try to mount the Exchange mailbox store, you may receive the below event log description mentioned in the application event log:

Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event ID: 9175
Date: 7/9/2001
Time: 5:32:11 PM
User: N/A
Computer: XYZ
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

Causes:

Some of the reasons for the occurrence of above event are:

• Most of the time this event occurs if an Exchange Mailbox store failed to mount.
• System Attendant (SA) is attempting to make an Offline Address Book (OAB).
• Information Systems store services are stopped.
• Corruption in Exchange Mailbox store.

Solution:

You can try the following solution:

• Check whether Exchange Information Store service is running or not. If the Information store is not running, try to start it.
  

• If the Information store is working and the event is still logged. Confirm that the default Exchange mailbox store is mounted. If it is not mounted, try to mount it.
• If the Information Store is corrupt, you will need run built-in ESEUTIL/P command line utility.

If the above said repair utility fails to repair the corrupted Information Store, then you'll have to use a third-party Exchange recovery application to repair the damaged Exchange Information Store.

Such third party Exchange Server Recovery software are specifically developed to recover data from logically or physically damaged Exchange database (EDB) file. The repaired and recovered edb file can be saved at default or user's specified location.

How to Solve Event 217 and 478 In MS Exchange Server ?

Microsoft Exchange server has been using in small to large sized organization as the server side of e-mail communication systems. In case of Exchange Server crashes, storage groups and exchange databases that stores the data, are the most important component for recovery. When a corruption situation occur in database, You might observe some unexpected behavior. For example, you may not be able to backup it and the corresponding event which indicates the failure is logged in application event log file with the detail description of the cause. However, a damaged or corrupted Exchange database (.edb) file should be restored from the backup. But in the absence of backup, you need an effective Exchange Repair tool to repair and restore the same.

For example, suppose you try to perform an online backup of the ESG (Exchange Storage Group), the operation may fail and you might see the below events logging into application log:

Event 217:

Event Type: Error
Event Source:ESE
Event Category:Logging/Recovery
Event ID: 217
Date:11/23/2006
Time:10:21:32 PM
User:N/A
Computer:EXCHANGE
Description:
Information Store (5484) First Storage Group: Error (-613) during backup of a database (file drive:\Program Files\Exchsrvr\mdbdata\priv1.stm). The database will be unable to restore.

Event 478:

Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 478
Date:11/23/2006
Time:10:21:32 PM
User: N/A
Computer: EXCHANGE
Description:
Information Store (5484) The streaming page read from the file "drive:\Program Files\Exchsrvr\mdbdata\priv1.stm" at offset 7250493440 (0x00000001b029c000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 2914298788 (0x00000000adb4aba4) and the actual checksum was 4278044063 (0x00000000fefdc59f). The read operation will fail with error -613 (0xfffffd9b). If this condition persists then please restore the database from a previous backup.


Cause

Event 217 in Exchange Server illustrates backup failure and event 478 exihibits the corruption in database. Event 217 might also be occured because of "beyond end of file (EOF)" condition.

Solution

Make sure all the hotfixes and latest updates are available for your Exchange Server. In order to solve the database corruption issue, you need to perform following steps:

1. Restore the Information Store database, using last online backup
2. Attempt to transfer user mailboxes to another store, if you are using Enterprise edition of Exchange Server 2000 or 2003
3. If above solution doesn't works, try to repair the exchange database by executing eseutil /p repair command followed by eseutil /d command to defragment the database. But these command line utility deletes the pages that it encounters as corrupted. For safe MS Exchange repair, you should run EDB Repair tool that uses safe and advanced algorithms to repair and restore damaged Exchange databases.

The interface of these Exchange mail repair utilities are simple and easy to use that provides complete Exchange Server Repair results. You just need to browse or search the corrupt .edb (exchange database) file and the tool scans the damaged file entirely to repair it.


Stellar Exchange Repair is a powerful tool that provides systematic MS Exchange Server repair. It is a secure EDB Repair Software that supports Exchange Server version 2010, 2007, 2003, 2000 and 5.5. This Repair Exchange tool saves the repaired and recovered exchange mailboxes in individual .pst files, which can be directly accessed in MS Outlook. Thus the software also works as EDB to PST Converter and efficiently repairs the corrupt edb file in all corruption scenarios.

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

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/

Fixing 'Unable to Mount the Mailbox Store with error c104173c …' error in Exchange Server

Information store is the most vital component of Microsoft Exchange. When the Exchange Server is hit by corruption issues, information store also gets affected. It is made up of four database files viz Priv1.edb, Priv1.stm, Pub1.edb and Pub1.stm. When corruption occurs either Prive1.edb or Pub1.edb falls prey to it. In event of corruption, an Exchange administrator can observe various symptoms including the MS Exchange Information Store service won't start, or clients cannot send or retrieve e-mails or abrupt error messages. In order to isolate the issues, the administrator must use the updated backup copy of the database. However, if no backup is available, he should immediately switch to MS Exchange Repair solutions.

Consider a scenario, wherein, you, being the administrator, try to mount the mailbox store in Exchange System Manager, and receive the following error message:

“Unable to Mount the Mailbox Store with error c104173c The Information Store is Busy”

Cause

The above error indicates the possible corruption in one or both edb files (Priv1.edb or Pub1.edb) of information store.

Resolution

In order to troubleshoot the issue, you must perform the following Exchange Repair steps:

1. Run eseutil/mh command in order to determine if the database is consistent
2. If you get the following output 'Clean Shutdown' , move out all the log files from Exchsvrmbddata folder
3. But if you get 'Dirty Shutdown' as output, perform soft recovery by using eseutil/r
4. If database does not come to a consistent state, perform hard repair by using eseutil/p command.
5. If you use the above command, you may lose some Exchange Server data, including the messages that were contained in the log files that were not committed to the information store database. Therefore, it is a wise decision to use a third-party MS Exchange Repair application.

Such tools repair corrupt .edb files safely and employ improved scanning algorithms to recover inaccessible data in a hassle-free manner. Being-read only they do not modify the original content. Therefore, you can use them blindly and isolate the information store corruption issues efficiently.

Stellar Phoenix Mailbox Exchange Recovery is a powerful and reliable application which repairs corrupt .edb files and restores the mailboxes as individual PSTs. Compatible with Exchange Server 5.5, 2000, 2003, and 2007, this Exchange repair software recovers all e-mail messages, notes, journals, tasks, contacts and other components.

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.

Tips To Resolve “Operation terminated with error...” Error Message

Eseutil/p is an inbuilt repair utility of MS Exchange Server that repairs corrupted Exchange Server databases at both table and page level. While the repair utility proves successful in repairing most of the corrupted databases, there are certain situations wherein the command fails to repair a corrupt database. In such situations, it displays an error message. This happens when the database is severely damaged. Since the database cannot be repaired, it remains corrupt, and the data saved in it remains inaccessible. To access database in such situations, a user needs to restore database from a previous online backup. However, in the absence of an updated backup, a user needs to repair the database using a third-party Exchange Server Repair application.

For detailed explanation of the above problem, consider a practical case wherein your Exchange Server database gets corrupted. And, when you try to repair the database using Eseutil/p utility, you encounter:

“Operation terminated with error -1605 (JET_errKeyDuplicate, Illegal duplicate key) after xxx.xxx seconds.”

Data saved in the database becomes inaccessible after the above error message appears. Additionally, the same error message repeatedly occurs when you try to repair your database.

Cause:

The fundamental reason for the occurrence of the above error message is that the repair utility might rebuild B-trees incorrectly. This will change the complete metadata structure of the database, leaving it in a permanently non-repairable state.

Resolution:

To resolve the above error message and to access the records saved in the database, a user needs to obtain the latest service pack of MS Exchange Server 5.5 and perform repair. However, if the repair utility is unable to repair the database even after installing the service pack, then you need to opt for an advanced commercial Exchange Server Repair application.

An Exchange Repair software is a powerful utility specifically designed to repair MS Exchange database, that has become corrupted due to logical crash. The read only utility performs repair without making any change in the original database file.

Exchange Repair Software provides absolute repair of Exchange Server 5.5, 2000, 2003, and 2007 after any logical crash. The repair tool recovers almost all objects of database, such as, emails, notes, appointments, tasks, and attachments. Designed for Windows 7, Vista, XP, 2003, and 2000, the Exchange Server Repair software comes with an interactive user interface.

Troubleshooting Event Ids 9518, 9175, and 454 at MS Exchange Startup

The Event Ids in Microsoft Exchange Server form most important parts of system diagnosis. These cryptic error messages allow the user to diagnose the logging problems. While there are various reasons for the occurrence of these event id, the most important is the corruption in the 'Information Store'. For easy resolution of any event id, the user can restore the database from an updated backup. However in case of absence of an updated backup, the user requires a powerful Exchange Server Repair software to repair the database.

As a practical case, your server locks up for no reason and when you reboot, the MS Exchange 2003 does not start. On viewing the event log, you view a series of event ids:

“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.”

Next, when you try to mount the 'Mailbox' or 'Public Folder', you encounter the below error message:

“The database files in this store are corrupted”

Cause:

The cause for the occurrence of the above error message is corruption of Exchange Server database.

Resolution:

To resolve the above error message and to repair the Exchange Server database, you have to use an effective Exchange Server Repair application. Such Exchange Repair utilities employ extensive scanning techniques to repair and restore corrupt Exchange Server database.

MS Exchange Repair is an answer to all logically corrupted Exchange Server databases. With recovery of deleted mailboxes, the Exchange Repair application repairs databases created in Exchange Server 5.5, 2000, 2003, and 2007. The repaired EDB file is saved in a .pst file format.

Exchange Database Corruption after Installing SP2

Microsoft Exchange Server 2003 SP2 offers new features, more reliability and easier administration over its earlier counterparts. SP2 is a cumulative update that improves the Exchange messaging environment by including improvements in mobile messaging, mailbox and protection against spam. Before you upgrade your servers to Exchange Server SP2, it is recommended that you make complete backup of system state, file system and most importantly, Exchange databases. This assures of data availability in case the installation goes wrong in any way. But cases occur when your Exchange databases get corrupt when no clean backup is present. In such situations, you should use a powerful Exchange Server Repair product that can use safe scanning algorithms to repair a corrupted Exchange database.  

For instance, you can consider a scenario describes below:

1. You run Exchange Server 2003 SP1 or an earlier version
2. You decide to upgrade to Exchange Server 2003 SP2. During the installation of SP2, the setup failed to stop ExIFS (Exchange Installable File System) service but continues with no notice
3. After this, when you try to mount Information Store, it fails and events 470, 9519, 9518 and 104 are logged in the application log.

Cause 

The above symtoms suggest that Exchange database may have got corrupted due to installation of SP2. It can also occur if an antivirus software is scanning the Exchange databases. Solution Before making any database restoration attempts, you should make sure that Exchange databases are excluded from any antivirus scanning.

If databases appear as corrupted, you should consider these suggestions:

1.Try repairing the corrupted database by running eseutil /r command

2. If it fails, restore the database from the last backup you have

3. When no clean backup is available, you should use a Exchange Repair software.

Exchange Server Repair products are highly competent utilities with powerful scanning algorithms to repair a corrupted Exchange database. These software are infallible solutions to any issue of database inconsistencies. Equipped with graphically rich interface and options, such software provide guide you through easy to implement procedure of repairing the database.

Exchange Repair is an advanced and safe Exchange Repair utility that employs powerful scanning algorithms to repair a damaged Exchange Server database. It is compatible with Exchange Server 5.5, 2000 and 2003. It is a safe Exchange Server Repair utility with impressive set of features. The tool extracts user mailboxes in individual .pst file format files.

How to Solve Table Index Corruption in Exchange Server?

The main repository of mailbox data in Exchange Server is the .edb file that is primarily composed of b-trees. Since a b-tree is allowed to have a considerable depth, b-trees deploy indexes to permit quick data access. In Exchange EDB, there are few ancillary trees that hold table indexes to work with the main tree. If these indexes go corrupted, the entire table and sometimes, the whole database become unusable. This is what we refer as logical database corruption. In critical situations, when this type of corruption is not limited to index page corruption, you need to implement Exchange Server Repair solutions.

To understand such potential problems with Exchange database further, consider the discussed scenario and error. When using Exchange Server 2007, you can encounter event 467 logging in the application log. Additionally, on viewing the description section of the same event, you receive an error that reads similar to below:

Information Store (number) Index [index name] of table [table name] is corrupted.

This error typically indicates a corrupted index in the Exchange store. As symptoms, you might observe access violations and repeated crashes. Also, this type of corruption might go undetected for long without any symptoms. Even the Exchange-aware backup may fail to detect this corruption. Event 467 suggests logical corruption at Database (JET database engine) level and is exhibited when JET engine touches this location in the database while reporting it as event 447. For specific root causes, one needs to view the application and system log cautiously as these errors can damage your data badly.

Solution

Following suggestions can help you isolate the depicted problem:

1. If corruption is limited to index leaf pages and not with the database pages, running Eseutil /d (offline defragmentation) alone can perform Exchange Server Repair.

2. In critical problems, you may need to use ExMerge utility to move the mailboxes to a new, blank Information Store.

3. The Exchange Server might be affected from page or database level corruption together with index page corruption. In such cases, you can execute Eseutil /p and then Isinteg -fix commands as Eseutil /d command may not work. You can further use ExMerge tool to put the database again in use.

4. To avoid data loss problems due to Eseutil /p utility, it is however, recommended to opt for a safe third-party Exchange Repair utility.

The Exchange Repair is a professional utility that repairs corrupted Exchange EDB file and restores the mailboxes in separate *.pst files. The EDB Repair product is easy to use with its self-explanatory interface. Designed for Exchange Server 5.5, 2000, 2003, and 2007, the tool is also competent to recover deleted mailboxes.

JET_errBadPageLink, Database corrupted Error in Exchange Server

An Exchange Server Information Store might get corrupted due to several errors, including unexpected shutdown and network errors. Corruption might involve any database files, called .edb files, that reside in Exchsrvr\Mdbdata folder. While Information Store corruption, you might observe server behaving slowly, Information Store Service not starting or not stopping, email delivery issues and several errors showing that the database is inconsistent. You should use your backup to restore such corrupted database or run ESEUTIL utility to repair it. However, if none of the solutions works, you should use Exchange Repair Software that could repair and restore a damaged Exchange database. For an instance, consider that you run ESEUTIL /D utility to defragment your database and the process fails. When you view the Windows NT Application log of Event Viewer, you come across the below error message: