windows connot do any thing

[tigergad]

بسم الله
اخوانى الاعزاء
فى عندى مشكلة و هى كالتالى فى عندى Active Directoryو شغال ممتاذ و كل شىء سوى عندى userمعين بعينه userدا كان شغال كويس و فجأة غير قادر على الدخول
طبعا راجعت كل شىء خاص بالمشكلة دى من اسم مستخدم و كلمة مرور على الجهاز المعتاد الدخول ن عليه و منفعشى .
جربت الدخول من جهاز اخر و كمان منفعشى
قلت اغير كلمة السر بتاعتة من على Active Directoryبيعطينى رسالة بتقول
windows cannot complete the password change for(USERNAMe) because: An internal error occurred
طيب لو حاولت حذفه الرسالة كالتالى
windows cannot delete the object(USERNAME)because" An internal error occurred

على فكرة دا بس مع userدا فقط انما اى شىء شغال مع البقية

يا ريت اى احد عنده فكرة كيف حل المشكلة يساهم
و شكرا

[MNabrawy]

problem in active not in user yo can check go to restore mode in active and try again in not you may be want to fix it

plz check it and reply if it is worked or not

[tigergad]

thanks for ur repaly
really after I checked Event viewer i founf ther is a proin AD data base
I tried to restore database but the problem I lost the last system state
now in event viewser always shows an error for AD data base
want now if u can help to stop this error and start this database with out any error "NTDS"

[عادل شبل]

ال event id بتاع ال error ده كام؟ او ابقى خده واكتبه فى الموقع ده هيجيبلك كل تفاصيله وحل المشكله

www.eventid.net

[tigergad]

Event ID 474 Source NTDS ISAM


Event ID474SourceNTDS ISAMTypeErrorDescriptionNTDS (<PID>) NTDSA: The database page read from the file "<path to edb file>" at offset <offset> for <value> bytes failed verification due to a page checksum mismatch. The expected checksum was <checksum> and the actual checksum was <checksum>. The read operation will fail with error <error code> (<error code>). If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware.Comments and links for event id 474 from source NTDS ISAM
Contribute
If you have details about an event with id 474 that is not listed in our database, please, send it to us. The submitted event will be forwarded to our consultants for analysis. We recommend you to check the EventID.Net Processing Queue to see if the event was already been submitted by another contributor.

[e_bawadi]

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

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

"Directory Services cannot start" error message when you start your
Windows-based or SBS-based domain controller
https://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)

https://support.microsoft.com/defaul...kb;en-us;315131

How to complete a semantic database analysis for the Active Directory
database by using Ntdsutil.exe
https://support.microsoft.com/defaul...kb;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
https://support.microsoft.com/?id=315136

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

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

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

315131 HOW TO: Use Ntdsutil to Manage Active Directory Files from the
Command

https://support.microsoft.com/?id=315131


and anthor source
https://forums.techarena.in/small-bu...er/1001722.htm

[tigergad]

Thank you
I try this but still the same error not solved although every step was done successfuly for recovering the database and the following steps

so ,do u have another soluation
regards