Unable to install bundled cabi 4.1: Received status (4) on response (for sendRcv) for cmd = 'probe_config_get' name = 'wasp'

book

Article ID: 133769

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After deploying cabi 4.1 to a windows robot cabi won't start and error seen in log is:


giu 24 15:47:18:510 [main, cabi] request failed: (4) not found, Received status (4) on response (for sendRcv) for cmd = 'probe_config_get' name = 'wasp'

giu 24 15:47:18:510 [main, cabi] (4) not found, Received status (4) on response (for sendRcv) for cmd = 'probe_config_get' name = 'wasp'

 at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:622)

    at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:573)

    at com.nimsoft.nimbus.NimClientSession.send(NimClientSession.java:173)

    at com.nimsoft.nimbus.NimRequest.sendImpersonate(NimRequest.java:264)

    at com.nimsoft.nimbus.NimRequest.sendImpersonate(NimRequest.java:237)

    at com.nimsoft.nimbus.NimRequest.send(NimRequest.java:208)

    at com.ca.cabi4uim.utilities.ProbeUtils.request1(ProbeUtils.java:383)

    at com.ca.cabi4uim.utilities.ProbeUtils.request(ProbeUtils.java:391)

    at com.ca.cabi4uim.utilities.ProbeUtils.waspConfigGet(ProbeUtils.java:234)

    at com.ca.cabi4uim.utilities.ProbeUtils.waspConfigGetAndHandleKeyNotFoundCondition(ProbeUtils.java:661)

    at com.ca.cabi4uim.utilities.ProbeUtils.isWaspSaaS(ProbeUtils.java:629)

    at com.ca.cabi4uim.Probe.setupcabi(Probe.java:371)

    at com.ca.cabi4uim.Probe.initOnTimer(Probe.java:700)

    at com.nimsoft.nimbus.NimProbe.doForever(NimProbe.java:418)

    at com.ca.cabi4uim.Probe.run(Probe.java:892)

    at com.ca.cabi4uim.Probe.main(Probe.java:123)

giu 24 15:47:23:401 [main, cabi] nimEx.getCode()=4, nimEx.getMsgForCode()=not found, nimEx.getMessage()=Received status (4) on response (for sendRcv) for cmd = 'probe_config_get' name = 'wasp'

Environment

Release : 9.1.0

Component : UIM - CABI Bundled 4.1

Resolution

We have seen this issue resolved after a clean reinstall of cabi and after having removed the current install folder and removed the existing DB tables:

Follow the instruction described in this article

Additional Information

CAUIM CABI - How to Uninstall / Reinstall Bundled CABI