UIM 20.4 - Alarm Filters with Operator "in" for hostname do not work (Fixed)

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We are running UIM 20.4

When creating an alarm filter with an Operator of 'in' for the 'Host Name' field it is returning 0 matches.
It happens after creating an alarm filter either via ACL or Alarm windows Edit Filters. 

 

This issue also affects The ACL Alarm Filters in Account Admin

The following error may be visible in the wasp log: 

Jan 04 11:01:41:160 ERROR [http-nio-80-exec-4, com.firehunter.ump.exceptions.DataFactoryException] Incorrect syntax near '('. 
Jan 04 11:01:41:160 ERROR [http-nio-80-exec-4, com.firehunter.ump.exceptions.DataFactoryException] com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near '('. 
 at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:258) 
 at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1535) 
 at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:467) 
 at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:409) 
 at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7151) 
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2478) 
 at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:219) 
 at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:199) 
 at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:331) 

Other Operators such as "is" work fine

Environment

Release : 20.4

Component : UIM OPERATOR CONSOLE - WASP & CORE

Cause

DEFECT in UIM 20.4

Resolution

FIX: alarmviewer-api-20.4.0-TF1.jar fixes this issue. 

• Go to IM and deactivate wasp.
• Go to the OC installation  location. Backup the file alarmviewer-api-20.4.0.jar from the path ~\Nimsoft\probes\service\wasp\webapps\alarmviewer-api\WEB-INF\lib and delete it from the directory
• Download the alarmviewer-api-20.4.0-TF1.jar file attached to the defect.
• Place the alarmviewer-api-20.4.0-TF1.jar in to the path ~\Nimsoft\probes\service\wasp\webapps\alarmviewer-api\WEB-INF\lib
• Activate wasp

 

Additional Information

Note: The old jar file must be removed from the lib folder. 

Note: Preexisting alarm filters will need to be deleted and new filters created after alarmviewer-api-20.4.0-TF1.jar has been loaded. 

This fix is expected to be included in the Feb. update for 20.4.