atiqc
asked on
Why a -1017 error is encountered on the Exchange server while recovering Priv.edb
We had been facing a problem on our Exchange server for last ten days. When a user tried to send a message the process used to terminate with an error "The operation failed". We ran an integrity check with ESEUTIL /G /ISPRIV /X /V and it revealed that we have errors in the database. An envent ID 195 was being recorded in the eventlog "MSExchangeIS ((606)) Internal trace: lv.cxx@400.
The result of the integrity check showed that we have JET Error -1206 on table "Msg" with bad leaf page links. Table "DeliveredTo" had the same problem as table "Msg". Other errors included were as described below:
Table "1-8FA11" 1131 index entries inconsistent
Table "1-2EC03" 32 index entries inconsistent
Table "1-2EC03" 412 index entries inconsistent
Table "1-2EC03" 25 index entries incosistent
Table "1-24" bad page pointer to leaf page and subtree check failed with err -1206
On seraching the microsoft knowledge base we came accross an KB#181824. This artical described the similar problems and we started the receoved according to the guidelines set forht in the artical. The ese.dll was copied to the system32 directory and ESEUTIL /p started on priv.edb.
Almost at the end of the process eseutil was terminated with error -1017 and even id 138 was recorded in the eventlog for maybe 100 times. Description of this event id is ((123)) The database engine lost one or more bad columns of data in one record.
We are not able to proceed further as the ESEUTIL /D terminates with same error -1017. Any suggestion, how we should proceed further?
The result of the integrity check showed that we have JET Error -1206 on table "Msg" with bad leaf page links. Table "DeliveredTo" had the same problem as table "Msg". Other errors included were as described below:
Table "1-8FA11" 1131 index entries inconsistent
Table "1-2EC03" 32 index entries inconsistent
Table "1-2EC03" 412 index entries inconsistent
Table "1-2EC03" 25 index entries incosistent
Table "1-24" bad page pointer to leaf page and subtree check failed with err -1206
On seraching the microsoft knowledge base we came accross an KB#181824. This artical described the similar problems and we started the receoved according to the guidelines set forht in the artical. The ese.dll was copied to the system32 directory and ESEUTIL /p started on priv.edb.
Almost at the end of the process eseutil was terminated with error -1017 and even id 138 was recorded in the eventlog for maybe 100 times. Description of this event id is ((123)) The database engine lost one or more bad columns of data in one record.
We are not able to proceed further as the ESEUTIL /D terminates with same error -1017. Any suggestion, how we should proceed further?
Your database is unrepairable. If it still mounts you can use Exmerge to get the mail out. Otherwise you're looking at a 3rd party solution such as ontrack (www.ontrack.com).
ASKER
Marc, your comments are appreciated but I would like to know which particular product of ontrack will be applicable to me as ontrack has a lot of recovery products available. Will be grateful for your feedback.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.