<div class="content"><p>The Path method is received by the server in an RPC_REQUEST
packet. In response, the server returns the subpath for the specific <a href="1939cfaf-92c9-40b5-9cca-791c531c01e6" data-linktype="relative-path">IAppHostConfigLocation</a>.</p><dl>
<dd>
<div><pre> [propget] HRESULT Path(
   [out, retval] BSTR* pbstrLocationPath
 );
</pre></div>
</dd></dl><p><b>pbstrLocationPath: </b>Contains the path for the
specific IAppHostConfigLocation. If the path is &#34;&#34; (an empty string),
it represents the same path as the containing <a href="3687acff-fb79-4e02-8349-6ca2f49df2a5" data-linktype="relative-path">IAppHostConfigFile</a>.</p><p><b>Return Values: </b>The server MUST return zero if
it successfully processes the message that is received from the client. In this
case, *pbstrLocationPath is not NULL. If processing fails, the server MUST
return a nonzero <a href="../ms-dtyp/a9046ed2-bfb2-4d56-a719-2824afce59ac" data-linktype="relative-path">HRESULT</a>
code as defined in <a href="../ms-erref/1bc92ddf-b79e-413c-bbaa-99a5281a6c90" data-linktype="relative-path">[MS-ERREF]</a>.
The following table describes the error conditions that MUST be handled and the
corresponding error codes. A server MAY return additional
implementation-specific error codes.</p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Return value/code</p>
   </th>
   <th>
   <p>Description</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>
  <p>0X00000000</p>
  <p>NO_ERROR</p>
  </td>
  <td>
  <p>The operation completed successfully.</p>
  </td>
 </tr><tr>
  <td>
  <p>0X80070057</p>
  <p>ERROR_INVALID_PARAMETER</p>
  </td>
  <td>
  <p>One or more parameters are incorrect or null.</p>
  </td>
 </tr><tr>
  <td>
  <p>0X00000008</p>
  <p>ERROR_NOT_ENOUGH_MEMORY</p>
  </td>
  <td>
  <p>Not enough memory is available to process this
  command.</p>
  </td>
 </tr></tbody></table>
</dd></dl><p> </p></div>