What does Windows error code 1925 (RPC_S_PROFILE_NOT_ADDED) mean?

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: The RPC name service could not create or add the specified profile entry.

Previous	Next
RPC_S_INTERFACE_NOT_EXPORTED	RPC_S_PRF_ELT_NOT_ADDED

RPC_S_PROFILE_NOT_ADDED

The requested RPC profile entry was not added.

RPC_S_PROFILE_NOT_ADDED is Win32 status 1925 (0x785). RPC profiles organize interface references with member entries, versions, priorities, and annotations so clients can import a suitable binding. This status concerns creating or establishing the profile entry itself, before diagnosing an individual profile element that could not be inserted.

Why profile creation cannot complete

the profile name already belongs to an incompatible namespace entry type
the caller lacks permission to create or modify the selected name-service path
the namespace provider is unavailable or cannot persist the new entry
the entry name or syntax resolves to an unintended location
concurrent provisioning and rollback operations race over profile ownership

Profile-provisioning evidence

Capture the profile entry name and syntax, intended interface UUID and version policy, member entry, priority, annotation, caller identity, namespace provider, existing entry type, and the exact profile API sequence. Record whether the profile entry existed before the call. Internal annotations and member paths can disclose topology, so apply administrative access controls to the log.

Diagnostic sequence

Resolve and inspect the target entry before adding elements. Verify that it is absent or already a compatible RPC profile, and confirm the caller can create entries in the parent namespace. Test creation under a dedicated temporary path to separate provider and permission failures from a naming collision.

Review concurrent installers, service instances, and cleanup jobs. If the profile exists, enumerate it instead of assuming the add failed before any state was written. Distinguish 1925 from RPC_S_PRF_ELT_NOT_ADDED, which points to one element inside an established profile.

Recovery and profile ownership

Choose or create a profile entry owned by the application, correct namespace permissions or provider health, and then add profile elements through the documented API. Do not delete an incompatible existing entry until its owner and dependencies are known.

Provisioning should be idempotent: verify the profile role, reconcile intended elements, and tag deployment ownership outside opaque RPC state where possible. Clients should have a controlled fallback when a profile is temporarily unavailable rather than importing arbitrary bindings.

Difference from a profile-element failure

RPC_S_PROFILE_NOT_ADDED concerns establishing the profile entry. RPC_S_PRF_ELT_NOT_ADDED means the profile exists but a particular member/interface/version element could not be added.

Example

Two services use the same default RPC entry; the first created it as a group. The second tries to provision a profile and receives 1925. Assigning a service-specific profile path avoids destroying the valid group and allows its profile elements to be added.

References

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