Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can't open attachments after a mail restore

Status
Not open for further replies.

Andy542

MIS
Jul 3, 2002
60
ZA
I ran the eseutil /p on my exchange server (priv.edb) after the edb.log was deleted by the antivirus. The run was successful and the even IS service started. I stopped the service to try an run a defrag which bombed out and the IS couldn't start. I tried rerunning the eseutil /p. During this run the server froze and the process stopped (or was taking too long - nearly 6 hours). I later run it successfully and after the database became consistent I ran the isinteg -fix -alltests and fixed all the errors. I restarted the services but now users can't open any attachment prior to the failure time. The error message is
"Operation Failed."
The errors I have encountered include the following service specific errors; 4294966781, 4294966746, 4294966274, 4294967041, 4294966766.

I don't have the latest backup so I can't restore a previous backup.
Any help?? I've run short of ideas!


Andy
 
with isinteg -fix -alltests you need to run it repeatedly until it says that there were no errors. when my antivirus software deleted the logfile we had to run it about 3 times before it went through without any errors. The process that we ran to successfully bring it back to usability was to run that command. However, wehn people came into work the next day the mail got caught for some reason in the IMC outbound queue. we ran eseutil /mh to ensure consistancy, for good measure we ran eseutil /R then we ran isinteg -fix -alltests -verbose until no errors were found. We had to restart the server before we did this however. After this it ran fine but for good measure we restored a previous version of the database from before the antivirus incident. But the main commands we used were eseutil /r /ispriv and isinteg -fix -alltests -verbose

hope this helped
 
sorry, we also ran eseutil /g before trying to do eseutil /p just in case. After running isinteg -fix and eseutil /p we'd run eseutil /g again. when we did that it eseutil /g still crapped out so we restored a previous PrivIS.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top