asked on

ESEUTIL and ISINTEG on Exchange 2000 SP3

Hello,

Our server has been running for 2.5 years, but the previous admin never ran ESEUTIL. Additionally, our existing database is approaching 50GB, which I am in the process of splitting into three smaller databases, in order to improve performance and manageability. When moving user mailboxes from the larger store to either of the smaller stores, I received an error message stating I had to run ISINTEG to correct errors.

I thought I remembered reading "Do not run ISINTEG unless you have to" somewhere on this site. So, I copied the priv1.edb file to a non exchange machine and ran ESEUTIL /g command as a practice run and received the following error: Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db).

I've checked the log file and all errors state 0 after 0 or 1 seconds. Do I have a real integrity problem?

Is ESEUTIL /g the same as ISINTEG?

Should I concern myself with defragmenting the original database, before moving the mailboxes?

Sorry for all the questions, but I intend on implementing the necessary repairs on live data and hope to resolve these issues before I move forward with live data.

Thanks in advance.

SOLUTION

David Wilhoit

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

Exchange_Admin

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

rj4510

ASKER

This is the exact article I used when running the ESEUTIL from the non exchange machine. Am I to assume I can run ISINTEG, the move my users and then delete the existing database, or should I run ESEUTIL to defragment the database?

rj4510

ASKER

Thanks for your help.