Event Id 467 Indicates Database Corruption In Exchange Server
Exchange Information Store is the soul component of Exchange Server, without which none of the operation will work in the application. This contains all the components of Exchange server, the mailboxes being the most important one. But what if the Information service stops responding at all? Perhaps the situation is critical to handle for most of us. The frequent hangs in the service can also doubt towards EDB database corruption which may need Exchange Server repair to correct.
Now, whether the problem is due to database corruption or not, look in the application event log. If you see Event ID 467 therein and Event IDs 7011 and 7031 in system event log, the condition surely points to EDB database corruption.
If you still doubt it, go through the 1025 warning, which generates in MSExchangeIS Public/Private Store, similar to the following:
Warning 1025:
An error occurred on database "First Storage Group\Public Folder Store (server_name)".
Function name or description of problem: SLINK::EcUpdate Error:0xfffffa7a
Event ID 467 indicates that the secondary index is being inconsistent with the corresponding table. Actually, at the time you insert a record in the table and thus index entry is being made, the corrupted page gets flushed, but not the index. As a result the database inconsistency is seen.
Microsoft has suggested defragmenting the database via Eseutil/d. After this, use Eseutil/g to see the database corruption, if it is still showing corruption, use EDB repair mechanism to correct. Actually, it would be better to have Exchange Server recovery, before record insertion could flush out the corrupted page as this would result data loss.
The EDB repair option of Exchange Server only includes deleting the corrupted page, instead of actually repairing it. So make use of third party application to repair your database. EDB recovery software are the designated tool for the same. Through their scanning abilities and read-only conduct, these would make Exchange Server repair completely safe and complete.
Stellar Phoenix Mailbox Exchange Recovery is the product to have EDB recovery at best. This Exchange Server recovery application proves valuable for Exchange Server 5.5, 2000 and 2003.
You would find all the e-mails, notes, journals, tasks, appointments, calendar and other EDB objects repaired and restored safely. The interface is too easy to work for EDB repair.
