Search Engine: Elastic

Article ID: 115439, created on Jan 24, 2013, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 5.4
  • Operations Automation 5.0


A customer clicks the Open File Manager link in POA CCP in one of their IIS website properties. The Windows File Manager displays the error message on top of the CP screen:


Exception type: System.IO.DirectoryNotFoundException


The config folder is absent in the webspace where customer's website is hosted. The folder contains the filemanager.xml file with Windows File Manager settings for the customer's webspace. The problem also may be caused by improper permissions on the above mentioned file and/or folder.


Create the config/filemanager.xml file in the customer's webspace with the following content:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>

<owner name="AD_DOMAIN\fm00WS_ID">
    <account name="AD_DOMAIN\i00WS_ID">
    <account name="AD_DOMAIN\IIS_APP_POOL_IDENTITY">
    <account name="AD_DOMAIN\w00WS_ID">


Replace the following parameters in the example above with their actual values:

  • AD_DOMAIN - NETBIOS name of AD domain where IIS server is installed
  • WS_ID - ID of customer's webspace, it may be found in POA Customer CP in the list of websites
  • IIS_APP_POOL_IDENTITY - identity of IIS Application Pool which serves customer's webspace

Make sure that AD users fm00WS_ID and i00WS_ID have read access to the filemanager.xml file.

Use IIS Manager to find the value of the IIS_APP_POOL_IDENTITY parameter:

  • Run IIS Manager on the Windows Shared Hosting server where customer's webspace is created
  • Select the website with ID of customer's webspace in it
  • Click Basic Settings in Actions panel
  • Remember the value in the Application pool field


  • Switch to the list of Application Pools in IIS Manager
  • Find the IIS Application Pool from the previous step
  • The Identity fieLd contains the IIS_APP_POOL_IDENTITY:


caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07 c27596ac4fff6cb4c8ec8891dae57001 2554725ed606193dd9bbce21365bed4e ac82ce33439a9c1feec4ff4f2f638899

Email subscription for changes to this article
Save as PDF