-
Title
Issue with Alarm Activity while adding custom alert -
Description
Message:<HTML><HEAD><TITLE>400 Error: at least one monitored entity must be defined in com.quest.adk.configuration.alarmaction.MonitoredEntityCriterion@a3a9f91</TITLE></HEAD><BODY BGCOLOR="#D1E9FE"><H2>400 Error: at least one monitored entity must be defined in com.quest.adk.configuration.alarmaction.MonitoredEntityCriterion@a3a9f91</H2><HR><ADDRESS><A HREF="http://nnnnn.net">D. nnnnnnn with Android support (aka Acme.Serve) Version 1.105, $Revision: 1.267 $</A></ADDRESS></BODY></HTML>Source:009A796A (Spotlight.005A696A) 10.0.2.7001Call stack:009A796A (Spotlight.005A696A) 10.0.2.7001008BC3EB (Spotlight.004BB3EB) 10.0.2.700100A5F9EC (Spotlight.0065E9EC) 10.0.2.7001005A3F19 (Spotlight.001A2F19) 10.0.2.7001Alarm Activity causing error: at least one monitored entity must be defined (on any alarm) -
Cause
bug fixed in 10.5 -
Resolution
It seems that in the past windows and SQL Server connections were deleted for one of the connections, but there were alarm actions pertaining to these connections still there. This error is a known bug in Spotlight 10.0 and will be fixed in the 10.5 release.
You should be able to delete the problematic actions and click OK in the alarm action editor.
The actions you should delete might be callled i.e:
• Alarm Backup - Days Since Last Full Backup for nnn
• Alarm Databases - SQL I/O Errors for nnnn
• Alarm I/O Wait Time for nnn
• Alarm Network - SQL Server Packets Error Rate for nnn
• Alarm SQL Agent - Status for nnn
• Alarm VMware Overhead for nnn
Where nnn is the connection that was previously deleted.
-
Defect ID
SOSSE-2491