Announcement

Collapse
No announcement yet.

Help needed for Exchange 2003 Server database revovery

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Help needed for Exchange 2003 Server database revovery

    Hi, we have Exchange 2003 Enterprise SP2 installed in the same machine with our Domain Controller (single) and few days ago we got an error stated if database corruption has occured:
    Event Type: Error
    Event Source: ESE
    Event Category: Database Corruption
    Event ID: 447
    Date: 11/04/2011
    Time: 7:13:15 PM
    User: N/A
    Computer: KDT-SERVER
    Description:
    Information Store (276) First Storage Group: A bad page link (error -327) has been detected in a B-Tree (ObjectId: 1197, PgnoRoot: 153305) of database E:\Exchange\Mailbox Store 1.edb (8135576 => 1866652, 1858587).

    For more information, click http://www.microsoft.com/contentredirect.asp.

    The Server has 2 mailbox stores, 1 on default location and another in E drive (Users data here). We have a backup before the error occured (turn it off after that) but since the new emails keep coming (in large amount) then I've requested to try to recover the latest database data. Fortunately, all users have copy of their data in their local computers (maybe we can use it later in case the database cannot recovered).

    After doing some reasearch, then I built a new domain controller and then install Exchagne Server 2003 on it (no choice at that time, only one computer available). Then test migrating user inbox (create a new one and also with one of the user inbox) to the new exchagne server mail store and everything working fine (internal and external email working well on both test). After that, I'm transferring FSMO rules to the new DC following this guide: http://community.spiceworks.com/how_to/show/164 and then preparing to remove the old Exchagne Server following this guide: http://support.microsoft.com/kb/822931/

    After that, start moving other users inbox to the new server but the process failed in the middle of the process and found some errors:

    Event Type: Warning
    Event Source: MSExchangeIS Mailbox Store
    Event Category: General
    Event ID: 1025
    Date: 11/04/2011
    Time: 8:40:09 PM
    User: N/A
    Computer: KDT-SERVER
    Description:
    An error occurred on database "First Storage Group\Mailbox Store 1".
    Function name or description of problem: SLINK::EcUpdate
    Error: 0xfffffbd3

    For more information, click http://www.microsoft.com/contentredirect.asp.

    and then followed by other errors similar like this for all mailbox that in middle of moving process:
    Event Type: Error
    Event Source: MSExchangeIS Mailbox Store
    Event Category: Logons
    Event ID: 1022
    Date: 11/04/2011
    Time: 8:41:03 PM
    User: N/A
    Computer: KDT-SERVER
    Description:
    Logon Failure on database "First Storage Group\Mailbox Store 1" - Windows 2000 account KUDETA\ben; mailbox /o=Kudeta/ou=First Administrative Group/cn=Recipients/cn=ben.
    Error: -1069

    For more information, click http://www.microsoft.com/contentredirect.asp.

    Event Type: Error
    Event Source: MSExchangeIS Mailbox Store
    Event Category: Move Mailbox
    Event ID: 8507
    Date: 11/04/2011
    Time: 8:42:24 PM
    User: N/A
    Computer: KDT-SERVER
    Description:
    Unable to move mailbox Harie.
    A problem occurred while getting the properties for a message.

    Parent folder name: Jasper Manifold; Message subject: store roster; Error code: 0xfffffbd3.

    Run ISINTEG to check for any problem in the database "First Storage Group\Mailbox Store 1".

    For more information, click http://www.microsoft.com/contentredirect.asp.

    Event Type: Error
    Event Source: MSExchangeIS Mailbox Store
    Event Category: Logons
    Event ID: 1022
    Date: 11/04/2011
    Time: 8:45:34 PM
    User: N/A
    Computer: KDT-SERVER
    Description:
    Logon Failure on database "First Storage Group\Mailbox Store (KDT-SERVER)" - Windows 2000 account KUDETA\Administrator; mailbox /o=Kudeta/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=KDT-SERVER/cn=Microsoft System Attendant.
    Error: -1069

    For more information, click http://www.microsoft.com/contentredirect.asp.

    Event Type: Error
    Event Source: MSExchangeIS Mailbox Store
    Event Category: Logons
    Event ID: 1022
    Date: 11/04/2011
    Time: 8:45:34 PM
    User: N/A
    Computer: KDT-SERVER
    Description:
    Logon Failure on database "First Storage Group\Mailbox Store (KDT-SERVER)" - Windows 2000 account KUDETA\Administrator; mailbox /o=Kudeta/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=KDT-SERVER/cn=Microsoft System Attendant.
    Error: -1069

    For more information, click http://www.microsoft.com/contentredirect.asp.

    Found if the old server hardware failed and then preparing another similar hardware and move the system and data disk on it, installing the driver and have it running well.

    Found continuous error in the event viewer:
    Event Type: Error
    Event Source: MSExchangeSA
    Event Category: MAPI Session
    Event ID: 9175
    Date: 11/04/2011
    Time: 9:05:37 PM
    User: N/A
    Computer: KDT-SERVER
    Description:
    The MAPI call 'OpenMsgStore' failed with the following error:
    The attempt to log on to the Microsoft Exchange Server computer has failed.
    The MAPI provider failed.
    Microsoft Exchange Server Information Store
    ID no: 8004011d-0512-00000000

    For more information, click http://www.microsoft.com/contentredirect.asp.

    Then install Exchange Troubleshooting assistant and ran it against old server database - on last backup the database size around 70 GB (with IS service stopped) and the state was Dirty shutdown and then following recommended action to repair the database using this command: eseutil /R E00 /I (run it from the log file folder - copy eseutil.exe and ese.dll to that folder). The process has been running for 3 days and still no status when it will be completed, always in this state:
    C:\PROGRA~1\Exchsrvr\MDBDATA>eseutil /R E00 /I

    Microsoft(R) Exchange Server Database Utilities
    Version 6.5
    Copyright (C) Microsoft Corporation. All Rights Reserved.

    Initiating RECOVERY mode...
    Logfile base name: E00
    Log files: <current directory>
    System files: <current directory>

    Performing soft recovery...

    Now my question is:
    Some users mailbox have been in the new server store and the rest that have not been moved (or failed on moving process) still in the old store which is cannot mounted and still no status regarding it. What choice I've here to have the new Exchange Server at the new Domain Controller take over the operational? How to merge/move other users data that are still in the old store? When ran exchange task on the user properties (still on the old store) it's like the mailbox exist).

    Any advices really appreciated.

    Best regards,

    Acung
    Last edited by lzd212; 16th April 2011, 16:41.

  • #2
    Re: Help needed for Exchange 2003 Server database revovery

    there's probably a better way to do this, but

    create a new mailstore, move the data onto the new mailstore.
    delete old mailstore.

    you could also look at tools ISINTEG and ESEUTIL

    this link may be of assistance:
    http://technet.microsoft.com/en-us/l...CHG.65%29.aspx
    Last edited by tehcamel; 17th April 2011, 09:44. Reason: did some actual research
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: Help needed for Exchange 2003 Server database revovery

      That is the issue... the old database cannot mounted, if it can be mounted problem solved

      Comment


      • #4
        Re: Help needed for Exchange 2003 Server database revovery

        Solved the mail store mounting issue following this KB: http://support.microsoft.com/?kbid=313184
        Now I've 2 Exchange Servers and some of the mailboxes that are failed in the migration process exist in server A (old server) and Server B (new server), how to resolved this issue? When right click on the user's origin mailbox (server A) properties and try to move it, it's already belongs to server B. That mailbox exist on Server A and B, how to merge them or resolving this issue? I'm not sure if the mailbox has been moved completely because the server has been died before the migration completed.

        Please advice.

        Regards,

        Acung

        Comment


        • #5
          Restore a single mailbox
          Run the following command to restore the content of mailbox 'company mailbox' in the Recovery
          Database to the production mailbox:
          Restore-Mailbox �Identity "company mailbox" �RecoveryDatabase "Recovery Database"
          Say 'Yes' for the confirmation asked. Restore process will start immediately.
          When completed, you will get statistics about the restore mailbox job. You can see the information about the source and target mailbox database etc.

          Comment


          • #6
            I hope that, 5 year after the original thread was created, the poster isn't still waiting for a solution.
            Also note that they are using Exchange 2003, so PowerShell definitely WONT work
            Tom Jones
            MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
            PhD, MSc, FIAP, MIITT
            IT Trainer / Consultant
            Ossian Ltd
            Scotland

            ** Remember to give credit where credit is due and leave reputation points where appropriate **

            Comment


            • #7
              Wow, this is good.

              Comment


              • #8
                really glad...to get the solution as I was facing the same issue

                Comment


                • #9
                  Originally posted by 8586virat View Post
                  really glad...to get the solution as I was facing the same issue
                  Really, you are running Exchange 2003? I hope you are not using Outlook Express with it.
                  1 1 was a racehorse.
                  2 2 was 1 2.
                  1 1 1 1 race 1 day,
                  2 2 1 1 2

                  Comment


                  • #10
                    Pegasus mail - that's the future

                    Comment

                    Working...
                    X