Home News An Easy Way To Fix Common Ntds Internal Error 1481

An Easy Way To Fix Common Ntds Internal Error 1481



This guide describes some of the possible causes that can lead to internal failure. Then you can try to fix this problem.



Question: how are you trying to determine the source of the error:

ntds general 1481 internal error

Event type: Â error
Event Source: NTDS General
Event Category: Internal Processing
Event ID: 1481
Internal error: The operation on the object failed.

Additional data
Error value:
2 000020EF: NameErr: DSID-032500F4, issue 2001 (NO_OBJECT), data -1603, best match:


Event type: Â info
Event Source: NTDS General
Event Category: Internal Processing
Event ID: 2041
User: N / A
Removed duplicate event log entries.

See the previous event log entry for more information. A record is considered duplicate if the event code and all insert parameters match. The period for this series of duplicates is from the time of the previous event to the time of this event.

Event ID:
Number of duplicate entries:

Esentutil and ntdsutil show no problem when starting in DS recovery mode, while dcdiag, replmon or repadmin show errors.

Operating system: Windows 2003 R2 (64-bit and 32-bit), the most updated. Note. ALL domain controllers report this error with an NTDS log of 5, but no other errors.

This issue prevents 2008 and 2012 servers from being promoted to domain controllers.

All NTDS logs are up at 5am, hoping to find other messages, but to no avail.

No other errors are logged, only this empty element.


This issue occurs when Active Directory contains the following third-party attribute:

Windows 2000 SP4 and Windows Server 2008 accept UNICODE data with the SYNTAX_UNICODE_TYPE attribute type. However, Windows Server 2003 does not accept this data type. Therefore, Windows Server 2003 does not replicate this attribute data type.

Note. In the events that appear in the Symptoms section, the affected attribute is printMediaReady. This attribute is set in the PrintQueue class. This attribute is written by a third party printer driver. You may run into this issue with other third party attributes.

1. Restoring Active Directory Using ESENTUTL

Restart the failed domain controller in Directory Restore Mode (DSRM). There are several ways to do this. Fortunately, you need to remember the DSRM password that was created when you promoted the server to a domain controller or when you first set up the forest.

Note. If you don’t have a DSRM password and only have one domain controller, you will need to rebuild the forest from scratch, join the computer to the new domain, and configure everything from there. Start.

  • Option 1 – F8
    Restart your device and press F8 at startup. Wait while you are prompted to select DSRM. Of course, you will need physical or console access for this.
  • Option 2 – MSConfig
    Open MSConfig.msc, go to the Boot tab, click Safeboot and ActiveDirectoryRepair.
  • Option 3 – Command Line
    One of the command line window types uses the bcdedit / set safeboot dsrepair command

After restarting the server in DSRM mode, click the Start button and open a Command Prompt window with cmd.

It is important to back up the database by storing a copy of the file elsewhere. for example, in c: scripts.

First you need to check the integrity of the database. This can be done by running the following command:

esentutl / g c: windows ntds ntds.dit

If the result says BROKEN, you must run the restore switch and attempt to restore the database. This can be done with the following example:

esentutl / p c: windows ntds ntds.dit

When the process completes, delete the log files, if any, from the C: Windows ntds folder.

Then remove the DSRM parameter and restart the server. If all goes well, the problem should be fixed.