Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Powershell Monitor Output Issue

After a lot of research and looking around on here, I'm stumped with a Powershell montior I'm working on. The script is calling the API for GlobalScape's EFT server.

On one server this script works perfectly, returning the correct statistic value and displaying it in Orion. (IPs, etc.obscured)

$srvObj = New-Object -ComObject "SFTPCOMInterface.CIServer"

$srvObj.Connect("xxx.xxx.x.xx", "xxxx", "xxxx", "xxxxxx")

$count = $srvObj.ConnectedUsersNumber

write-host "Message:"

write-host "Statistic: $count"

Another server, (using the same script, just different params on the "Connect" object), fails with this error:

Testing the script output returns the following:

Any ideas on what is wrong here? Thanks!

Find more posts tagged with

Accepted answers

All comments

cdowning

I don't know anything about the COM object you're using, but from the error details and the "NaN", (Not A Number), in the script test, I'd bet that $count is null when you send it to output. Is it possible that $count = $srvObj.ConnectedUsersNumber isn't returning anything? What does it return if there are 0 users connected? If you expect that to be a number, (i.e. 0), then verify your connection parameters and that your connect statement is working.

t0ta11ed74

It returns zero, as shown in the first example for server1 that's working.

If the script is run locally (or remotely via invoke-command) on the non-working server2, it returns zero and works fine as well. The only difference between the two scripts is the connection parameters. So you can see why I'm puzzled 0_o

cdowning

That is a strange one... And sorry I missed the output in your original post.

I'm sort of grasping for straws here, so don't be offended by stupid simple suggestions:

Could it be a permissions issue with the user Orion is running the script as? Maybe some permission is set correctly on server1 and not on server2?
Have you tried starting PowerShell on the Orion server using the credentials that Orion is running the script as and then executing the script against the remote server?
Have you tried starting PowerShell on server2 using the credentials that Orion is running the script as and then executing the script?
Have you verified on your application template that "Execution Mode" is "Remote Host"?
If it is, have you tried changing that to "Local Host" and modifying the script to use Invoke-Command?

tomasv

Does polling run via agent or agentless?

t0ta11ed74

Ok, answering in order here...appreciate the help.

1. Orion account is a Domain Admin. I've verified both servers see it as one.

2. Something interesting happened here. I ran the script from the Orion server as the Orion account.

First, some background. The API expects this to be done via a x86 Powershell call, so the polling platform was set to x86. This wasn't an issue, BUT, when I run this code in the x86 instance of Powershell on Orion server as Orion remotely against server 2 via invoke-command, I get:

Retrieving the COM class factory for component with CLSID {A59E7747-3284-435B-8947-4E004361A6AC} failed due to the following error: 80040154 Class not registered (Exception from HRESULT:

0x80040154 (REGDB_E_CLASSNOTREG)).

This is expected when the call is made in x64, but I'm running x86 Powershell.

Now, if I append this to invoke-command, I get the correct results. Seems Powershell on Server2 is confused about which this should execute under?

Invoke-Command -computer xxxx {

$srvObj = New-Object -ComObject "SFTPCOMInterface.CIServer"

$srvObj.Connect("xx.xx.x.xxx", "65500", "Admin", "xxxxx")

$count = $srvObj.ConnectedUsersNumber

write-host "Message: $count"

write-host "Statistic: $count"

} -ConfigurationName Microsoft.Powershell32

Thinking this was the problem, I set the monitor to local host and ran the above code but that results in the same "NaN" response. Conversely, trying the same thing in x64 produces the same results.

3. Running the code locally on server2 has always worked. It works when run under the Orion account on the server locally too.

4 & 5. I've tried both.

Polling is running agentless.

tomasv

I have such experience with running powershell script remotely, that opened remote session follow native bitness of the remote operating system.

Try to create simple check in remote session:

[IntPtr]::Size

When it returns 4 then shell runs 32bit, when returns 8 then 64bit.

And it make sense, these machines can be 32bit or 64bit operating systems - you never know, what could be the calling and remote side system ....

I was trying once to achieve running 64bit powershell from 32bit session - may be you can use similar approach for the reverse direction ....

set-alias ps64 "$env:windir\sysnative\WindowsPowerShell\v1.0\powershell.exe" $fileName = [System.IO.Path]::GetTempFileName();Write-Host $fileName$fileName | ps64 {     $WorkerProcessIs32bit= ([IntPtr]::size -eq 4);     $ProcessorArchitecture = $ENV:PROCESSOR_ARCHITECTURE;     $objToReturn = 'something clever'     Export-Clixml -Path $input  -InputObject $objToReturn}$objToReturn = import-clixml $fileNameIf (Test-Path $fileName){  Remove-Item $fileName}$returnObj = New-Object PSObject -Property $objToReturn$returnObj

Hope it helps.

t0ta11ed74

Thanks, using that, I can see that no matter what the platform the polling job is set to run on it's executing in x64. I've tried forcing it to use x32 in the script, but no luck so far.

t0ta11ed74

This code appears to be working, getting numbers back now

Set-Alias Start-PowerShell32 "$env:windir\syswow64\WindowsPowerShell\v1.0\powershell.exe"

Start-PowerShell32 { $srvObj = New-Object -ComObject "SFTPCOMInterface.CIServer"

$srvObj.Connect("xx.xx.x.xxx", "65500", "xxxx", "xxxxx")

$results = $srvObj.ConnectedUsersNumber

write-host "Message: $results"

write-host "Statistic: $results"

}