I tried using exmerge with the repaired database but it will not run even though I am logged in with Exchange's service account. The attachements will not open. Any suggestions?
Honestly, it becomes difficult to guess out of thin air as to what the issue could be until you provide facts. To begin with.
Which version of Exchange / Windows were on production AND test server. How big were the database you repaired - how long did it take for repair / defrag. How many fixes did the IsInteg fix - how many times did you run it? Which account you are using to work with ExMerge? Which groups are the user part of (The exMerge account) What is the error you are facing while running ExMerge (Check ExMerge.log)
Even after running the repair - you still find problems opening the old email attachments i think third-party tools like On Track"might" be able to help - rare chance - but honestly, after you have run the repair - defrag - isinteg successfully - you still face issues with regards such case - Exchange might not be of help beyond this level of troubleshooting.
Thanks for your reply. Do you think I should try using Exmerge first then repair the database? I would then use Exmerge again to merge back the pst files into the repaired ones. Seems quite long and manual....
If you were able to export messages using Ex Merge after repair-defrag-isinteg. I would be more interested in opening those PST in outlook and check if the attachments are able to be seen in OL. If not then Exchange wont help you any bit.
In this case try looking for some third-party tools unless you plan to repair the database couple of more times (which i dont find any sensible reason to do so).
Thinking on those the R-D-I terms - how many fixes did you find when you ran the IsInteg for the second time - was it "zero" ??
Yeah, I was able to use ExMerge after the R-D-I. OL recognises the attachements and enables me to open some of them. Other messages contain the attachement symbol but can't be opened. I only see the message and the paper clip symbol.
I can't recall if the number of fixes after the second Isinteg eventually reduced to zero. Should it be an essential information, I could repeat the operation again from scratch although it would take much time...
So far as inbuilt exmerge.exe and repair utilities are concerned, these tools remove the corrupt database pages. Eseutil looks at each Exchange database page and table and ensures consistency and integrity within each table. Isinteg repairs a database at the application level and ensures the integrity of the relationships between tables. As these utilities do not repaired the corrupt pages else delete them to bring the database back to consistent state, users have to face data loss situations.
This graphically rich application supports all versions of MS Exchange server (5.5, 2000, 2003, 2007 and 2010) and provides two options: - EDB to PST conversion: Repair the corrupt or damaged database and then export Exchange mailboxes into .pst files - Rebuild Database: Repair and rebuild the corrupt or damaged Exchange database file to mount the database directly to the Server.
Free demo version of the product is also available to test the features and functionality.
http://www.recoverytoolbox.com/exchange_server.html reconstructs corrupted exchange folders, messages and rest items are damaged by power shortages or surges, physical damage and incorrect user's actions. Utility doesn't change original corrupted exchange file during repairing, it creates the copy and restores it. Tool starts under all Windows OS, starting with Win 98.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 5.5] >> General >> Corrupt database 
Corrupt database - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
