tdanner ✭✭✭✭✭

The install doesn't place any assemblies in the GAC or System32 directories. Everything is installed under C:\Program Files (x86)\SolarWinds\Orion SDK. Could you clarify what you are expecting to see in Visual Studio? The VBClient and CSClient projects are just sample code - you have to build them.

With Connect-Swis, are you typing in a username/password or are you using the -Trusted option to pass your login token? Are you able to connect if you use a non-AD (Orion) account? I have seen issues with SWIS and AD authentication in some environments. Connect-Swis doesn't actually open a connection. That is deferred…

No, you can't insert data into Orion.Events through CRUD. You'll get the same message with any credentials.

You can do a full text search of the NCM config archive using the Cirrus.ConfigArchive.ConfigSearch verb. See this post for details: Re: Config files available via NCM

Are you using (planning to use) the agent-initiated or server-initiated communication mode?

What version of the product are you using? You were on the right track about needing to provide a parameter to Connect-Swis to let it know that you need to connect to the v2 address. That parameter is "-v2". It is mentioned in the "Orion SDK.pdf" file (under the description of Connect-Swis on page 24), but I can definitely…

The "java.lang.IllegalArgumentException: 9" and "java.lang.IllegalArgumentException: 10" exception seem to be coming from your own code. From the names of the methods in the stack trace, my guess is that you are mapping the Status numbers to names. You can get the complete list of status names and numbers by querying…

Report Writer is putting the Notes field into the GROUP BY clause in the SQL query. This isn't your fault - it's just the way the availability report works. The database 'text' type (Custom Property Editor refers to it as 'Memo') is nice because it's virtually unlimited in length, but it has these limitations in how you…

Could you be more specific? I don't know exactly you mean by "ServerStatus".

I recommend you work out the query you want using SWQL Studio (you can download an installer from https://github.com/solarwinds/OrionSDK/releases/latest ) before building your API calls. SWQL does not support the SELECT * construct. You must list the specific properties you want returned. You can see this list graphically…

What do your working and not-working Connect-Swis calls look like?

You can increase the number of nodes that load in each batch by editing \Inetpub\Solarwinds\Orion\Nodes\Controls\NodeTree.ascx. Around line 234, there's a place where it says RowsRange="25". Try increasing that number and see what works.

If you make a full backup of your database, you should be able to restore that backup after you wipe the box and install Windows 2003. Then install Orion 8.5 and point it at the restored 8.0 database.

Try looking in the SWISv3 log to see what the actual error is. C:\ProgramData\SolarWinds\InformationService\v3.0\Orion.InformationService.log

There are various API improvements in NPM 12. I'll be gathering them up and making a post about them soon. But just to set expectations: there are no major improvements to the process of adding nodes.

URL filtering is changing the backslash to a forward slash, even when you %-encode it. We have a fix for it in the next release.

For the current version of Orion, I can't think of any way to do this with a single server. In the future when we consolidate on asp.net and get rid of the proxy, this might be possible (but no promises).

Make sure the SolarWinds Orion Information Service is running. Check the Windows event log for any errors related to that service.

mikearama, the list of groupings in System Manager is not customizable. cnorborg, which grouping list are you referring to? The node tree on the summary view, web node management, or something else? Also, which version are you on?

Nothing special should be required. It should be able to compare the string to the GUID without issue. Your query works fine for me when I change the actual guid and nodeID to reflect an actual active alert in my test system. What are you seeing? An error from SWIS? No result when you expect a result? Also, what…

This seems to be indicating that either you don't have a stored credential with ID 189 or that the credential with ID 189 is not of type UsernamePasswordCredential and is thus not suitable for WMI polling. How did you find this credential ID?

Thanks. I have entered a bug to give a better error message in this case. Ideally the text you marked in red would be in the error dialog. That should be easy to do and would have saved you a bunch of time (or, in the case of a less savvy user, saved our support team a bunch of time).

I tested this out. At first I thought I had confirmed a bug because I got the same error you did. But after looking in the logs, I found that the NodeID I had picked (1) doesn't actually exist. When I used a valid NodeID, it worked correctly. Could that be the cause of the problem you are having?

The N-Central and Orion systems have separate APIs. The Orion SDK won't be useful for talking to N-Central. Have you looked at the N-Central API docs? https://secure.n-able.com/webhelp/NC_9-1-0_SO_en/Default.htm#SA_docs/API_Level_Integration/API_Integration_WebServiceLevel.html

I don't have F5 data handy to test with, but this should be close: SELECT DISTINCT N.F5Devices.VirtualServers.ShortName AS [Publication Name], N.F5Devices.VirtualIPAddresses.ShortName AS [Publication IP], N.F5Devices.VirtualIPAddresses.IPAddress AS [Virtual IP Address], N.F5Devices.VirtualServers.Port AS [Virtual IP Port],…

For lots of statistics Orion gathers, this pattern is used: there's a xxx_Detail table, a xxx_Hourly table, and a xxx_Daily table. Newly collected statistics go into _Detail. Database maintenance moves old data from _Detail to _Hourly, older data from _Hourly to _Daily, and oldest data just gets deleted from _Daily. Each…

I am assuming you are using the SwisClient class from OrionSDK/SwisClient.cs at master · solarwinds/OrionSDK · GitHub . If that's not the case then all bets are off. You have wrapped this in a "try" block. I don't see the "catch" block, but I am guessing this is throwing an exception from the server. Most likely the server…

What do you mean by "add nodes to alerts"? In general, I would recommend designing your alert configurations so that they don't reference specific nodes. Instead, use attributes of the nodes (including custom properties where appropriate) to control which alerts trigger on which nodes.

Currently the DiscoverInterfacesOnNode verb does not provide any information about interface status, so there's not really anything you can do. It's a good idea though - I'll enter a feature request for it.

We keep a list of partners and resellers on this page: Locate SolarWinds’ Resellers