Skip to content

Latest commit

 

History

History
85 lines (65 loc) · 3.2 KB

nf-rpcasync-rpcbindingunbind.md

File metadata and controls

85 lines (65 loc) · 3.2 KB
UID title description helpviewer_keywords old-location tech.root ms.assetid ms.date ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.ddi-compliance req.unicode-ansi req.idl req.max-support req.namespace req.assembly req.type-library req.lib req.dll req.irql targetos req.typenames req.redist ms.custom f1_keywords dev_langs topic_type api_type api_location api_name
NF:rpcasync.RpcBindingUnbind
RpcBindingUnbind function (rpcasync.h)
Unbinds a binding handle previously bound by RpcBindingBind.
RpcBindingUnbind
RpcBindingUnbind function [RPC]
rpc.rpcbindingunbind
rpcasync/RpcBindingUnbind
rpc\rpcbindingunbind.htm
Rpc
a9e30764-22ea-4dbf-9311-f37bd55ed2c4
12/05/2018
RpcBindingUnbind, RpcBindingUnbind function [RPC], rpc.rpcbindingunbind, rpcasync/RpcBindingUnbind
rpcasync.h
Rpc.h
Windows
Windows Vista, Windows XP with SP2 [desktop apps \| UWP apps]
Windows Server 2008, Windows Server 2003 with SP1 [desktop apps \| UWP apps]
Rpcrt4.lib
Rpcrt4.dll
Windows
19H1
RpcBindingUnbind
rpcasync/RpcBindingUnbind
c++
APIRef
kbSyntax
DllExport
Rpcrt4.dll
RpcBindingUnbind

RpcBindingUnbind function

-description

The RpcBindingUnbind function unbinds a binding handle previously bound by RpcBindingBind.

-parameters

-param Binding [in]

RPC_BINDING_HANDLE structure that contains the binding handle to unbind from the RPC server.

-returns

This function returns RPC_S_OK on success; otherwise, an RPC_S_* error code is returned.

Note  For a list of valid error codes, see RPC Return Values.
 

-remarks

RpcBindingUnbind unbinds a previously bound binding handle from an RPC server. An unbound handle can be modified with calls like RpcBindingSetOption and RpcBindingSetAuthInfoEx. A binding handle in the unbound state can be bound again and re-used to make calls.

The results of an unbind operation are undefined if it is called on a binding handle that currently has RPC calls in progress at the time of unbinding. It is the responsibility of the caller to ensure that no calls are in progress at the time an unbind operation is attempted.

Note that calling RpcBindingUnbind does not necessarily disconnect the client from the server. It will invalidate any cached information used by the binding handle, but actually disconnection is not ensured. To ensure disconnection, free the binding handle with RpcBindingFree.

Windows Vista:  Currently, this function supports only the ncalrpc protocol sequence.

-see-also

RpcBindingBind

RpcBindingFree