Recover/Merge Contact to Store from Recovery Store

Had a wonderful weekend of getting exchange back up after a database failure. Long story short I am now at the point were I am trying to recover certain mailboxes from the recovery store and cannot do it. Most of them worked fine but still have a few that error out. Below are the 3 error logs I get when doing these users.

1. The MAPI call 'OpenMsgStore' failed with the following error:
The client operation failed.
An unexpected, unknown error has occurred.
Microsoft Exchange Server Information Store
ID no: 8004010f-0501-00000000

2. Unable to get an administrative interface to the mailbox store on server 'GAREXCHANGE'.
Error: The client operation failed.
An unexpected, unknown error has occurred.
Microsoft Exchange Server Information Store
ID no: 8004010f-0501-00000000

3. Unable to recover mailbox temp'.
Error: The client operation failed.
An unexpected, unknown error has occurred.
Microsoft Exchange Server Information Store
ID no: 8004010f-0501-00000000

If anyone has any ideas please lay them on me. Thanks... again, didnt have this issue with about 90% of the other users.
gsswho6Asked:
Who is Participating?
 
lucid8Connect With a Mentor Commented:
If the LegacyExchangeDN issue doesn't pan out, then did you run an ISINTEG on that db after your ran the /P?  If not I would try that as well since it could just be an integrity issue that needs to be resolved.  

NOTE: When you run ISINTEG you need run it until you have 0 errors fixed.  Usually you have to run it at least twice.  

NOTE 2: You mentioned you ran /P against your active DB, this weekend?  Did you then run a eseutil /D and and ISinteg -fix against it before putting it back into production?  If not you are going to want to do that ASAP or you may run into additional issues.  Other option is to create a new database and move users into it ASAP so that you have a clean non-repaired EDB.

Other option is a 3rd party utility like Amit suggested but I would definitely clean up the DB with Isinteg before you go that route since utilities may or may not be able to overcome this issue for you and IMO always best to have a clean database.  However with most you can at least open the DB and walk the mailboxes with a demo license so that you can see the data you want to recover before making a purchase.  If you want to discuss other options offline you can obtain my contact info from my profile

 NOTE 3:  hopefully you have not exeuted the /P against your only copy of the EDB.  Either way before you execute any additional commands against the RSG version or the production version ensure you have an offline copy so that in case something goes south you can quickly roll back.    


0
 
AmitIT ArchitectCommented:
Repair the DB and try again.
0
 
gsswho6Author Commented:
I really didnt want to go that route again... Had a long weekend of doing that just to get exchange backup with some data left. :(

Any other option here?  
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
AmitIT ArchitectCommented:
I am asking to repair the RSG DB and try again.
0
 
gsswho6Author Commented:
ok... so you mean eseutil /p correct? I just want to make sure I dont screw anything up on my current production database. Just being cautious I guess.
0
 
AmitIT ArchitectCommented:
ya...you are right....sometime due to db corrupting these error will come. Normally after repairing DB, it use to be fixed. Do it on RSG DB. Dismount the db first and then run it
0
 
gsswho6Author Commented:
SO i h ave a dumb question... IF I have multiple sets of the edb/stm files named different things. Lets say I have priv1, priv2, priv3/etc.... Can I just dismount the recovery store and change the DB/STM path to the other to see if those files work for exporting? Just wondering since i can give each set a test and see if they work. Each set I have is a different date/file size.

Thanks
0
 
AmitIT ArchitectCommented:
You cannot run repair on mounted db. So don't need to worry about prod db. For finding RSG DB path, you will find the folder with Recovery Storage Group. If you haven't changed it else check the path and run the eseutil /p against RSG DB and you need to run it against .edb only. I assume you have Exchange 2003 as stm are no longer part of 2007 or 2010.

ESEUTIL /P dbfilename.edb

Mount the DB after repair and use Exmerge
0
 
gsswho6Author Commented:
ok i will give it a shot... thanks... However what about my other question? Can i just chance the DB path to an alternate location if I have another DB I want to test with?
0
 
gsswho6Author Commented:
Ok did the repair... Same exact thing for those users. Any other ideas?
0
 
AmitIT ArchitectCommented:
This answer discuss about incorrect legacyexchangedn issue can you verify it.

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_21642159.html

If this doesn't works and mailboxes are very important you can look for 3rd party tool
http://www.exportedbtopst.com/
0
 
lucid8Commented:
What version of Exchange are you running?
0
 
gsswho6Author Commented:
2003.
0
 
gsswho6Author Commented:
I ended up purchasing QUEST and repaired my database and did some mailbox restores... Was pretty simple and was able to do what the eseutil couldnt.
0
 
lucid8Commented:
Glad you were able to get things resolved and thanks for the points!
0
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.

All Courses

From novice to tech pro — start learning today.