Exchange Store Is Empty

We have Windows 2003 SBS, we had a server crash. We got the server back up and now the Exchange store will not mount. The EDB and STM files together are only 2 GB. There are 7GB of logfiles. Ran the eseutil on the DB and got it to a Clean Shutdown state and got the store to mount only now there are no mailboxes showing. I have verified that the file sizes are the same before and after running the eseutil. I have gone back to backups with the same end result. I even used VSS backups with no difference. I reinstalled Exchange and that did not correct the issue. Next I am going to try and mount the store on another server. Has anyone encountered this before?
intermakersAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Alan HardistyCo-OwnerCommented:
Have you run eseutil /p, then eseutil /d and then isinteg -s servername -fix -test alltests?
If not, this may well fix your problems.
/p is repair, /d is defragment and isinteg checks integrity.
0
amdaxiomCommented:
Any idea how big your .edb and .stm files should be?  If they are supposed to be something like 40 gigs you are not going to be able to repair your files and will have to restore from backup.  I'm assuming no backups?  Otherwise this would be a relatively simple process.
0
intermakersAuthor Commented:
We have VSS backups and they all show edb and stm file being around 2 GB and the logs being around 7gb. This sounds about right for this company.
We tried to run the integrity check and it did not show any indicators or movement for 18 hours so we stopped it.. We are desperate to get this data. Any other ideas?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Alan HardistyCo-OwnerCommented:
Have you followed all suggestions in my first post?
0
intermakersAuthor Commented:
We did eveything in your suggestion. The problem is, when we ran the isinteg it just sat there for 18 hours without any indication of movement.
0
stu29Commented:
Have you verified your db and log file locations match the location and name of your restored files in ESM?
0
intermakersAuthor Commented:
Stu
Yes they match. We tried mounting the store on another exchange server but it still comes up with no mailboxes.  We don't know how to retrieve the data.
0
intermakersAuthor Commented:
another comment. We ran a repair on the 2nd exchnage server (test server) and when it completes it indicates "database has been repaired!". We then mount the store successfully and there are no mailboxes in the store. We don't know how to get the data out since exmerge will not see any mailboxes. In addition we have been mounting the store in the recovery storage group.
0
stu29Commented:
This may sound like a really dumb question .. but does ESM show an email traffic?
0
intermakersAuthor Commented:
The production server's store is not mounted so I am assuming there is no traffic. Our issue however is with getting the data out of the mail store.
0
stu29Commented:
does your production store mount if you try?

May be time to break out adsiedit.msc and browse to the storage groups and stores
under the configuration container and under security properties see if
they are denies to the everyone group or something similiar.
0
Alan HardistyCo-OwnerCommented:
When you ran isinteg did you get to choose the mailstore you wanted to check?
0
intermakersAuthor Commented:
I ended up fixing this issue once we loaded the mdb onto a new server. Thanks everyone.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.