adatole ✭✭✭✭✭

Glad to help. Don't forget to like the content. I'm 410 points away from 11th level!

The next test I would make is to re-create a job through the actual report scheduler and see if it works. if it does, then something is missing in your manual recreation. If it doesn't work, then something is broken overall.

Awwwwww! Just click the picture of my fuzzy face, and in the upper-right corner you should see a "follow" button. I'll even friend you if you ask!

If you are NOT comfortable with MS-SQL, please stop reading. Really. I mean it. You have a better chance of keeping your sanity if you read "The Necrinomicon" on a dark winter night by candle light surrounded by bloodthirsty wolverines. Still reading? Yeah, that warning didn't stop me either. If you are comfortable with…

AHHHHH, Right. You used the "Test" button, didn't you? Don't do that. Just... don't. It doesn't work. It doesn't populate variables. It was a nice idea that didn't really pan out. It's one more really good reason to upgrade to NPM 11.5. But if that's not something you can do in the next 5 minutes, then do this instead:…

In Solarwinds, parent-child really just "injects" an extra polling cycle. So you have a greater chance of seeing the switch go down before the server. BUT if the servers are polling at 60 seconds and the switch is polling at 120, you are right that parent child is going to fail you sometimes. It's another reason to have…

YOU CAN'T HAVE HER. SHE IS OURS AND WE ARE KEEPING HER FOREVER AND EVER AND EVER!!!

You insert the code I gave you into a "SWQL" variable. So go into the alert message, click the "insert variable" button, check the "Define SQL/SWQL" checkbox at the bottom, select whether your query is SQL or SWQL (the code I gave you was SWQL, but it all depends on what you are doing specifically), and then insert that…

Once again, I know that aLTeReGo will correct me if I mis-state anything: The baselines calculated from Node data (CPU, RAM, etc) will change over time, but they do use the aggregate data. So if you have a box that is hot during the day and cold at night, you're going to get an amalgamation of that. But as time goes on, so…

<BLACK MAGIC VOODOO!! YOU WILL TAINT YOUR SOUL IF YOU PROCEED> I will say that it *is* possible to update things within SQL itself (by the way, SolarWinds *always* runs on SQL. It doesn't go to any other database). So you could run select nodes.nodeid, nodes.caption, nodes.location, nodes.blablah from nodes and pull that…

That was ultimately what resolved it for me. For future reference, ask the tech to look up ticket 454357 - that should point them in the right direction.

Right, but what I want is a screenshot of the trigger CONDITION tab, not the trigger actions. And also please add an action to either email or write to a file so that you can see how all the variables are enumerated in a more neutral output (I say "neutral" because scripts are very syntax sensitive. Pushing to a file…

Hey aLTeReGo I'm just sitting over here smiling and not saying anything!

Corporate standard is IE8. Can't upgrade it on my box.

Nope, I forgot that everyone doesn't have that custom field. Here's the updated SQL: select nodes.caption, Nodes.GroupStatus, nodes.nodeid, nodes.percentloss, a1.downtime from Nodes left outer join (select AlertStatus.ActiveObject as nodeid, CONVERT(varchar, alertstatus.triggertimeoffset/60/60/24) as days,…

I completely missed that sucker in the 10.1 update. This is exactly what we were looking for. Consider this case closed. Thanks! - Leon

you missed the word "where". Your exact addition is: where engines.interfaces > 200 Hope that helps.

This, sir, is black magic voodoo of the darkest sort. Your soul is surely permanently corrupt. And I salute you in respect and admiration.

Thanks for the link. I had actually looked there, but I didn't find the new fields (vbdata1) because they aren't listed on 334, but instead are found on 232. Just FYI. Sadly, I am not finding any other super-secret fields. I was hoping for ${SQL to work in traps, but no such luck. Thanks! - Leon

Nope, it was all done within SolarWinds. No separate utilities, tools, or subroutines needed. Let me know if you get stuck.

PS to everyone: I'm glad this has sparked such a good discussion! Thanks for participating.

I just want to outline the situation I'm in right now, until a fix is created (and I have a suggestion for that, so read on) START: We have a lot of new users due to AD integration (rather than generic accounts) * update the AD GROUP with “view customization” * Then log into SolarWinds as the user (but I don’t have their…

I'd be surprised if it's not in there, but there's always a chance we're making some assumptions about the starting point. Upgrades (unlike hotfixes) will almost always work either way - as a clean install or as an upgrade to an existing system. That said, the typical route is: 1) download the new version to your existing…

So I just tested this: Where ALL are true NodeId = 1 Where NONE are true Node status is up Node status is down Result? Instant ticket (Node 1 is up) Then I tested this Where ALL are true NodeId = 1 Where NOT ALL are true Node status is up Node status is down To your point about the English language, If I recall in the…

We just had this problem (having had it a while ago, ticket # 207458, but without clear resolution). We noticed that the user's account worked fine when we logged into the primary poller, but not when we logged into the Additional Web Server. Things we tried that did NOT work: * deleting the user's info from the…

RichC: I don't think that's the case (pulling up the view to see customer's systems. They would see a view, but it would only be populated with THEIR devices, not the customers. if the view was created in such a way that none of the customer's devices fit, the view would be empty. So again, it's an annoyance, but not the…

I pulled it together using a series of UnDP monitors. I'll get it posted to content exchange shortly.

Brandon: The problem with setting passwords to "never expire" is that we'd fail any security audit which is a deal breaker for many of our customers, not to mention our own internal standards. To all: After a bit of investigation, I came up with 4 possible solutions (at least until SolarWinds solves it internally): *…

I'm not in front of my system right now, but I would create a new field (because you can't change them - :-( grrr! ) that is the long number format rather than integer. That's good for two reasons: 1) it's how I have mine set up 2) it lets you set a threshold when the level is at >95.5 instead of a straight 96 (or…

Ah, so "add the node" means "into SolarWinds" not "into this here list of devices to apply a template". I submit to you that my original premise was true: SAM is being a tease.