event id 474: inconsistent ntds.dit

dear w2k ad gurus,
after a harddisk failure i have the event id 474. it says, that there is an
inconsitence in the c:\windows\ntds\ntds.dit is there a way to correct this
error or to restore the files from a backup ? the error occurs on the one
and only dc in a w2k3 environment. i do a nightly backup with symantec's
backup exec 10 including the system state.

thanx alot
tim

Hi

Could you please give more info?

How many Dcs in the Domain?
Exact Error and Source?
What kind of problems do you have?
Did you replace the disk with a new one or is it the same?
What setps did you taked to recover the disk?




--
Best Regards
Systems Administrator
MCSA + Exchange



"Tim Moor" <tim.moor@nospam.com> wrote in message
news:44465883$1_7@news.bluewin.ch...
> dear w2k ad gurus,
> after a harddisk failure i have the event id 474. it says, that there is
> an inconsitence in the c:\windows\ntds\ntds.dit is there a way to correct
> this error or to restore the files from a backup ? the error occurs on the
> one and only dc in a w2k3 environment. i do a nightly backup with
> symantec's backup exec 10 including the system state.
>
> thanx alot
> tim
>
>
>

hello jmnts
thank you for your reply. i only have one dc in this w2k3 domain. the error
occurs on the dc (w2k3, sp1, no exchange installed). if i try to open ad
users and computers it takes very long. then i receive an error message
saying, that ad users and computers is not available. after a certain time,
the ad users and computers gui starts. i had a harddisk crash on a sata
raid1. even after replacing the faulty disk, the following error shows up.
so far i have no idea how to solve the problem. all i have is a vaild backup
(veritas backup) before the disk crash happend.

tim




Event Type: Error
Event Source: NTDS ISAM
Event Category: Database Page Cache
Event ID: 474
Date: 23/09/2005
Time: 16:31:34
User: N/A
Computer: SRV01
Description:
NTDS (1504) NTDSA: The database page read from the file "d:\ntds\ntds.dit"
at offset 6832128 (0x0000000000684000) for 8192 (0x00002000) bytes failed
verification due to a page checksum mismatch. The expected checksum was
1616634593 (0x605be2e1) and the actual checksum was 3314267797 (0xc58bb695).
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.


"Jmnts" <Jmnts@hotmail.com> schrieb im Newsbeitrag
news:%23yDWgg9YGHA.4120@TK2MSFTNGP04.phx.gbl...
> Hi
>
> Could you please give more info?
>
> How many Dcs in the Domain?
> Exact Error and Source?
> What kind of problems do you have?
> Did you replace the disk with a new one or is it the same?
> What setps did you taked to recover the disk?
>
>
>
>
> --
> Best Regards
> Systems Administrator
> MCSA + Exchange
>
>
>
> "Tim Moor" <tim.moor@nospam.com> wrote in message
> news:44465883$1_7@news.bluewin.ch...
>> dear w2k ad gurus,
>> after a harddisk failure i have the event id 474. it says, that there is
>> an inconsitence in the c:\windows\ntds\ntds.dit is there a way to correct
>> this error or to restore the files from a backup ? the error occurs on
>> the one and only dc in a w2k3 environment. i do a nightly backup with
>> symantec's backup exec 10 including the system state.
>>
>> thanx alot
>> tim
>>
>>
>>
>
>

Hi

Did you check the available Disk space?

Based on my research, the specified issue may caused by corrupted AD
database. If you have a recent backup I recommend you to perform restore
operation to resolve the issue.



However if the backup is not recent, and you'll loose many objects you can
try to repair the Database, In some situation, certain configurations will
be lost with this procedure.

Before you start the computer in Directory Services Restore Mode, obtain the
password for the offline administrator account.

For more information about how to change the password in Windows Server
2003, click the following article number to view the article in the
Microsoft Knowledge Base

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

"Directory Services cannot start" error message when you start your
Windows-based or SBS-based domain controller
http://support.microsoft.com/?id=258062

Next step:

How to Recover the Database and if it fails try How to Repair the Database
(Be careful withis last one read carefully)

http://support.microsoft.com/default...b;en-us;315131

How to complete a semantic database analysis for the Active Directory
database by using Ntdsutil.exe
http://support.microsoft.com/default...b;en-us;315136







If you fail to repair a corrupted Active Directory, try the following:
You may try the following steps to recover the corrupted Active Directory.

1. Reboot the server and press F8. Choose Directory Services Restore Mode
from the Menu.
2. Check the physical location of the Winnt\NTDS\ folder.
3. Check the permissions on the \Winnt\NTDS folder.



The default permissions are:

Administrators - Full Control
System - Full Control

4. Check the Winnt\Sysvol\Sysvol folder to make sure it is shared.
5. Check the permissions on the Winnt\Sysvol\Sysvol share.



The default permissions are:

Share Permissions:
Administrators - Full Control
Authenticated Users - Full Control
Everyone - Read

NTFS Permissions:
Administrators - Full Control
Authenticated Users - Read & Execute, List Folder Contents, Read
Creator Owner - none
Server Operators - Read & Execute, List Folder Contents, Read
System - Full Control

Note: You may not be able to change the permissions on these folders if the
Active Directory database is unavailable because it is damaged, however it
is best to know if the permissions are set correctly before you start the
recovery process, as it may not be the database that is the problem.

6. Make sure there is a folder in the Sysvol share labeled with the correct
name for their domain.
7. Open a command prompt and run NTDSUTIL to verify the paths for the
NTDS.dit file. These should match the physical structure from Step 2

To check the file paths type the following commands:

NTDSUTIL <enter>
Files <enter>
Info <enter>

The output should look similar to:

Drive Information:

C:\ NTFS (Fixed Drive) free (2.9 Gb) total (3.9 Gb)
D:\ NTFS (Fixed Drive) free (3.6 Gb) total (3.9 Gb)

DS Path Information:

Database : C:\WINNT\NTDS\ntds.dit - 10.1 Mb
Backup dir: C:\WINNT\NTDS\dsadata.bak
Working dir: C:\WINNT\NTDS
Log dir : C:\WINNT\NTDS - 30.0 Mb total
res2.log - 10.0 Mb
res1.log - 10.0 Mb
edb.log - 10.0 Mb

This information is pulled directly from the registry and mismatched paths
will cause Active Directory not to start. Type Quit to end the NTDSUTIL
session.

8. Rename the edb.chk file and try to boot to Normal mode. If that fails,
proceed with the next steps.

9. Reboot into Directory Services Restore mode again. At the command prompt,
use the ESENTUTL to check the integrity of the database.
NOTE: You can use NTDSUTIL to check the Integrity, however esentutl is
usually more reliable.

Type the following command:
ESENTUTL /g "<path>\NTDS.dit" /!10240 /8 /v /x /o <enter>
(Note: Type the path without the quotes).

Note: The default path would be C:\Winnt\NTDS\ntds.dit; however it may be
different in some cases.

The output will tell you if the database is inconsistent and may produce a
jet_error 1206 stating that the database is corrupt. If the database is
inconsistent or corrupt it will need to be recovered or repaired . To
recover the database type the following at the command prompt:

NTDSUTIL <enter>
Files<enter>
Recover <enter>

If this fails with an error, type quit until back at the command prompt and
repair the database using ESENTUTL by typing the following:

ESENTUTL /p "<path>\NTDS.dit" /!10240 /8 /v /x /o <enter>
(Note: Type the path without the quotes).

Note: If you do not put the switches at the end of the command you will
most likely get a Jet_error 1213 "Page size mismatch" error.

10. Delete the log files in the NTDS directory, but do not delete or move
the ntds.dit file.
11. The NTDSUTIL tool needs to be run again to check the Integrity of the
database and to perform a Semantic Database analysis.

To check the integrity, at the command prompt type:

NTDSUTIL <enter>
Files <enter>
Integrity <enter>

The output should tell you that the integrity check completed successfully
and prompt that you should perform a Semantic Database Analysis.

Type quit.

To perform the Semantic Database Analysis type the following at the NTDSUTIL
Prompt type:

Semantic Database Analysis <enter>
Go <enter>

The output will tell you that the Analysis completed successfully.
Type quit and closes the command prompt.

NOTE: If you get errors running the Analysis then type the following at the
semantic checker prompt:

semantic checker: go fix <enter>

This puts the checker in Fixup mode, which should fix whatever errors there
were.

12. Reboot the server to Normal Mode.

If any of these steps fail to recover the database the only alternative is
to perform an Authoritative System State restore from backup in Directory
Services Restore mode.

For more information, please refer to the following articles:

315136 HOW TO: Complete a Semantic Database Analysis for the Active
Directory
http://support.microsoft.com/?id=315136

265706 DCDiag and NetDiag in Windows 2000 Facilitate Domain Join and DC
Creation
http://support.microsoft.com/?id=265706

258007 Error Message: Lsass.exe - System Error : Security Accounts Manager
http://support.microsoft.com/?id=258007

265089 Event 1168: Windows 2000 DCs Unable to Boot into Active Directory
http://support.microsoft.com/?id=265089

315131 HOW TO: Use Ntdsutil to Manage Active Directory Files from the
Command
http://support.microsoft.com/?id=315131




--
Best Regards
Systems Administrator
MCSA + Exchange



"Tim Moor" <tim.moor@gmx.net> wrote in message
news:4446a2d0$1_2@news.bluewin.ch...
> hello jmnts
> thank you for your reply. i only have one dc in this w2k3 domain. the
> error occurs on the dc (w2k3, sp1, no exchange installed). if i try to
> open ad users and computers it takes very long. then i receive an error
> message saying, that ad users and computers is not available. after a
> certain time, the ad users and computers gui starts. i had a harddisk
> crash on a sata raid1. even after replacing the faulty disk, the following
> error shows up. so far i have no idea how to solve the problem. all i have
> is a vaild backup (veritas backup) before the disk crash happend.
>
> tim
>
>
>
>
> Event Type: Error
> Event Source: NTDS ISAM
> Event Category: Database Page Cache
> Event ID: 474
> Date: 23/09/2005
> Time: 16:31:34
> User: N/A
> Computer: SRV01
> Description:
> NTDS (1504) NTDSA: The database page read from the file "d:\ntds\ntds.dit"
> at offset 6832128 (0x0000000000684000) for 8192 (0x00002000) bytes failed
> verification due to a page checksum mismatch. The expected checksum was
> 1616634593 (0x605be2e1) and the actual checksum was 3314267797
> (0xc58bb695).
> 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.
>
>
> "Jmnts" <Jmnts@hotmail.com> schrieb im Newsbeitrag
> news:%23yDWgg9YGHA.4120@TK2MSFTNGP04.phx.gbl...
>> Hi
>>
>> Could you please give more info?
>>
>> How many Dcs in the Domain?
>> Exact Error and Source?
>> What kind of problems do you have?
>> Did you replace the disk with a new one or is it the same?
>> What setps did you taked to recover the disk?
>>
>>
>>
>>
>> --
>> Best Regards
>> Systems Administrator
>> MCSA + Exchange
>>
>>
>>
>> "Tim Moor" <tim.moor@nospam.com> wrote in message
>> news:44465883$1_7@news.bluewin.ch...
>>> dear w2k ad gurus,
>>> after a harddisk failure i have the event id 474. it says, that there is
>>> an inconsitence in the c:\windows\ntds\ntds.dit is there a way to
>>> correct this error or to restore the files from a backup ? the error
>>> occurs on the one and only dc in a w2k3 environment. i do a nightly
>>> backup with symantec's backup exec 10 including the system state.
>>>
>>> thanx alot
>>> tim
>>>
>>>
>>>
>>
>>
>
>

hello jmnts,
thank you for this detailed information. i go through this ...

all the best
tim



"Jmnts" <Jmnts@hotmail.com> schrieb im Newsbeitrag
news:%23OsLyo$YGHA.4248@TK2MSFTNGP05.phx.gbl...
> Hi
>
> Did you check the available Disk space?
>
> Based on my research, the specified issue may caused by corrupted AD
> database. If you have a recent backup I recommend you to perform restore
> operation to resolve the issue.
>
>
>
> However if the backup is not recent, and you'll loose many objects you can
> try to repair the Database, In some situation, certain configurations will
> be lost with this procedure.
>
> Before you start the computer in Directory Services Restore Mode, obtain
> the password for the offline administrator account.
>
> For more information about how to change the password in Windows Server
> 2003, click the following article number to view the article in the
> Microsoft Knowledge Base
>
> http://support.microsoft.com/kb/322672/
>
> "Directory Services cannot start" error message when you start your
> Windows-based or SBS-based domain controller
> http://support.microsoft.com/?id=258062
>
> Next step:
>
> How to Recover the Database and if it fails try How to Repair the Database
> (Be careful withis last one read carefully)
>
> http://support.microsoft.com/default...b;en-us;315131
>
> How to complete a semantic database analysis for the Active Directory
> database by using Ntdsutil.exe
> http://support.microsoft.com/default...b;en-us;315136
>
>
>
>
>
>
>
> If you fail to repair a corrupted Active Directory, try the following:
> You may try the following steps to recover the corrupted Active Directory.
>
> 1. Reboot the server and press F8. Choose Directory Services Restore
> Mode from the Menu.
> 2. Check the physical location of the Winnt\NTDS\ folder.
> 3. Check the permissions on the \Winnt\NTDS folder.
>
>
>
> The default permissions are:
>
> Administrators - Full Control
> System - Full Control
>
> 4. Check the Winnt\Sysvol\Sysvol folder to make sure it is shared.
> 5. Check the permissions on the Winnt\Sysvol\Sysvol share.
>
>
>
> The default permissions are:
>
> Share Permissions:
> Administrators - Full Control
> Authenticated Users - Full Control
> Everyone - Read
>
> NTFS Permissions:
> Administrators - Full Control
> Authenticated Users - Read & Execute, List Folder Contents, Read
> Creator Owner - none
> Server Operators - Read & Execute, List Folder Contents, Read
> System - Full Control
>
> Note: You may not be able to change the permissions on these folders if
> the Active Directory database is unavailable because it is damaged,
> however it is best to know if the permissions are set correctly before
> you start the recovery process, as it may not be the database that is the
> problem.
>
> 6. Make sure there is a folder in the Sysvol share labeled with the
> correct name for their domain.
> 7. Open a command prompt and run NTDSUTIL to verify the paths for the
> NTDS.dit file. These should match the physical structure from Step 2
>
> To check the file paths type the following commands:
>
> NTDSUTIL <enter>
> Files <enter>
> Info <enter>
>
> The output should look similar to:
>
> Drive Information:
>
> C:\ NTFS (Fixed Drive) free (2.9 Gb) total (3.9 Gb)
> D:\ NTFS (Fixed Drive) free (3.6 Gb) total (3.9 Gb)
>
> DS Path Information:
>
> Database : C:\WINNT\NTDS\ntds.dit - 10.1 Mb
> Backup dir: C:\WINNT\NTDS\dsadata.bak
> Working dir: C:\WINNT\NTDS
> Log dir : C:\WINNT\NTDS - 30.0 Mb total
> res2.log - 10.0 Mb
> res1.log - 10.0 Mb
> edb.log - 10.0 Mb
>
> This information is pulled directly from the registry and mismatched paths
> will cause Active Directory not to start. Type Quit to end the NTDSUTIL
> session.
>
> 8. Rename the edb.chk file and try to boot to Normal mode. If that fails,
> proceed with the next steps.
>
> 9. Reboot into Directory Services Restore mode again. At the command
> prompt, use the ESENTUTL to check the integrity of the database.
> NOTE: You can use NTDSUTIL to check the Integrity, however esentutl is
> usually more reliable.
>
> Type the following command:
> ESENTUTL /g "<path>\NTDS.dit" /!10240 /8 /v /x /o <enter>
> (Note: Type the path without the quotes).
>
> Note: The default path would be C:\Winnt\NTDS\ntds.dit; however it may be
> different in some cases.
>
> The output will tell you if the database is inconsistent and may produce a
> jet_error 1206 stating that the database is corrupt. If the database is
> inconsistent or corrupt it will need to be recovered or repaired . To
> recover the database type the following at the command prompt:
>
> NTDSUTIL <enter>
> Files<enter>
> Recover <enter>
>
> If this fails with an error, type quit until back at the command prompt
> and repair the database using ESENTUTL by typing the following:
>
> ESENTUTL /p "<path>\NTDS.dit" /!10240 /8 /v /x /o <enter>
> (Note: Type the path without the quotes).
>
> Note: If you do not put the switches at the end of the command you will
> most likely get a Jet_error 1213 "Page size mismatch" error.
>
> 10. Delete the log files in the NTDS directory, but do not delete or move
> the ntds.dit file.
> 11. The NTDSUTIL tool needs to be run again to check the Integrity of the
> database and to perform a Semantic Database analysis.
>
> To check the integrity, at the command prompt type:
>
> NTDSUTIL <enter>
> Files <enter>
> Integrity <enter>
>
> The output should tell you that the integrity check completed successfully
> and prompt that you should perform a Semantic Database Analysis.
>
> Type quit.
>
> To perform the Semantic Database Analysis type the following at the
> NTDSUTIL Prompt type:
>
> Semantic Database Analysis <enter>
> Go <enter>
>
> The output will tell you that the Analysis completed successfully.
> Type quit and closes the command prompt.
>
> NOTE: If you get errors running the Analysis then type the following at
> the semantic checker prompt:
>
> semantic checker: go fix <enter>
>
> This puts the checker in Fixup mode, which should fix whatever errors
> there were.
>
> 12. Reboot the server to Normal Mode.
>
> If any of these steps fail to recover the database the only alternative is
> to perform an Authoritative System State restore from backup in Directory
> Services Restore mode.
>
> For more information, please refer to the following articles:
>
> 315136 HOW TO: Complete a Semantic Database Analysis for the Active
> Directory
> http://support.microsoft.com/?id=315136
>
> 265706 DCDiag and NetDiag in Windows 2000 Facilitate Domain Join and DC
> Creation
> http://support.microsoft.com/?id=265706
>
> 258007 Error Message: Lsass.exe - System Error : Security Accounts Manager
> http://support.microsoft.com/?id=258007
>
> 265089 Event 1168: Windows 2000 DCs Unable to Boot into Active Directory
> http://support.microsoft.com/?id=265089
>
> 315131 HOW TO: Use Ntdsutil to Manage Active Directory Files from the
> Command
> http://support.microsoft.com/?id=315131
>
>
>
>
> --
> Best Regards
> Systems Administrator
> MCSA + Exchange
>
>
>
> "Tim Moor" <tim.moor@gmx.net> wrote in message
> news:4446a2d0$1_2@news.bluewin.ch...
>> hello jmnts
>> thank you for your reply. i only have one dc in this w2k3 domain. the
>> error occurs on the dc (w2k3, sp1, no exchange installed). if i try to
>> open ad users and computers it takes very long. then i receive an error
>> message saying, that ad users and computers is not available. after a
>> certain time, the ad users and computers gui starts. i had a harddisk
>> crash on a sata raid1. even after replacing the faulty disk, the
>> following error shows up. so far i have no idea how to solve the problem.
>> all i have is a vaild backup (veritas backup) before the disk crash
>> happend.
>>
>> tim
>>
>>
>>
>>
>> Event Type: Error
>> Event Source: NTDS ISAM
>> Event Category: Database Page Cache
>> Event ID: 474
>> Date: 23/09/2005
>> Time: 16:31:34
>> User: N/A
>> Computer: SRV01
>> Description:
>> NTDS (1504) NTDSA: The database page read from the file
>> "d:\ntds\ntds.dit"
>> at offset 6832128 (0x0000000000684000) for 8192 (0x00002000) bytes failed
>> verification due to a page checksum mismatch. The expected checksum was
>> 1616634593 (0x605be2e1) and the actual checksum was 3314267797
>> (0xc58bb695).
>> 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.
>>
>>
>> "Jmnts" <Jmnts@hotmail.com> schrieb im Newsbeitrag
>> news:%23yDWgg9YGHA.4120@TK2MSFTNGP04.phx.gbl...
>>> Hi
>>>
>>> Could you please give more info?
>>>
>>> How many Dcs in the Domain?
>>> Exact Error and Source?
>>> What kind of problems do you have?
>>> Did you replace the disk with a new one or is it the same?
>>> What setps did you taked to recover the disk?
>>>
>>>
>>>
>>>
>>> --
>>> Best Regards
>>> Systems Administrator
>>> MCSA + Exchange
>>>
>>>
>>>
>>> "Tim Moor" <tim.moor@nospam.com> wrote in message
>>> news:44465883$1_7@news.bluewin.ch...
>>>> dear w2k ad gurus,
>>>> after a harddisk failure i have the event id 474. it says, that there
>>>> is an inconsitence in the c:\windows\ntds\ntds.dit is there a way to
>>>> correct this error or to restore the files from a backup ? the error
>>>> occurs on the one and only dc in a w2k3 environment. i do a nightly
>>>> backup with symantec's backup exec 10 including the system state.
>>>>
>>>> thanx alot
>>>> tim
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Let me know if that worked ok for you

Best Regards
Systems Administrator
MCSA + Exchange

"Tim Moor" <tim.moor@nospam.com> escreveu na mensagem
news:444749cf$1_5@news.bluewin.ch...
> hello jmnts,
> thank you for this detailed information. i go through this ...
>
> all the best
> tim
>
>
>
> "Jmnts" <Jmnts@hotmail.com> schrieb im Newsbeitrag
> news:%23OsLyo$YGHA.4248@TK2MSFTNGP05.phx.gbl...
>> Hi
>>
>> Did you check the available Disk space?
>>
>> Based on my research, the specified issue may caused by corrupted AD
>> database. If you have a recent backup I recommend you to perform restore
>> operation to resolve the issue.
>>
>>
>>
>> However if the backup is not recent, and you'll loose many objects you
>> can try to repair the Database, In some situation, certain configurations
>> will be lost with this procedure.
>>
>> Before you start the computer in Directory Services Restore Mode, obtain
>> the password for the offline administrator account.
>>
>> For more information about how to change the password in Windows Server
>> 2003, click the following article number to view the article in the
>> Microsoft Knowledge Base
>>
>> http://support.microsoft.com/kb/322672/
>>
>> "Directory Services cannot start" error message when you start your
>> Windows-based or SBS-based domain controller
>> http://support.microsoft.com/?id=258062
>>
>> Next step:
>>
>> How to Recover the Database and if it fails try How to Repair the
>> Database (Be careful withis last one read carefully)
>>
>> http://support.microsoft.com/default...b;en-us;315131
>>
>> How to complete a semantic database analysis for the Active Directory
>> database by using Ntdsutil.exe
>> http://support.microsoft.com/default...b;en-us;315136
>>
>>
>>
>>
>>
>>
>>
>> If you fail to repair a corrupted Active Directory, try the following:
>> You may try the following steps to recover the corrupted Active
>> Directory.
>>
>> 1. Reboot the server and press F8. Choose Directory Services Restore
>> Mode from the Menu.
>> 2. Check the physical location of the Winnt\NTDS\ folder.
>> 3. Check the permissions on the \Winnt\NTDS folder.
>>
>>
>>
>> The default permissions are:
>>
>> Administrators - Full Control
>> System - Full Control
>>
>> 4. Check the Winnt\Sysvol\Sysvol folder to make sure it is shared.
>> 5. Check the permissions on the Winnt\Sysvol\Sysvol share.
>>
>>
>>
>> The default permissions are:
>>
>> Share Permissions:
>> Administrators - Full Control
>> Authenticated Users - Full Control
>> Everyone - Read
>>
>> NTFS Permissions:
>> Administrators - Full Control
>> Authenticated Users - Read & Execute, List Folder Contents, Read
>> Creator Owner - none
>> Server Operators - Read & Execute, List Folder Contents, Read
>> System - Full Control
>>
>> Note: You may not be able to change the permissions on these folders if
>> the Active Directory database is unavailable because it is damaged,
>> however it is best to know if the permissions are set correctly before
>> you start the recovery process, as it may not be the database that is the
>> problem.
>>
>> 6. Make sure there is a folder in the Sysvol share labeled with the
>> correct name for their domain.
>> 7. Open a command prompt and run NTDSUTIL to verify the paths for the
>> NTDS.dit file. These should match the physical structure from Step 2
>>
>> To check the file paths type the following commands:
>>
>> NTDSUTIL <enter>
>> Files <enter>
>> Info <enter>
>>
>> The output should look similar to:
>>
>> Drive Information:
>>
>> C:\ NTFS (Fixed Drive) free (2.9 Gb) total (3.9 Gb)
>> D:\ NTFS (Fixed Drive) free (3.6 Gb) total (3.9 Gb)
>>
>> DS Path Information:
>>
>> Database : C:\WINNT\NTDS\ntds.dit - 10.1 Mb
>> Backup dir: C:\WINNT\NTDS\dsadata.bak
>> Working dir: C:\WINNT\NTDS
>> Log dir : C:\WINNT\NTDS - 30.0 Mb total
>> res2.log - 10.0 Mb
>> res1.log - 10.0 Mb
>> edb.log - 10.0 Mb
>>
>> This information is pulled directly from the registry and mismatched
>> paths will cause Active Directory not to start. Type Quit to end the
>> NTDSUTIL session.
>>
>> 8. Rename the edb.chk file and try to boot to Normal mode. If that
>> fails, proceed with the next steps.
>>
>> 9. Reboot into Directory Services Restore mode again. At the command
>> prompt, use the ESENTUTL to check the integrity of the database.
>> NOTE: You can use NTDSUTIL to check the Integrity, however esentutl is
>> usually more reliable.
>>
>> Type the following command:
>> ESENTUTL /g "<path>\NTDS.dit" /!10240 /8 /v /x /o <enter>
>> (Note: Type the path without the quotes).
>>
>> Note: The default path would be C:\Winnt\NTDS\ntds.dit; however it may be
>> different in some cases.
>>
>> The output will tell you if the database is inconsistent and may produce
>> a jet_error 1206 stating that the database is corrupt. If the database
>> is inconsistent or corrupt it will need to be recovered or repaired . To
>> recover the database type the following at the command prompt:
>>
>> NTDSUTIL <enter>
>> Files<enter>
>> Recover <enter>
>>
>> If this fails with an error, type quit until back at the command prompt
>> and repair the database using ESENTUTL by typing the following:
>>
>> ESENTUTL /p "<path>\NTDS.dit" /!10240 /8 /v /x /o <enter>
>> (Note: Type the path without the quotes).
>>
>> Note: If you do not put the switches at the end of the command you will
>> most likely get a Jet_error 1213 "Page size mismatch" error.
>>
>> 10. Delete the log files in the NTDS directory, but do not delete or
>> move the ntds.dit file.
>> 11. The NTDSUTIL tool needs to be run again to check the Integrity of the
>> database and to perform a Semantic Database analysis.
>>
>> To check the integrity, at the command prompt type:
>>
>> NTDSUTIL <enter>
>> Files <enter>
>> Integrity <enter>
>>
>> The output should tell you that the integrity check completed
>> successfully and prompt that you should perform a Semantic Database
>> Analysis.
>>
>> Type quit.
>>
>> To perform the Semantic Database Analysis type the following at the
>> NTDSUTIL Prompt type:
>>
>> Semantic Database Analysis <enter>
>> Go <enter>
>>
>> The output will tell you that the Analysis completed successfully.
>> Type quit and closes the command prompt.
>>
>> NOTE: If you get errors running the Analysis then type the following at
>> the semantic checker prompt:
>>
>> semantic checker: go fix <enter>
>>
>> This puts the checker in Fixup mode, which should fix whatever errors
>> there were.
>>
>> 12. Reboot the server to Normal Mode.
>>
>> If any of these steps fail to recover the database the only alternative
>> is to perform an Authoritative System State restore from backup in
>> Directory Services Restore mode.
>>
>> For more information, please refer to the following articles:
>>
>> 315136 HOW TO: Complete a Semantic Database Analysis for the Active
>> Directory
>> http://support.microsoft.com/?id=315136
>>
>> 265706 DCDiag and NetDiag in Windows 2000 Facilitate Domain Join and DC
>> Creation
>> http://support.microsoft.com/?id=265706
>>
>> 258007 Error Message: Lsass.exe - System Error : Security Accounts
>> Manager
>> http://support.microsoft.com/?id=258007
>>
>> 265089 Event 1168: Windows 2000 DCs Unable to Boot into Active Directory
>> http://support.microsoft.com/?id=265089
>>
>> 315131 HOW TO: Use Ntdsutil to Manage Active Directory Files from the
>> Command
>> http://support.microsoft.com/?id=315131
>>
>>
>>
>>
>> --
>> Best Regards
>> Systems Administrator
>> MCSA + Exchange
>>
>>
>>
>> "Tim Moor" <tim.moor@gmx.net> wrote in message
>> news:4446a2d0$1_2@news.bluewin.ch...
>>> hello jmnts
>>> thank you for your reply. i only have one dc in this w2k3 domain. the
>>> error occurs on the dc (w2k3, sp1, no exchange installed). if i try to
>>> open ad users and computers it takes very long. then i receive an error
>>> message saying, that ad users and computers is not available. after a
>>> certain time, the ad users and computers gui starts. i had a harddisk
>>> crash on a sata raid1. even after replacing the faulty disk, the
>>> following error shows up. so far i have no idea how to solve the
>>> problem. all i have is a vaild backup (veritas backup) before the disk
>>> crash happend.
>>>
>>> tim
>>>
>>>
>>>
>>>
>>> Event Type: Error
>>> Event Source: NTDS ISAM
>>> Event Category: Database Page Cache
>>> Event ID: 474
>>> Date: 23/09/2005
>>> Time: 16:31:34
>>> User: N/A
>>> Computer: SRV01
>>> Description:
>>> NTDS (1504) NTDSA: The database page read from the file
>>> "d:\ntds\ntds.dit"
>>> at offset 6832128 (0x0000000000684000) for 8192 (0x00002000) bytes
>>> failed
>>> verification due to a page checksum mismatch. The expected checksum was
>>> 1616634593 (0x605be2e1) and the actual checksum was 3314267797
>>> (0xc58bb695).
>>> 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.
>>>
>>>
>>> "Jmnts" <Jmnts@hotmail.com> schrieb im Newsbeitrag
>>> news:%23yDWgg9YGHA.4120@TK2MSFTNGP04.phx.gbl...
>>>> Hi
>>>>
>>>> Could you please give more info?
>>>>
>>>> How many Dcs in the Domain?
>>>> Exact Error and Source?
>>>> What kind of problems do you have?
>>>> Did you replace the disk with a new one or is it the same?
>>>> What setps did you taked to recover the disk?
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards
>>>> Systems Administrator
>>>> MCSA + Exchange
>>>>
>>>>
>>>>
>>>> "Tim Moor" <tim.moor@nospam.com> wrote in message
>>>> news:44465883$1_7@news.bluewin.ch...
>>>>> dear w2k ad gurus,
>>>>> after a harddisk failure i have the event id 474. it says, that there
>>>>> is an inconsitence in the c:\windows\ntds\ntds.dit is there a way to
>>>>> correct this error or to restore the files from a backup ? the error
>>>>> occurs on the one and only dc in a w2k3 environment. i do a nightly
>>>>> backup with symantec's backup exec 10 including the system state.
>>>>>
>>>>> thanx alot
>>>>> tim
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>

hello jmnts
i went to the ad-repair process described in your posting. your instruction
are very precise ! thank you. but i could not recover the ad (ntds.dis). so
all i can do is try to restore from the backup.

btw: the options to: ESENTUTL may be a little different on w2k3.

anyway, thank you very much again

tim



"Jmnts" <jmnts@hotmail.com> schrieb im Newsbeitrag
news:%23PiR9yFZGHA.4944@TK2MSFTNGP02.phx.gbl...
> Let me know if that worked ok for you
>
> Best Regards
> Systems Administrator
> MCSA + Exchange
>
> "Tim Moor" <tim.moor@nospam.com> escreveu na mensagem
> news:444749cf$1_5@news.bluewin.ch...
>> hello jmnts,
>> thank you for this detailed information. i go through this ...
>>
>> all the best
>> tim
>>
>>
>>
>> "Jmnts" <Jmnts@hotmail.com> schrieb im Newsbeitrag
>> news:%23OsLyo$YGHA.4248@TK2MSFTNGP05.phx.gbl...
>>> Hi
>>>
>>> Did you check the available Disk space?
>>>
>>> Based on my research, the specified issue may caused by corrupted AD
>>> database. If you have a recent backup I recommend you to perform restore
>>> operation to resolve the issue.
>>>
>>>
>>>
>>> However if the backup is not recent, and you'll loose many objects you
>>> can try to repair the Database, In some situation, certain
>>> configurations will be lost with this procedure.
>>>
>>> Before you start the computer in Directory Services Restore Mode, obtain
>>> the password for the offline administrator account.
>>>
>>> For more information about how to change the password in Windows Server
>>> 2003, click the following article number to view the article in the
>>> Microsoft Knowledge Base
>>>
>>> http://support.microsoft.com/kb/322672/
>>>
>>> "Directory Services cannot start" error message when you start your
>>> Windows-based or SBS-based domain controller
>>> http://support.microsoft.com/?id=258062
>>>
>>> Next step:
>>>
>>> How to Recover the Database and if it fails try How to Repair the
>>> Database (Be careful withis last one read carefully)
>>>
>>> http://support.microsoft.com/default...b;en-us;315131
>>>
>>> How to complete a semantic database analysis for the Active Directory
>>> database by using Ntdsutil.exe
>>> http://support.microsoft.com/default...b;en-us;315136
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> If you fail to repair a corrupted Active Directory, try the following:
>>> You may try the following steps to recover the corrupted Active
>>> Directory.
>>>
>>> 1. Reboot the server and press F8. Choose Directory Services Restore
>>> Mode from the Menu.
>>> 2. Check the physical location of the Winnt\NTDS\ folder.
>>> 3. Check the permissions on the \Winnt\NTDS folder.
>>>
>>>
>>>
>>> The default permissions are:
>>>
>>> Administrators - Full Control
>>> System - Full Control
>>>
>>> 4. Check the Winnt\Sysvol\Sysvol folder to make sure it is shared.
>>> 5. Check the permissions on the Winnt\Sysvol\Sysvol share.
>>>
>>>
>>>
>>> The default permissions are:
>>>
>>> Share Permissions:
>>> Administrators - Full Control
>>> Authenticated Users - Full Control
>>> Everyone - Read
>>>
>>> NTFS Permissions:
>>> Administrators - Full Control
>>> Authenticated Users - Read & Execute, List Folder Contents,
>>> Read
>>> Creator Owner - none
>>> Server Operators - Read & Execute, List Folder Contents, Read
>>> System - Full Control
>>>
>>> Note: You may not be able to change the permissions on these folders if
>>> the Active Directory database is unavailable because it is damaged,
>>> however it is best to know if the permissions are set correctly before
>>> you start the recovery process, as it may not be the database that is
>>> the problem.
>>>
>>> 6. Make sure there is a folder in the Sysvol share labeled with the
>>> correct name for their domain.
>>> 7. Open a command prompt and run NTDSUTIL to verify the paths for the
>>> NTDS.dit file. These should match the physical structure from Step 2
>>>
>>> To check the file paths type the following commands:
>>>
>>> NTDSUTIL <enter>
>>> Files <enter>
>>> Info <enter>
>>>
>>> The output should look similar to:
>>>
>>> Drive Information:
>>>
>>> C:\ NTFS (Fixed Drive) free (2.9 Gb) total (3.9 Gb)
>>> D:\ NTFS (Fixed Drive) free (3.6 Gb) total (3.9 Gb)
>>>
>>> DS Path Information:
>>>
>>> Database : C:\WINNT\NTDS\ntds.dit - 10.1 Mb
>>> Backup dir: C:\WINNT\NTDS\dsadata.bak
>>> Working dir: C:\WINNT\NTDS
>>> Log dir : C:\WINNT\NTDS - 30.0 Mb total
>>> res2.log - 10.0 Mb
>>> res1.log - 10.0 Mb
>>> edb.log - 10.0 Mb
>>>
>>> This information is pulled directly from the registry and mismatched
>>> paths will cause Active Directory not to start. Type Quit to end the
>>> NTDSUTIL session.
>>>
>>> 8. Rename the edb.chk file and try to boot to Normal mode. If that
>>> fails, proceed with the next steps.
>>>
>>> 9. Reboot into Directory Services Restore mode again. At the command
>>> prompt, use the ESENTUTL to check the integrity of the database.
>>> NOTE: You can use NTDSUTIL to check the Integrity, however esentutl is
>>> usually more reliable.
>>>
>>> Type the following command:
>>> ESENTUTL /g "<path>\NTDS.dit" /!10240 /8 /v /x /o <enter>
>>> (Note: Type the path without the quotes).
>>>
>>> Note: The default path would be C:\Winnt\NTDS\ntds.dit; however it may
>>> be different in some cases.
>>>
>>> The output will tell you if the database is inconsistent and may produce
>>> a jet_error 1206 stating that the database is corrupt. If the database
>>> is inconsistent or corrupt it will need to be recovered or repaired .
>>> To recover the database type the following at the command prompt:
>>>
>>> NTDSUTIL <enter>
>>> Files<enter>
>>> Recover <enter>
>>>
>>> If this fails with an error, type quit until back at the command prompt
>>> and repair the database using ESENTUTL by typing the following:
>>>
>>> ESENTUTL /p "<path>\NTDS.dit" /!10240 /8 /v /x /o <enter>
>>> (Note: Type the path without the quotes).
>>>
>>> Note: If you do not put the switches at the end of the command you will
>>> most likely get a Jet_error 1213 "Page size mismatch" error.
>>>
>>> 10. Delete the log files in the NTDS directory, but do not delete or
>>> move the ntds.dit file.
>>> 11. The NTDSUTIL tool needs to be run again to check the Integrity of
>>> the database and to perform a Semantic Database analysis.
>>>
>>> To check the integrity, at the command prompt type:
>>>
>>> NTDSUTIL <enter>
>>> Files <enter>
>>> Integrity <enter>
>>>
>>> The output should tell you that the integrity check completed
>>> successfully and prompt that you should perform a Semantic Database
>>> Analysis.
>>>
>>> Type quit.
>>>
>>> To perform the Semantic Database Analysis type the following at the
>>> NTDSUTIL Prompt type:
>>>
>>> Semantic Database Analysis <enter>
>>> Go <enter>
>>>
>>> The output will tell you that the Analysis completed successfully.
>>> Type quit and closes the command prompt.
>>>
>>> NOTE: If you get errors running the Analysis then type the following at
>>> the semantic checker prompt:
>>>
>>> semantic checker: go fix <enter>
>>>
>>> This puts the checker in Fixup mode, which should fix whatever errors
>>> there were.
>>>
>>> 12. Reboot the server to Normal Mode.
>>>
>>> If any of these steps fail to recover the database the only alternative
>>> is to perform an Authoritative System State restore from backup in
>>> Directory Services Restore mode.
>>>
>>> For more information, please refer to the following articles:
>>>
>>> 315136 HOW TO: Complete a Semantic Database Analysis for the Active
>>> Directory
>>> http://support.microsoft.com/?id=315136
>>>
>>> 265706 DCDiag and NetDiag in Windows 2000 Facilitate Domain Join and DC
>>> Creation
>>> http://support.microsoft.com/?id=265706
>>>
>>> 258007 Error Message: Lsass.exe - System Error : Security Accounts
>>> Manager
>>> http://support.microsoft.com/?id=258007
>>>
>>> 265089 Event 1168: Windows 2000 DCs Unable to Boot into Active Directory
>>> http://support.microsoft.com/?id=265089
>>>
>>> 315131 HOW TO: Use Ntdsutil to Manage Active Directory Files from the
>>> Command
>>> http://support.microsoft.com/?id=315131
>>>
>>>
>>>
>>>
>>> --
>>> Best Regards
>>> Systems Administrator
>>> MCSA + Exchange
>>>
>>>
>>>
>>> "Tim Moor" <tim.moor@gmx.net> wrote in message
>>> news:4446a2d0$1_2@news.bluewin.ch...
>>>> hello jmnts
>>>> thank you for your reply. i only have one dc in this w2k3 domain. the
>>>> error occurs on the dc (w2k3, sp1, no exchange installed). if i try to
>>>> open ad users and computers it takes very long. then i receive an error
>>>> message saying, that ad users and computers is not available. after a
>>>> certain time, the ad users and computers gui starts. i had a harddisk
>>>> crash on a sata raid1. even after replacing the faulty disk, the
>>>> following error shows up. so far i have no idea how to solve the
>>>> problem. all i have is a vaild backup (veritas backup) before the disk
>>>> crash happend.
>>>>
>>>> tim
>>>>
>>>>
>>>>
>>>>
>>>> Event Type: Error
>>>> Event Source: NTDS ISAM
>>>> Event Category: Database Page Cache
>>>> Event ID: 474
>>>> Date: 23/09/2005
>>>> Time: 16:31:34
>>>> User: N/A
>>>> Computer: SRV01
>>>> Description:
>>>> NTDS (1504) NTDSA: The database page read from the file
>>>> "d:\ntds\ntds.dit"
>>>> at offset 6832128 (0x0000000000684000) for 8192 (0x00002000) bytes
>>>> failed
>>>> verification due to a page checksum mismatch. The expected checksum was
>>>> 1616634593 (0x605be2e1) and the actual checksum was 3314267797
>>>> (0xc58bb695).
>>>> 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.
>>>>
>>>>
>>>> "Jmnts" <Jmnts@hotmail.com> schrieb im Newsbeitrag
>>>> news:%23yDWgg9YGHA.4120@TK2MSFTNGP04.phx.gbl...
>>>>> Hi
>>>>>
>>>>> Could you please give more info?
>>>>>
>>>>> How many Dcs in the Domain?
>>>>> Exact Error and Source?
>>>>> What kind of problems do you have?
>>>>> Did you replace the disk with a new one or is it the same?
>>>>> What setps did you taked to recover the disk?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards
>>>>> Systems Administrator
>>>>> MCSA + Exchange
>>>>>
>>>>>
>>>>>
>>>>> "Tim Moor" <tim.moor@nospam.com> wrote in message
>>>>> news:44465883$1_7@news.bluewin.ch...
>>>>>> dear w2k ad gurus,
>>>>>> after a harddisk failure i have the event id 474. it says, that there
>>>>>> is an inconsitence in the c:\windows\ntds\ntds.dit is there a way to
>>>>>> correct this error or to restore the files from a backup ? the error
>>>>>> occurs on the one and only dc in a w2k3 environment. i do a nightly
>>>>>> backup with symantec's backup exec 10 including the system state.
>>>>>>
>>>>>> thanx alot
>>>>>> tim
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>