Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2050
  • Last Modified:

Active Directory Errors

I installed a new server with active directory with the following configuration.  2 - 250 GB Mirrored drives for the C: drive and  3 - 500  GB drives in a raid 5 configuration for a file share.

On the C: drive I have been getting the following active directory errors and my active directory will become corrupt and I have to reboot the server.  If I run a Chkdsk /f /r the errors will not appear for 3 or 4 days. If I do a reboot around 10:00 pm the errors will occur at 3:00 am. when no one is on the system.  IBM says there is no hardware problem, Microsoft says it is "Event ID 482 occurred on DHCP database, DNS database and so on. We can see the same error “failed after 0 seconds with system error 1117 (0x0000045d): 'The request could not be performed because of an I/O device error. '”  Based on these error, it may be caused by the hardware access problem. "   Their solution is to put a new server in.

Could this be a problem with the Mirror Configuration?  Any help would be appreciated.


Log Name:      Directory Service
Source:        NTDS ISAM
Date:          9/7/2011 3:09:42 AM
Event ID:      482
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      IBMServer.CCHS.ORG
Description:
NTDS (692) NTDSA: An attempt to write to the file "C:\Windows\NTDS\ntds.dit" at offset 13254656 (0x0000000000ca4000) for 8192 (0x00002000) bytes failed after 0 seconds with system error 1117 (0x0000045d): "The request could not be performed because of an I/O device error. ".  The write operation will fail with error -1022 (0xfffffc02).  If this error persists then the file may be damaged and may need to be restored from a previous backup.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NTDS ISAM" />
    <EventID Qualifiers="0">482</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-09-07T08:09:42.000Z" />
    <EventRecordID>802</EventRecordID>
    <Channel>Directory Service</Channel>
    <Computer>IBMServer.CCHS.ORG</Computer>
    <Security />
  </System>
  <EventData>
    <Data>NTDS</Data>
    <Data>692</Data>
    <Data>NTDSA: </Data>
    <Data>C:\Windows\NTDS\ntds.dit</Data>
    <Data>13254656 (0x0000000000ca4000)</Data>
    <Data>8192 (0x00002000)</Data>
    <Data>-1022 (0xfffffc02)</Data>
    <Data>1117 (0x0000045d)</Data>
    <Data>The request could not be performed because of an I/O device error. </Data>
    <Data>0</Data>
  </EventData>
</Event>

Log Name:      Directory Service
Source:        NTDS ISAM
Date:          9/7/2011 3:09:42 AM
Event ID:      417
Task Category: Logging/Recovery
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      IBMServer.CCHS.ORG
Description:
NTDS (692) NTDSA: Unable to write to section 3 while flushing logfile C:\Windows\NTDS\edb.log. Error -1022 (0xfffffc02).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NTDS ISAM" />
    <EventID Qualifiers="0">417</EventID>
    <Level>2</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-09-07T08:09:42.000Z" />
    <EventRecordID>804</EventRecordID>
    <Channel>Directory Service</Channel>
    <Computer>IBMServer.CCHS.ORG</Computer>
    <Security />
  </System>
  <EventData>
    <Data>NTDS</Data>
    <Data>692</Data>
    <Data>NTDSA: </Data>
    <Data>C:\Windows\NTDS\edb.log</Data>
    <Data>-1022 (0xfffffc02)</Data>
  </EventData>
</Event>
Log Name:      Directory Service
Source:        NTDS ISAM
Date:          9/7/2011 3:09:42 AM
Event ID:      492
Task Category: Logging/Recovery
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      IBMServer.CCHS.ORG
Description:
NTDS (692) NTDSA: The logfile sequence in "C:\Windows\NTDS\" has been halted due to a fatal error.  No further updates are possible for the databases that use this logfile sequence.  Please correct the problem and restart or restore from backup.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NTDS ISAM" />
    <EventID Qualifiers="0">492</EventID>
    <Level>2</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-09-07T08:09:42.000Z" />
    <EventRecordID>805</EventRecordID>
    <Channel>Directory Service</Channel>
    <Computer>IBMServer.CCHS.ORG</Computer>
    <Security />
  </System>
  <EventData>
    <Data>NTDS</Data>
    <Data>692</Data>
    <Data>NTDSA: </Data>
    <Data>C:\Windows\NTDS\</Data>
  </EventData>
</Event>
0
Nancy Villa
Asked:
Nancy Villa
1 Solution
 
AwinishCommented:
The AD database is corrupted & surely mirror can't be the reason for generating such events.
Did you exclude scanning of AD database/Sysvol by antivirus, if not its a good option to configure it.

I would suggest demote the DC & promote it again. if running chkdsk /r reports an error, it is surely a disk error due to bad sector & you should replace it.
0
 
Nancy VillaDirector of ITAuthor Commented:
How do you know which one of the two?
0
 
Vinchenzo-the-SecondCommented:
I would remove the disk so the mirror switches to other drive, then do ur chkdsk to make sure this drive is ok?  Run dcdiag /v to see if ur AD is corrupt on this drive, if so do a dcpromo.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
AwinishCommented:
Well the amber light on the server should tell you for corruption or there is some tool supplied with setup disk for testing hardware/disks/ram etc for servers.

You can remove one disk, run chkdsk by hot swapping it & check it.
0
 
5g6tdcv4Commented:
As a test I would move the AD database to another physical drive on the server.
http://technet.microsoft.com/en-us/library/cc816720%28WS.10%29.aspx
0
 
Nancy VillaDirector of ITAuthor Commented:
sorry it took so long, it was the hard drive
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now