Fix ERROR_DS_NO_REQUESTED_ATTS_FOUND (0X00002074)

Quick Check (30 seconds)

Most of the time, this error happens because of a simple typo. The LDAP query asks for an attribute that doesn't exist in Active Directory. Here's what you do first:

1. Open the tool that gave you the error — LDP.exe, ADSI Edit, or a custom script.
2. Look at the attribute names in your query. Are they spelled exactly right? Active Directory attribute names are case-insensitive, but one wrong character breaks it. For example, givenName is correct, but givenname also works. givennamee won't.
3. Check if the attribute is a constructed attribute. Some attributes like msDS-ReplAttributeMetaData are only available on domain controllers with the right schema. If you're querying a read-only domain controller (RODC), it might not have them.

After you fix the typo — rerun the query. If the error goes away, you're done. If not, move to the moderate fix.

Moderate Fix (5 minutes)

The real fix is often in the schema. Active Directory has a schema that lists every allowed attribute. When an LDAP query asks for an attribute that isn't in the schema, you get 0x00002074. Let's check the schema.

1. Open ADSI Edit (install it from Server Manager if you haven't).
2. Right-click ADSI Edit in the left pane, choose Connect to.
3. In the Connection Settings dialog, under Select a well-known Naming Context, choose Schema.
4. Click OK.
5. In the left pane, expand the Schema container. You'll see thousands of attributes listed.
6. Find the attribute you were querying. Right-click it, choose Properties.
7. Look for attributeID and attributeSyntax. If the attribute exists, the syntax tells you what kind of data it stores (string, integer, DN, etc.).
8. If the attribute isn't there — that's your problem. The attribute doesn't exist in your schema.

If the attribute is missing, you have two options:

• Option A: Change your LDAP query to use an attribute that does exist. For instance, if you were querying customAttribute1, try extensionAttribute1 or otherTelephone. These are common extension attributes that exist in most AD schemas.
• Option B: Extend the schema to add the missing attribute (advanced fix below).

After you adjust the query — test it again. If it works, great. If not, you need the advanced fix.

Advanced Fix (15+ minutes)

You need to add the missing attribute to your Active Directory schema. Schema updates are permanent and affect your entire forest — so be careful.

Before you start: Schema updates can't be undone easily. Make sure you have a backup of your domain controllers and the schema master FSMO role holder. If you're in a production environment, do this during a maintenance window.

1. Log into the domain controller that holds the Schema Master role. If you're not sure which one it is, run this in PowerShell:

Get-ADDomain | Select-Object SchemaMaster

2. Open a Command Prompt as Administrator. Run:

regsvr32 schmmgmt.dll

This registers the Schema Management snap-in.

3. Open MMC (Microsoft Management Console). Press Windows Key + R, type mmc, press Enter.
4. Go to File > Add/Remove Snap-in.
5. Find Active Directory Schema in the list, click Add, then OK.
6. In the left pane, right-click Active Directory Schema, choose Operations Masters. Make sure The Schema may be modified on this Domain Controller is checked. If not, check it and click OK.
7. Right-click Attributes under the Schema node, choose Create Attribute.
8. Fill in the required fields:
• Common Name: A descriptive name, like MyCustomAttribute.
• LDAP Display Name: The name you'll use in LDAP queries, like myCustomAttribute.
• Unique X500 OID: This must be unique. Microsoft provides a base OID 1.2.840.113556.1.8000.2554 — append your own numbers after a dot. For example, 1.2.840.113556.1.8000.2554.12345. Don't reuse someone else's OID.
• Syntax: Choose the right data type. For text, pick Unicode String. For numbers, pick Integer. For a list of values, check Multi-valued.
9. Click OK to create the attribute.
10. Now you need to add this attribute to an object class (like User or Computer) so it shows up in LDAP queries. Right-click Classes under Schema, find the class you need (for users, that's User), right-click, choose Properties.
11. Go to the Attributes tab, click Add. Find your new attribute in the list, double-click it, then click OK.
12. Close the MMC. The schema change replicates to all domain controllers. This can take 15 minutes or longer depending on your replication topology.

After replication, rerun your LDAP query. The attribute should be found now. If you still get the error, verify the attribute's LDAP display name — one wrong letter and you're back to square one.

One more thing: If you used LDP.exe to test, remember that it caches schema data. Close and reopen LDP before testing again. Otherwise you'll see the same error even after the schema update.