UIM 20.3 Alarm window Actions menu items result in Request failed with status code 400
search cancel

UIM 20.3 Alarm window Actions menu items result in Request failed with status code 400

book

Article ID: 204503

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

At the Alarm window when trying to perform any of the alarm options available via the Actions list it fails with Request failed with status code 400. 

Environment

Release : 20.3

Component : UIM - OPERATOR CONSOLE

Cause

The alarm Actions functions are dependent upon ems at the primary hub. 

Resolution

Ensure ems is activated at the primary hub. 

Additional Information

OC robot wasp log has:

Dec 04 19:01:01:218 ERROR [http-nio-80-exec-1, com.firehunter.ump.exceptions.DataFactoryException] java.lang.RuntimeException: (120) Callback error, Received status (120) on response (for sendRcv) for cmd = 'dispatcher'
 at com.ca.shift.client.RequestPoolRemoteEndpoint.invoke(RequestPoolRemoteEndpoint.java:39)
 at com.ca.shift.client.RemoteInvocation.invokeEndpoint(RemoteInvocation.java:133)
 at com.ca.shift.client.RemoteInvocation.createInvocation(RemoteInvocation.java:123)
 at com.ca.shift.client.RemoteInvocation.invoke(RemoteInvocation.java:62)
 at serviceProxy$com.nimsoft.events.api.NasAlarmService.assignAlarms(Unknown Source)
 at com.nimsoft.events.client.EmsClient.assignAlarm(EmsClient.java:416)
 at com.ca.alarmviewer.alarms.EmsAlarmProvider.assignAlarms(EmsAlarmProvider.java:187)
 at com.ca.alarmviewer.alarms.AlarmServiceUtils.assignAlarms(AlarmServiceUtils.java:189)
 at com.ca.alarmviewer.alarms.DataFactory.assignGroupAlarms(DataFactory.java:185)
 at com.ca.alarmviewer.controller.AlarmController.assignAlarm(AlarmController.java:279)

If ems is running check the log for the specific action such as assign_alarm

calling assign_alarm callback on NAS
Dispatcher caught unchecked service exception. 
java.lang.RuntimeException: java.lang.reflect.InvocationTargetException

nas 
nimVerifyLogin request verify_login failed (permission denied)
cmdd+assign_alarms failed 

In this case the permission problem was due to ems missing from IM > Security > Probe Administration.

Added ems there with admin * and actions work. 

Attachments