How to fix “The schema object could not be found. [ERROR_DS_INVALID_DMD (0x20A8)]” – Error Code 8360

Overview

In this article, we’ll focus on resolving the issue described as: “The schema object could not be found. [ERROR_DS_INVALID_DMD (0x20A8)]”. This error, identified by the error code 8360, can impede your system’s performance; here’s how to fix it.

Identifying the Problem

Error Code 8360 occurs when the Active Directory server cannot find the specified schema object. This can happen due to several reasons, including:

• Incorrect or missing schema object
• Corrupted or damaged Active Directory database
• Replication issues

Common Fixes

1. Verify the Schema Object
Ensure that the schema object you are trying to access exists. You can use the command line tool Ldp.exe to verify the schema object:
– Run Ldp.exe as an administrator.
– Connect to your Active Directory server.
– Navigate to schema browsing in the left pane.
– Search for the schema object you need.

2. Restart the Active Directory Replication Service
Replication issues can cause Error Code 8360. Restarting the replication service may resolve the problem:
– Open Services.msc.
– Restart the Active Directory Replication service.

3. Repair the Active Directory Database
A corrupted or damaged Active Directory database can cause Error Code 8360. Repairing the database may solve the issue:
– Run NTDSUTIL.EXE.
– Type set ds database show verbose.
– Check the consistency status of the database.
– Run repair database if the database is inconsistent.

Advanced Troubleshooting

1. Reset the Schema Cache
A corrupt schema cache can cause Error Code 8360. Resetting the cache may fix the problem:
– Run CMD as an administrator.
– Run the command schtasks.exe /run /tn "MicrosoftWindowsDirectoryServicesResetADSchemaCache".
– Restart the computer.

2. Check for Corrupted Object Metadata
Corrupted object metadata can cause Error Code 8360. Use the following command to repair corrupted metadata:
– Run CMD as an administrator.
– Run the command Repadmin /repair /metadata.

Conclusion

Error Code 8360 can be a frustrating issue, but by following the solutions outlined in this article, you can resolve it effectively. Remember to verify the schema object, restart the Active Directory Replication service, repair the database, reset the schema cache, and check for corrupted object metadata. By taking these steps, you can ensure your system’s integrity and prevent this error from recurring.