USM on secondary UMP fails with unknown error

Document ID : KB000077202
Last Modified Date : 18/04/2018
Show Technical Document Details
Issue:
Trying to access the USM portlet in a secondary UMP fails with the following error message:

An unknown error has occurred.
Refreshing your browser may resolve the issue.

Details:
com.firehunter.ump.exceptions.DataFactoryException : There are no alarm services available!
Please check the log for more information.
Stack Trace:
(1) error, There are no alarm services available!
at com.nimsoft.events.client.EmsClient.ensureAtLeastOneAlarmServiceAvailable(EmsClient.java:716)
at com.nimsoft.events.client.EmsClient.getAlarms(EmsClient.java:50)
at com.firehunter.usm.alarms.EmsAlarmProvider.getAlarmsResult(EmsAlarmProvider.java:93)
at com.firehunter.usm.alarms.EmsAlarmProvider.getAlarmUpdates(EmsAlarmProvider.java:60)
at com.firehunter.usm.AlarmUtils.getAlarmsFromDb(AlarmUtils.java:320)
at com.firehunter.usm.AlarmUtils.getAlarms(AlarmUtils.java:82)
at com.firehunter.usm.DataFactory.getAlarms(DataFactory.java:1078)
at com.firehunter.usm.DataFactory.getAlarms(DataFactory.java:1070)
Environment:
UIM 8.51
UMP 8.51
 
Cause:
There is a version dependency between webservices and ump. The webservice_rest package version needs to match the ump wasp version otherwise you will get the message that you have reported.
Resolution:
Please double-check the documentation for multiple UMP servers configuration:

https://docops.ca.com/ca-unified-infrastructure-management/8-5-1/en/installing-ca-uim/install-unified-management-portal-ump/configure-multiple-ump-servers

If the issue still occurs please do the following:

On the UMP robot please open the controller GUI > Status > Installed Packages and check if webservices_rest is installed. If so, please make sure it's v8.51, as the wasp. If it's not there, please distribute it from the Archive.

Restart the wasp and check if the issue reoccurs.

If this doesn't work:

1. Deactivate the wasp probes on both UMP robots
2. Delete the <installPath>\Nimsoft\service\wasp\work directory and its contents on both UMP robots (when the wasp probe is restarted it will recreate this directory and repopulate it with current information)
3. Activate the wasp probe on the primary UMP robot and when it has a PID and port, activate the wasp probe on the secondary UMP robot
4. Clear the browser cache from the beginning of time then try logging into the secondary UMP
Additional Information:
https://docops.ca.com/ca-unified-infrastructure-management/8-5-1/en/installing-ca-uim/install-unified-management-portal-ump/configure-multiple-ump-servers

https://comm.support.ca.com/kb/usm-fails-to-load-dashboard-after-upgrade-to-851/kb000006393