Error c104173b - database files are corrupt. 1

[rookery]

Hi guys,

Our Exchange has fallen over and when we try to mount the database we're getting the above error. Any ideas how to remedy this situation? This is really urgent if anyone can help.

TIA.

 

[Andreh]

You probably have two options -this is an indication that your database is corrupt.

Restore from backup or repair the database manually using a repair tool.

http://www.dugger-it.com/articles/e2kdrtools.asp

http://support.microsoft.com/default.aspx?scid=kb;en-us;812357

I had to do this sort of recovery once for a system running Exchange 5.5 with a 8Gb database that was totally stuffed. It took 18 hours one Saturday but the effort (and experience) was well worth it. My guess your hardware is alot quicker that this situation.

Goodluck

 

[xenotec]

Check the Event Log for errors
Potentially

http://support.microsoft.com/default.aspx?scid=kb;EN-US;241855

Also, For best practices I recommend reviewing the following

http://support.microsoft.com/default.aspx?scid=kb;EN-US;245822

 

[rookery]

Thanks guys for your help. Managed to get it back up and running by mounting it into two empty shells.

 

[999Dom999]

"rookery (Programmer) Sep 1, 2003
Thanks guys for your help. Managed to get it back up and running by mounting it into two empty shells. "

I have exactly the same problem, how exactly did you fix this? I have no backup and I dont want to do a eseutil /p unless absolutely nesessary, not sure what you mean about empty shells.

Any info would be great. Has anyone else done a eseutil /p and did it work?

 

[rookery]

Hi Dom,

Apologies but I cant quite remember what "I" did. It was something to do with creating two new objects and moving all the objects from the corrupted objects into them. It wasnt me that did it see so I'm not to sure.

Sorry cant be of more help.

 

[999Dom999]

OK i managed to fix this with a little help from Microsoft. I have searched the internet and there is not any decent documents that fully explain how to repair an exchange database from start to finish. Both mailbox store and public folder store were corrupt.

This is what I did:

eseutil and isinteg are found in c:\program files\exchsvr\bin directory, to run these go to a command prompt and change to this directory

Public folder store repair:

eseutil /p "e:\program files\exchsvr\mdbdata\pub1.edb" /s "e:\program files\exchsvr\mdbdata\pub1.stm"

change path to where your database is.


Mailbox Store repair:

eseutil /p "e:\program files\exchsvr\mdbdata\priv1.edb" /s "e:\program files\exchsvr\mdbdata\priv1.stm"

change path to where your database is.

Once this is done you need to clear out all the transaction logs, so that all you have left in the mdbdata folder is priv1.edb priv1.stm pub1.edb pub1.stm

Then you should be able to mount both stores then dismount them and run

isinteg -s exsvr01 -fix -test -alltests

Change exsvr01 to your exchange servers name, then it asks you which store you want to run on, do the mailbox store then if you repaired the public folder aswell repeat the process and choose public folder store.


This was probably just a problem with my server but when i ran

isinteg -s exsvr01 -fix -test -alltests

It just gave me the options to use with isinteg so I just copied an example which was

isinteg -s server1 -fix -test -alltests

this came back with server not found then i repeated

isinteg -s exsvr01 -fix -test -alltests

and it worked fine, weird I know but thought I would mention it!

Anyway I hope this makes things a little clearer for anyone with the same problem, having a working backup would have saved all this trouble. I have marked this thread so reply if wish to ask me anything about the above.

Dominic Goff

 

[999Dom999]

I missed out once you have run isinteg, mount the stores and all should be fine!

Dom

 

[rookery]

Thanks for the follow-up Dom.
Sure this will be of use in the future!