Toll Free: +1 888 900 4529
| 
Toll Free: +44 800 088 5522 
Toll Free: +1 888 900 4529
| Toll Free: +44 800 088 5522 Exchange Error -1022 JET_errDiskIO generally happens when Exchange database undergoes physically corruption, that means your Exchange Database has got corrupted somewhere in file structure. To get more information about Physical Corruption check out my previous post “How to Solve Physical & Logical Corruption Causes of Exchange Database”.
In this blog, we will discuss about the Error code 1022 JET_errDiskIO. So lets start:
This Jet error happens when you attempt to access the file that is highly corrupted. The error -1022 JET_errDiskIO occurs due to a fault in an underlying system, a few sections of the files are missing or the file that you are trying to access is inaccessible. In such cases Jet Error Code 1022 pops up with the error message given below:
“1022 (JET_errDiskIO) The hardware, device driver, or operating system is returning errors”.
When failure occurs at I/O Disk i.e. When you request for the page that is available in the Exchange Database and the Operating System was not able to access it due to some reason, then the above mentioned error occurs.
The above mentioned Error can also happen in the Exchange Database when an uncompleted set of transaction log is replied. This may result in many problems like system hang, system crash, accessing data etc.
Consider an Example that a transaction, that is going in the log 7 but does not completed because of the database size that has exceeded the threshold limit but for that a new page reference log 8 has been created. These kinds of incomplete transaction logs will result in error code 1022.
You may also receive an error 1032 while dealing with exchange server database, that happens when the information store tries to access a file, but is not able to access it because it is held by some other database, in such case you will receive error code jet error 1032 (JET_errFileAccessDenied) instead of 1022.
To Resolve the error, follow the steps mentioned below:
1). If the error is happening due to the corruption in database, then repair Exchange database and try again.
2). If you have updated backup, then you can easily recover Exchange database from the updated backup.
