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

Max of 10 outputs in Script Monitor

I am getting the following error in Powershell SAM even though my output is limited to 10 items:

"A maximum of 10 output pairs can be monitored per script monitor. You currently have 10 pairs defined and are trying to generate more, bringing the total above the allowed 10. Processing will not start until existing statistics are disabled or removed."

The script I'm running does a final SELECT of 10 values and outputs them using "| select -First 10 |" in my script. Anyone have a work around for DYNAMIC output? I don't know what Solarwinds is using to determine the number of output values...

This script is working on several servers but some are failing with this error.

Find more posts tagged with

Accepted answers

All comments

300

Hi,

Did you find out a resolution for this error?
I am also using "Windows powerShell Monitor" and getting this error for a monitor that shows 10 output pairs.To make it even weird for me, I have another monitor in the same template where everything else is same except a minor change in SQL that selects 10 rows from SQL Server DB. So 2 monitors both selecting 10 rows and should show 10 output pairs.

One of them is working fine while second gives the same error you have mentioned.

I would greatly appreciate if anyone can provide some help.

FormerMember

Not yet. Of course this issue was overcome by other events so I haven't had time to get back to it. Sorry

jrouviere

It might help to see a sample of your script and a screenshot of the Get Script Output section you're seeing, but what comes to mind from my own adventures is that if you've previously returned statistics (1-10) and are now trying to return new statistics (say, 2 - 11) then it can give you issues with that as you would be trying to return 10 statistics, but it's tracking the first for 11 total if that makes sense.

This happens to me if I change the fields that I'm returning. Rather than being statistic.1, statistic.2, etc I name them so it's statistic.cpu, statistic.memory and if I add/remove new ones I will need to delete the old ones from the monitor itself or can run into this issue.

300

Thank you for your reply jrouviere

The script is:

$Error.Clear();

function Get-ODBC-Data{

param(

[string]$query=$("SELECT [name] as DBName, CONVERT(int, is_auto_update_stats_on) AS is_auto_update_stats_on FROM sys.databases"),

[string]$username='dbusername',

[string]$password='dbpassword'

)

$conn = New-Object System.Data.Odbc.OdbcConnection

$conn.ConnectionString = "DRIVER={SQL Server};Server=${IP};Initial Catalog=master;Uid=$username;Pwd=$password;"

$conn.open()

$cmd = New-object System.Data.Odbc.OdbcCommand($query,$conn)

$ds = New-Object system.Data.DataSet

(New-Object system.Data.odbc.odbcDataAdapter($cmd)).fill($ds) | out-null

$conn.close()

$ds.Tables[0]

$rowCount = 1;

foreach ($row in $ds.Tables[0].Rows)

{

Write-Host ("Statistic.{0}: {1}" -f $rowCount, $row.is_auto_update_stats_on);

Write-Host ("Message.{0}: Auto update statistics for {1} is {2}" -f $rowCount, $row.DBName, $row.is_auto_update_stats_on);

$rowCount++;

}

$result = Get-ODBC-Data

exit 0

And I have attached screenshot of Get Script Output as well.

300

I think I found the problem. I had created 1 monitor and it was working fine for 10 pairs of output.

So I went ahead and created a copy of it and modified it for the minor changes in SQL query and other changes.

This second monitor was giving me error.

When I deleted the second monitor and created it manually instead of copying it from existing monitor, it gave expected output and succeeded.

Thank you for your help.