Applications Systems
Website configuration failed: Access to the path 'C:\Program Files (x86) \SolarWinds\Orion\AgentManagement\ SolarWinds.AgentManagement.Strings.dll' is denied (SAM)
This article describes how other users being logged into SolarWinds applications can result in locked files in the \AgentManagement folder that cause the following message to display in the SolarWinds Configuration Wizard: Access to the path 'C:\Program Files (x86)\SolarWinds\Orion\AgentManagement\SolarWinds.AgentManagement.Strings.dll' is denied.
First published date
Last published date
Overview
This article describes how other users being logged into SolarWinds applications can result in locked files in the \AgentManagement folder that cause the following message to display in the SolarWinds Configuration Wizard:
Access to the path 'C:\Program Files (x86)\SolarWinds\Orion\AgentManagement\ SolarWinds.AgentManagement.Strings.dll' is denied.

Product section
Cause
Resolution
There are several ways to resolve this error. First, try logging other users out of the system.
- Open Task Manager.
- Go to the Users tab.
- Log out any other users other than the account currently being used.
- Make sure that no other SolarWinds applications are running (for example, Report Writer, LogAdjuster, etc).
- Run the Configuration Wizard again.
Next, try stopping IIS Manager and running the Configuration Wizard again.
- Open Task Manager on the Orion Server.
- Locate the Agent and Deep Packet Inspection (DPI) services, and click End Task.
- Click Start > All Programs> SolarWinds Orion > Advanced Features > Orion Service Manager to open the Orion Service Manager.
- Stop the Agent service. (Do not disable the service; just stop it.)
- Navigate to the Server tab in IIS Manager and click Stop on the right side, under Manage Server.
- Run the Configuration Wizard again and click Yes when prompted to start IIS.
- If the issue persists, reboot the server and run the Configuration Wizard again.
The Access Denied message may also appear if SolarWinds SAM fails to shut down when the Configuration Wizard runs. In that case, stop all services and run the Configuration Wizard again.
If the procedure above does not help, that is because the file is locked preventing you to close it, you can reboot the server and after that run the configuration wizard.