Link to home
Start Free TrialLog in
Avatar of shaneh426
shaneh426Flag for United States of America

asked on

SBS 2003 Exchange Store possibly corrupted

Good afternoon experts,

I've got a mess of an Exchange situation that I just recently inherited and I really need some help.  My client's server bit the dust and another IT company virtualized their server to get them back up and running as quickly as possible.  Their server is a Windows SBS 2003 server (non-R2) and it is running as a virtual machine in hyper-v on a Server 2008 box.  They've been having email issues for quite a while now and I've finally been able to pinpoint it to the Exchange store.

When I first took over, everyone's Outlook was connected to the Exchange server.  However, they used Outlook to download their email from an external mail host and stored it in their Exchange mailbox.  Many users had issues of Outlook downloading the messages and then when they were synced up to the server, the messages would disappear.  Other users would have all attachments that they sent and received stripped from emails, and a few were downloading duplicate emails over and over.  

ScanOST confirmed the vanishing emails were on the server but were not downloading to the local mailbox.  ScanPST kept finding corruption in the local mailbox and repairing it.  I tried setting up the POP3 Connector to download and deliver all email so that everyone would just be using Outlook but when I tested this with a few users, they could no longer send or receive email at all.

The Exchange store says it is in a clean shutdown state but everything I've tried before says there is massive corruption in the store.  

I used Exmerge to export everyone's mailboxes to PST, disconnected Outlook from the Exchange server completely and set everyone up to only use the POP3 host.  This is only temporary so that I can take the Exchange server offline and repair it.  I tried using instructions for eseutil to repair it overnight (before I got everyone off of it) but it didn't seem to work.  Based on the output it gave me, I would like to try running it again with assistance.

Any help anyone can give me will be greatly appreciated!

Shane
Avatar of Joseph_Barron
Joseph_Barron

So the problem with E-mail downloads from the external mail host pre-dates the server crash and naturalization?

If you have a temporary patch in place and data exported to PST's, it might be better to stop working on this issue of corruption and spend time moving them up to Exchange 2010. I don't know if you have the budget, or if they are hell bent on staying to a decade old solution, but it seems like it might be time.
Avatar of shaneh426

ASKER

To be honest, I don't know for sure if the problem predates the crash.  I've asked several people many times and I get slightly different answers.  Most of them say the issues didn't start until after the server crash.  

I agree that we've got to get them off of Exchange 2003 but they are a non-profit and don't have the budget right now. I have no problem keeping them on the external host permanently but the problem is that Exmerge was not able to extract all of the mail out of the store.  According to Exmerge, the store houses about 15GB worth of data but it was only able to extract 1.29GB total from the store with all email accounts selected.  I've got to at least recover the emails currently stored on the server if at all possible.
eseutil reported what kind of output? Was the DB in a clean state before running it or after?
Also, and I'm afraid to ask this question, what Backups of the Exchange Data Store are available?
The DB was in a clean state before and after running eseutil.  Yep, you guessed it.  They didn't have any backups of any kind before I took over.  I did snag a backup of the MDBDATA folder before trying anything with the store but of course it is not before the corruption.
Are the emails being deleted once downloaded to user computer?
I would configure POP/IMAP, what ever services customer is using and configure it on Exchange.
So emails are directly downloaded to exchange and then distributed to user.
I used Exmerge to export everyone's mailboxes to PST, disconnected Outlook from the Exchange server completely and set everyone up to only use the POP3 host.
this essentially is a backup of your exchange database, correct.

This is only temporary so that I can take the Exchange server offline and repair it.
why not delete the database create a new one and import pst files back into it. Why try to repair a corrupt database when you don't need it.

I tried using instructions for eseutil to repair it overnight (before I got everyone off of it) but it didn't seem to work.  Based on the output it gave me, I would like to try running it again with assistance.
create a new database and import into it.
Supports:  I tested that as one possible solution and it is what I plan on doing as a permanent solution but, I tested one client on that setup and Exchange would download their email but nothing would show up in Outlook.  This is why I believe the store is corrupted and am trying to repair it.

Works2011:  As I mentioned in one of my comments, Exmerge was only able to extract 1.3 GB from the store which is over 15 GB.  Once I can extract all the data from the store, I will most likely recreate the database as long as I can do so safely.  I've heard its not as easy on SBS Server.
If all the emails are still store in Clients PST. My suggestion would be to create a new Exchange database.

Otherwise you require this
http://www.msexchange.org/tutorials/exchange-isinteg-eseutil.html
ASKER CERTIFIED SOLUTION
Avatar of shaneh426
shaneh426
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
No solution resolved my issue.  Even though I wound up recreating the database as many experts suggested, I was not able to extract all of the corrupted email which was my sole intent for posting this question on here.