repadmin /syncall /AePdq
Error issuing replication : 8451 (0x2103)
The replication operation encountered a database error.
Press F8 on Boot. (If its on VMware enter bios menu . Then exit and press F8)
Check if Database is corrupted. if its corrupted . please proceed with next steps.
C:\Windows\NTDS> C:\Windows\NTDS>ESENTUTL /g C:\windows\NTDS\ntds.dit /!10240 /8 /o Initiating INTEGRITY mode... Database: C:\windows\NTDS\ntds.dit Temp. Database: .\TEMPINTEG4820.EDB Checking database integrity. The database is not up-to-date. This operation may find that this database is corrupt because data from the log files has yet to be placed in the database. To ensure the database is up-to-date please use the 'Recovery' operation. Scanning Status (% complete) 0   10  20  30  40  50  60  70  80  90 100 |----|----|----|----|----|----|----|----|----|----| ................................................... Integrity check completed. Database is CORRUPTED, the last full backup of this database was on 04/20/2019 1 2:31:03 Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database fi le or corrupted db) after 7.93 seconds. C:\Windows\NTDS>NTDSUTIL NTDSUTIL: active instance ntds Error parsing Input - Invalid Syntax. NTDSUTIL: activate instance ntds Active instance set to "ntds". NTDSUTIL: files file maintenance: info Drive Information: C:\ NTFS (Fixed Drive ) free(40.5 Gb) total(59.6 Gb) DS Path Information: Database  : C:\Windows\NTDS\ntds.dit - 314.1 Mb Backup dir : C:\Windows\NTDS\dsadata.bak Working dir: C:\Windows\NTDS Log dir   : C:\Windows\NTDS - 80.0 Mb total edbtmp.log - 10.0 Mb edbres00002.jrs - 10.0 Mb edbres00001.jrs - 10.0 Mb edb07737.log - 10.0 Mb edb07736.log - 10.0 Mb edb07735.log - 10.0 Mb edb07734.log - 10.0 Mb edb.log - 10.0 Mb file maintenance: Recover Initiating RECOVERY mode... Log files: C:\Windows\NTDS. System files: C:\Windows\NTDS. Performing soft recovery... Database recovery is successful. It is recommended you run semantic database analysis to ensure semantic database consistency as well. file maintenance: quit NTDSUTIL: ESENTUTL /ml c:\windows\ntds\edb C:\Windows\NTDS> C:\Windows\NTDS>ESENTUTL /ml c:\windows\ntds\edb Extensible Storage Engine Utilities for Microsoft(R) Windows(R) Version 6.3 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating FILE DUMP mode... Verifying log files... Base name: edb Log file: c:\windows\ntds\edb07734.log - OK Log file: c:\windows\ntds\edb07735.log - OK Log file: c:\windows\ntds\edb07736.log - OK Log file: c:\windows\ntds\edb07737.log - OK Log file: c:\windows\ntds\edb.log - OK No damaged log files were found. Operation completed successfully in 0.453 seconds. C:\Windows\NTDS>ESENTUTL /g C:\windows\NTDS\ntds.dit /!10240 /8 /o Initiating INTEGRITY mode... Database: C:\windows\NTDS\ntds.dit Temp. Database: .\TEMPINTEG3496.EDB Checking database integrity. Scanning Status (% complete) 0   10  20  30  40  50  60  70  80  90 100 |----|----|----|----|----|----|----|----|----|----| ................................................... Integrity check successful. Operation completed successfully in 20.156 seconds. C:\Windows\NTDS>ntdsutil ntdsutil: activate instance ntds Active instance set to "ntds". ntdsutil: semantic database analysis semantic checker: go Fixup mode is turned off ......Done. Writing summary into log file dsdit.dmp.0 SDs scanned:          3475 Records scanned:     27034 Processing records..Done. Elapsed time 7 seconds. semantic checker: quit ntdsutil: quit C:\Windows\NTDS>
if semantic database find any errors. you can use go fix.
 database is corrupt; the server cannot authenticate AD domain members and will not boot into normal mode.){kind=link}
Hey Thanks, This helped a lot, though the errors typed in the example I repeated as well. Not a deal breaker however.
In the end I had to type ESENTUTL /p C:\windows\NTDS\ntds.dit /!10240 /8 /o in order to repair the database, but this was the only article that remotely put me on the right track.
Thanks you Sir!