How repair a EDB database with error -1022
Unexpectly a database on an exchage 2007 ENT was dismounted (aprox 41Gb of size) whe I tried to run the command eseutil /mh I get the following error:Operation terminated with error -1022 <JET_errDiskIO, Disk IO error> after 0.47 seconds.I copied the EDB and transactions logs on a windows xp with the management tools installed and run the same command and I get the same message. Can someone guide me to repair and recover the mailboxes??? (I don't have a working backup of the database).Warm regardsJoskyJJ
December 30th, 2009 8:56pm

Take a look at:http://support.microsoft.com/default.aspx/kb/314917Understanding and analyzing -1018, -1019, and -1022 Exchange database errorshttp://technet.microsoft.com/en-us/library/bb217951(EXCHG.80).aspxhowever, what errors occured when the database dismounted?I'm not sure why you copied the edb and logs.Will the store mount on the productin server? If not, what errors are generated in the event logs?
Free Windows Admin Tool Kit Click here and download it now
December 30th, 2009 9:51pm

I copied the EDB file and inside the folder where the database was located I found a folder named catalogdata-xxxxxxxxxxxxxxxxxxxxxxxxxx i copied it too and another folder that contains the logs (e00.chk E00.log and the others log files inside).JJ
January 5th, 2010 4:58pm

Hello Josky, Unexpected error messages have now become common in any database or files & folders. As you have mentioned about the error message it is a straight sign of EDB corruption. And to resolve this issue there is no need to make heavy noise. EDB Repair is best tool to fix this issue. I will suggest repairing the file first and then taking or thinking about other steps. Thanks!
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2010 2:55pm

Hi Josky, The cause of this behavior is missing log files or corrupt backup file. In these cases, MS Exchange Server cannot access the source database and you face this issue. To resolve this issue you can use inbuilt Eseutil /p utility that is command line tool or by restoring the database again from backup. If possible, move unaffected files from problem database to new database. If the above method does not work, you need to use some third-party EDB Repair tool such as Stellar Exchange Recovery software to repair and restore corrupt database. ThanksAxel Culver
November 25th, 2010 11:03pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics