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
Store

Alert Action Execute External Program PowerShell Script 64-bit v. 32-bit Module Cmdlets

I need to use the PowerShell module SqlServer (Invoke-Sqlcmd). I believe this is a 64 bit module. The script I wrote to use the cmdlet works great in a 64-bit PS session as the service account user. The only way I know to tell SolarWinds to use the 64-bit PowerShell session is how I call it when defining the alert action.

32-bit PowerShell: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
64-bit PowerShell: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

What I'm finding is that the SolarWinds Alerting Service V2 doesn't like the 64-bit version. Do I have this right and if so, how do I make alert actions like this 64-bit compatible?

Find more posts tagged with

Comments

tony.johnson

interesting, do you have an example script I could use as a reference?

jameslindsay

Previous to this I tried everything under the Sun to simply make a System.Data.SqlClient.SqlConnection but, it seemed that was never going to work with a Domain account.

I decided to use the SQLServer Module, specifically Invoke-Sqlcmd. I found that no matter what I did, when the line was called a 32bit PS session was invoked and this created problems where the module couldn't load or locate DLLs it needed.

Could not load file or assembly 'Microsoft.SqlServer.BatchParser, Version=15.100.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

I confirmed there were no pathing issues and that the module was available, etc. by logging output from the script.

"***BEGIN for " + $sysName| Out-File $logName -Append
[datetime]$theStart = Get-Date -Format "yyyy/MM/dd HH:mm:ss"
"Start Time: " + $theStart| Out-File $logName -Append
Write-Host "***BEGIN Start Time: " $theStart

"Is 64bit Session: "| Out-File $logName -Append
[Environment]::Is64BitProcess| Out-File $logName -Append

$env:PSModulePath = $env:PSModulePath + "$([System.IO.Path]::PathSeparator)C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules\sqlserver"

"PSModulePath: "| Out-File $logName -Append
$env:PSModulePath -split ';'| Out-File $logName -Append

"What Module does the Invoke-Sqlcmd come from?"| Out-File $logName -Append
Get-Command -Name Invoke-Sqlcmd | Select-Object -ExpandProperty Module| Out-File $logName -Append

$PSVersionTable| Out-File $logName -Append

"What cmdlets does the module support?"| Out-File $logName -Append
Get-Command -Module SqlServer| Out-File $logName -Append

#Get-Module -ListAvailable | Select-Object -Property Name, Path| Out-File $logName -Append

Import-Module SqlServer

Invoke-Sqlcmd -InputFile $sqlCmd -ConnectionString "Server=$sqlServer;Database=$theDb;Integrated Security=True;"| Out-File $logName -Append

In every case no matter what I tried on the alert action line, the session came back 32bit. With the help of support, I even tried a .cmd wrapper to spawn a 64bit PS session but no luck.

In the end, I ended up with C#.Net exe to launch a 64bit PS session with a script as an input paramter.

tony.johnson

Thanks,

I gave this a quick workup in my lab and what I found so far is that this seems to work in the following scenario.

Alert created using 'execute an external program' trigger action.
Path to program set C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -Command C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Invoke-SQL.ps1

Passed script with a single Invoke-Sqlcmd

Invoke-Sqlcmd -Query "SELECT Top 1 * from [NodesData]" -ServerInstance $SQLServer -Username $UserName -Password $PassWord | Out-File  -FilePath "C:\Windows\SysWOW64\WindowsPowerShell\v1.0\SQLOUT.txt"

The only variable that comes to mind is the domain auth, which if I understand was only a challenge for you when using the System.Data.SqlClient namespace.

Is there anything I may have overlooked which could be of relevance?

jameslindsay

What output did you get from this in the spawned alert action session?

[Environment]::Is64BitProcess

also I was using SQL Integrated Security in my connection string.
-ConnectionString "Server=$sqlServer;Database=$theDb;Integrated Security=True;"

That said, no matter if I used
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
or
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

Is64bit came back false

Quick Links

Cisco ASR Devices
Cisco ASR Devices.pollerCisco ASR Devices
Basic SWQL Syntax
SWQL is built on the framework of SQL and as such supports most of the standard clauses as part of a query. A very simple example query is: SELECT Caption, IPAddress, Vendor, ResponseTime FROM Orion.Nodes Dissecting this query is relatively straightforward: show some fields (Caption, IP address, Vendor, and Response Time)…
Cisco ASA SSL Tunnels
Active SSL Tunnels-ASA.UnDPThis poller *should* display the number of Active SSL VPN (Anyconnect) Tunnels currently connected to your box. However, I tried it with my 5520 running 8.0.4 and for some reason I get a OID Not Supported. Here's my post in the forum: *EDIT* This is confirmed working with at least Interm release…
HP ProCurve Switches Hardening check
HP ProCurve Switches Hardening check.xmlGeneral hardening for HP switches