cmdown
asked on
Exchange 2007 - Eseutil returns Jet Error 1022 ** URGENT **
Following a serious power outage an Exchange 2007 server is reporting Jet Error -1022 when attempting to run eseutil /k to check the consistency of the .edb files.
Store is dismounted and services stopped but still getting the error. Chkdsk has been run in check only mode - no repair switch !! - no disc errors found.
Local admin has full control and domain admin also has full control to both the location of eseutil and the mailbox datastore folders
Please can anyone advise what the problem may be and how to get things back up again
Thanks
Store is dismounted and services stopped but still getting the error. Chkdsk has been run in check only mode - no repair switch !! - no disc errors found.
Local admin has full control and domain admin also has full control to both the location of eseutil and the mailbox datastore folders
Please can anyone advise what the problem may be and how to get things back up again
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi all - thanks for the replies. The store service was dropping out whch was fixed by dismounting the stores, restarting all exchange services and then running eseutil. All stores can back as clean so has gone live again. However, I would like to run a full diagnostic and possible rebuild to eradicate any possible inconsistancies as I am occassionally finding 'black holes' that emails disappear into - they do not show in their respective folder and you can only 'find' them if you do an advanced search. Any thoughts before I accept & close this post ?
run eseutil /g "x:\program files\exchsrvr\mdbdata\pub
run eseutil /p "x:\program files\exchsrvr\mdbdata\pub
then run isinteg -s (server) -fix -test alltests
That should sort you out.
run eseutil /p "x:\program files\exchsrvr\mdbdata\pub
then run isinteg -s (server) -fix -test alltests
That should sort you out.
If you have run ESEUTIL /P, this will remove the corrupted pages, this may cause you data lose or any unexpected inconsistencies with the database. Run ISINTEG fix -test alltests for the database which you have issue. This will resolve your issue up to some extent.
For reference: http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html
Another option: If you have an option to create a new mailbox store, I would suggest you to move the users of corrupted database to new store.
For reference: http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html
Another option: If you have an option to create a new mailbox store, I would suggest you to move the users of corrupted database to new store.
ASKER
Thanks Guys
The original problem was due to the store service not restarting properly. Stopped all exchange servicesm, rebooted server & then able to proceed with dismounting stores and running eseutil checks
The original problem was due to the store service not restarting properly. Stopped all exchange servicesm, rebooted server & then able to proceed with dismounting stores and running eseutil checks
Run eseutil /mh "database" and Check if it is Dirty Shutdown.
Do you have any errors in event log??