wasp cannot obtain connection string from data_engine and fails to start
search cancel

wasp cannot obtain connection string from data_engine and fails to start


Article ID: 145755


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


Wasp probe fails to start on CABI and UMP robots with the following error in the wasp.log

[main, com.nimsoft.nimbus.probe.service.wasp.Probe] Cannot obtain connection string from data_engine
[main, com.nimsoft.nimbus.probe.service.wasp.Probe] (1) error, Received status (1) on response (for sendRcv) for cmd = 'get_connection_string'
 at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:615)
 at com.nimsoft.nimbus.NimSessionBase.sendRcv(NimSessionBase.java:561)
 at com.nimsoft.nimbus.NimClientSession.send(NimClientSession.java:171)
 at com.nimsoft.nimbus.NimRequest.sendImpersonate(NimRequest.java:264)
 at com.nimsoft.nimbus.NimRequest.send(NimRequest.java:219)
 at com.nimsoft.nimbus.probe.service.wasp.Probe.getConnectionStringFromDE(Probe.java:904)
 at com.nimsoft.nimbus.probe.service.wasp.Probe.doit(Probe.java:302)
 at com.nimsoft.nimbus.probe.service.wasp.Probe.main(Probe.java:110)

Data_engine probe utility get_connection_string callback fails with the following error in the data_engine.log

0 de: fopen failed for "Ceritificate.pemFilePath"
de: getCheckSumForFile - nimMD5CheckSum calculation failed
0 de: crypt key is empty
0 de: No crypt key


Release : 9.0.2

Component : UIM - UMP


Double quotes were added to the path in the UIM server's robot.cfg cryptkey variable and path cannot be read.

Example: "C:\Nimsoft\security\certificate.pem"


Removed the double quotes from the cryptkey path on the UIM server's robot.cfg.

Example change from "C:\Nimsoft\security\certificate.pem" to C:\Nimsoft\security\certificate.pem