Issue detected at Never

Hi All,

Can anyone tell me why i'm seeing at least 3 of our servers displaying issues at "Never"

Error on ISSSAPPSSQL33 at Never

An issue has been detected at Never on Windows 2008 R2 Server device named ISSSAPPSSQL33 (IP: 192.168.224.194, DNS: ISSSAPPSSQL33)

Where is Never? it sounds a little scary...

I'm getting management moaning because these servers don't have a problem. Do you think it could be restarting Orion services has caused this?

Adam

Find more posts tagged with

Alert

npm

never

event

Accepted answers

All comments

jlim13

Did this happen just after restarting the Orion service? If so, please try to do another restart, it could be that there were some components that did not start successfully causing this behavior.

FormerMember

I cannot be sure when this occurred a user who receives alerts noticed it. I'll keep an eye on it and when I do any server reboots or service restarts i'll see if it happens again. I was hoping someone may have seen this before and would know a definitive answer to the "Never" location.

geoff.hubbard

Could it be the date/time variable messing up for some reason?

cahunt

Please elaborate - is this text from a Syslog, Trap or an Alert?

And assumption is that this is coming from NPM about the server - Just to confirm it is NOT coming from SAM about your SQL?

*SNMP or WMI monitoring on your server?

FormerMember

Yes the three nodes I received e-mail alerts about use SAM monitoring for the SQL databases. It does appear that there are problems on these nodes so I will disable the application monitoring until I can find out what is going on, hopefully that will stop these errors. Thanks

cahunt

And your alert conditions are?

*Asking mainly due to noticing this is in NPM forum, but reference to a sql server could mean app or db issues depending*

FormerMember

These are just standard alert conditions, (default).