tdanner ✭✭✭✭✭

Very detailed! Thanks. That's all fairly current stuff. We'll figure this out somehow. Please run this query in SWQL Studio: SELECT EntityName, Name, CanInvoke FROM Metadata.Verb And let me know what the results are.

This may be due to the firewall issue you mentioned in another thread. The HTTPS connection happens on port 17778. The "Orion v3" option uses port 17777.

<CredentialID> needs to contain a number. You are sending a PSCredential object. I don't know what that will look like when it gets turned into XML, but it is not going to be a number. The CredentialID values correspond to the ID property of the Orion.Credential entity. You can find your stored credentials with a query…

This thread started in 2014 about unmanaging nodes and has way too many replies now. Please ask your question in a new thread in this forum and I'll get you fixed up.

You could add some Write-Host statements. It's not clear what information you want in the log.

I can help you with issues concerning the Orion API and how to call it, but how to hook up a GUI to a working script is getting beyond the scope of this forum.

The way I wrote it, the text file would need to be in the current working directory (which may or may not be the same location as the script). For clarity and safety, I would just put the fully qualified path to the text file in the script.

SolarWinds-Traps.mib depends on SolarWinds-Products.mib, so you need to load both of them at once. This is normal for mibs and the tools that deal with them.

This is fixed in Orion Platform 2018.2 / NPM 12.3, out today.

Ok, so you are not calling DiscoverInterfacesOnNode and using that list. Let me see if I can put something together in Perl.

This script works correctly for me (after I change solarwinds.com to localhost). I noticed that in the full script, you are only passing one parameter (the query) to swis.service.QueryXml. But in the post above, the line that threw the error was: x=swis.service.QueryXml("SELECT TOP 1 Uri FROM Orion.Nodes WHERE…

> I'm assuming that it follows the same logic as SQL - if there's a unique field name returned, you can just reference that field by name. Yup, that's what it does. With an important exception: references to navigation properties properties must be qualified with the entity name or alias. So you can do "SELECT Caption FROM…

Looking at this again a month later, I noticed something in your script that seems strange. You are looping over a list of custom properties from the csv file, building up one variable for each parameter of CreateCustomProperty as a list of values, then making one call to CreateCustomProperty passing the list of lists.…

Hope that works! Let me know how it goes.

You seem to have a quite old version of SWQL Studio. You can get the new one by installing SDK 1.7 from http://downloads.solarwinds.com/solarwinds/Release/Orion/OrionSDK-v1.7.zip (referenced in this post: Orion SDK Information).

That's very strange! When you have one of these "kind of a string, but not really" objects, what do you get when you call .GetType() on it?

Do lab and production have the same versions of the product(s), including service packs, installed? I assumed they did but forgot to ask.

If you just want to adjust the interfaces on an existing node, then you can skip creating it. You just need the NodeID of the existing node in order to use the discover/add interfaces verbs.

Can you post the query you are working on?

What version of NCM are you on? 7.3 and 7.3.1 have a problem where jobs created programmatically for nodes assigned to Additional Polling Engines can get in this state. This problem is fixed in 7.3.2. If that doesn't sound like your situation, please send me a couple of files to tim.danner@solarwinds.com:…

I found the place to change SWQL Studio's timeout and put the instructions in my reply above where I previously said it couldn't be changed. Please try that and see if it gives it enough time to complete.

No, unfortunately we don't have a document listing the changes from 1.3 to 1.4, but it would definitely be helpful. We will provide a "what's changed" section for the next SDK update and in the future.

The problem is these lines: WHEN '2701131793' THEN 'CCM_SIP_600_BUSY_EVERYWHERE' WHEN '2717909013' THEN 'CCM_SIP_603_DECLINE' WHEN '2734686209' THEN 'CCM_SIP_604_DOES_NOT_EXIST_ANYWHERE' WHEN '2751463455' THEN 'CCM_SIP_606_NOT_ACCEPTABLE' These numbers are greater than the maximum value that can be represented by an int,…

Kenny, It's looking for C:\Program Files\Common Files\SolarWinds\JobEngine\SWJobEngineSvc.exe. Does this file exist? If not, do any of the directories in that path exist? This is installed by the "SolarWinds Job Engine v1.1" package. I know you've already done a bunch of repairing, but is that package installed in…

We have a bug in NPM 11.5 (and other releases based on the Orion Platform 2015.1 release) that makes custom properties not work for nodes created through the API. Jan Pelousek posted a workaround here: Re: Upgrade from NMP 11.0.1 to 11.5 breaks SDK 1.10 set CustomProperties

You need two more pollers: N.Status.ICMP.Native and N.ResponseTime.ICMP.Native. I just noticed these are missing from OrionSDK/CRUD.AddNode.ps1 at master · solarwinds/OrionSDK · GitHub, so I added them.

I haven't personally seen any problems resolved by removing .NET 2.0. That doesn't mean there couldn't be any - just that I haven't seen any myself.

jhay317, from the web server, can you ping "orion"? If the problem is that this is a DNS alias that the web server doesn't realize points to itself, we can help you.

The SDK comes with a reference for the schema (listed as "Orion SDK/Schema Documentation" on the start menu), but it doesn't have descriptions - just a list of the entities and the properties. For Nodes.Status, the Orion.Status entity has details about the set of possible values. '0' corresponds to "Unknown". If the node…

"DELETE FROM CPULoad WHERE NodeID=49" worked for alterego because he was only having this problem with one node (the one with id 49) and because he first disabled CPU polling for that node (which would have just added more of the problem data). Since you have 200+ devices with this issue, fixing it that way would be really…