tdanner ✭✭✭✭✭

Also, while IE6 sometimes can't change font sizes, IE7 always can.

Orion has a few ways to slice this. The first thing you should do is use the Custom Property Editor to create a property you can use to differentiate the various groups of nodes. Maybe "LocationType" with values like "Store", "Distribution Center", and "Corporate Office". Then you can filter your Top 10 resource like this:…

For "create a new row" in the NodeSettings table, the SWIS entity Orion.NodeSettings supports CRUD, so you can use the powershell New-SwisObject/Set-SwisObject cmdlets for handling that.

Orion users can be found in Orion.Accounts. Each account has (up to) three limitations referenced by the LimitationID[1-3] properties. Definitions for those limitations are found in Orion.Limitations.

The attached zip file contains an update for the ajax node tree that addresses two issues reported in this thread: * Custom SQL filters that use "OR" cause nodes to appear in multiple groups. * Custom property values that contain an apostrophe (or a couple of other special characters) break the tree. There are two files in…

The ajax node tree uses the asp.net javascript web service client to transfer chunks of the tree. This web service client puts a hard limit on the size (in bytes) of the payload that can be returned. You found that this limit seems to correspond to about 350 nodes. It would vary somewhat depending on things like the length…

Have you tried it with an Orion account, not a Windows/AD account?

Here's a python script that uses the REST API to do essentially the same thing as DiscoverSnmpV3Node.ps1: https://github.com/solarwinds/orionsdk-python/blob/master/samples/discover_one_node.py

Invoke-SwisVerb does not accept pipeline input. You were on the right track with needing a loop. In PowerShell one way to do that is to pipe your objects to the ForEach-Object cmdlet and put the loop body in a script block. Like this: $oldprofiles | ForEach-Object { Invoke-SwisVerb $swis -EntityName Orion.discovery -Verb…

Try adding an ORDER BY clause at the end.

The schema available in SWQL is not just a copy of the database schema. In this case, the data you are looking for is in the NCM_Nodes table.

The "Nodes with Problems" resource doesn't look at the Status field. Instead, it looks at the Severity field, which will be zero if everything is hunky dory and greater than zero if there are any problems with the node, including with the monitored interfaces and volumes on the node. So that would be one reason a node…

Sounds like a file permissions problem. I would check that the .ascx file has the same permissions as the other files in that directory.

(Followed up with Jesper by email.)

Jesper, On line 63, the ascx file sets up the path for the EDIT link to: /Orion/NetPerfMon/Resources/FilterEdit.aspx That's where it was for the 9.x releases, but it looks like it was moved in 10. The new location is here: /Orion/NetPerfMon/Controls/EditResourceControls/FilterEdit.aspx If you make that change in the file,…

The HAVING clause must appear only after a GROUP BY clause. The second query has: group by name, [Trigger Object], RelatedNodeCaption But there is no GROUP BY in the first query nor in your combined query.

When I wrote this resource, I assumed that users would have node custom properties called “Department” and “Comments”, but we only started adding them to new installs a couple of versions ago – upgraders won’t have them. If you're getting the "SQL filter is incorrectly formatted" error, I’m guessing you don’t have these…

I'm glad you figured it out! I was stumped.

kjmartin and jimmydarko - Maybe it's a permissions issue? Check that the ACL on the new resource file looks the same as the other files in that directory.

jimmydarko - did you restart IIS after making that permission change? Orion caches the list of resources since most users never mess with it.

This should work on 9.5.1 with no changes. Could you send me your OrionWeb.log file? See these instructions from earlier: run LogAdjuster.exe in the Orion installation folder (usually C:\Program Files\SolarWinds\Orion), set the log level for the Website to DEBUG, and hit OK. Reload the page so you get the "Custom SQL…

VegardAa - run LogAdjuster.exe in the Orion installation folder (usually C:\Program Files\SolarWinds\Orion), set the log level for the Website to DEBUG, and hit OK. Reload the page so you get the "Custom SQL filter is incorrectly formatted" error again, then zip up C:\Documents and Settings\All Users\Application…

kjmartin - What directory did you put the file in?

rsprim - Open the file in a text editor. Find the line that says "ORDER BY Nodes.Caption" (should be about line 27). Change it to "ORDER BY Nodes.Department, Nodes.Caption". Save.

A user noticed that this resource doesn't work properly with account limitations - it says "SQL Error" instead of showing the down nodes. (No data is shown inappropriately - it just an error message.) I updated the file to fix it. If you downloaded it before now, you should grab the updated version.

Very nice. As a reminder - I post released versions (not beta) on Chocolatey as well. https://chocolatey.org/packages/orionsdk . So "choco upgrade orionsdk" will get you current.

I made an ASP.NET resource (9.5 compatible) by combining this code with the stock Down Nodes resource and posted it here: . See if it works for you.

I'm not aware of any breaking changes to the API. Existing SDK-based automation should continue to work after the NPM 12.4 upgrade.

No, Orion doesn't provide a way to open up Poll Now to accounts without Node Management rights.

nakoz69 - can you use the other Poll Now buttons in the website? Or do they give the same error?