What does Windows error code 1926 (RPC_S_PRF_ELT_NOT_ADDED) mean?

 
Previous Next
RPC_S_PROFILE_NOT_ADDED RPC_S_PRF_ELT_NOT_REMOVED

RPC_S_PRF_ELT_NOT_ADDED

An RPC profile element could not be added.

RPC_S_PRF_ELT_NOT_ADDED is RPC status 1926 (0x786). An RPC profile contains elements that map an interface identifier and version policy to a member entry, priority, and optional annotation. This result means the profile entry may exist, but the particular element requested by RpcNsProfileEltAdd was not committed.

Why one profile element is rejected

  • the profile name resolves to an entry of the wrong type or to a namespace path owned by another service
  • the caller cannot modify the profile or one of its parent name-service entries
  • the interface UUID, version option, member entry, priority, or name syntax is invalid for the provider
  • the same logical element already exists and provisioning code does not reconcile existing state
  • the name-service provider becomes unavailable after the profile was opened but before the element is stored

Evidence to preserve

Log the profile and member entry names, name syntaxes, interface UUID and version, version option, priority, annotation length, caller identity, namespace provider, and the exact RPC status. Enumerate the profile after failure because an interrupted or retried deployment may have left a compatible element already present. Avoid logging topology annotations when they contain sensitive host or tenant information.

Diagnostic sequence

Confirm that the target entry is an RPC profile, then enumerate its elements with the profile inquiry functions. Compare UUID, version policy, member name, and priority rather than comparing only the annotation. Validate both entry-name syntaxes and test whether the caller can modify a temporary profile in the same namespace.

Separate a naming or authorization failure from an interface-registration problem. The profile can reference a member that is not currently reachable; therefore endpoint availability should be tested after, not substituted for, verification of the name-service write.

Recovery and safe retry

Correct the entry type, syntax, permissions, or element fields, then retry idempotently. If the intended element already exists, accept the matching state instead of repeatedly adding duplicates. Do not delete an unfamiliar profile to make installation succeed until its owner and consumers are identified.

Deployment code should record ownership outside the opaque profile annotation and roll back only elements it created. A service should not announce discovery readiness until the element can be enumerated back from the profile.

Difference from profile creation failure

RPC_S_PROFILE_NOT_ADDED concerns creating or establishing the profile entry itself. Status 1926 is narrower: the profile exists or is addressable, but one member/interface element was not added.

Example

An installer creates /.:/acme/reporting as a profile, then tries to add a member using an unsupported name syntax. The add returns 1926 while the empty profile remains. Correcting the member syntax and reconciling the profile adds the intended element without recreating the profile.

References

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