tdanner ✭✭✭✭✭

The "parameters" argument to Invoke is indeed an array of XmlElements. These should be the serialized representation of what the verb expects. In this case, the verb expects one parameter: an array of AlertInfo objects. You can use code like this to convert an arbitrary set of stuff you want to pass to the verb to…

To create a "Dynamic IP" node, set the "DNS" property to the fqdn of the device and set the "DynamicIP" property to true. Within a few minutes Orion will resolve the DNS name, fill in the IP address properties, and start polling the device.

Do you have NPM and NCM installed separately? I thought they were on the same server. If they are separate, then this call would need to go to the one with NCM. If the exception info is not coming back with the 500 error, you should be able to find it in the log file:…

No, like this: [ [ 1, 2, 3, 4 ] ]

Have you tried using our python client wrapper instead of the plexxi one? GitHub - solarwinds/orionsdk-python: Python client for interacting with the SolarWinds Orion API

That depends what you have to work with. You can get a list of all currently active alerts with a query like this: SELECT AlertDefID, ActiveObject, ObjectType FROM Orion.AlertStatus See Re: SWIS REST/JSON API for how to run queries through the API, or install the Orion SDK (download from Orion SDK Information) on a Windows…

"Couldn't connect to host" sounds like a possible firewall issue. Can you use "telnet solarwinds.mydomain.com 17778" to verify reachability?

This thread is from 2014. Since then, we have deprecated this API (it still works, but is not recommended for new scripts) and introduced a new one that is documented here: Alerts · solarwinds/OrionSDK Wiki · GitHub . I recommend you review that page and use the Orion.AlertActive/Acknowledge verb to ack alerts.

No, opening a ticket wouldn't really change anything.

Short answer: you need to delete \InetPub\SolarWinds\Orion\custom.config. Long answer: Let me give you a bit of background on how the website works in 8.5.x that should clear up some of the confusion here. Pre-8.5, the Orion website was implemented in classic ASP using VBScript. You can do a lot with those tools, but…

It depends what kind of timeout you are getting. What's the actual error message?

SWIS operates on UTC. Use [DateTime]::UtcNow.

I don't think I understand what you want to do. SWQL Studio is a GUI tool. If all you want to do is have a human read the value, just read the value. Computing the substring only matters if you want to do further processing on it.

I have stopped fighting with SOAP encoding for these things. It is too finicky. Fortunately SWIS also supports json encoding. Here's a Perl script that calls AddInterfacesOnNode using the JSON encoding instead: AddInterfacesOnNode.pl · GitHub (thwack formatting was giving me too much trouble, so I posted it as a gist…

I created a wiki page to cover account management. The verb you should be using for this is either CreateOrionAccount or CreateWindowsAccount, depending on the type you want to create. Account Management · solarwinds/OrionSDK Wiki · GitHub

I haven't used SoapUI for REST calls (only SOAP - go figure ), but it looks like it does not need you to URL encode the query string value. It must be doing that for you.

I can't really do anything with that number out of context. Can you copy and paste in the surrounding lines from the log file?

Without seeing more of your code it is hard to know what is going on. Could you post a larger chunk?

Yes. The internal tracking number is CORE-11083.

Thanks for the info! I'll let the product manager know about this request.

Simplicity, mainly.

What version of the product are you using?

Alert verbs are documented here: Alerts · solarwinds/OrionSDK Wiki · GitHub

Yes. There are two steps: copying the custom property definitions and copying the data. Copying the definitions: if you have a relatively small number of custom properties, you can just manually create properties on the target system to match the properties on the source system. If the number of properties is large enough…

I think I found the problem. The alert I used for testing exported to XML contained zero newlines. Many of the alerts have newlines in their description or trigger actions or something. When there are newlines in the string, Set-Content works correctly (writing the whole string to a file unmolested), but then when you read…

The SOAP interface is still supported, but I wouldn't recommend it for new code. The REST interface is usable from any language. For Python, we have a simple client wrapper for the REST API at https://github.com/solarwinds/orionsdk-python. (This repo also has a few samples.) You can install it with "pip install orionsdk"…

AppendNote is a verb on Orion.AlertActive, not Orion.AlertStatus.

Nope, that's exactly what it's supposed to be. Strange. Has the problem persisted across a restart of IIS?

I think what has happened here is that the request was sent to SWIS. In processing that request, SWIS has some kind of error. This error was returned to your program as a SOAP fault message. The Axis web service client failed to parse this fault message, so it threw an exception. The other way to see what error occurred on…

I forwarded your question to the relevant product manager.