sodcalculator

10 Tech How-To

Fix Active Directory Error 0x000020a3: Deleted Name

Guide 10-47066 · Updated · Step by step

This guide walks you through resolving Active Directory error 0x000020a3, which typically appears as “The specified deleted name is not found” or “DS_NO_DELETED_NAME.” This error occurs when a tool or script tries to reference a deleted Active Directory object (like a user, computer, or group) that no longer exists in the tombstone or recycle bin. The fix involves identifying what is referencing the stale object and either removing the reference, restoring the object, or cleaning up the source of the request.

What You’ll Need

  • Domain administrator credentials (or equivalent permissions to modify Active Directory objects)
  • Access to a domain-joined computer with Active Directory Administrative Center (ADAC) or PowerShell with the Active Directory module installed
  • Knowledge of what operation triggered the error (e.g., a specific PowerShell cmdlet, a sync tool, or an application)

Step-by-Step

  1. Identify the exact operation causing the error. Note the full error message, the command or tool you were using, and the object name or DN (distinguished name) mentioned in the error. This tells you which deleted object is being referenced.
  2. Determine if the object is in the Recycle Bin or Tombstone. Open PowerShell as an administrator and run:
    Get-ADObject -Filter {Name -eq ""} -IncludeDeletedObjects -Properties * | Format-List Name, DistinguishedName, Deleted, LastKnownParent
    Replace with the name from the error. If results appear, the object exists in a deleted state.
  3. If the object is in the Recycle Bin (Enabled Forest/Domain functional level 2008 R2+), restore it. Run:
    Get-ADObject -Filter {Name -eq ""} -IncludeDeletedObjects | Restore-ADObject
    This brings the object back to its original location. Wait a few minutes for replication, then retry the original operation.
  4. If the object is only a tombstone (Recycle Bin not enabled), you cannot restore it directly. Instead, you must remove the reference. Look at what was trying to use the object—a group membership, a GPO link, a service account dependency, or a script variable. Remove that reference manually.
  5. Clean up stale references in Active Directory. If the error came from a group policy, open Group Policy Management Console (GPMC), find the GPO that references the deleted object, and edit the security filtering or delegation to remove the stale entry. If it came from a distribution group, use ADAC to open the group and remove the deleted member from its membership list.
  6. If a script or application keeps generating the error, update its configuration. Look for hardcoded DNs, SAM account names, or GUIDs in scripts, scheduled tasks, or application config files. Replace them with the current object’s values or remove the reference entirely.
  7. Force replication if needed. Run repadmin /syncall /AdeP from an elevated command prompt to ensure all domain controllers have the latest state, then retry the operation.
  8. If the error persists and the object is critical, consider re-creating it. Create a new user, computer, or group with the same name and attributes, then update any references to point to the new object.

Common Mistakes

  • Assuming the Recycle Bin is enabled. Many environments have it disabled. Check with Get-ADOptionalFeature -Filter * | Where-Object {$_.Name -like "*Recycle Bin*"} | Select-Object Name, EnabledScopes. If it shows no enabled scopes, you cannot restore deleted objects.
  • Using the wrong object name. The error may show a GUID or a DN that doesn’t match the friendly name. Always use the exact identifier from the error message in your queries.
  • Restoring to the wrong location. If the object’s last known parent OU was deleted, the restore may fail or place it in the LostAndFound container. Check the LastKnownParent attribute before restoring.
  • Editing AD on a read-only domain controller. Ensure you’re connected to a writable DC. RODCs cannot perform restore or delete operations.
  • Ignoring replication lag. After restoring or removing references, replication can take up to 15 minutes or longer. Retrying immediately can still show the error.

Tips

  • Enable the Active Directory Recycle Bin if your domain functional level is 2008 R2 or higher. This gives you a 180-day window to restore deleted objects without backup. Use Enable-ADOptionalFeature -Identity "CN=Recycle Bin Feature,CN=Optional Features,CN=Directory Service,CN=Windows NT,CN=Services,CN=Configuration,DC=,DC=" -Scope ForestOrConfigurationSet -Target .
  • Use the Active Directory Administrative Center for a graphical restore option. Under “Deleted Objects,” right-click the object and select “Restore.”
  • Maintain a script inventory. Document which scripts and applications reference AD objects by DN or SAM name so you can quickly update them when objects are deleted.
  • Test restores in a lab environment to understand how your specific AD structure behaves before doing it in production.
  • Regularly back up AD with System State backups or a dedicated AD backup tool. This is your last resort if the Recycle Bin is unavailable.

Troubleshooting

If the restore command fails with “Access Denied”: Verify you’re running PowerShell as administrator and that your account has the “Reanimate Tombstones” permission. This is typically granted to Domain Admins, but if you’re using a delegated account, add the permission to the appropriate OU.

If the object appears in the Recycle Bin but restore still fails: Check if the parent OU still exists. If the parent was also deleted, restore the parent first, then the child object. If the parent was deleted and purged, you’ll need to recreate the OU structure and then restore the object, or use a system state restore.

If you get the error from a specific application: The application may cache the object’s DN. Restart the application service or the server hosting it after cleaning up the reference. If it’s a web application, clear its cache or restart the app pool.

If the error occurs during a sync with Azure AD or another identity provider: The sync engine (like Azure AD Connect) may have a stale reference in its metaverse. Run a full sync cycle after fixing the source object, or use the sync service’s management agent to remove the deleted connector space object.

If the error only appears on one domain controller: That DC may have lingering objects. Run repadmin /removelingeringobjects on the affected DC, specifying the GC partition and the DC that has the authoritative copy. This is an advanced operation—test carefully.

If nothing else works: Perform an authoritative restore from a system state backup. Boot the DC into Directory Services Restore Mode (DSRM), restore the System State, and use ntdsutil to mark the object as authoritative. This is a last resort and requires downtime.

Frequently Asked Questions

Q: Can I recover a deleted AD object without the Recycle Bin enabled?
A: Only from a system state backup. If no backup exists, the object is permanently gone, and you must recreate it manually.

Q: How long do tombstones last by default?
A: The default tombstone lifetime is 180 days, but it can be configured differently in your environment. After that, the object is permanently purged.

Q: Does error 0x000020a3 always mean the object is deleted?
A: Yes, this specific error code indicates the deleted object cannot be found. It usually means the object was purged or the Recycle Bin was never enabled.

Q: Can I restore a deleted OU with all its child objects?
A: If the Recycle Bin is enabled, yes. Restore the parent OU first, then its children. If the Recycle Bin is disabled, you must restore from backup.

Q: Will restoring an object bring back its group memberships?
A: Yes, if the Recycle Bin is used, group memberships are restored. However, if the groups themselves were deleted and purged, those memberships will be lost.

Q: Why does my script still fail after I restored the object?
A: The script may be using a cached DN or GUID. Update the script to reference the object by its current values, or wait for replication to complete across all DCs.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →