tdanner ✭✭✭✭✭

It's in the current NPM beta.

In my test, an empty dictionary worked fine (swis.factory.create('ns4:dictionary')) but None did not.

We haven't removed this, but it should automatically rotate the files now, so they won't have the unlimited growth they had in 8.5.1. And you can still just delete the SolarWinds_Logging directory to make it stop.

Yes, that looks normal. And if you set some custom property values through the UI and fetch them through PowerShell?

Remove-SwisObject will accept multiple Uris as pipeline input. Like this: $uris = @( $uri1, $uri2, $uri3 ) $uris | Remove-SwisObject $swis It doesn't have to be an explicit collection like that. Any pipeline source of Uris would work.

In the start menu under "SolarWinds Orion SDK", there's a link called "Schema Documentation (v3.0)" that has a list of the entity types and their properties. You can also run SWQL Studio, connect to Orion, and explore the object model this way.

Adding a "SWIS version supported" column to the function table is a good idea. I'll get that in for the next SDK release. There are no plans to add features to SWISv2. I recognize that it is painful to deal with some features only being available in one service (it's annoying for our developers too), but our direction is…

You are passing an int as the first parameter, but it is expecting an int[] (array). In PowerShell, that looks like this: $ids = New-Object int[] 1 $ids[0] = 1 $result = Invoke-SwisVerb $swis Orion.AlertActive AppendNote @( $ids, $newnote ) In NPM 12 this gets a bit simpler because it will accept a PowerShell list instead…

If you want to put a line break in a label, you can hit shift-enter or control-enter. I don't think I understand what you mean by "how to delete objects that have been saved". Can't you just right-click on a Map at the top of the tree and delete it?

neilmborilla, what errors are you hitting in web node management?

When you are getting access denieds for a few files deep in the tree, one easy way to fix the problem would be to go higher in the tree (say, to \inetpub\solarwinds\orion) and do Properties -> Security -> Advanced -> Replace permission entries on all child objects with entries shown here that apply to child objects -> Ok…

I checked - no update yet. I added another bump.

The "hostname" in a SWIS URI is not used for addressing or DNS lookups. We call it a "system identifier" and it is really used for telling the difference between (for example) NodeID 1 on one Orion system vs. NodeID 1 on a different Orion system. I don't know if you use Additional Polling Engines, but if you did you would…

You should be able to skip steps 1-4 and just do discovery only, providing the IP of the node you want to discover.

I'm afraid your script is going to have to connect to both SWISv2 and v3 and perform some operations (the call to New-SwisObject) on the v3 connection and others (any NCM verbs) on the v2 connection.

I see the problem. NTA 3.11 is still only on SWISv2, but the JSON API is only on SWISv3. To get NTA 3.11 data over HTTP you will have to use SOAP.

Can you unmanage node 712 through the website? If not, fix that first. If so, try calling the Unmanage verb through a different entry point, such as SWQL Studio: connect, expand Orion.Nodes in the tree, right-click on Unmanage and choose "Invoke...", fill out the form and click Invoke.

Oops, sorry about that. Q. is there a document or page somewhere that lists out the 'ErrorCode(s)'? A. I don't think so. Here's all the ones I could find: AccessDenied = 20 InvalidArguments = 30 InternalError = 50 StorageError = 51 Q. is Unmanaging a Node (& the i-faces) the correct way to accomplish this? A. Yes, planned…

This functionality is available now in Orion Platform 2018.4 (NPM 12.4). It is documented at Credential Management · solarwinds/OrionSDK Wiki · GitHub .

Can you see anything notably different between systems where it works as expected and systems where it does not? All polled via SNMP? Same vendors?

Your Connect-Swis line looks like this: $swis = Connect-Swis -host '10.43.2.43' You are not providing the credentials to connect, even though you set up those variables in your script. Try something like this: $cred = New-Object -typename System.Management.Automation.PSCredential -argumentlist $username, $password $swis =…

Following up much later - this is fixed in SAM 6.0 (in beta - http://thwack.solarwinds.com/community/solarwinds-community/product-blog/blog/2013/05/29/server-application-monitor-60-beta-3--introducing-appinsight-for-sql). In that version the verb works properly in SWISv3.

Orion's "pass-through" authentication feature works like this: IIS performs Integrated Windows Authentication on the user. Generally this means AD/Kerberos, though it can also be a local windows account on the web server. Orion then takes the name of the authenticated user (in "domain\username" format) and looks for an…

Oh, I see - I thought you were in the Orion reporting interface. SWQL Studio does not have a way to extend the timeout. This query would be almost identical in SQL. You could just run it there. edit: there is a way to extend SWQL Studio's 2-minute timeout. Edit C:\Program Files (x86)\SolarWinds\Orion SDK\SWQL…

I have seen a similar problem (not the same - just similar) be resolved by installing .NET 4.5.1. You could try that. (Or 4.5.2, which is out now.)

I think you are pretty close. The Acknowledge verb expects an array of AlertInfo objects. This line should do the trick: swis.Invoke("Orion.AlertStatus", "Acknowledge", PrepareInvokeArguments(new[] { alertInfo }));

Start with the property list for Orion.Volumes: https://solarwinds.github.io/OrionSDK/schema/Orion.Volumes.html. At the bottom of that page is the list of navigation properties supported by Orion.Volumes. That's where you'll see the "Node" property listed. Since "Node" is a navigation propertly, it is linked to the page…

Just the port, I think. I tried setting mine to a bogus hostname and the service still started up fine.

It depends on what database you are putting the data into. For SQL Server, you can use the built in String Functions (Transact-SQL). Other databases will have something similar.

Upgrading to either the latest 8.1 hotfix or to 8.5 should fix this problem.