To fix this, you will need to perform a recovery on the store using ESEUTIL with the /r option. This should bring it back to a consistent state.
Any time you run ESEUTIL on a store, it's a good idea to copy the store and transaction logs to an alternate location or take a backup of the file system. Then navigate to the storage group that the affected store belongs to, and from Properties -> General tab, note the "Log file prefix" -- E00 by default for the first storage group.
To start the recovery process, go to a command prompt and type: EXCHSRVRBINESEUTIL.EXE /r /l
Do you have comments on this Ask the Expert Q&A? Let us know.
Related information from the TechTarget Windows Network:
Dig Deeper on Exchange Server setup and troubleshooting
Related Q&A from Bharat Suneja
Find out how to troubleshoot problems scripting Exchange Server email disclaimers and signatures. Continue Reading
Learn how to bulk modify alternate recipients and other Active Directory objects in Exchange Server 2003. Continue Reading
Discover tools and methods to globally disable IMAP and POP in Microsoft Exchange Server 2003. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.