The RpcEpResolveBinding function resolves a partially-bound server binding handle into a fully-bound server binding handle.
RPC_STATUS RpcEpResolveBinding( RPC_BINDING_HANDLE Binding, RPC_IF_HANDLE IfSpec );
Partially-bound server binding handle to resolve to a fully-bound server binding handle.
Stub-generated structure specifying the interface of interest.
||The call succeeded.|
||The binding handle was invalid.|
||This was the wrong kind of binding for the operation.|
An application calls the RpcEpResolveBinding function to resolve a partially-bound server binding handle into a fully-bound binding handle.
Resolving binding handles requires an interface UUID and an object UUID (which may be nil). The RPC run-time library asks the endpoint-mapping service on the host specified by the Binding parameter to look up an endpoint for a compatible server instance. To find the endpoint, the endpoint-mapping service looks in the endpoint-map database for the interface UUID in the IfSpec parameter and the object UUID in the Binding parameter, if any.
How the resolve-binding operation functions depends on whether the specified binding handle is partially- or fully-bound. When the client specifies a partially-bound handle, the resolve-binding operation has the following possible outcomes:
- If no compatible server instances are registered in the endpoint-map database, the resolve-binding operation returns the EPT_S_NOT_REGISTERED status code.
- If a compatible server instance is registered in the endpoint-map database, the resolve-binding operation returns a fully-bound binding and the RPC_S_OK status code.
In neither the partially- nor the fully-bound binding case does the resolve-binding operation contact a compatible server instance.
|Minimum supported client||Windows 2000 Professional [desktop apps | UWP apps]|
|Minimum supported server||Windows 2000 Server [desktop apps | UWP apps]|
|Header||rpcdce.h (include Rpc.h)|