RE: Database corruption after moving mailbox from 5.5 to 2003?

  • From: "saleem" <sroumald@xxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Fri, 18 Jun 2004 11:49:00 -0400

Hello guys ,
I do not know which version of Exchange did you install , Is it standard or 
enterprise , Check the *.edb size if it is near to 7GB you are in trouble may 
be an upgrade to enterpise could a solution . I got this problem before i 
upgrade it after now it is ok . also when you moved from exchange 5.5 to 
exchange 2000/2003 make sure you have a lot of space For example if you are 
moving 5gb of mail make sure in temp folder you have more than  5GB or else you 
are in trouble

        -----Original Message----- 
        From: Tom Battersby [mailto:tomb@xxxxxxxxxx] 
        Sent: Fri 6/18/2004 12:28 PM 
        To: [ExchangeList] 
        Subject: [exchangelist] Database corruption after moving mailbox from 
5.5 to 2003?
        We are currently moving from a single Exchange 5.5 server (NT4 SP6a BDC)
        to a single 2003 standard edition server SP1 running on windows 2003
        server standard, with all SUS deployable patches installed. We have got
        the two servers running in the same site, replicating etc. Our AD has
        mainly 2000 SP4 domain controllers, and the exchange server itself is a 
        (2003). The Active Directory connector is on the new 2003 server. We are
        in AD mixed mode due to the legacy mail server.
        We moved test mailboxes over OK, and I moved my own mailbox (c.
        45MB)without any problems. However, the last two mailboxes that I moved
        using the move mailbox wizard have caused the mail store to report 
        corrupted (both were c. 80MB).
        There is no loss of functionality in Outlook for the moved user, the 
        will mount and dismount OK, and the event log just says that it moved 
        mailbox. The wizard also says everything is fine when you do the move.
        However eseutil /g says 'Database is CORRUPTED!' and backups of the
        information store fail both with NTbackup and backup exec 9 sp1 agent 
        exchange. The first time I wasn't sure it was the migration as i didn't
        spot it straight away, but i have just moved another box, running 
        /g immediately before and after the move. Before - OK. After - corrupt.
        BUT - if i run eseutil /d on the database, it completes fine, and 
        /g subsequently reports all is well, ie it has fixed itself.
        And although the information store object can't be backed up when it
        reports as corrupt, i could still back up every mailbox without any
        The only errors I have got in the event log are related to the system
        attendant trying to access the store whilst it is dismounted for defrag 
        I have two 9175 and two 1005 errors.
        Anybody seen this before, know how to avoid it or what? Anybody know if 
        is a real problem or not?
        List Archives:
        Exchange Newsletters:
        Exchange FAQ:
        Other Internet Software Marketing Sites:
        World of Windows Networking:
        Leading Network Software Directory:
        No.1 ISA Server Resource Site:
        Windows Security Resource Site:
        Network Security Library:
        Windows 2000/NT Fax Solutions:
        You are currently subscribed to this Discussion List as: 
        To unsubscribe visit

Other related posts: