What does Windows error code 8637 (ERROR_DS_OID_MAPPED_GROUP_CANT_HAVE_MEMBERS) mean?

ERROR_DS_OID_MAPPED_GROUP_CANT_HAVE_MEMBERS

OID mapped groups cannot have members.

Windows assigns decimal 8637 and hexadecimal 0x000021BD to ERROR_DS_OID_MAPPED_GROUP_CANT_HAVE_MEMBERS. The constant belongs to Active Directory Domain Services; its name is not enough to identify the affected directory object, DNS zone, policy, installer, package, or resource context.

Operational meaning

The key question is whether the object is used only for its OID mapping and is not modified with member values. The value describes an OID-mapped directory group that is not a normal membership container; it does not prove that the whole domain, DNS service, network, servicing stack, application package, or operating system has failed.

Likely impact: Adding membership would change the meaning of an object reserved for identifier mapping. Record the scope that was actually tested instead of escalating from one rejected object or phase to a system-wide outage.

Where the result appears

• This result can appear while processing an OID-mapped directory group that is not a normal membership container.
• This result can appear while an LDAP, replication, domain-join, schema, trust, or directory-management request.
• This result can appear while a request routed to one particular domain controller whose replica and site state matters.
• It can appear while a management tool that translates LDAP extended diagnostics into a Win32 result.

Typical causes

• automation treats every group class as membership-capable.
• a schema or authorization mapping object is mistaken for a security group.
• the target DN is wrong.
• migration copies member attributes indiscriminately.

Diagnostic sequence

1. capture it immediately after the failing or status-returning call and record whether the API uses Win32, DNS_STATUS, HRESULT conversion, or callback semantics.
2. identify the exact target involved in an OID-mapped directory group that is not a normal membership container, including stable GUIDs, DNs, zone names, package identities, file hashes, policy names, or process identifiers as applicable.
3. prove the state boundary: the object is used only for its OID mapping and is not modified with member values.
4. collect group DN and object class and OID mapping attributes before restarting services, deleting objects, rebuilding packages, or changing policy.
5. correlate attempted member values with Directory Service events, Security events, LDAP extended error text, replication metadata, dcdiag output, repadmin output, and the caller trace.
6. determine whether the result is a failure, warning, informational completion, continuation request, or marker constant before choosing retry behavior.
7. after changing one responsible condition, repeat the same smallest operation and verify both success and absence of unintended partial effects.

Evidence to preserve

• collect group DN and object class.
• collect OID mapping attributes.
• collect attempted member values.
• collect schema definition.
• collect provisioning rule that selected the object.

Correlate this evidence with Directory Service events, Security events, LDAP extended error text, replication metadata, dcdiag output, repadmin output, and the caller trace. Preserve raw identifiers and the first detailed diagnostic: translating everything to 8637 can hide whether the cause was validation, topology, authorization, replication, policy, file I/O, packaging, or an intentional continuation state.

Recovery and retry

The recovery objective for it is to target a normal security or distribution group for membership and leave the OID-mapped object without members.

Retry only after the recorded boundary changes and prior completion is known. Read-only discovery for it can usually be repeated with bounded backoff; directory mutations, DNS updates, policy installation, servicing actions, and PRI writes require a state check first. Backoff for it cannot repair malformed input, unsupported structure, identity collision, missing authority, or incompatible package metadata.

Telemetry and support fields

• record ds_oid_mapped_group_cant_have_members_operation — producing API, command, callback, or servicing phase.
• record ds_oid_mapped_group_cant_have_members_target — stable object, zone, policy, package, file, or account identity.
• record ds_oid_mapped_group_cant_have_members_state_before and ds_oid_mapped_group_cant_have_members_requested_state.
• record ds_oid_mapped_group_cant_have_members_first_status — earliest component-specific code before translation.
• record ds_oid_mapped_group_cant_have_members_server, ds_oid_mapped_group_cant_have_members_process, UTC timestamp, and correlation ID.

A support bundle for it should include decimal 8637, hexadecimal 0x000021BD, the smallest reproducible request, target identity, effective configuration, and evidence from the owning Windows component. When documenting it, remove secrets from exported logs but keep SIDs, GUIDs, package-family names, record types, and hashes when they are needed to distinguish objects.

Difference from nearby results

ERROR_DS_ATTRIBUTE_OR_VALUE_EXISTS concerns duplicate attribute values; this code prohibits member values by object semantics This distinction determines whether the correct next step is input correction, topology repair, continuation, policy review, package rebuild, or no error handling at all.

Practical validation scenario

A generic group sync selects an OID-mapped group by name and tries to add users. Filtering by object class routes members to the intended security group. A negative test should reproduce it with the responsible condition preserved; the recovery test should alter only that condition and confirm the intended final state.

Developer and administrator guidance

Developers should model it explicitly in the result domain instead of collapsing every nonzero value into “failed.” Administrators should capture evidence before destructive remediation and use the component that owns an OID-mapped directory group that is not a normal membership container. Monitoring for it should suppress range markers and classify warning, informational, cancellation, and continuation values separately from terminal failures.

References

• Microsoft: exact Win32 system error range — official context relevant to it.
• Microsoft: AD DS troubleshooting — official context relevant to it.
• Microsoft: dcdiag — official context relevant to it.
• Microsoft: repadmin — official context relevant to it.

Looking for a different code? Search another status or error code.