What does Windows error code 8635 (ERROR_DS_FLAT_NAME_EXISTS_IN_FOREST) mean?

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: The flat name of the trusted domain already exists in the forest.

Previous	Next
ERROR_DS_DOMAIN_NAME_EXISTS_IN_FOREST	ERROR_INVALID_USER_PRINCIPAL_NAME

ERROR_DS_FLAT_NAME_EXISTS_IN_FOREST

The flat name of the trusted domain already exists in the forest.

A wrapper may expose ERROR_DS_FLAT_NAME_EXISTS_IN_FOREST through PowerShell, RPC, REST, JSON, or an installer log, but the actionable evidence remains in the original Windows component. Keep decimal 8635, hexadecimal 0x000021BB, and the producing function together.

Operational meaning

The key question is whether the proposed flat name is unique across domains and trusted-domain metadata. The value describes a trusted-domain flat or NetBIOS name that already exists in the forest; it does not prove that the whole domain, DNS service, network, servicing stack, application package, or operating system has failed.

Likely impact: Legacy logon names and trust routing depend on this namespace being unique. 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 a trusted-domain flat or NetBIOS name that already exists in the forest.
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

another domain already uses the flat name.
a stale trust object retains it.
a migration preserved a conflicting NetBIOS name.
the caller checks only DNS uniqueness.

Diagnostic sequence

capture it immediately after the failing or status-returning call and record whether the API uses Win32, DNS_STATUS, HRESULT conversion, or callback semantics.
identify the exact target involved in a trusted-domain flat or NetBIOS name that already exists in the forest, including stable GUIDs, DNs, zone names, package identities, file hashes, policy names, or process identifiers as applicable.
prove the state boundary: the proposed flat name is unique across domains and trusted-domain metadata.
collect proposed flat name and trustedDomain flatName attributes before restarting services, deleting objects, rebuilding packages, or changing policy.
correlate domain and forest inventory with Directory Service events, Security events, LDAP extended error text, replication metadata, dcdiag output, repadmin output, and the caller trace.
determine whether the result is a failure, warning, informational completion, continuation request, or marker constant before choosing retry behavior.
after changing one responsible condition, repeat the same smallest operation and verify both success and absence of unintended partial effects.

Evidence to preserve

collect proposed flat name.
collect trustedDomain flatName attributes.
collect domain and forest inventory.
collect stale object replication metadata.
collect trust wizard or API request.

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 8635 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 select a unique flat name or remove only verified stale trust metadata before recreating the trust.

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_flat_name_exists_in_forest_operation — producing API, command, callback, or servicing phase.
record ds_flat_name_exists_in_forest_target — stable object, zone, policy, package, file, or account identity.
record ds_flat_name_exists_in_forest_state_before and ds_flat_name_exists_in_forest_requested_state.
record ds_flat_name_exists_in_forest_first_status — earliest component-specific code before translation.
record ds_flat_name_exists_in_forest_server, ds_flat_name_exists_in_forest_process, UTC timestamp, and correlation ID.

A support bundle for it should include decimal 8635, hexadecimal 0x000021BB, 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_DOMAIN_NAME_EXISTS_IN_FOREST concerns the DNS name; this value concerns the short flat name 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

Two companies merge with distinct DNS names but the same legacy NetBIOS name. Assigning a new flat name before trust creation resolves the collision. 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 a trusted-domain flat or NetBIOS name that already exists in the forest. 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.