Event ID 1022 is an Exchange database error. The error normally occurs as a result of hardware errors, especially...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
those of a disk sub system such as device driver, bad hard disk drive or even a faulty disk controller. There are ways that you can deal with this error, and, in fact, help to ensure that you don't get them at all.
The 1022 error results in the database engine requesting a page from disk, but receiving an error from the I/O subsystem instead. When this error occurs the best way to start troubleshooting is by examining the System Log. Start the Event Viewer and click on System Log in the left-hand pane. Of course, you can also run disk diagnostics, such as ScanDisk, available through the Management Console, to determine if the disk has a problem.
A good proactive approach you can apply to detect physical corruptions is to perform regular online backups. Online backup is one of the best ways to determine whether there is a corruption in a database file, because it uses a process that systematically checks every single page in the database. Also setting up redundant disk arrays for the Exchange databases can rule out the possibility of a disk going bad, which can result in corrupted Exchange databases.
System logs can also provide early warning detection of any problems occurring.
Of course periodic visits to the System logs can also provide early warning detection of any problems occurring.
Adesh Rampat has 10 years experience with network and IT administration. He is a member of the Association Of Internet Professionals, the Institute For Network Professionals, and the International Webmasters Association. He has also lectured extensively on a variety of topics.
Dig Deeper on Microsoft Exchange Server Database Management