Ran with the /p switch? Yeah, that'll result in data loss alright. Without knowing the root cause of the issue, it's hard to determine what you could have done differently. So I guess step one in doing things differently is determine the root cause and evaluate plans of action before executing eseutil with a /p switch which is a step of last resort.
Your database is currently in a state I wouldn't trust if it were my server. I'd highly recommend looking for a way to get the users onto a new clean database/ determine what the root cause of the problem was so that it can be prevented from occurring in the future. Since Exchange 5.5 support ends in a few months, perhaps moving to Exchange 2003 can be the method by which you achieve that objective. Chris Scharff MessageOne -----Original Message----- From: Aristotle Zoulas [mailto:[EMAIL PROTECTED] Posted At: Friday, April 30, 2004 3:18 PM Posted To: swynk Conversation: eseutil Subject: eseutil We were having many problems on our exchange 5.5 server. Store.exe was crashing and was runnign 100%CPU. We ran eseutil /ispriv /g and eseutil /p /ispriv /x. It found many bad items (over 5000) Now users are companing they lost some or all of their attachements. Is there anything we can do to prevent it from happening again? What could we have done differently? Thanks In Advance. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
