If your database is corrupted heavily, it is likely jet errors will occur. In most cases, Jet errors are not repairable. The most common error our customers usually see is: JET_errRecordNotFound, which is never recoverable using the eseutil.exe program. In fact, in many cases where this error appears, running eseutil will result in additional lost time and data. Another problem are
1003 0xFFFFFC15 JET_errInvalidParameter Invalid API parameter 4294966293 error codes.
Also, watch for "
JET_errKeyDuplicate Illegal duplicate key", which is another common jet error message that occurs due to database corruption. This also typically cannot be restored with eseutil.
Finally, other important errors to watch for are
ESE97 Error Codes:
JET_errReadVerifyFailure Read verification error 4294966278, which can typically be the symptom one or two of four main issues. The first, that your hard drive has sector errors. The second being that some information may have been written incorrectly into the database file, which is often caused by third party software. The third being that pages in the database file are corrupt, with the fourth being that the Exchange Server Jet Engine is corrupt.
No matter your Exchange Server's drive configuration or file size, dtidata can have you up and running right away. Please contact us at the toll free number above, or if the recovery request is not mission-critical, contact 727-723-3840.
Dtidata repairs and recovers Exchange Server databases that have experienced many different errors and problems. Some of these issues include:
* Physical hard drive failure
* Jet Errors
* Controller card malfunctions or failure
* Drive sector errors within the main Exchange files
* Improper shutdowns such as power failures (which can corrupt files and data)
* Email deletion, whether accidental or not
* Viral attack and Exchange
* Exchange program failure or boot problems
* Partition table issues
* Human error
* File size errors
If any of the above situations have occurred, we recommend you contact us immediately before you attempt any form of file recovery.
Things To Watch For:
When you have an Exchange Server problem, there are certain things you should watch out for, and be careful of doing. First, you may want to use the Eseutil program, which can frequently fix errors in the Exchange database. Be careful during this process, as improper overwrites of the data can occur. As well, it is best to not reinstall Exchange until you have made proper backups of the .edb files. And, ensure you have also backed up these files if you attempt to restore from an older .edb file. These steps will ensure that your Exchange files are not damaged beyond repair.
Running Out of Disk Space
One of the most common problems we get calls on is transaction logs filling up hard drives and taking up disk space
Also, when Information Stores are over the 16gb Limit.
IMPORTANT: Catastrophic RAID Container Crash! Do not try to rebuild an Exchange Server which has already been running in a degraded mode!
Stop and call us Now! We can help immediately!
Exchange Recovery Experts!
Exchange Disaster Recovery