Event ID 447 - Database Corruption - Only One User Effected

Discussion in 'Windows Small Business Server' started by KevM, Jan 9, 2008.

  1. KevM

    KevM Guest

    Hi

    I am having the following appear in the Event Log on my SBS 2003 Server :

    Source : ESE
    Category : Database Corruption
    Event ID : 447
    Information Store (8068) First Storage Group: A bad page link (error -327)
    has been detected in a B-Tree (ObjectId: 8692, PgnoRoot: 3361) of database
    D:\Exchange\mdbdata\priv1.edb (3815 => 131033, 3816).

    All but one of my users (of which there are 8) are working fine, however one
    user has a problem with Outlook, error as follows :

    11:30:43 Error synchronizing folder
    11:30:43 [80004005-501-FFFFFC07-560]
    11:30:43 The client operation failed.
    11:30:43 Microsoft Exchange Server Information Store

    If you send an email to them it will sometimes get delivered and be visible
    in OWA but not Outlook.

    If it isn't delivered you get the following return email :
    Delivery Status Notification (Delay)
    This is an automatically generated Delivery Status Notification.
    THIS IS A WARNING MESSAGE ONLY.
    YOU DO NOT NEED TO RESEND YOUR MESSAGE.
    Delivery to the following recipients has been delayed.


    It would seem from reading this newsgroup that the logical database
    structure has become corrupted and that I need to repair the database using
    the esetuil commands.

    My questions are therefore :
    Why has the exchange database corruption only effected one user ?

    Is there anything that I can do to just correct the problem for the one
    user, delete their account and restore from .pst for example or do I have to
    carry out the esetuil commands on the whole database ?

    Kev
     
    KevM, Jan 9, 2008
    #1
    1. Advertisements

  2. KevM

    Pedro CR Guest

    I've seen that event too and I don't really know if I should worry or not...

    However I recommend you run ESEUTIL in RCOVERY (NOT Repair) mode.
    Next running isinteg to check for Information Store Inconsistencies.
    And finally run ESEUTIL to defrag the the exchange databases.
     
    Pedro CR, Jan 10, 2008
    #2
    1. Advertisements

  3. KevM

    KevM Guest

    Hi

    Thanks for your reply.

    According to this KB article http://support.microsoft.com/?kbid=810190 - "is
    best if you restore from an online backup as soon as you can and avoid using
    the database"

    My database seems to have had this problem for about 3 weeks and everyone is
    working fine other than one user.

    Running the commands you have suggested, will that put any data at risk ?

    Kev
     
    KevM, Jan 10, 2008
    #3
  4. KevM

    Al Williams Guest

    I'd run eseutil on the priv1.edb - take exchange offline (stop all services)
    and then make a copy of the file before you continue. Eseutil only works on
    the edb file itself (although I'd also make a full system backup first as
    well). Just do checks of the DB at first, only do a repair if absolutely
    needed, see:

    http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html

    Exchange is usually pretty bulletproof so do you know why the corruption
    occurred? Common causes would be:
    1) Server resets (not clean shutdowns). Do you have a UPS?
    2) The hard disk where the EDB files are located is suspect. Do a chkdsk on
    it.
    3) File based antivirus scanning of the exchange databases (a no-no). See
    http://support.microsoft.com/kb/822158 and
    http://support.microsoft.com/kb/823166/en-us
     
    Al Williams, Jan 10, 2008
    #4
  5. KevM

    KevM Guest

    Hi Al

    Thanks for your comments, I will have a read of the link you included.

    I am not sure why the problem occurred, the server has a working UPS, I
    think the hard disks are OK but I will check, and I excluded the Exchange
    Database from the Virus Scanner.

    The first I knew of the problem was when the user reported not getting mail
    and there were sync errors in Outlook

    Kev

     
    KevM, Jan 10, 2008
    #5
  6. KevM

    Pedro CR Guest

    running eseutil in RECOVERY mode will not pose any risk to the data. It's
    safe to run it. The link posted bellow by Al Williams point to a very very
    good article on running eseutil and isinteg to keep exchange healthy.

     
    Pedro CR, Jan 11, 2008
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.