| When you upgrade Microsoft Exchange Server to | | | | message pops up that reads as below: |
| a later version, the upgrade process first | | | | "JET_errDatabaseIncompleteUpgrade" |
| upgrades the database before copying any code | | | | This error is associated with decimal value of -563 |
| of the later version to Exchange Server | | | | and hexadecimal value of 0xFFFFFDCD. |
| computer. Then it makes corresponding changes | | | | Cause |
| in registry, services, and system. The reason is | | | | The above error is encountered when you |
| that in case the database upgrade fails, one is | | | | attempt to upgrade the Exchange database, but it |
| allowed to perform a complete rollback by doing | | | | is only partially converted to the required |
| operations like moving the mailboxes. But the | | | | database format. As a result, user cannot mount |
| situations become critical when the database is | | | | or use this database further. |
| left in partially upgraded state and with no suitable | | | | Solution |
| recovery option other than backup. Another | | | | The upgrade usually fails because the current |
| alternative to deal with such Exchange database | | | | system doesn't conform to the system |
| corruption issues is to use a read-only exchange | | | | requirements asked by the later version or the |
| recovery utility. | | | | database is extremely fragmented (however, |
| Consider, you use Exchange Server 5.5 and | | | | there can be other reasons as well). To prevent |
| attempt to upgrade it to Exchange Server 2003. | | | | such post upgrade consequences, it is |
| Next, you notice that the upgrade operation | | | | recommended to backup the database prior to |
| cannot proceed successfully and an error | | | | upgrading. |