tdanner ✭✭✭✭✭

Oh, I see. You may have only WebClient access and not real FTP access. If you can't confirm this directly with the site administrator, you could try it with a standalone FTP client such as our FTP Voyager or Filezilla. Your code looks fine, but to troubleshoot it further, you could wrap it in a try/catch block and print…

Are you able to log in with your AD account on the website?

It turns out this is a bug. The fix should be coming out shortly. I'll update this thread when it is available.

One note: the results of that query will reflect the privileges of the account you are using to query. In other words, if you run the query as an admin account you will get one list of entity types. If you run it as guest you will get zero results, since guest isn't allowed to create anything.

Not programmatically. You have to use the website.

You could try running the configuration wizard again. That might be all it takes to clear this up. If that doesn't get it, you should probably open a support ticket.

> Okay so that would be any of the servers such as the NPM server? Which would then communicate with the SQL Server that is not necessarily on the same host? Yes, that is correct. > Could I just connect to the SQL server directly? There's nothing stopping you from talking to the database directly using database…

Some SWIS entities are based on SQL views already. Is there something in particular you have in mind?

In that case, I recommend you open a case with SolarWinds support.

Could you look in C:\ProgramData\Solarwinds\Logs\ on the VM?

The "Orion AD" connection type in SWQL Studio is using the net.tcp protocol and passing Windows credentials (this will be handled using NTLM or Kerberos under the hood). At this time, we don't support connecting over HTTPS using Windows accounts. It will have to be a regular Orion user account.

If you look in Orion.DiscoveryLogs, you can find the BatchID for a particular discovery run. With that BatchID you can query Orion.DiscoveryLogItems and get the more details about what was actually added. Any clues there?

Under normal operation, SAM is only collecting information about processes you have an component monitor for. When you launch the real-time process monitor, it starts separate out-of-band collection (in memory only) for all the processes on the target server. But this operation is not exposed through the API.

It looks like we quoted you the wrong OID to check. While your routers do need to support rttMonAppIResponder, the OID we check for is 1.3.6.1.4.1.9.9.42.1.1.7.1.2.13, which is a specific entry in the rttMonApplSupportedRttTypesTable table. Any device that supports that will also support rttMonAppIResponder, which is older…

The request format for invoking a verb is here: https://github.com/solarwinds/OrionSDK/wiki/REST#invoke-request

My best guess for the cause of this one would be that the credential indicated by that credentialID either doesn't exist or is not the right kind. There should be more details in this log file: C:\ProgramData\SolarWinds\Logs\Orion\Core.BusinessLayer.log

That AlertInfo class is the parameter to the Orion.AlertStatus.Acknowledge verb. It is used for specifying which alerts you want to acknowledge, not parsing the query results. In the GetOneAlert function, the query results are parsed by looking for the "data" result element, then the "A" element under that. The "data"…

Funky. If you can make sure the IIS website and IIS application pool are running, try to browse to the page again. If you get the exception about "Bad file name or number", I would try to debug that using a Process Monitor trace (to find out what file it's talking about). Since you're a trial customer, there are people in…

If the files and reg keys are gone, it should go fine. Don't forget 9.1 SP1.

Dropping tables is easy - just use your db management tool of choice (SQL Management Studio, Orion's Database Manager, sqlcmd, etc.) to run "DROP TABLE tablename", where tablename is the name of the table. AppMon adds the following tables: * Applications * ApplicationStatistics_Daily * ApplicationStatistics_Detail *…

This timeout is controlled by web.config (C:\Inetpub\SolarWinds\web.config if your website is in the default location). Edit this file (make a backup copy outside the web directory first) and add a <location> element for this page. Like this: <location path="Orion/NetPerfMon/ntareport.aspx"> <system.web> <httpRuntime…

The "Polling Method: Status Only: ICMP" radio button on the Add/Edit Node page corresponds to the ObjectSubType property of the Orion.Nodes entity being set to 'ICMP'.

The GroupStatus/StatusDescription fields did occur to me when I was looking at that code. I'll ask around and see if anyone knows why we aren't using those. If nobody has a good reason, I'll see about changing it in a future release. It would definitely be faster.

Here: Server & Application Monitor Feature Requests

The easiest way to get them is to run the Diagnostics tool (it's only the start menu in the Support section under Orion). That will generate a zip file with a bunch of info that's useful for troubleshooting. You can then attach it to your ticket and the support crew will see it.

Get-SwisData and running a query from SWQL Studio are using essentially the same code paths. Get-SwisData has a "-Timeout" option (takes a timeout value in seconds) that you can use to override the default timeout of 30 seconds. Is it actually timing out on the Get-SwisData line? That query looks simple - unless something…

The right way to do it is to add the node to Orion.Nodes, then call Cirrus.Nodes.AddNodeToNCM. We don't have a supported way to add a node to NCM without adding it to Orion.Nodes first.

The NCM ("Cirrus") verbs are currently only available when connecting to SWISv2. The URL for SWISv2 should not have "v3" in it.

I answered your question in the other thread: Re: Set-SwisObject : Update or insert of view or function 'dbo.AlertStatusView' failed

Look in the NPM.BusinessLayer.log file in your install directory and post any errors you find.