# Profile Says ‘List Error’ on Share

- Link: https://www.agilicus.com/faq/profile-says-list-error-on-share/
- Published: 2025-01-23T19:51:23+00:00
- Author: Don Bowman

![Agilicus Profile 'List Error on Share' Troubleshooting: User profile in Agilicus
Access Management displaying a 'List Error' when attempting to share resources. 
Check user permissions, group memberships, and resource configurations to resolve
the sharing issue. For detailed steps, refer to the Agilicus FAQ.](https://www.agilicus.
com/www/7033d8d2-image.png)

An end user might see a ‘List Error’ on a share in Profile. This usually implies
that the associated connector cannot read the underlying directly. In turn, this
normally is a permissions problem. A common cause is a Windows system where the 
connector runs as LocalSystem, and, the LocalSystem account does not have permission
to the shared file (or it in turn is another inbound Share).

To make a network drive mount available to the LocalSystem account on Windows, you
need to modify the share permissions on the network folder to explicitly grant the“
LocalSystem” group full control access, allowing the system account to access the
mounted drive. 

Steps:

 1.  **Access the Shared Folder Properties:**
 2.   * Navigate to the shared folder on the network drive using File Explorer.
      * Right-click on the folder and select “Properties”.
 3.  **Open Sharing Tab:**
 4.   * In the Properties window, go to the “Sharing” tab.
 5.  **Manage Permissions:**
 6.   * Click “Advanced Sharing”.
      * Click “Permissions”.
 7.  **Add LocalSystem Group:**
 8.   * Click “Add”.
      * In the “Enter the object names to select” field, type “LocalSystem” and click“
        Check Names” to verify.
      * Click “OK”.
 9.  **Grant Full Control:**
 10.  * Select the “LocalSystem” group from the list.
      * Under “Allow” column, check the box next to “Full Control”. 

Important Considerations:

 * **Security Implications:**Granting full control to the LocalSystem account can
   be a security concern, so only do this if absolutely necessary and ensure the
   network share is properly secured otherwise.
 * **Alternative Methods:**Depending on your specific situation, you might be able
   to achieve the desired access by using a different system account with appropriate
   permissions instead of directly using “LocalSystem.” 
