Powershell SAM monitor issue

Hello,

I am trying to setup a Powershell SAM monitor and I get the below error - The operation failed because of an HTTP error. The HTTP error (12152) is: The server returned an invalid or unrecognized response .

The 5985 port is open.

WInrm service is configured.

Can someone suggest on how to fix the issue ???

Find more posts tagged with

Accepted answers

All comments

Seashore

Are the PS scripts ran locally or remote? What is the "execution mode"? Depending on that it behaves differently.

ajaz.ahamed

Hello, the PS script is set to run on remote machine - the execution mode is set to Remote

Seashore

On the application monitor configuration page, you can set debug logging to "on":

Then you get a log file on the orion polling server at "C:\ProgramData\SolarWinds\Logs\APM\ApplicationLogs", one folder per application ID with debug enabled.

Some googling shows several that has issues with antivirus program, giving that error message.

You can also test with the following power shell command from the Orion server:
Test-wsman -computername IP/servername -autentication default

adam.beedell

Recommend making sure it works as a script first (ie remote to a good test server, get the powershell working)
then getting it running in a scriptblock from the solarwinds server

if it runs in a scriptblock you're probably good, if it doesnt you can probably troubleshoot the errors easier. Worst-case you can also just set to local here and it should work then.

ajaz.ahamed

Thank you , I will check that

ajaz.ahamed

Yes, Adam - I have tested the PS script, the PS script is giving the right results on the remote machine locally and on the test server

SteveK

I've had issues in the past with PowerShell script execution in general. Do you have other Powershell based scripts working remotely, or is this the first one?

Whenever I start with a new powershell script I normally add the component. and set my script as:
Write-Host "Message: $($ENV:ComputerName)"

and run just that to see if I see the correct test node, polling engine, or if it even makes it through.

ajaz.ahamed

Hi, thank you for the test step, We found the issue with a firewall exception and the monitoring is now fine