| Previous | Next |
| RPC_S_OBJECT_NOT_FOUND | RPC_S_TYPE_ALREADY_REGISTERED |
RPC_S_ALREADY_REGISTERED
The duplicate is an object registration, not an endpoint collision
RPC_S_ALREADY_REGISTERED is returned when an object UUID is already registered in the RPC runtime's object/type mapping. In the standard object model, a non-nil object UUID can be associated with a type UUID so incoming calls are dispatched to the manager implementation registered for that type.
This is different from RPC_S_DUPLICATE_ENDPOINT. The endpoint map deals with interface and network-address reachability; object registration deals with selecting an implementation for an object UUID.
Typical causes
- Initialization code runs twice and calls
RpcObjectSetTypeagain for the same object. - Two modules believe they own the same object UUID but assign different type UUIDs.
- Reload or failover logic recreates object registration without first resetting the old association.
Inventory the object UUID, requested type UUID, and module that performs the registration. If the existing mapping is intentional, treat the second registration as an initialization bug. To remove an association, use the documented reset behavior rather than registering a competing type.
References
Looking for a different code? Search another status or error code.
