• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 407
  • Last Modified:

move users to new mailbox store (existing DB's corrupt)

I have a client whose exchange DB is corrupt. I've run
ESEUTIL integrity and verification checks and confirmed such (626 page errors). Store will
not mount, and the Transaction Logs were set to circular.
Assume for now that backup is non-existent. Keep reading.

Very small company so the quickest thing to do was
extract mail to PST's.  Negligible amount of Public
Folder Data was copied and extracted as well.  All went
smoothly.  All mail has effectively been saved in PSTs.

I assumed the easiest thing to do would be create a new
mailbox store and exmerge the PSTs.  However, I am
unclear as to the proper way to associate the existing
domain (and users) with the new mailbox store.

I was thinking that I could 'clear exchange attributes'
for each user, delete each user's old mailbox and recreate a new
mailbox for each, but was unsure as to the full effect of
this move.  

Is there not a way just to 'RESET' the old mailbox
store/db?  We have the old Data in PSTs, so I essentially
just want a new, empty mailbox store in the same place
with the same users/attributes to begin exmerging the PSTs into.  Am I dreaming?

1 Solution
Rename the folders that contain the Exchange databases and log files. Then create a new directory. Be sure that you do this on all drives on the server.
Now when you mount the databases, new ones will be created. You can then EXMERGE the data into the new mailboxes. Prior to the EXMERGE process, you may have to send a test email to all users.
RussianblueAuthor Commented:
The renaming of folders worked without a hitch.  Took me 5 min.  Should have asked here earlier!  

Exmerge failed from the server with "Error creating Message Service (MSPST MS)"

MSKB 174197 says:

If you receive the following error:
Error creating Message Service (MSPST MS)
Make sure that Exchange client is installed on the computer that Exmerge.exe is running on.

Outlook, I take it?  On the server?  Hmmm.  Thought I'd been specifically directed NOT to do this!  I'll just import from the user workstation.  No biggie.  You got me through the tough part!  Thanks for the quick help.


Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now