While requesting Exchange database and getting a most common EDB JET_Error 1022 then immediately you ask for an IT specialist to resolve this error because it may led to shut down your organizations communications. So here I am giving you detailed discussion and an easiest way to deal with this error. After reading this article you are very much familiar with this error and easily you can resolve by following some steps.
Let us start from the basic and go on next level of difficulty step by step at the end of this article I am dam sure that you are able to understand the meaning of 1022 JET_ErrorDiskIO error and its recovery process.
Before going deep in this error firstly let us discuss Exchange database and related errors, every organization needs to store the current information for the future use to achieve this company's move to setup an Exchange server, the recommended & popular server is Microsoft Exchange Server.
Microsoft Exchange Server stores all data in EDB file so called Exchange Database, a database is a physical storage device which enables users to perform two type of operation i.e. READ or WRITE. To perform read/write operation database requires physical as well as logical connection with other hardware and application softwares respectively.
Now Exchange Server Database JET_errDiskIO 1022 is a physical database error, this error encounters when hardware is unable to respond to a particular request because unavailability of particular hard ware, log file, device driver software and highly corrupted EDB file or any other reason Exchange is not able to access database then an error message will be prompted like.
"-1022 (JET_errDiskIO) the hardware, device driver, or operating system is returning errors".
The disk input/output (IO) device unable to respond on request or when operating system unable to access requested page due to any reason then this error occurs. In this case Exchange requests a page number that is larger than the total number of pages in database which causes DiskIO error.
The above error can be occur when a log file is missing or not able to complete the write operation to the database and this situation may cause sudden system crash, System may hang while starting and accessing data. Let us take an example to understand it better, suppose a log file with DBTime Stamp value log5 is performing write operation, it is not completed the write operation yet and file size exceeded to database size due to which new page reference is generated and added to new log file i.e. log6 and this situation led to an DiskIO error 1022.
Now let us one more case to understand it, if a transection replay has to start with log m but the administrator deletes the cheakPoint file and log m then the transection replay is forced to start with log m+1. In this situation JET_errDiskIO 1022 occurs, one more thing this situation removers from Exchange server 2003 and later versions because it uses ESE 98 utility inbuilt in Exchange server.
I am putting here some reasons that makes the database page inaccessible by the Exchange Server and leads to the error -1022 JET_ErrorDiskIO.
Here I have completed all the possibility that can cause the -1022 JET_ErrorDiskIO error now let us discuss an easy way to deal with this error.
The resolution method vary as the causing factor of this error varies.
Note: - if you don't have updated backup then you have to move to second method i.e. given bellow.
Note: - Eseutil.exe is the tool provided by Microsoft that runs on Microsoft PowerShell.
Conclusion I have discussed all possible resolution method which is useful to resolve -1022 JET_ErrorDiskIO error, if further you have any problem regarding this error, feel free to contect us.
