| Microsoft Exchange Server Calendaring agent is | | | | accessing the database "0xfffffc0d". |
| the tool that allows performing several scheduling | | | | You may also encounter Event IDs: 2 and 7200 |
| tasks, which include creating and saving | | | | describing the failure of Exchange Calendaring |
| appointments etc. For the tool to function | | | | agent. |
| properly, it is required that Exchange directory | | | | Cause |
| structure remains excluded from antivirus | | | | Exchange Database Server exhibits the above |
| scanning. Another disadvantage of scanning your | | | | described behavior when a file-level antivirus |
| Server directory structure is that it may also lead | | | | software is installed and is configured to scan the |
| to corruption of the most important files in your | | | | Server directory (EXCHSRVR) structure. |
| Information Store, such as.edb,.stm,.chk, and.log | | | | Solution |
| files. Since most of your important data resides in | | | | The solution to this problem is to reconfigure your |
| your.edb files, EDB Recovery becomes essential | | | | antivirus software and not to include EXCHSRVR |
| while such instances. | | | | directory and drive 'M' in this scan. |
| To illustrate such scenarios with Calendaring agent, | | | | A file-level antivirus software locks and scans the |
| suppose you try to save few appointments in MS | | | | file that is currently being tried to access by MS |
| Exchange Server. Your observe that Calendaring | | | | Server. Thus, the Information Store fails to lock |
| agent fails to function properly. Some or all of the | | | | this file and eventually, the file may become |
| calendar information are lost. Additionally, you | | | | corrupt and unusable. When this occurs, your first |
| receive the similar entries logging in application | | | | recommendation is to restore the database from |
| event log of Server: | | | | a previous backup or apply eseutil repair utilities ( |
| Event ID: 8206 | | | | p and/or /r switches) for the affected |
| Source: EXCDO | | | | database(s). |
| Description: Calendaring agent failed with error | | | | However, if none of the database restore |
| code 0x80040229 while saving appointmentand | | | | method works, you need to use an EDB file |
| Event ID: 1160 | | | | recovery software that can scan and repair the |
| Source: MsExchangeIS | | | | corrupted database effectively. The EDB |
| Description: Database resource failure error First | | | | Recovery utilities are exclusively designed and |
| Storage Group\Mailbox Store (MAIL) occurred in | | | | simple products that allow to repair and restore |
| function JTAB_BASE::EcPrepareUpdate while | | | | the damaged Exchange database. |