Results 1 to 6 of 6

Thread: Event ID 447 - Database Corruption - Only One User Effected

  1. #1
    Join Date
    Aug 2004

    Event ID 447 - Database Corruption - Only One User Effected

    I am getting the below error that is appearing in the Event Log on my SBS Server 2003:

    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).

    There is one user that is having problem with Outlook and getting the following errors:

    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

    Incase an email is send to them then it will sometime gets delivered and be visible in OWA but not Outlook, but if it isnt delivered then you will get the following return email:

    Delivery Status Notification (Delay)
    This is an automatically generated Delivery Status Notification.
    Delivery to the following recipients has been delayed.

    Does anyone know how to solve this error? Thanks.

  2. #2
    Join Date
    Dec 2005

    Re: Event ID 447 - Database Corruption - Only One User Effected

    I dont think you have to worry about the error that you are getting because I am seeing that too. But I would suggest you to run ESEUTIL in recovery mode. And then try to run isinteg to check for Information Store Inconsistencies. After that finally run the ESEUTIL to defrag the exchange databases.

  3. #3
    Join Date
    Mar 2005

    Re: Event ID 447 - Database Corruption - Only One User Effected

    If you receive these errors in your application log, it is best if you restore from an online backup as soon as you can and avoid using the database. A bad page link error signifies logical corruption at the Jet level in the database. Go to this link for more information here -

  4. #4
    Join Date
    Jan 2006

    Re: Event ID 447 - Database Corruption - Only One User Effected

    I think that it should be best to run eseutil on the priv1.edb and then take exchange offline and stop all services and then make a copy of the file before you continue. Eseutil will only work on the edb file, although you should first make a full system backup first. After that do the checks of the database at first and then only do a repair if needed.

  5. #5
    Join Date
    Aug 2004

    Re: Event ID 447 - Database Corruption - Only One User Effected

    Thank you all for the replies, I will go with the links and your suggestions that you have given. But I am not sure why this issue occurred, the server has a working UPS, I think that the hard disks are fine but I will check and I have excluded the Exchange Database from the Virus Scanner. When the user reported that he was not getting mail and there were sync errors in outlook, then only I came to know about this issue.

  6. #6
    Join Date
    Jan 2006

    Re: Event ID 447 - Database Corruption - Only One User Effected

    Well, you can try to run eseutil in recovery mode which will not do any hard to the data, since it is very safe to run. The link posted above in the posts, point to be a very nice article on how to run eseutil and isinteg to keep Exchange healthy.

Similar Threads

  1. NTDS ISAM: Database Corruption
    By BoanHed in forum Small Business Server
    Replies: 3
    Last Post: 03-01-2014, 09:41 AM
  2. Microsoft Access to prevent database corruption
    By Xylina in forum Windows Software
    Replies: 5
    Last Post: 27-03-2010, 12:33 AM
  3. Granting privileges to New database user
    By Ainsley in forum Software Development
    Replies: 4
    Last Post: 06-02-2010, 04:38 PM
  4. Replies: 3
    Last Post: 07-07-2009, 08:51 PM
  5. NTDS ISAM 467 database corruption
    By low40p in forum Active Directory
    Replies: 8
    Last Post: 03-07-2007, 12:52 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts