Jet Error 1022 Exchange
Contents |
» » How to resolve Exchange error -1022 JET_errDiskIO? In this article, we are going to discuss about the Exchange error -1022 JET_errDiskIO. This error occurs due to physical Exchange database corruption. It indicates file level damage in the Exchange database. To know more eseutil error 1032 about physical corruption, refer my previous article: "How to detect and prevent physical Exchange database corruption?"
Eseutil /mh
Exchange error -1022 JET_errDiskIO: The error -1022 JET_errDiskIO occurs due to a fault in an underlying system. Whenever you try to read a file that is severely damaged, some parts of the file data missing entirely or inaccessible due to some other reason, then the error will be prompted: "-1022 (JET_errDiskIO) The hardware, device driver, or operating system is returning errors". Why does error -1022 JET_errDiskIO occur? The above error occurs because of a disk input/output (I/O) failure. Whenever the exchange requests a database page and the operating system cannot gain access to that page due to any reason then the error occurs. In such case, Exchange requests a page number that is larger than the number of pages in the database file. The above can also occurs if an incomplete transaction log set is replayed in the database. It can also result to sudden system crashes, system may hang while starting and accessing data. For example: if a transaction is being going on in log 9, it couldn't not be completed as it has exceeded the database size but the new pages reference has been added to log 10 then what would happen? Such incomplete transaction would lead to error -1022. Consider one more case, if a transaction replay is to be started from log n and if the administrator deletes the checkpoint file and log n, then the transaction replay could be forced to start from the log n+1. In such case the above error can occur. In case of exchange 2002, this isn't possible as it prevents such incomplete transaction log replay that can cause damage to the database. It is easily possible in the exchange version 5.5. Below given are some reasons that make the database pages inaccessible by the exchange server and leads to the error -1022 JET_errDiskIO. What causes Exchange error -1022 JET_errDiskIO? Damaged/corrupt database file Damaged file system or other Issues in the file system Missing file elements Truncated file elements improper transaction log replay Other applications are keeping the database pages open, that don't let exchange to access them Third party software that prevents the Information Store service from accessing the Exchange data How to resolve Exchange error -1022 JET_errDiskIO? The resolution method to fix the error may var
March 23, 2014 | Download Complete PDF Elaborating Error 1018, 1019, 1022 in Details Overview » This section aims at providing information about Exchange Server error message -1018, -1019, and -1022. Also, it explains the difference between all these errors and what kind of problem in database results in this kind of these errors. Detailed Information » In Microsoft Exchange Server, there is built-in functionality to identify EDB file-level damage to the pages. Amongst the various symptoms that inform about this sort of damage to the DB, three of the very famous errors are: -1018 JET_errReadVerifyFailure -1019 JET_errPageNotInitialized http://recover-email.blogspot.com/2014/09/how-to-resolve-exchange-error-1022.html -1022 JET_errDiskIO Nevertheless, damage to database of Exchange Server can take place at different levels. Possibility is the pages in the EDB file are corrupt, or the B-tree structure is dis-ordered, or the index of EDB file is damaged. Depending upon the scenario, DB corruption is classified as: Page level Database level Application level Using Eseutil.exe /K switch, page-level integrity of database can be checked out and fixed. http://www.exchangerecover.com/blog/exchange-server-error-messages.html In order to detect database and application level inconsistency, Isinteg utility is available for help free of cost by Microsoft. Page level damage that generally occurs due to issues with Operating System, drivers, hardware is categorized as Physical Corruption. On the other hand, Database and Application Level damage caused due to problem in B-tree structure, table or index of EDB file comes under Logical Corruption. Exchange Server error messages discussed in this article are caused due to page-corruption of EDB file. Amongst all, -1018 is the mostly-encountered error and thus there is more discussion done in this section on its cause and recovering from it. The other two errors: -1019 and -1022 are generally caused because of bug in the application (Exchange Server) but not in every case. Exchange Database Page and Checksum Calculation In order to understand reason for errors -1018 and -1019, it is important to understand how pages are organized in Exchange database .edb file. At a logical level, an EDB file is a set of 4KB (or multiple of 4) pages that are numbered in a consecutive manner. The ESE database is an organized in a B-Tree structure that comprises of pages pointing to next adj
I get the following error:Operation terminated with error -1022