SBS2003 - Exchange Errors - Event ID 9792

Hi Everyone,

Recently I have had some strange issues with Exchange so we ran the following command:

isinteg -s servername -test alltest

This ran through and found 22 erros. I ran the test again as you should and it came up clean. I am now getting the following errors regularly throughout the day:

Source: MSExchangeIS Mailbox
Catagory: Background Cleanup
Event ID: 9792

Cleanup of the DeliveredTo table for database 'First Storage Group\Mailbox Store (RMSERVER)' failed with error -1017. 0 entries were purged before the failure was encountered.

I think my only option may be a hard repair (Eseutil) but am aware this can delete data. Just wondered what everyone else thought.

Thanks

Dave
TriumphLTDAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

davorinCommented:
It look that your DB is corupted.
As always it is good to have a backup.
http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html

Other possibility is to create additional mailbox database and move all mailboxes to new database.
TriumphLTDAuthor Commented:
Ok thanks for the advice, any other ideas any one or am I looking at an ESEUTIL or fresh DB install?

Thanks
Alan HardistyCo-OwnerCommented:
If you run isinteg you should add the -fix switch to actually fix the errors, but this is always good after running:
eseutil /p
eseuti /d
then isinteg -s servername -fix -test alltests
Maximize Customer Retention with Superior Service

The IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more to help build customer satisfaction and retention.

TriumphLTDAuthor Commented:
Hi Alan,

My mistake, this is the command I ran already, I did do the -fix switch too.

Dave
Alan HardistyCo-OwnerCommented:
No probs - I was hoping you had : )
Are there are other ESE errors in the Application Event Logs?
TriumphLTDAuthor Commented:
Just checked and they are the only errors, nothing else at all.
Alan HardistyCo-OwnerCommented:
Good news.

Running eseutil /p, then eseutil /d then isinteg can lose data for you, but generally only data that is corrupt anyway, so not much use to you.

Make sure you have a full database backup before you start and ideally take a copy of the .EDB and .STM files, repair those and then move the originals out of the way and replace the repaired ones with the originals, then mount the database and all should be fine.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TriumphLTDAuthor Commented:
Ok good advice thankyou. I will get this booked in.

Dave
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.