tdanner ✭✭✭✭✭

That's a good idea, but unfortunately there is no API for ​removing ports either.

Great!

You are right - it's corrupted when I download it as well. I still have the original zip, and it's fine. I'll try posting it again with this message.

Orion connects to remote databases using TCP.

If sedmo's report isn't what you are looking for, this query might give you a head start on building it as an Advanced SQL Report: SELECT Caption, Status, Unmanaged, UnmanageFrom, UnmanageUntil FROM Nodes WHERE UnmanageUntil > 0 AND Unmanaged=0 The "UnmanageUntil>0" condition will filter to give you only nodes that have…

NPM 11.5.1 has been released. It addresses this bug. Once you have upgraded to that release, you can and should remove the "Insert into NodesCustomProperties" workaround. Update May-11: the fix has not been released yet.

Currently the only documentation for this API is forum posts. There's a PowerShell example in this thread: Re: Discovery through SDK is no longer working as expected PowerShell

That looks like it could work, but I would strongly recommend previewing the output of that query to make sure it is what you expect before committing the changes with the Set-SwisObject calls.

A few questions: 1. You said this bug showed up in 11.5.2. What is the last version it worked correctly in? 2. Does this affect interfaces on all device types, or just some? 3. The code shown here includes the call to AddInterfacesOnNode, but not the call to DiscoverInterfacesOnNode. Can you show that code as well?

I love the Custom Query Resource - it gives power users a lot more control over how data is presented than they could get with just customizing existing resources. Things like threshold coloring (for the whole row or just one cell) and group headers would be nice additions. What do you mean by "node editing" in this…

The footer on the website will tell you if you have Service Pack 3.

When you get this error, there should be a "Save Error Report Locally" button. Please click that to get a text file with details and post it here.

If the uninstall option for AM is broken, you will need to follow the steps I describe here: and here:

This operation is not currently supported in the API.

If I just copy the "SELECT CONCAT(CASE WHEN DAY(16 November 2017 12:26) ..." query out of your message and try to run it in SWQL Studio, I get this error: no viable alternative at input 'November' in Select clause Which makes sense. The solution is to wrap it in quotes. So in the trap template, everywhere you have…

Can you send me a complete script? With that I can try to reproduce your issue and make a better recommendation.

Yes, this should be a safe way to chop those values off at the maximum rate for the circuit. You may also want to apply the same logic to In_Averagebps and In_Minbps.

bishopolis​, mnchetz​ - there are many possible causes of 403 responses. Please start new, separate threads in this forum to work through this.

The next place to look would be in the SWISv3 log file on the Orion server: C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log. Reproduce the error again and check that log for any details.

In this case we can just use json in the json. Like this: ["tdanner",{"AllowMapManagement":true}] Note that for the various "AllowXXX" properties you should use actual json booleans (true/false) and not the weird legacy "Y" and "N" values you get when you query Orion.Accounts.

Yes, this is possible. When I tried it, I needed to put the condition in the report itself. When you put the report in the "Report from Orion Report Writer" resource on a Group Details page, the ${Name} macro will be replaced with the name of the current group. You can use this in a condition in the report filter, like…

The Database Manager tool connect to SQL Server for running SQL queries. The query you have there is a SWQL query that needs to run against SWIS. You can do that in SWQL Studio. Since the python script didn't cause any errors to show up in the SWIS log, I suspect a connectivity issue. Let's see what happens if we make a…

You don't need to use a SQL query. If you want to do this in the reporting system, you can make a report for nodes that includes whatever properties you need, including custom properties, just by picking them from the list. If you prefer to do this from a script, you can use a Query request to get a complete list of nodes…

The Query method is unfortunately broken in the current release. Use the QueryXml method instead (just pass null for the second parameter). In the current development branch, we have removed the Query method. QueryXml has been the recommended method for the past several releases. Sorry for the confusion!

What URL are you requesting? If it starts with /SolarWinds/InformationService/v3, then you are using a SWISv3 endpoint. If not, you are using the SWISv2 endpoint.

Yes, the Net.Tcp Port Sharing Service is required. Starting with Orion 9.0 we are trying to standardize on port 17777 (to simplify configuration for customers who have firewalls between their various Orion servers) for all of the SolarWinds services that communicate with each other on the Microsoft Net.Tcp protocol.…

I took a look at this query. The "Incorrect syntax near '='" error is actually coming from SQL Server in response to a (bad) SQL query generated by SWIS. I'll open a bug for that. In hopes of finding a workaround for you, I attempted to rearrange the query to produce the same results but trick SWIS into not generating the…

If you don't mind Python, here's a script. Translating to perl shouldn't be hard. This one imports the SwisClient.py module (source on github: OrionSDK/SwisClient.py at master · solarwinds/OrionSDK · GitHub). from SwisClient import SwisClient swis = SwisClient('localhost', 'admin', '')config =…

It's at the top of my list, but I don't have a date for you.

'fraid not. Probably time to kick this issue to support.