oracle probe giving 'Unable to contact' communication error(80040402) on saving modifications

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)
• Unified Infrastructure Management for Mainframe

Issue/Introduction

Strangely, only the oracle probe is giving a communication error while saving/applying changes in configuration.

   Unable to contact /<domain>/<hub>/<robot>/controller communication error(80040402)

It was working fine earlier. Port used by Oracle probe (48008 in this case ) is open connecting on telnet. Tried cold start and redeploying configuration but still no luck. No obvious/related errors in the oracle or controller logs at loglevel 5 or 6 (controller).

Environment

• Release: 20.3 or higher
• Component: UIM - ORACLE
• oracle: v5.45
• robot: 9.33HF1

Cause

• corrupt oracle_monitor.cfg file

Resolution

Altered some small errors, e.g., extra (unnecessary) spaces in the messages section for custom-defined messages for a few custom checkpoints within the oracle_monitor.cfg. After a change to a profile when saving by clicking Apply or Ok , which would restart the probe, the oracle probe would crash and throw a communication error which would also cause the robot to restart.

Now the oracle probe doesn't crash nor hang when you click Apply or OK to save the a change to a profile, nor does the robot (controller) restart when the oracle probe crashes.

Additional Information

Here is an example of the Windows (Application Log) events when the controller AND the oracle probe crashed and the probe modifications could not be saved:

oracle probe

Faulting application name: oracle_monitor.exe, version: 0.0.0.0, time stamp: 0x5e54b7f9
Faulting module name: ntdll.dll, version: 10.0.14393.4530, time stamp: 0x60e33cac
Exception code: 0xc0000005
Fault offset: 0x00000000000197ed
Faulting process id: 0xc34
Faulting application start time: 0x01d8020e6313ccf1
Faulting application path: C:\Program Files (x86)\Nimsoft\probes\database\oracle\oracle_monitor.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 8e01a107-54be-48b3-b134-e34cdd6c6ecd
Faulting package full name: 
Faulting package-relative application ID:

Controller probe

Faulting application name: controller.exe, version: 0.0.0.0, time stamp: 0x60c70889
Faulting module name: controller.exe, version: 0.0.0.0, time stamp: 0x60c70889
Exception code: 0xc0000409
Fault offset: 0x000000000018b074
Faulting process id: 0x1d70
Faulting application start time: 0x01d8020e8bd225bd
Faulting application path: C:\Program Files (x86)\Nimsoft\robot\controller.exe
Faulting module path: C:\Program Files (x86)\Nimsoft\robot\controller.exe
Report Id: d4dea6ce-c1b3-449b-a7f0-6a16ca3135ee
Faulting package full name: 
Faulting package-relative application ID:

Note:

Be careful and confirm the final configuration file if cutting and pasting changes into a <probe>.cfg, as sometimes it creates unwanted spaces or characters/special characters/tabs and it's sometimes hard to identify/locate them even with Notepad++.

In this .cfg file you could not see any odd symbols, but a few of the custom messages had too many spaces in them. Once eliminated, the oracle probe no longer threw the communication error.