Event ID: 478

10 pts.
Tags:
Backup Exec
Event ID
Exchange Backup
Microsoft Exchange errors
NTBackup
Small Business Server
Hello all First I like to thank for your time I am new to IT field and I am administering small business exchange server. A few week ago the exchange server had a hard crash due to insufficient disk space. after I do some clean up I am not able to do back up in back up exec as well as NT back up. I look at the exchange server even view there is error SES, Event ID: 478. after I do some research it lead me to do repair exchange database using eseutil /p and eseutil /d. My question is 1. is the information I got it from my research is correct 2. if this is correct, could you please help me how to do this? I have never done this so i am not comfortable doing without detail step by step and good advise from your expert. again thank you soo much for your time

Answer Wiki

Thanks. We'll let you know when a new response is added.

Here is an excellent guide for you.

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following