<div class="content" name="GetLogFilePath" uuid="966f6bad-300a-4696-9781-bb3acaaac887"><p>The <b>GetLogFilePath</b> method<a id="Appendix_A_Target_55"></a><a aria-label="Product behavior note 55" href="6ea29e14-9c33-4927-90a8-258fd1d6d042#Appendix_A_55" data-linktype="relative-path">&lt;55&gt;</a> returns the server-relative
path of a log file that was generated by a preceding call to the <b>GenerateLogEx</b>
method (section <span><a href="bf3e46ea-c867-4d91-94e7-542015c9a9b2" data-linktype="relative-path">3.19.4.1</a></span>).  </p><dl>
<dd>
<div><pre> HRESULT GetLogFilePath {
   [ in ] ULONG Index,
   [ out ] BSTR* LogFilePath
 };
</pre></div>
</dd></dl><p><b>Index:</b>
The index of the log file generated by a preceding call to <b>GenerateLogEx </b>(section
3.19.4.1).</p><p><b>LogFilePath:</b>
Upon successful completion of this method, the server MUST set this parameter
to the location where the server has exposed a file containing the requested
diagnostic log data. The path is relative to the machine and starts with a <span><a href="b30bcd1c-8ff6-46d2-a27e-61bd85ace9f4#gt_a49a79ea-dac7-4016-9a84-cf87161db7e3" data-linktype="relative-path">share</a></span>
name. The format is &#34;&lt;share&gt;\&lt;filename&gt;&#34; where
&lt;share&gt; is a share name, and &lt;filename&gt; is the name of the file or <span><a href="b30bcd1c-8ff6-46d2-a27e-61bd85ace9f4#gt_4712ded2-d927-4930-9450-29499f98cef4" data-linktype="relative-path">device</a></span>.
The <i>LogFilePath</i> parameter MUST form a valid <span><a href="b30bcd1c-8ff6-46d2-a27e-61bd85ace9f4#gt_d5a07545-a023-45ad-89a6-0b5c944bcfd4" data-linktype="relative-path">UncPath</a></span> if
\\servername&gt;\ is prepended to its contents. On unsuccessful completion of
this method, the client MUST ignore this value.</p><p><b>Return Values:</b>
A signed 32-bit value that indicates return status. If the method returns a
negative value, it has failed. Zero or positive values indicate success, with
the lower 16 bits in positive nonzero values containing warnings or flags
defined in the method implementation. For more information about Win32 error
codes and HRESULT values, see <span><a href="../ms-erref/1bc92ddf-b79e-413c-bbaa-99a5281a6c90" data-linktype="relative-path">[MS-ERREF]</a></span>
section <span><a href="../ms-erref/18d8fbe8-a967-4f1c-ae50-99ca8e491d2d" data-linktype="relative-path">2.2</a></span>
and <span><a href="../ms-erref/0642cb2f-2075-4469-918c-4441e69c548a" data-linktype="relative-path">2.1</a></span>.</p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Return value/code</p>
   </th>
   <th>
   <p>Description</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>0x00000000 S_OK</td>
  <td>The call was successful.</td>
 </tr><tr>
  <td>0x8007000E E_OUTOFMEMORY</td>
  <td>Index is out of range for the list of available logs.</td>
 </tr></tbody></table>
</dd>
<dd>
<p>For any other condition, this
method MUST return a value that is not one of the values listed in the
preceding table. The client MUST behave in an identical manner for all return
values not listed in the preceding table.</p>
</dd></dl><p>Exceptions Thrown: No exceptions are thrown beyond those
thrown by the underlying RPC protocol <span><a href="../ms-rpce/290c38b1-92fe-4229-91e6-4fc376610c15" data-linktype="relative-path">[MS-RPCE]</a></span>
</p><p>The opnum field value for this method is 11.</p><p>When processing this call, the server MUST do the following:</p><ul><li><p><span><span> 
</span></span>If <b>Index</b> is greater than the count of logs generated by a
preceding call to <b>GenerateLogEx</b>, return <b>E_OUTOFMEMORY.</b></p>
</li><li><p><span><span> 
</span></span>Otherwise, generate the server-relative path to the file
referenced by the <b>Index</b> parameter.</p>
</li></ul><p>Return the following information to the client:</p><ul><li><p><span><span> 
</span></span>The server-relative path to the file.</p>
</li></ul></div>