<div class="content" name="FAX_GetPortEx" uuid="6e9e5f47-0016-43b9-9565-c6d135d2c061"><p>The <b>FAX_GetPortEx (Opnum 46)</b> method is called by the
client to retrieve port status information for a requested port at the server.
The device ID that is passed in SHOULD be obtained from <b>FAX_EnumPorts</b> (section
<a href="7143a58b-d7c5-4353-8857-39c7f708e778" data-linktype="relative-path">3.1.4.1.28</a>). This
method is an extended version of <b>FAX_GetPort</b> (section <a href="f7fa6fcf-ace1-47a2-b2a4-f5e408212d78" data-linktype="relative-path">3.1.4.1.51</a>).</p><p>The server MUST validate that the client&#39;s fax user account
has the access to obtain port status information. The server MUST validate that
the <i>dwDeviceId</i> parameter is for a valid device. The <i>Buffer</i>
parameter MUST NOT be <b>NULL</b>.</p><p>On success, the server MUST return information about the
specified fax port in <i>Buffer</i>.</p><p>The client SHOULD free the returned buffer.</p><dl>
<dd>
<div><pre> error_status_t FAX_GetPortEx(
   [in] handle_t hFaxHandle,
   [in] DWORD dwDeviceId,
   [out, size_is(, *BufferSize)] LPBYTE* Buffer,
   [out, ref] LPDWORD BufferSize
 );
</pre></div>
</dd></dl><p><b>hFaxHandle: </b>The RPC binding handle for this
call. The client SHOULD reuse the RPC binding handle used as an input <i>hBinding</i>
argument for the <b>FAX_ConnectFaxServer</b> (section <a href="5cbfd38d-7a14-4560-ad24-9ed78f19a3bb" data-linktype="relative-path">3.1.4.1.10</a>) or <b>FAX_ConnectionRefCount</b> (section
<a href="a92941ac-bd07-4a71-af85-c2c157c97cf9" data-linktype="relative-path">3.1.4.1.11</a>) method call
used to connect to the fax server.</p><p><b>dwDeviceId: </b>A <b>DWORD</b> (<a href="../ms-dtyp/cca27429-5689-4a16-b2b4-9325d93e4ba2" data-linktype="relative-path">[MS-DTYP]</a>
section <a href="../ms-dtyp/262627d8-3418-4627-9218-4ffe110850b2" data-linktype="relative-path">2.2.9</a>)
that indicates a unique identifier that distinguishes the device. The value of <i>dwDeviceId</i>
MUST be greater than zero.</p><p><b>Buffer: </b>A pointer to a buffer to hold a <b>_FAX_PORT_INFO_EXW</b> (section
<a href="7eced07f-d7be-4554-ada6-e1a1e56f1ae1" data-linktype="relative-path">2.2.46</a>) structure.</p><p><b>BufferSize: </b>A pointer to a <b>DWORD</b> in
which to return the size, in bytes, of the buffer.</p><p><b>Return Values: </b>This method MUST return
0x00000000 (ERROR_SUCCESS) for success; otherwise, it MUST return one of the
following error codes, one of the fax-specific errors that are defined in
section <a href="cbe6c4fb-4dda-4f6c-9701-0d490ba0d105" data-linktype="relative-path">2.2.52</a>, or one
of the other standard errors defined in <a href="../ms-erref/1bc92ddf-b79e-413c-bbaa-99a5281a6c90" data-linktype="relative-path">[MS-ERREF]</a>
section <a href="../ms-erref/18d8fbe8-a967-4f1c-ae50-99ca8e491d2d" data-linktype="relative-path">2.2</a>.</p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Return value/code</p>
   </th>
   <th>
   <p>Description</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>ERROR_ACCESS_DENIED 0x00000005</td>
  <td>Access is denied. The client&#39;s fax user account does not have the FAX_ACCESS_QUERY_CONFIG access rights required for this call.</td>
 </tr><tr>
  <td>ERROR_NOT_ENOUGH_MEMORY 0x00000008</td>
  <td>Not enough storage is available to process this command. The fax server cannot allocate sufficient memory to hold the FAX_PORT_INFO_EXW (section 2.2.45) structure to be returned to the client.</td>
 </tr><tr>
  <td>ERROR_BAD_UNIT 0x00000014</td>
  <td>The system cannot find the port for the receiving device by using the line identifier specified by the dwDeviceId argument.</td>
 </tr><tr>
  <td>ERROR_INVALID_PARAMETER 0x00000057</td>
  <td>The parameter is incorrect. The Buffer parameter is set to a NULL pointer value.&lt;127&gt;</td>
 </tr><tr>
  <td>ERROR_INTERNAL_ERROR 0x0000054F</td>
  <td>The fax server failed to custom marshal the FAX_PORT_INFO_EXW to be returned to the client.</td>
 </tr></tbody></table>
</dd></dl><p><b>Exceptions Thrown:</b> No exceptions are thrown
except those that are thrown by the underlying <a href="46aba9c4-ebb1-4b10-86ac-4bb3025657b9#gt_8a7f6700-8311-45bc-af10-82e10accd331" data-linktype="relative-path">RPC</a> protocol, <a href="../ms-rpce/290c38b1-92fe-4229-91e6-4fc376610c15" data-linktype="relative-path">[MS-RPCE]</a>.</p></div>