<div class="content" name="RRouterInterfaceQueryUpdateResult" uuid="2bfb329e-5e3d-4dae-a8fa-e08133421934"><p>The <b>RRouterInterfaceQueryUpdateResult</b> method<a id="Appendix_A_Target_284"></a><a aria-label="Product behavior note 284" href="3bb906f0-b077-47ab-ad11-d8d807afde26#Appendix_A_284" data-linktype="relative-path">&lt;284&gt;</a> returns the result of the
last <a href="a18e8f3f-f4c4-4a97-8877-1b6c970d1cfb" data-linktype="relative-path"><b>RRouterInterfaceUpdateRoutes (section 3.1.4.24)</b></a>
request of the RRAS server for a specified transport to update its routes for
an interface. This method MUST be called only once after <b>RRouterInterfaceUpdateRoutes</b>.  
</p><dl>
<dd>
<div><pre> DWORD RRouterInterfaceQueryUpdateResult(
   [in] DIM_HANDLE hDimServer,
   [in] DWORD hInterface,
   [in] DWORD dwTransportId,
   [out] LPDWORD pUpdateResult
 );
</pre></div>
</dd></dl><p><b>hDimServer: </b>A handle to the RRASM server where
the call is to be executed, see section <a href="1f8cdbcc-9791-4a35-ad78-878b8d110e15" data-linktype="relative-path">3.1.3</a>.</p><p><b>hInterface: </b>The unique identifier of an
interface. This identifier can be obtained from <a href="72bead5c-821f-4e98-bacd-0de279552379" data-linktype="relative-path"><b>RRouterInterfaceCreate (section 3.1.4.13)</b></a>
or <a href="b4cc4f8f-e2bc-4e8f-a521-08a0558d3e44" data-linktype="relative-path"><b>RRouterInterfaceGetHandle (section 3.1.4.12)</b></a>.
Because the RRASM server does not maintain interface handles, the RRAS server
SHOULD check and ensure that this handle represents a valid interface handle.  
</p><p><b>dwTransportId: </b>Specifies the transport for
which routing information needs to be updated. This MUST be one of the
following values.<a id="Appendix_A_Target_285"></a><a aria-label="Product behavior note 285" href="3bb906f0-b077-47ab-ad11-d8d807afde26#Appendix_A_285" data-linktype="relative-path">&lt;285&gt;</a> Otherwise an error is
returned.</p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Value</p>
   </th>
   <th>
   <p>Meaning</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>PID_IPX 0x0000002B</td>
  <td>IPX protocol</td>
 </tr><tr>
  <td>PID_IP 0x00000021</td>
  <td>IPv4 protocol</td>
 </tr></tbody></table>
</dd></dl><p><b>pUpdateResult: </b>A pointer to a <b>DWORD</b>
variable. This variable receives the result of the last call to <b>RRouterInterfaceUpdateRoutes</b>;
see the return values of <b>RRouterInterfaceUpdateRoutes</b>. </p><p><b>Return Values: </b>A-32 bit, unsigned integer
value that indicates return status. A return value of ERROR_SUCCESS
(0x00000000) indicates that the operation was completed successfully;
otherwise, the return value contains an error code, as specified in <a href="../ms-erref/1bc92ddf-b79e-413c-bbaa-99a5281a6c90" data-linktype="relative-path">[MS-ERREF]</a>
or in section <a href="5c0c991a-0d3d-4fe5-9503-5128d0d49fe1" data-linktype="relative-path">2.2.4</a>.
All values that are not in the table that follows MUST be treated the same by
the RRASM client. </p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Return value/code</p>
   </th>
   <th>
   <p>Description</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>ERROR_SUCCESS 0x00000000</td>
  <td>The call was successful.</td>
 </tr><tr>
  <td>ERROR_ACCESS_DENIED 0x00000005</td>
  <td>The calling application does not have sufficient privileges, as specified in section 2.1.1.1.</td>
 </tr></tbody></table>
</dd></dl><p>The opnum field value for this method is 24.</p><p>When processing this call, the RRASM server MUST do the
following.</p><ul><li><p><span><span> 
</span></span>Validate, as specified in section 2.1.1.1, whether this method
was called by a client that has access to the method. If the client does not
have access, then return error ERROR_ACCESS_DENIED (0x00000005).</p>
</li><li><p><span><span> 
</span></span>If <i>dwTransportId</i> is not specified in the <b>SupportedTransportsList</b>,
return an error other than those specified in the preceding table.</p>
</li><li><p><span><span> 
</span></span>Call the abstract interface <b>Invoke DIMSVC </b>method
specifying the operation and the parameters to enable RRAS server to perform the
required management task.</p>
</li><li><p><span><span> 
</span></span>If the RRAS server processes the request successfully, update the
<i>pUdateResult</i> with the information provided by RRAS server and return
ERROR_SUCCESS (0x00000000). Otherwise return the error status that the RRAS
server returns.</p>
</li></ul><p>No exceptions are thrown beyond those thrown by the
underlying RPC protocol <a href="../ms-rpce/290c38b1-92fe-4229-91e6-4fc376610c15" data-linktype="relative-path">[MS-RPCE]</a>.</p></div>