nickburns186

No mention of it affecting others. I feel like it is indeed a bug in the latest update. Hopefully we find out soon. 

Appreciate it.

I see. My problem is, when taking out the as [User] part to solve my other issue, the syntax becomes invalid in Solarwinds eyes. Do you see the same thing if you take that out as well? Maybe I'm missing some formatting as well.

Are you saying where I have circled below? If so I did try that.

Thanks. Just tried taking out AS [User] it throws an invalid syntax error. 

Custom query on classic. That's just it, the error is vague. Just says problem with column.

Interesting. I don't have any agents deployed though this may help others. Thank you!

Updated 2022.3 to 2023.1 last week. No issues during upgrade and only issue so far post upgrade is seeing constant SAM and NPM database maintenance messages saying it hasn't run in days. I ran it manually yesterday but the message for SAM still persists. I intend on opening up a case today. 

Thanks for replying. What Velo release are you on? 

Probably time to open a ticket.

If you are monitoring the device with SNMPv3 then you should be able to receive V3 traps. Have you compared the SNMP creds/encryption on the device and in Solarwinds to make sure they match? We have hundreds of devices sending V3 traps.

Same here. See failures on deleting temp sys files but completes otherwise.

If I'm swapping out exact hardware, then a simple rediscover is usually all thats needed. No need to delete first.

Yeah, that query seems to be killing SQL for some reason. Seeing same thing.

Add this: Where DateTime >= ADDHOUR(-1,DateTime) You'll need to make sure your select clause is set to * though. Edit: Can't select * so maybe top 100

Its gone. https://thwack.solarwinds.com/product-forums/network-performance-monitor-npm/f/forum/96523/after-update-2022-3-no-syslog-available-as-widget

Nice! Thanks for posting.

I'm not sure why you are seeing only traps instead of syslog. Interesting.

This happened to us after the latest update to 2022.3.0. Had to run a manual rediscover on all APC UPS's in our environment to get polling back but otherwise fine so far.

I added the node caption field as well for anyone interested. We just need some color. SELECT TOP 10 let.Name AS [Message Type] ,Level AS [Severity] ,nod.Caption AS [Node] ,TOLOCAL(DateTime) AS [Log Time] ,SUBSTRING(Message,1,100) AS Message…

Thanks

From what I read, we don't get that widget/functionality anymore unless you upgrade OLV to Log Analyzer. Thats insane.

Same. Mine has been this way for months. Same for the updates & evals tab.

I've never seen needing to import a MS cert for 365 SMTP, but I'm researching. Anyone else had to do this??

Unfortunately, the only way we could get it to work is via port 25, which isn't a solution. It all points to TLS negotiation being the issue so I'm just not sure.

I've tried it checked and unchecked so far with no luck, and it is a normal user mailbox created just for this purpose.

We've hit this recently with third party software accessing DC's with WMI. A LOT of people have due to a recent Windows patch it seems. I haven't heard a single viable solution at this point.

Same thing. As usual.

Maybe we're talking about different things though. The event summary isn't part of the PCU widget so I should clarify that so you know where I'm coming from. I see what you are saying though, via polling it may kick on/off battery quick enough where a polling cycle misses it versus a trap. I've been used to using universal…

I appreciate that and realize that, but I'm also trying to understand the intended functionality of the PCU widget and what it takes to make it function. I made a custom query with custom pollers only to find this widget.