5 replies
by mckaytech
If you go to Microsoft's TechNet site and search on "Exchange v5.5 and earlier" and "Dr. Watson on STORE.EXE", you'll come up with a bunch of information. Many of these events are related to certain types of bad messages and have been fixed in SP3 or later for Exchange. So the first step would be to verify your Exchange service pack level.
That having been said, in my experience, the most common cause for what you're seeing is a corrupted Information Store. Since your server is currently off-line anyway, you should run eseutil.exe (instructions and command-line parameters can be found on TechNet in article Q182903) and see if it confirms the corruption.
If this is the case, your best bet is going to be to restore from backup. ESEUTIL can perform a repair on the existing database but my experience with it has not been good and you nearly always lose significant amounts of data.
paul
by jaydev
by complexmind
Had a similar problem "store.exe Exception Access Violation"
Even after restoring from backups I had this problem.
Ended up running:
"Isinteg -pri -fix -test folder,message,mailbox" and
"Isinteg -pri -fix -test folder,message"
Suggest yourefer to MS Technet articles Q147244 and Q182081 for information on fixing this problem.
Hope this helps. It was a nightmare for me when this happened.
by jaydev
by jaydev
This discussion is closed to new replies.
Trending Software posts
Sort by Trending