Article ID: 124088, created on Dec 29, 2014, last review on Oct 24, 2015

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5

Symptoms

Permissions cannot be retrieved when going to POA Customer Control Panel > File manager and opening Get info for any file:

    Size :  9 KB
    Path :  HTTP/tests
    Modified :      Jul 25, 2013 07:17 PM
    Locked :        no
    Application Pool User : failed
    Webspace Group :        failed
    Anonymous Users :       failed

Browser console shows

{"error":"Failed to get permissions for <USERNAME>}

Where <USERNAME> contains the webspace ID

Cause

  1. 445 and 139 ports between Windows File Manager and Windows shared hosting nodes are filtered.

  2. File manager identity permission is not added to the permissions list of the webspace in question.

Resolution

The ports 445 and 139 are used by Windows File Manager during some operations with files permissions. These ports should be opened between Windows File Manager node and Windows shared hosting node. Otherwise, the user won't be able to edit permissions via Windows File Manager. This information is added to the Firewall Configuration Guide

In case the network is not limited, do the following:

  1. Access the File Manager host,
  2. Access IIS manager,
  3. Locate the Application pool identity of the application pool used by the webfilemanager site,
  4. Access the IIS server hosting the webspace,
  5. Verify that the WFM idenity has access to share (Right-click customer data > Properties > Sharing > Permissions...)
  6. Verify that the WFM identity has permissions to access individual files inside webspaces (these permissions are inherited from CustomerData)

Search Words

The Web server is configured to not list the contents of this directory.

file manager isn't responsive

Set file permissions in File Manager

Unable to set permissions for Anonymous Users in File Manager

failed to load file permissions

issues with permissions in the file manager

Web File Manager: {"error":"Failed to get permissions for <USER>}

file manager cannot check permisions

5b048d9bddf8048a00aba7e0bdadef37 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF