prawij

Could well be, there used to be a bug in WPM that did the same thing with event times - they fixed that one with a patch/hotfix.

Hi bluefunmetal, Thanks for the response, actually we didn't get around to fixing this. I'm afraid I'm unfamiliar with the SDK so not sure what I'm doing wrong. I changed the --sort by age line to "order by ToLocal(v.lastsync) desc" but time is still shown in UTC. When I tried modifying the first mention of v.lastsync to…

Issue was resolved by offsetting the three reports to run 5 minutes apart. If you are having trouble with multiple instances of the same report being sent out - check you don't have them scheduled for the same time.

No resolution as of yet, case # for the triple scheduled report issue is 1003398, just got the initial email response requesting diagnostics at 9PM, will send them on Monday.

Please also enable 2 factor authentication for VM actions when this is enabled

Expand the node you want to delete a volume on (the little triangle to the left of the check box for the node. Then it will expand to show all volumes and interfaces. Mouse over each volume until you find the one (or several) that are showing as red/unresponsive. Select Delete from the action bar above the field names.…

Hi Serena, Had some feedback for NPM/Orion in general, hope it's OK to include here - we recently got the notification in our Orion GUI that product upgrades were available to install... However, when looking at the support portal, they are all still in RC2 state - we definitely don't install those in Prod anymore. Did…

Upgraded to NPM 12, SAM 6.24, SRM 6.3, NTA 4.2, upgrade process itself was smooth. However had to open a ticket today re: a scheduled report that fires three times (sending out three emails) instead of the expected once. Definitely nothing like the complete horror show that NPM 11.5 was. Oh, also had a problem with the…

Using Core 2015.1, NPM 11.5 Entering the code in a Custom SWQL Query resource I get this response when I enter that query: "Error: A query to the SolarWinds Information Service failed."

OK that works without an error - gives me 22 entries that look like this: NOW LOCAL3/11/2015 7:43:33 AM3/11/2015 3:43:33 AM3/11/2015 7:43:33 AM3/11/2015 3:43:33 AM3/11/2015 7:43:33 AM3/11/2015 3:43:33 AM3/11/2015 7:43:33 AM3/11/2015 3:43:33 AM3/11/2015 7:43:33 AM3/11/2015 3:43:33 AM3/11/2015 7:43:33 AM3/11/2015 3:43:33…

Any idea when we will get the points posted for the first two weeks of this mission (answering the 10 questions)?

Diagnostics uploaded, ticket updated.

We are using this code, however v.LastSync is returning UTC time instead of our current timezone (EDT). Is this a bug? Or can we modify the SWQL code to subtract 4 hours from the time v.lastsync returns?

I'd like to be able to have multiple mutes and unmanagement periods available for a single node. Currently, if we have say three maintenance windows coming up for a single server, I have to use the mute scheduling for one of them, the unmanage schedule for the 2nd period, and then make a note to go back in after the mute…

Found another possible bug: Case # 1004357: When using a custom time period for the Events resource (http://solarwinds/Orion/NetPerfMon/Events.aspx) the end time is offset by 4 hours when the results are displayed: To replicate: 1. Click on Events 2. Set Time period to custom, enter begin and end date/time 3. Click refresh…

What I've found is that the DPA Orion integration component that's installed on the primary poller along with NPM 12/SAM 6.24 was affecting our alerting (some alerts were working, others weren't). We don't have DPA installed, I uninstalled the DPA Orion integration piece and our alerting is working now. Also have the…

"Additionally the ability to cancel scheduled mutes as well" This can be done now - after scheduling a mute or un-manage, go into the Node Details view and it should show the future scheduled mutes/unmanage periods, you can click "Cancel" on those to remove them:

So on the triple report problem, we had three different reports scheduled to fire at 6AM, looked at the logs with support this afternoon and it looked like it was getting confused with the timing of all three at once, we've offset each one now so we send one at 6AM, one at 6:05AM and one at 6:10AM, will find out if that…

Good Afternoon Serena, Just double checking prior to upgrading that the offline installer packages are synced up and have the latest available online updates/ Orion 2018.2 hot fix 3 etc? The offline installer in the portal shows an update date of May 31st, which was before hotfix 3 I believe? Thanks.

There seems to be many components that I can access/sort by in the Report Writer tool that I cannot do with the web console. Specifically any custom properties I've defined. It's not so much a problem for me as I always use the Report Writer tool, however it's a pain because I can't give that capability to some of our…

If you don't have access to the Orion GUI to deactivate your existing licences you will need support to reset them for you.

Just to clarify, you were told by SW support that the DB is safe?

Here is the link to the trial version, if you don't have existing access to the customer portal: https://www.solarwinds.com/network-performance-monitor/registration That should install with a 30 day eval license.

I've had this happen in the past, it was just a visual bug but things were solid underneath. Fix was for SW to modify the db to get rid of an outstanding installer.

Does this mean that those on 2020.2.1 without hot fixes aren't affected? As it was presumably released after "Orion Platform v2020.2 with no hotfix or 2020.2 HF 1"? So in terms of chronology: 2020.2 2020.2 HF1 2020.2.1 - this version is "safe"? Obviously we'll apply HF2 when available but trying to understand the risk…

Just did ours, from 2020.2.1 HF2, one primary and four additional pollers, 9 Orion components, took about 1.5 hours via centralized upgrade. Primary sat at the config wizard step for a while but that's usual.

Yes, personally I think the Security Advisory page should be updated to emphasize that 2020.2.4 should be upgraded to immediately. And we should have received communications from SolarWinds that 2020.2.4 is available - back on the 25th of January.

Sorry to hear that, yes if this was a normal HF I would have waited at least a month or two to see what kind of bugs and defects it introduced but sadly our hands were forced in this case.

Yes that's classic SW behavior, not updating the release date of an offline installer package even if it contains a newer release. We are also waiting for the date to be updated, running it in the hopes the actual files are in fact updated is not an option.

I would add to this: - Waiting on phone hold for 2 hours then getting disconnected - 10,000 Thwack points and a T-shirt