After Exchange database corruption, online backups prove as the most prominent source for Exchange server repair as then you need not to look for some third party applications to do the course. But, in few of the cases, when you think that you have the full online backup and the database has been restored successfully, as a failure, the Information Store may fail to start, with the error messages like:
"Error -1414 or 0xfffffa7a or 4294965882 (JET_errSecondaryIndexCorrupted)"
Or
"Error -1032 or 0xfffffbf8 or 4294966264 (JET_errFileAccessDenied)"
Or
"Error -1030 or 0xfffffbfa or 4294966266 or c8000406 or 3355444230 (JET_errAlreadyInitialized)"
In this case, the application log may be found full with Event IDs 172, 177, 1080, 5000, 145, 1120 and others which state the words that Exchange server recovery is not completed yet.
The culprit running behind can be the change in Windows NT service pack level and computer name. Actually, with the service level change, Exchange server gets activated to rebuild the indexes to resist incompatibility issues. In condition that the computer name has got changed, the mentioned error messages may appear. So, for the success, there should be the service level match between the recovery server and Exchange server computer. The same problem has also been seen with the changed computer names and same service levels.
| Report this article |