Scroll Top

The way to Mend Change Server Error "Error – 1022=’JET_errDiskIO’ = Disk I/O Error"?

How to Mend Exchange Server Error "Error – 1022=’JET_errDiskIO’ = Disk I/O Error"?

Database of MS-Exchange server leads to several errors. These errors makes it quite difficult to work smoothly. Sometimes it happens that database file of Exchange server refuses to open. On each attempt to open database of server, you remain unsuccessful. Corruption of Exchange database is one of the reasons for such a behavior. Because of this, data cannot be approached. You fail to access the content of database. To avoid such data loss situations use a backup. However if backup falls short in recovering data, then perform Exchange recovery with the help of third-party tool.

Related to above topic let’s study an error message. As discussed above, Exchange server gives an error message on the screen when you attempt to open database of Exchange server. Database cannot be opened and when you see the details of the error you notice the following event log in the description:

Event Type: Error

Event Source: ESE

Event Category: General

Event ID: 489

Computer:Computer Name

Description: Process name [process id] file name: An attempt to open the file [path\file name] for read-only access failed with [Error Code and Explanation]. The open file operation will fail with error [-1022].

Root of the issue:

The “Error -1022=’JET_errDiskIO’ = Disk I/O error” is caused when a disk I/O error stops Exchange from accessing requested database page or a check file.This could be because of disk or controller that prevents you from accessing the disk (though this may be temporary). Also check the log for drive or input/output errors around the time of Event 490. The problem occurs when the path for check file is wrong, may be due to drive failure.


To handle above error execute “chkdsk /f /r” command. If executing this command does not solve the problem, then verify the permissions on Exchsrvr folder. Ensure that SYSTEM has full control of Exchsrvr and all the sub-folders (on every partition) that contain Exchange data.

If you cannot mount databases, then you will need to troubleshoot Windows NT file-level anti-virus software that might be running on the Exchange server. Also check the log for drive or input/output errors around the time of Event 490. Verify and correct the path for the check file. You can also correct the root cause, and use an updated backup to retrieve data of the database.

If all else fails, then performing Isinteg -fix, and ExMerge command to a new Information Store also helps you to sort out the problem.

However if no satisfactorily results are found after using above commands, then opt for a third party Exchange Recovery tool. A lot of tools are available in the market that have the main objective to recover exchange server.

Stellar Phoenix Mailbox Exchange Recovery is a sophisticated and utility that successfully performs Exchange Server recovery in all the cases of corruption. This Exchange Recovery Software recovers all the data of.edb files contained in messages, notes, tasks, attachments, and in other objects.

#Mend #Exchange #Server #Error #quotError #1022JET_errDiskIO #Disk #Errorquot

Will be pleased to have you visit my pages on social networking .

 Facebook page here.

Twitter account is here.

Linkedin account here

Post byBedewy for info askme VISIT GAHZLY


Related Posts

Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.