EXCHANGE 2003 - Information Store loads and then the server freezes

This is an SBS 2003 installation with Exchange 2003 SP1.  The mail server was working fine for 1 week with heavy volume.  I did a bonehead move late one night and did a backup to disk.  I normally back it up to a SAN disk drive but I choose the same volume the server is installed on (E: partition).  I did a full backup, so basically it crashed part way through when it was trying to backup the backup folder to itself.  Since then, I've had intermittent freezing problems with exchange information store.  Now the information store loads and within 60 seconds will freeze the server.  If I load everything but IS, it won't freeze.

How do I run some repairs against the database without starting IS?

ALso, I am wondering if I may need to do a SBS2003 re-install (much as I have done with Exchange 2003 in the past) where it won't overwrite data or settings but re-install the system files.

LVL 1
fitzpabAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SembeeCommented:
How much space on this drive?
Any errors in the event log? It should be logging something if there is this type of error.

Simon.
0
fitzpabAuthor Commented:
Nor errors.  That is what is frustrating about it.  Just freezes.
70GB free space.  It is a large SATA Raid1 array.
0
fitzpabAuthor Commented:
Anyone know how to start the information store with unmounted databases?  I know once i start msexchangeis I can go to system mgr and dismount them, but it freezes before I can do that...
hmmm...
0
SembeeCommented:
Exchange doesn't just freeze without logging something, unless the database is totally screwed up.
If it is the database then there are some tools from MS, specifically eseutil that might repair the database, but you have to be very careful about running them as they can do more damage if not done correctly. If you aren't sure, then there is only one thing to do...

However I personally would call MS. Don't usually recommend that as most problems can be resolved. They will sit you through every step, and stay with you on the phone until it is done.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.