none
Event ID 474

    Question

  • Hello,

    We have a a single Windows 2003 R2 domain contoller, no Exchange that is looging error

     event ID 474.  We had both a hard drive failure (RAID5, successful rebuild) and a power outage.  This event error is logging - how can I fix this.....we do not have a clean system state backup.

    Thank you

    Friday, July 01, 2011 2:45 AM

Answers

  • Can you take this DC offline after hours and do a defrag?  Don't know if this will help but it might fix the error.
    http://support.microsoft.com/kb/232122

    How about running some recovery tools after it.  Spinrite may be your best friend in this instance.  It takes time to run but over the weekend it might be able to help as well.
    http://www.grc.com/spinrite.htm

    I would take a backup prior to making any mods.

    --
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://www.pbbergs.com    Twitter @pbbergs
    http://blogs.dirteam.com/blogs/paulbergson

    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by Bruce-Liu Friday, July 29, 2011 7:25 AM
    Friday, July 01, 2011 12:19 PM
    Moderator
  • I fixed it! I performed an offline defragmentation of the AD database as pbbergs suggested here and it corrected the error:

    http://support.microsoft.com/kb/232122

    I immediately did a system state backup using the windows ntbackup utility and got a clean backup.....I also did an authoritative restore using the D4 option of the burflag registry key to clear up a journal_wrap_error message...all looks good -

    many thanks to everyone throughout this process -

    hoemee

     

    • Marked as answer by Bruce-Liu Friday, July 29, 2011 7:25 AM
    Saturday, July 09, 2011 12:20 AM

All replies

  • Please post the complete error message along with the details of your environment.

     

    Regards  


    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Friday, July 01, 2011 4:29 AM
    Moderator
  • Hi,

     

    Does this error come up again after successfully rebuilding RAID5?

     

    As Awinish has stated, please let us know the complete event message.

     

    Regards,

    Bruce

    Friday, July 01, 2011 9:29 AM
  • Hello,

    you have to provide as with the source of this event ID.

    You can start by that. Hope it helps.

    http://support.microsoft.com/kb/327334

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    Friday, July 01, 2011 11:09 AM
  • Thank you for the replies....we do not have exchange on this server. Yes, the error comes up after the raid rebuild.  I have a creen shot of the error, but do not know how to post it in this forum.  Here is the event:

    Event Type: Error
    Event Source: NTDS ISAM
    Event Category: Database Page Cache
    Event ID: 474
    Date:  7/1/2011
    Time:  2:00:49 AM
    User:  N/A
    Computer: YANKEE-DELL840
    Description:
    NTDS (396) NTDSA: The database page read from the file "C:\WINDOWS\NTDS\ntds.dit"
    at offset 5988352 (0x00000000005b6000) for 8192 (0x00002000) bytes failed verification
    due to a page checksum mismatch.  The expected checksum was 3413674554 (0xcb788a3a) and
    the actual checksum was 2724629050 (0xa2668a3a).  The read operation will fail with error -1018 (0xfffffc06).
     If this condition persists then please restore the database from a previous backup. 
    This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    Let me know what you need for more details of our environment........

    Friday, July 01, 2011 12:13 PM
  • Can you take this DC offline after hours and do a defrag?  Don't know if this will help but it might fix the error.
    http://support.microsoft.com/kb/232122

    How about running some recovery tools after it.  Spinrite may be your best friend in this instance.  It takes time to run but over the weekend it might be able to help as well.
    http://www.grc.com/spinrite.htm

    I would take a backup prior to making any mods.

    --
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://www.pbbergs.com    Twitter @pbbergs
    http://blogs.dirteam.com/blogs/paulbergson

    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by Bruce-Liu Friday, July 29, 2011 7:25 AM
    Friday, July 01, 2011 12:19 PM
    Moderator
  • Thank you pbbergs.........running an offline defrag, won't correct errors will it?  It will just compact the size of the database.......just want to be sure before I attempt this........
    Saturday, July 02, 2011 11:46 PM
  • Give a try running chkdsk /r in read only mode to scan the disk corruption. I would also suggest check integrity of AD database using Ntdsutil for any suspected corruption caused using below article.

    http://support.microsoft.com/kb/258062

     

    Regards  


    MVP-Directory Services 

    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Sunday, July 03, 2011 4:54 AM
    Moderator
  • To add to what I Awinish said, try running  chkdsk /r /f so that your server will try to repair detected errors.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    Sunday, July 03, 2011 8:50 AM
  • Hello,

    if the mentioned steps with checkdisk and database defrag doesn't help then and you don't have a backup of the machine it seems that you have to start from scratch.

    If it is high important to keep the environment you should contact Microsoft PSS, maybe thay are still able to help you with having some deeper look into the system. This kind of support is not for free.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Sunday, July 03, 2011 9:57 AM
  • ran chckdsk /r /f........no errors, volume is clean. Have a sinking feeling I will have to rebuild AD from scratch.  I don't know how to do this.....I do have another Server 2003 box I can bring into the domain...
    Sunday, July 03, 2011 7:10 PM
  • Learn the lesson & start maintaining system state backup of AD at regular basis or when there is change in AD. It is advisable to have min two server configured as DC/DNS/GC,because even though there are 10-50 users but downtime may cause severe impact in the environment when there are users as well as application is dependent on AD for authentication & name resolution.

     

    Regards  


    MVP-Directory Services

    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Monday, July 04, 2011 4:51 AM
    Moderator
  • This is not my network, but a friend of mine.  He has a nightly system state backup, but when the hard drive failed, we were preoccupied with the repair and replacement of that.  The backups only went back two weeks - by that time the time had expired for a clean backup.  As you can tell, I am trying to learn and help him with this.  He originally had a SBS 2003 server which we migrated to a Server 2003 R2 and I learned a lot during that process  sometimes with the help of Microsoft :) .  It is possible to use a Server 2003 box (not R2) to fix this problem?

     

    Thank you very much for your time and patience - Steven

    Monday, July 04, 2011 12:01 PM
  • Hello,

    a system state backup can only be used on the same hardware and with the EQUAL OS version as it was taken from.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Monday, July 04, 2011 12:53 PM
  • Switching to server 2003 will not help as problem looks in AD & things didn't go well. You might go for fresh installation, but would suggest go through the IPD guide.

    Did you follow the below article for migration of SBS to standard/Enterprise edition.

    http://technet.microsoft.com/en-us/library/cc747454%28WS.10%29.aspx

     

    Regards


    MVP-Directory Services

    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Monday, July 04, 2011 12:57 PM
    Moderator
  • Yes we followed that - however, exchange was removed from the SBS prior to the migration.  We ended up having to do a dcpromo /forceremoval with metadata cleanup.  Everything has been fine until this latest problem.  What is the IPD guide? 
    Monday, July 04, 2011 1:37 PM
  • Below is the IPD guide.

    Infrastructure Planning and Design(IPD)

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=732

    Active Directory Design Guide

    http://www.microsoft.com/download/en/details.aspx?id=8133

     

    Regards


    MVP-Directory Services

    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Monday, July 04, 2011 3:06 PM
    Moderator
  • Thank you for the information.  If I bring another domain controller running Server 2003 R2 standard (the same as we are running now), can I fix this? 
    Tuesday, July 05, 2011 12:49 AM
  • No, while configuring the second DC, AD database from the existing DC will only be copied. So,if sources is corrupted, you will see same into target DC too.

     

    Regards  


    MVP-Directory Services

    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Tuesday, July 05, 2011 4:06 AM
    Moderator
  • So - do I have to demote the current dc with corrupted AD, which will remove Active Directory - and then promote it back to a domain controller?
    Tuesday, July 05, 2011 11:47 AM
  • Since, its a last DC, demoting will make you to configure everything from the scratch.


    Regards


    MVP-Directory Services 

    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Tuesday, July 05, 2011 12:23 PM
    Moderator
  • Does that mean DNS, DHCP, user groups, etc.? Will current programs be retained?
    Tuesday, July 05, 2011 12:26 PM
  • Nothing will remain, everything(DNS/DHCP/AD etc) will be wiped out on fresh install.

     

    Regards


    MVP-Directory Services 

    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Wednesday, July 06, 2011 4:08 AM
    Moderator
  • Will this also affect the terminal server portion and the terminal server licensing?

     

    Thank you

    Wednesday, July 06, 2011 12:58 PM
  • Its like, if house is destroyed by fire, how can anything remains. Regarding Terminal server license, if you have purchase information, you can reuse it during new configuration by contacting MS & giving details of your previous purchased details, so you don't have to pay again for the same license & validity time.

     

    Regards


    MVP-Directory Services 

    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

    Wednesday, July 06, 2011 1:02 PM
    Moderator
  • I fixed it! I performed an offline defragmentation of the AD database as pbbergs suggested here and it corrected the error:

    http://support.microsoft.com/kb/232122

    I immediately did a system state backup using the windows ntbackup utility and got a clean backup.....I also did an authoritative restore using the D4 option of the burflag registry key to clear up a journal_wrap_error message...all looks good -

    many thanks to everyone throughout this process -

    hoemee

     

    • Marked as answer by Bruce-Liu Friday, July 29, 2011 7:25 AM
    Saturday, July 09, 2011 12:20 AM
  • Good to hear, issue has been resolved & thanks for the updated.

     

    Regards


    MVP-Directory Services 

    Awinish Vishwakarma| CHECK MY BLOG

    Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights.

     

    Saturday, July 09, 2011 4:04 AM
    Moderator