| Previous | Next |
| RPC_S_NOT_ALL_OBJS_EXPORTED | RPC_S_PROFILE_NOT_ADDED |
RPC_S_INTERFACE_NOT_EXPORTED
The RPC interface was not published in the namespace.
RPC_S_INTERFACE_NOT_EXPORTED is Win32 status 1924 (0x784). Exporting an RPC interface makes its server bindings discoverable through a name-service entry. This status means the interface portion of that publication did not become available at the requested entry, so clients relying on namespace lookup cannot discover it there even if the server is locally listening.
Reasons an interface export fails
- the interface specification or version does not match the server’s registered interface
- the binding vector is empty, invalid, or was obtained before protocol sequences began listening
- the target entry has an incompatible type or belongs to another deployment
- name-service permissions or provider availability prevent updating the entry
- startup cleanup and publication race, leaving the entry in an unexpected state
Export evidence to preserve
Record the interface UUID and version, entry name and syntax, binding vector protocols and endpoints, object-vector presence, server process and generation, name-service provider, caller identity, preceding RPC startup results, and post-call namespace inventory. Restrict endpoint and UUID details to administrative diagnostics. A service “running” state is insufficient evidence that its interface was exported.
How to isolate the export stage
Confirm that RpcServerRegisterIf*, protocol-sequence setup, and RpcServerInqBindings succeeded before the name-service call. Export the same interface to a controlled test entry and inspect the resulting bindings. Verify that the interface specification passed to export is the one actually registered by the server.
Check namespace entry semantics and permissions separately from endpoint mapper registration. A server can register local endpoints successfully yet fail name-service publication. Review concurrent deployment instances and stale cleanup that may be modifying the same entry.
Recovery and startup behavior
Correct the interface or binding data, use an entry owned by the service, restore namespace access, and export again after successful listening setup. Remove partial publication only through matching RPC name-service APIs and only for the service’s own generation.
Services that require name-service discovery should not report fully ready until export is verified. Log endpoint registration and namespace export as separate stages, and implement bounded recovery without exposing a partially initialized service indefinitely.
Difference from incomplete object export
RPC_S_NOT_ALL_OBJS_EXPORTED describes a partial object-UUID vector while the interface may still be published. Error 1924 means the interface discovery entry itself was not exported as requested.
Example
An RPC service registers its interface but calls RpcNsBindingExport with a stale interface specification from the previous version. Local clients with hard-coded bindings work, while namespace clients fail and startup records 1924. Exporting the registered version fixes discovery.
References
- Microsoft: System Error Codes (1700–3999)
- Microsoft: RPC return values
- Microsoft: RpcNsBindingExport
- Microsoft: Registering RPC interfaces
Looking for a different code? Search another status or error code.