Re: Exchange 2003 mailbox import problems

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Nicholas Basile\(MSFT\) (nicbas_at_online.microsoft.com)
Date: 05/03/04 

Date: Mon, 3 May 2004 13:25:56 -0400

You most likely do not have the appropriate permissions to use Exmerge.
Check the following link on how to configure:
http://support.microsoft.com/default.aspx?scid=kb;en-us;823143 

-- 
Nicholas Basile(MSFT)
nicbas@online.microsoft.com
Microsoft PSS
Please do not send email directly to this alias is for newsgroup purposes
only!.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Leon McNichol" <not@set.com> wrote in message
news:OAaPjKTMEHA.808@tk2msftngp13.phx.gbl...
> Hi,
>
> We are trying to migrate over to 2003 from 5.5. We have been having a lot
of
> problems, and are now actually on our third install of the product.
>
> On the previous installation, I was able to use Exmerge to import my
> mailbox, and then view it from Outlook. However, I was unable to view it
(or
> any mailbox, except the Administrator box) with OWA.
>
> I fought with that for a bit, and had an export of the 5.5 mail store
> running on the 5.5 server. As this would take a very long time, I left and
> came back a few hours later to find that the database on the 2003 server
had
> corrupted itself so badly that even eseutil would not correct it.
>
> Yesterday, I stopped the services, moved the corrupt DB's and started the
> services then mounted "nothing", which allowed me to create new DB's. At
> that point, I could no longer import any mailbox other than the
> administrator box through exmerge.
>
> And, oddly, I was able to access my empty mailbox through OWA for some
> reason, as was another admin here.
>
> Today, we uninstalled the product and rebuilt the entire server from
> scratch. The databases corrupted themselves almost immediately with
nothing
> being done to them or the sever. This time, eseutil was able to correct it
> however.
>
> Now, I have created a new mailbox for myself, and once again can access if
> via OWA for some reason (info on the KB implies that it needs to first be
> activated, only this time it hasn't been), but I can only import the
> administrator mailbox with exmerge. It fails on every other box with an
> error of being unable to open the message store.
>
> Additionally, the Exchange Management Service will not start now. I can't
> help but wonder if the 2 are related, but I also can't find information on
> either in the KB. :(
>
>

Relevant Pages

  • Re: Proposal/RFC for FAQ on using ExMerge as backup aid in SBS2003
    ... How to Use Recovery Storage Groups in Exchange Server 2003 ... Mailbox Merge utility to export the mailbox that you need to a .pst, ... > Having struggled mightily recently to set up ExMerge correctly, I'm posting> what I think is the "right" way to do things. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange 2003 move mailbox wizard or Exmerge
    ... Exmerge is the way to go here. ... Please do not send email directly to this alias. ... > the mailbox on the new server and then copy the pst into the new mailbox. ...
    (microsoft.public.exchange2000.setup.installation)
  • Re: exmerge 14GB log file
    ... Move the mailbox to a new server (effectively recreates the mailbox and ... look for long chain corruption. ... Exmerge is a great ... running exmerge or you move it to another server in a different routing ...
    (microsoft.public.exchange2000.information.store)
  • Exmerge Error...cant find help!
    ... I am trying to run ExMerge on our Exchange 2000 server to backup some ... I put ExMerge in the /Bin directory and ran it. ... administrator account which has full access to the mailbox store, ...
    (microsoft.public.exchange2000.general)
  • Re: Proposal/RFC for FAQ on using ExMerge as backup aid in SBS2003
    ... (the second part - Mailbox Merge). ... Les Connor [SBS MVP] ... >> Having struggled mightily recently to set up ExMerge correctly, ... >> If you use the SBS Backup Wizard, you'll be backing up all your Exchange ...
    (microsoft.public.windows.server.sbs)