| Is your Exchange Server delivering outgoing mails | | | | identify the actual cause of this issue and perform |
| without attachments? Are you unable to see | | | | Microsoft Exchange Recovery by sorting it out. |
| attachments in your Exchange Server mailbox? | | | | Grounds of the issue: |
| Do you encounter ESE (Extensible Storage Engine) | | | | This behavior may occur due to the following |
| errors while accessing the EDB (Exchange Server | | | | possible causes: |
| Database) file? This behavior indicates Exchange | | | | 1. The transactions are not committed to the |
| Server database corruption. You need to go for | | | | hard drive by Disk Caching and the Exchange |
| Exchange Server Recovery to get your database | | | | Server is crashed or stopped responding. |
| repaired, if an updated and complete backup is | | | | 2. Wrong log files are replayed while restoring the |
| not in place. | | | | database. |
| In a practical scenario, you may see the below | | | | 3. Exchange Server hard drive is having logical |
| even log entries in the Application Event Log of | | | | problems, like operating system malfunction, virus |
| Exchange Server: | | | | infection, file system corruption, and more. |
| "Date: date Source: ESE | | | | 4. The database is corrupted due to improper |
| Time: time Category: Database Corruption | | | | system shutdown, virus infection, application |
| Type: Error Event ID: 447 | | | | crash, and other such reasons. |
| User: N/A | | | | Resolution |
| Computer: Server name | | | | In order to work around this issue, go through |
| Description: Information Store (nnnn) A bad page | | | | the below steps: |
| link (error -338) has been detected in a | | | | 1. If your hard drive has logical problems, run |
| B-Tree (ObjectId: 70950, PgnoRoot: 157120) of | | | | ChkDsk utility to detect and fix hard drive related |
| database e:\Program | | | | errors. |
| Files\exchsrvr\mdbdata\priv1.edb (157120 => | | | | 2. In case of database corruption and other |
| 296404, 296403)." | | | | database related issues, run DBCC CHECKDB. |
| The above problem may render your database | | | | However, if the database corruption cannot be |
| completely inaccessible. You cannot access your | | | | fixed by DBCC CHECKDB due to high extent of |
| precious emails, notes, contacts, tasks, journal, | | | | damage, you need to use third-party Exchange |
| calendar entries, and other mailbox items. In order | | | | Recovery Software. They work in most of the |
| to gain access of your data, it is essential to | | | | database corruption situations. |