search cancel

UIM 20.3 CABI Bundled - can't access dashboards " Data Access Error"

book

Article ID: 202554

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After upgrading UIM to 20.3 with CABI bundled 4.30 there is a problem to access Operator Console with error message:

(!) Data Access Error - Dashboard failed to load

Environment

UIM 20.3

CABI bundled 4.30 and Wasp

Cause

- Wrong path for the certificate.pem in the cryptkey variable in the robot.cfg file on the cabi server.

Resolution

Please follow up these instruction below that will lead you to resolve the issue with CABI dashboard:

 
Please review the UIM installer created certificate file (certificate.pem) in the security folder (C:\Program Files (x86)\Nimsoft\security\certificate.pem) as it is the symmetric key that is shared then used for communication with data_engine probe.

Copy certificate file to the remote UMP, UR, and CABI robots and provide the location of the file in the robot.cfg file by editing it in a text editor and adding into it as following (cryptkey = C:\Program Files (x86)\Nimsoft\security\certificate.pem.
 

Furthermore, if any impacted probe is not on the same computer where data_engine is present, copy the generated certificate file from UIM server (C:\Program Files (x86)\Nimsoft\security\certificate.pem) to the robot computer (where data_engine is not available) and update the robot.cfg file (C:\Program Files (x86)\Nimsoft\robot\robot.cfg) with the certificate (C:\Program Files (x86)\Nimsoft\security\certificate.pem) file location on that computer as mentioned above.
 
Note: No need to restart the robot.

Additional Information

As this is a part of the installation process and configuration of UIM 20.3, please refer to the following documentation below and proceed as require:

UIM 9.0.2 - UIM 20.3 Operator Console Home Page Shows "Data Access Error"

Installation Process Steps

Configure the robot.cfg File

 

And additionally:

- Some sites use third-party cookies to load their pages and du to organizational policy these cookies are blocked by default.

- Enabled flags related to same-site cookie(Chrome://flags).

- It can be also related the UMP session timeout when the OC is opened from UMP as it uses the same session.