| Previous | Next |
| RPC_S_PRF_ELT_NOT_ADDED | RPC_S_GRP_ELT_NOT_ADDED |
RPC_S_PRF_ELT_NOT_REMOVED
The selected RPC profile element could not be removed.
RPC_S_PRF_ELT_NOT_REMOVED is RPC status 1927 (0x787). Profile removal identifies an element by profile entry, interface UUID and version, member entry, and name syntax. The status does not mean that the whole profile was deleted unsuccessfully; it says the requested element could not be removed from that profile.
Common removal failures
- the element identity used for cleanup does not exactly match the stored UUID, version, or member entry
- the profile or member name is resolved with a different syntax than the one used during provisioning
- permissions permit reading the profile but not changing it
- another deployment instance removes or rewrites the element concurrently
- the name-service provider is unavailable or the profile entry changed type during migration
Cleanup telemetry
Record the full element key used by RpcNsProfileEltRemove, the profile entry type, caller identity, deployment owner, provider, and whether inquiry found zero, one, or several candidate elements before removal. After an error, enumerate again before deciding that stale discovery data remains. Do not treat annotations as a stable primary key.
How to investigate
Enumerate the current profile and compare the exact interface version, member path, and syntax. A textual member that looks equivalent can resolve differently under another name syntax. If no matching element exists, determine whether cleanup is already complete and make that state successful for an idempotent uninstaller.
If the element is present, verify write permission and test removal with the same service identity that originally provisioned it. Check for active installers or failover controllers changing the profile. Preserve unrelated elements even when they point to the same server.
Corrective action
Retry with the exact stored element identity after repairing provider availability or permissions. When ownership is uncertain, remove only the element that can be tied to the retiring deployment; deleting the entire profile can break other interfaces.
Provisioning systems should persist the canonical profile/member names and interface version used at creation. Cleanup should be a reconciliation operation: missing element means complete, matching element means remove, conflicting element means stop for review.
Difference from deleting a profile
RpcNsProfileDelete removes an empty profile entry. Error 1927 is returned while removing a particular profile element and should lead to element-level enumeration rather than immediate profile deletion.
Example
A service upgrade changes its interface minor version but the uninstaller tries to remove the new version from a profile that still contains the old one. It receives 1927. Enumerating the profile reveals the stored version, allowing cleanup of only the obsolete element.
References
- Microsoft: System Error Codes (1700–3999)
- Microsoft: Win32 Error Codes in MS-ERREF
- Microsoft: RPC return values
- Microsoft: RpcNsProfileEltRemove
- Microsoft: RpcNsProfileEltInqBegin
Looking for a different code? Search another status or error code.