Skip to content

Latest commit

 

History

History
111 lines (95 loc) · 3.05 KB

nc-resapi-prelease_routine.md

File metadata and controls

111 lines (95 loc) · 3.05 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
NC:resapi.PRELEASE_ROUTINE
PRELEASE_ROUTINE (resapi.h)
Releases the quorum resource from arbitration.
PRELEASE_ROUTINE
PRELEASE_ROUTINE callback
Release
Release callback function [Failover Cluster]
_wolf_release
mscs.release
resapi/PRELEASE_ROUTINE
resapi/Release
mscs\release.htm
MsCS
9e8e4557-b223-4f8f-9393-67f589181754
12/05/2018
PRELEASE_ROUTINE, PRELEASE_ROUTINE callback, Release, Release callback function [Failover Cluster], _wolf_release, mscs.release, resapi/PRELEASE_ROUTINE, resapi/Release
resapi.h
Windows
None supported
Windows Server 2008 Enterprise, Windows Server 2008 Datacenter
Windows
19H1
PRELEASE_ROUTINE
resapi/PRELEASE_ROUTINE
c++
APIRef
kbSyntax
UserDefined
ResApi.h
Release

PRELEASE_ROUTINE callback function

-description

Releases the quorum resource from arbitration. The PCLOSE_ROUTINE type defines a pointer to this function.

-parameters

-param Resource [in]

Resource identifier for the quorum resource to be released.

-returns

Return code/value Description
ERROR_SUCCESS
0
The quorum resource was successfully released and is no longer being defended.
Error code
The quorum resource was not successfully released.

-remarks

The Release entry-point function is implemented for quorum resources only. A quorum resource might have to be released when the Cluster service is shut down or when the quorum resource has to be physically moved to a different node in the cluster.

Note  All disk resources must explicitly call their own Release in their implementation of the Offline callback, since one is not made by the Cluster service Resource Monitor.
 

-see-also

Resource DLL Entry-Point Functions