Security Compliance

Fileshare permission change fails in ARM

This article describes the solution to a problem with changing a permission for a fileshare in ARM.

First published date

1/12/2024 11:29 AM

Last published date

1/13/2026 5:22 PM

Overview

The following error may show up in the Permissions Tab in the ARM Rich client:
The access was denied for: (ARM related service account)

Product section

Access Rights Manager

Cause

The possible causes are listed below. The 8MAN OU is where the ARM groups are stored.

The 8MAN OU does not exist in AD and needs to be created. It cannot be created because of a lack of authorization in AD.
The 8MAN OU already exists but the related ARM service account configured cannot access it, or the OU structure has changed.
The related ARM service account configured does not have Full control rights on the fileserver path trying to change the permissions.

Resolution

Check if the related ARM service account configured has the right authorization in AD to perform the operation.
Update the new path for the 8MAN OU in the related AD Scan config in ARM Config---Scans as shown in the example below.
Check if the related ARM service account configured has the right authorization in the NTFS filesystem to perform the operation.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.