<div class="content"><p>The GetFileScreenException method returns the <a href="809180e0-571e-40a0-8067-ffe89cbdcc40#gt_285a588e-ca67-4d67-90ec-c182c60c9d66" data-linktype="relative-path">file screen exception</a> from
the <b>List of Persisted File Screen Exceptions</b> (section <a href="6226bc6a-8346-416f-83f9-3c121bdd6e59" data-linktype="relative-path">3.2.1.3</a>) for the specified
path.</p><dl>
<dd>
<div><pre> [id(FSRM_DISPID_FILESCREEN_MANAGER | 0x05)] HRESULT GetFileScreenException(
   [in] BSTR path,
   [out, retval] IFsrmFileScreenException** fileScreenException
 );
</pre></div>
</dd></dl><p><b>path: </b>Contains the path of the file screen
exception to return. </p><p><b>fileScreenException: </b>Pointer to an <b>IFsrmFileScreenException</b>
interface pointer (section <a href="4885c84b-4016-4d2d-8166-c60a540ec473" data-linktype="relative-path">3.2.4.2.28</a>)
that upon completion contains a pointer to the file screen exception for the
specified path. The caller MUST release the file screen exception when it is
done with it.</p><p><b>Return Values: </b>The method MUST return zero on
success, or a nonzero error code on failure.</p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Return value/code</p>
   </th>
   <th>
   <p>Description</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>
  <p>0x80045301</p>
  <p>FSRM_E_NOT_FOUND</p>
  </td>
  <td>
  <p>A file screen exception has not been applied to the
  specified directory.</p>
  </td>
 </tr><tr>
  <td>
  <p>0x80045304</p>
  <p>FSRM_E_PATH_NOT_FOUND</p>
  </td>
  <td>
  <p>The file screen exception for the specified path could
  not be found.</p>
  </td>
 </tr><tr>
  <td>
  <p>0x80045306</p>
  <p>FSRM_E_INVALID_PATH</p>
  </td>
  <td>
  <p>The content of the <i>path</i> parameter exceeds the
  maximum length of 260 characters.</p>
  </td>
 </tr><tr>
  <td>
  <p>0x80070057</p>
  <p>E_INVALIDARG</p>
  </td>
  <td>
  <p>This code is returned for the following reasons:</p>
  <ul><li><p><span><span>  
  </span></span><span>The <i>path</i> parameter is
  NULL.</span></p>
  </li><li><p><span><span>  
  </span></span><span>The <i>fileScreenException</i>
  parameter is NULL.</span></p>
  </li></ul></td>
 </tr></tbody></table>
</dd></dl><p>Upon receiving this message, the server MUST validate
parameters:</p><ul><li><p><span><span> 
</span></span>Verify that <i>path</i> is not NULL.</p>
</li><li><p><span><span> 
</span></span>Verify that <i>fileScreenException</i> is not NULL.</p>
</li></ul><p>If any validation fails, the server MUST terminate
processing and return a nonzero error code.</p><p>Upon successful validation of parameters, the server MUST
perform the following actions or return a nonzero error code.</p><ul><li><p><span><span> 
</span></span>Create a new <a href="0902b6bb-43d6-4d38-bc17-a691e9245855" data-linktype="relative-path">Non-Persisted
File Screen Exception Instance (section 3.2.1.3.2.2)</a>.</p>
</li><li><p><span><span> 
</span></span>Populate its configuration data from the <a href="19db08c4-2033-47fc-b307-66b0488efcac" data-linktype="relative-path">Persisted File Screen
Exception (section 3.2.1.3.2.1)</a> in the <b>List of Persisted File
Screen Exceptions</b> with the specified path.</p>
</li><li><p><span><span> 
</span></span>Set <i>fileScreenException</i> to the <b>IFsrmFileScreenException</b>
interface pointer of the newly created Non-Persisted File Screen Exception
Instance.</p>
</li></ul><p>If a file screen exception does not exist for the specified
path, the server MUST return FSRM_E_NOT_FOUND.</p></div>