The Log files were deleted on our Exchange 2003 server due to the hard drive filling up. Now the store won't mount. We have ran the Integrity Checker and it was successful but the store still wont mount. We dont have a backup and need to have this repaired. Our next step is to run defrag the database and then run isinteg -s servername -fix -test alltests Here is the output from the checker logs Here is the output from the repair run it did: E:\Program Files\Exchsrvr\bin>eseutil.exe /P "e:\Program Files\Exchsrvr\MDBDATA\ priv1.edb" Microsoft(R) Exchange Server Database Utilities Version 6.5 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating REPAIR mode... Database: e:\Program Files\Exchsrvr\MDBDATA\priv1.edb Streaming File: e:\Program Files\Exchsrvr\MDBDATA\priv1.STM Temp. Database: TEMPREPAIR4492.EDB Checking database integrity. The database is not up-to-date. This operation may find that this database is corrupt because data from the log files has yet to be placed in the database. To ensure the database is up-to-date please use the 'Recovery' operation. Scanning Status (% complete) 0 10 20 30 40 50 60 70 80 90 100 |----|----|----|----|----|----|----|----|----|----| ............................................................. Integrity check successful. Note: It is recommended that you immediately perform a full backup of this database. If you restore a backup made before the repair, the database will be rolled back to the state it was in at the time of that backup. Operation completed successfully in 115815.609 seconds.

1. Your database is probably in a dirty shutdown and is missing logs ot needs to mount the DB. Check your DB using eseutil / mh - http://technet.microsoft.com/en-us/library/aa997795(EXCHG.65).aspx. When you run the command see if the database is in a clean or dirtyshutdown. 2. As you havent got a backup and cnt do a restore or get the logs back, you may he to repair the DB with the /p switchSukh

I understand you have no backup at all, is that correct? it appears that you already did an eseutil /P correct? Did you by chance make a copy of the database prior to running the eseutil /p? if not I would suggest you do this immediately Besides the drives filling up were there any other issues? When you deleted the logs was the database up and operational or had you taken it down first? If you did a /P then and it completed without error then it should just mount without issue, however could be you have some conflicting logs still in the path. If you have other databases on the system I would Take the databases offline Make a backup copy of the existing logs, or if the logs are in a separate directory then rename the log path, i.e. if its ExchLogs, rename to OLD_ExchLogs and then create a NEW directory named ExchLogs. Attempt to start the damaged database and report back. If it will not mount, you may want to do a sanity check by downloading Lucid8's DigiScope http://www.lucid8.com/product/digiscope.asp , obtain a demo license and mount the database. If it mounts without error then you know the database is fine and you have some other issue. Report back and we will try to assist ASAP. Worse case if you need to get everyone operational ASAP and want to back fill in the data later you can move the database file that wont mount out of the current path and then mount the database in the management console. This will create a new database and users will be able to send and receive email again and then you can use the MS RSG or DigiScope to open the old database and back fill into the new databaseTroy Werelius www.Lucid8.com

Hi WilcoIT, Any updates?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.