| Previous | Next |
| RPC_S_NO_MORE_MEMBERS | RPC_S_INTERFACE_NOT_FOUND |
RPC_S_NOT_ALL_OBJS_UNEXPORTED
Namespace cleanup can be partially successful
RPC_S_NOT_ALL_OBJS_UNEXPORTED belongs to RPC name-service cleanup. Servers can export object UUIDs together with binding information to a namespace entry. When the application later unexports objects, the runtime can report that not every requested object UUID was removed.
This is materially different from a complete namespace-service outage. Some requested changes may already have been applied, so blindly retrying the full original request can hide which object mappings were actually present.
What to inspect
- Record the namespace entry and complete object UUID vector used for unexport.
- Compare it with the object UUIDs originally exported by the same server version or instance.
- Handle partial cleanup explicitly during rollback and service restart; do not assume all-or-nothing behavior.
- Keep endpoint-map unregistration separate from namespace unexport. They are different registries with different APIs and lifetimes.
If the application dynamically changes its object set, persist or reconstruct the exact exported UUID list. That makes unexport deterministic and avoids stale namespace objects.
References
Looking for a different code? Search another status or error code.