Applications Systems

Windows PowerShell monitor status is down due to "Access Denied" error message

With the PowerShell component monitor, the credential used for execution of the script is dependent upon the "Execution Mode" and the value in the "Run the script under specified account".

First published date

11/15/2018 1:59 AM

Last published date

2/11/2025 7:20 PM

Overview

When monitoring with the use of Windows PowerShell scripts in SAM, you may notice its status as down due to an Access Denied error message.

Additionally, you may find following error in the application monitor's debug logging:

ERROR SolarWinds.APM.Probes.PowerShellProbe - System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.

Product section

Server Application Monitor

Cause

The permissions of credentials used to run the PowerShell script based on execution mode is not sufficient
Other permission and authentication issues in PSRemoting(© 2019 Microsoft, available at https://docs.microsoft.com/, obtained
on October 10, 2019)

Resolution

If the component type is Windows PowerShell Monitor, the credential used is based on the setting of the Execution Mode and the "Run the script under specified account".

If "Execution Mode" is Remote Host, the credential used will be the one listed under "Credential for Monitoring".
If "Execution Mode" is Local Host and "Run the script under specified account" is false, the credential used will be SYSTEM.
If "Execution Mode" is Local Host and "Run the script under specified account" is true, the credential used will be the one listed under "Credential for Monitoring".

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.