Remote Powershell Monitor fails in SAM with: The WSMan service could not launch a host process to process the given request

10/11/2018 8:55 PM

10/11/2018 8:55 PM

When attempting to run a Remote Execution Powershell Script with the "Windows Powershell Monitor" in SAM, the following error appears:

PowerShell script error. Connection to remote server 192.168.xxx.xxx failed 
with the following error message: The WSMan service could not launch a host process to 
process the given request. Make sure the WSMan provider host server and proxy are 
properly registered. 

Server Application Monitor

As indicated in the error message, make sure the WSMan provider host server and proxy are 
properly registered. 

If the host server and proxy are OK, this issue may be caused by a corrupted User Profile on the target machine being monitored.

First, open the application monitor in SAM to determine which credential on the target system is causing this issue, as displayed on the Edit Application page:

1. In the Orion Web Console, click Settings > All Settings > SAM Settings.
2. Click Component Monitor Library.
3. Scroll down to "Windows PowerShell Monitor" and then expand the tree to drill down and select the application monitor related to the issue.
4. Under Component Monitors, examine the Credential for Monitoring value.

Now that you know the credential, switch to the target system and recreate the User Profile linked to the credential.

1. On the target system, open the Control Panel.
2. Double-click "System".
3. Click "Advanced System Settings".
4. On the "Advanced" tab, click the "Settings" button in the "User Profiles" section.
5. Select the Profile for the User Account in question and click "Delete".
6. Log out of this system and log back in as that account to recreate the profile.

See also:
Use PowerShell in SAM
Windows PowerShell Monitor