tdanner ✭✭✭✭✭

The trouble with just updating the database (with or without a stored procedure) is that the new custom poller assignments may not be scheduled for polling right away. A restart of the Orion Module Engine service would cause the new assignments to get scheduled for polling. I can't explain why it would have worked on one…

The main node management page is fairly heavy in terms of javascript execution, and the two browsers you are using, IE6 and 7, and have (by far) the slowest javascript engines of any browser in use today. I wouldn't expect all your issues to go away, but you might see an improvement if you try a browser with a faster…

We did have a problem with that in 9.0. It was fixed in 9.0 SP1 or SP2.

I still don't understand your use case. If you are trying to send a file to a third party, don't you need an SFTP client? The server simply makes files available.

Sure. It's first.last at solarwinds dot com

No, this has not been implemented yet.

Here's a fancier version. This gets rid of the DataGrid with automatic databinding and replaces it with an ASP.NET Repeater control. This control requires you to specify all of your HTML explicitly, but the benefit is that you get more control. I used that control to make the node names links to their Node Details pages…

I don't think so. It's not one of the fields in the alert schema. But even if it were, what good would it do? If Orion can't talk to the database, it can't very well check the timestamp in the database for you.

The license keys off of various other hardware parameters. If you use the License Manager app (installed with Orion), you can unlicense the old server and return its key to your SolarWinds account pool. Then you can license the new server in the usual way. If that doesn't work out for whatever reason, support can get you…

In the time since this thread, SwisPowerShell has been released as a module on PowerShell Gallery (SwisPowerShell module released). This allows you to install it using a simple command ("Install-Module SwisPowerShell") instead of the msi. Unlike snapins, PowerShell modules don't have to be registered.

To get the syntax highlighting and line numbering on thwack, you have to click the "use advanced editor" link above the reply box. This will pop you over to an editor page with more options. It will carry over your in-progress draft, so don't worry if you realize that you need something rom the better editor halfway…

This did not make it into hotfix 2, but it will be fixed in 8.5.1.

Here's how I would do it: Add-PSSnapin SwisSnapin$swis = Connect-Swis latest-stable-builds -UserName admin -Password ""$queryResult = Get-SwisData $swis "SELECT TOP 1 AlertDefID AS DefinitionId, ActiveObject AS ObjectId, ObjectType FROM Orion.AlertStatus WHERE Acknowledged=0"$xmlString = "<ArrayOfAlertInfo…

No, we don't provide an API for running arbitrary SQL commands. We also don't support custom fields on alerts.

danabrash​'s script above in this thread shows how to assign a connection profile (identified by its ID) to a node. The key line is the last one: Set-SwisObject $swis -Uri $ProfileURI -Properties @{ConnectionProfile=$NCMConnectionProfileId}

Ask ding​ to prioritize UDT-692.

You are absolutely right. I thought this fix was supposed to be in 11.5.1, but it is not. It is in 11.5.2, which is not released yet. Sorry for the confusion.

(Just riffing here - no concrete plans.) One improvement the custom query resource could use is a way to set format options for each column. This would be outside the SWQL query - a set of options that you configure on the resource's Edit page. You could set up simple formatting this way (like "show column 3 as a…

There's a bug (internal number CORE-6278) in the report builder that causes it to mangle custom SWQL queries with UNION clauses. If the Custom Query Resource can meet your needs, you could use that instead. It does not suffer from this issue. Custom Query Resource does not support embedding HTML markup in the query results.

The next step to investigate this will be to use WCF tracing. This logging method is extremely verbose, so to avoid generating an unmanagable log file it is best to stop all Orion services, start "SolarWinds Information Service V3" only, reproduce the problem (generate the 403 error), and then immediately stop SWISv3. The…

Could you post the error you are seeing after hotfix 2?

It's time to call support on this one - they know all about wrestling IIS.

Unfortunately, we don't know why some people have seen the Remove option disappear for AM. I don't think it's related to upgrading, but who knows.

Apologies - I lost track of this thread in December and haven't responded. Is this still a problem for you or have you found a solution already?

Update: I found a real problem with this. If AccountID and Password are the first items after the ? in the query string, then it doesn't work. I'll get that entered as a bug. As a workaround, you can either move AccountID and Password to the end of the URL, or just stick a dummy value ("foo=bar" at the beginning.

At this point there is no nice way to zero-pad a number in SWQL. The best I have come up with is this: CASE WHEN X < 10 THEN ('0' + ToString(X)) ELSE ToString(X) END

I found two website timeouts in the log during the period when the log level was turned up. In both cases, it was a couple of minutes into the execution of the same query: Select * From CPULoad Where NodeID=49 AND DateTime >= '07/01/2008 00:00:00' AND DateTime <= '07/01/2008 16:06:53' Order By DateTime That's not a query…

I just noticed something in your script that I wish I had noticed last week. In this list of pollers, you have a mix of SNMP and WMI pollers. These have to match the node type (the ObjectSubType property of the node) and the appropriate credential has to be assigned (SNMP creds for SNMP nodes, Windows creds for WMI nodes).…

It sounds like you have already gone through the material we have. Learning to work with some other REST API would help you. Have you chosen a language to work in?

At this time, credential management operations in the API are limited to creating new credentials, not updating the passwords on existing ones. I'll add your vote to that feature request though.