| When you insert a new record in Exchange | | | | database page is corrupted and is causing JET |
| database table, Exchange inserts the | | | | engine to hang. |
| corresponding index entry into index. For any | | | | Solution |
| reason, if the data page is flushed, but its index | | | | To solve the issue, you need to first locate the |
| remains intact, database inconsistency might arise. | | | | corrupted database, which is specified in the |
| This state of database is known as 'lost flush'. | | | | Description section of event occurred. If you |
| Since the database comes to a dirty state, you | | | | cannot view this information, you should first |
| should immediately apply the appropriate eseutil | | | | install the supported hotfix to include it. After the |
| commands to repair it. If this doesn't solve the | | | | affected database is traced, follow these steps: |
| issue, you need to restore the database from | | | | 1. |
| backup or use effective Exchange Recovery | | | | Start Exchange System Manager and dismount |
| applications. | | | | the database causing the issue. |
| For instance, you might observe that Microsoft | | | | 2. |
| Exchange Information Store services stops | | | | Run eseutil /g command to confirm for database |
| responding at repeated intervals of time in a day. | | | | inconsistency |
| When you view the application event log, it shows | | | | 3. |
| event ID 467 associated with a 1025 warning as | | | | Run eseutil /d command to defragment and fix |
| below: | | | | the corruption |
| Warning 1025: | | | | 4. |
| An error occurred on database "First Storage | | | | Mount the database store |
| Group\Public Folder Store (server_name)". | | | | If the issue persists, delete the database provided |
| Function name or description of problem: SLINK :: | | | | you have a valid backup. In case of any issues |
| EcUpdate Error: 0xfffffa7a" | | | | with backup, you are suggested to use third-party |
| You come across a similar warning each time | | | | Exchange Server Recovery solutions. These are |
| when event 467 is logged in MSExchangeIS public | | | | powerful tools built to run high-end scanning |
| or private store. | | | | algorithms for repairing the corrupted Exchange |
| Cause | | | | database. Microsoft Exchange Recovery utilities |
| Event 467 typically indicates secondary index | | | | provide interactive design and thus, prove easy to |
| inconsistency with the associated table. The | | | | implement solutions. |