Hi, can someone guide me through the process of mounting an existing exchange database on a different server? I have the priv1.edb and priv1.stm files. The source and destination machines are both Exchange 2003.

Have a look here: http://technet.microsoft.com/en-us/library/aa997006(EXCHG.65).aspxWith kind regards Krystian Zieja http://www.projectnenvision.com Follow me on twitter My Blog

I've created an empty database on the new server, I then put the old database in place and tried to mount it but I'm getting an error message c1041724. Edit: In my application logs I get these messages: Information Store (2588) First Storage Group: Attempted to attach database 'E:\test.edb' but it is a database restored from a backup set on which hard recovery was not started or did not complete successfully. Error 0xfffffde0 starting database "First Storage Group\test" on the Microsoft Exchange Information Store. Is there any way to fix this?

1. Your database is may be in a dirty shutdown and may be missing logs that are needed 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. And see of any logs are required to bring it in a clean status 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 switch Sukh

Hi Michael, Please try this solution: http://support.microsoft.com/kb/253931 Best Regards!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.

I've just run eseutil /p which said it has repaired some corruption, I have tried to run eseutil /cc E:\test.edb but it says: Operation terminated with error -939586631 (Unknown Error, Unknown Error) after 0.81 seconds. I am still unable to mount the store, in my logs I'm getting this message: eseutil (440) Unexpected file system error 3 encountered while opening the restore environment file.

1. Run the eseutil /cc as per http://technet.microsoft.com/en-us/library/aa998097(EXCHG.65).aspx it's to replay the logs, you dont run on the edb itself. Make sure you run this in the dire whewre your restore.env. Sukh

Where do I find this env file? Is there any way of mounting or reading the database without this step? I just want to export some messages from a user's mailbox to a PST file.

Hello Michael- The restore.env file is created when you restore the database from backup. You usually will have some log files along with the restore.env file in the same folder location. This can vary but a lot of times it is in the temp directory within a folder you specify in the restore process. If those files are gone or never played back you cannot get this store to mount and you will need to either restore this again or find a clean shutdown copy of the files. Before you EVER run eseutil /p on a database you should save a copy if at all possible. Eseutil is a very powerful process and should not be run unless you know there is an issue that you cannot get around. As you have ran eseutil /p already on the database you can simply try going to the properties of the database in ESM and mark that the database can be overwritten by a restore and try mounting. (I would run eseutil /mh to confirm the clean shutdown state) If this fails you may want to look at third party solutions- there are many out there available by a "bing" search. I have heard of others using these utilities with success. There is a very specific recovery process with ESEutil, and any variance from that will leave the database unable to be accessed. Here is a good overall process with screen shots http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/

First create the store in new server(store,edb &stm should be as old) and mount it now dismount it and rename the new edb & stm copy the old edb & stm in the same place cut & copy all the transaction log to different location. run eseutil /r e00