Why is my ESEUTIL/P operation failing with " Operation terminated with error -1017 (JET_errRecordDeleted, Record has been deleted)".

To recover old emails I restore PRIV.EDB to a test server running Server2000 with SP4 and Exchange 5.5 with SP4 and all required fixes post SP4 for exchange.  These data bases always restore as being in an inconsistent state.  To fix, I run ESEUTIL/P /IS PRIV.EDB.  Since these are large databases, typically 60 GB - 90 GB, this take 18 to 30 hours.  The last two PRIV.EDB files I have tried to repair, aborted with the message Operation terminated with error -1017 (JET_errRecordDeleted, Record has been deleted)". .  This happened when the database scan was complete and the database repair started.  

The event log for the application shows a warning message from source EXE97, event id 136---- (1356) the database engine has lost 1 page of bad data. These messages appear 1 or 2 per second for about the last 80 minutes of the ESEUTIL/P utility run.  The first 12 to 16 hours run without errors in the event logs.  There are no corresponding events in the SYSTEM or SECURITY event logs.

BTW - I used VERITAS NetBackup 3.41GA to perform the restores.  Backups were done under a variety of versions of the same software 3.x - 3.4
Who is Participating?
The test server you are using, does it have the same name as the production server? Is it also using the same Exchange 5.5 service account and partition setup as the production server?

After the restore has finished, I suggest that instead of running eseutil/p use isinteg -patch instead.

dave7918Author Commented:
Thank you for the suggestion.   I tried it and it worked.   Now why it worked this time and did not work in the past I do not know, but the PRIV.EDB is up and I can access data in the mailboxes.  This is still a puzzle. I have 7 more of these restores to complete.   I am sure the real source of the this problem will sooner or later be identified.  Somewhere along the line of my learning, I though the PRIV.EDB had to be in a consistent state to be able to run ISINTEG  - patch.  I was wrong.  To answer your questions.  The server name is not the same as the original server.   The Organization name and Site name are the same for the Exchange software.  The restore server also uses the same Exchange Service Account and same Domain Admin account.  Partitioning is set the same as the original server. MTA is set to manual start prevent mail from actually transferring from the server to another server in the same site.
If you are restoring an ONLINE Exchange backup it will always be inconsistant. This is by design. The reason is that the PRIV.PAT file has to replay into the database. This happens when the Information Store service is started.

Here is what I recommend:
Stop the Information Store service.
Delete the contents of the MDBDATA folders on ALL drives.
Now restore your ONLINE backup and start the service.

Hope this helps.
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

dave7918Author Commented:
Previouisly I have only restored the PRIV.EDB, into the directory that exchange expects to find it on the test server.  Is it your recommendation that all the log files be restored as well?
You don't have that option when you do a restore of an ONLINE Exchange aware backup.

Is your backup program Exchange Aware?
And I don't mean that it has an Open File agent. An Open File agent is something totally different that should not be used to make Exchange backups. If an Open File agent was used to backup the databases, then this could be why you are having issues.

When you are restoring the Priv.edb onto the test server, choose the option overwrite existing logs. This will restore the priv.edb with the logs that were backed up.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.