| Is your Microsoft Exchange Server 2000 system | | | | renders your valuable data inaccessible. In order |
| behaving unusually? Are you unable to start | | | | to get your Exchange Server data back, you |
| various Exchange Server services? Is your EDB | | | | need to first identify the root cause of this |
| (Exchange Server Database) inaccessible? Such | | | | problem and then fix it with Microsoft Exchange |
| behavior indicate Exchange Server database | | | | Recovery. |
| corruption, which may occur due to a wide range | | | | Grounds of the issue |
| of reasons, ranging from simple user mistake to | | | | You may come across this behavior of Microsoft |
| catastrophic system crash. It leads to critical data | | | | Exchange Server due to any of the below |
| loss and needs Exchange Recovery to access | | | | reasons: |
| your mission critical data. | | | | 1. A message is received by the MS Exchange |
| Consider, | | | | Server 2000 system, which has a damaged time |
| A) You get Event ID 7011 while working on | | | | stamp. |
| Exchange Server. | | | | 2. The message has an invalid FILETIME attribute. |
| B) The SMTP (Simple Mail Transfer Protocol) | | | | 3. Exchange Server database is corrupted due |
| service on Exchange Server computer stops | | | | virus infection, improper system shutdown, and |
| responding or terminates improperly. | | | | application crash situations. |
| C) System freezes when you run - IISADMIN, | | | | Resolution |
| W3SVC, IMAP4SVC, RESVC, and POP3SVC | | | | Microsoft has a hotfix for this problem. You can |
| services. You need to restart your computer | | | | download it from Microsoft's website and install it |
| when it occurs. | | | | on your MS Exchange Server computer. |
| D) The services fail to stop when you try to stop | | | | However, it can not fix the database corruption |
| and restart them. | | | | problem and the database remains inaccessible. In |
| E) You may encounter error messages, similar to | | | | order to solve database corruption, Exchange |
| the followings:i. Timeout (30000 milliseconds) | | | | Server Recovery is needed. |
| waiting for a transaction response from the | | | | You can easily repair and restore damaged EDB |
| RESVC service.ii. Timeout (30000 milliseconds) | | | | file using Exchange Recovery Software. They are |
| waiting for a transaction response from the | | | | powerful enough to systematically scan the whole |
| IISADMIN service.iii. Timeout (30000 milliseconds) | | | | database and extract all damaged mailboxes from |
| waiting for a transaction response from the | | | | it. They extracts all the mailbox objects such as |
| W3SVC service. | | | | emails, notes, contacts, tasks, calendar entries, |
| This behavior of Microsoft Exchange Server | | | | and more. |