CA UIM / CABI - Unable to open the CABI UIM Summary dashboard. No dashboard found with path: /public/ca/uim/dashboards/common/uim_summary

Document ID : KB000107576
Last Modified Date : 23/07/2018
Show Technical Document Details
Issue:
When accessing the UIM Summary dashboard via the CABI portlet using the Chrome broswer, we receive the following error:

No dashboard found with path: /public/ca/uim/dashboards/common/uim_summary 
Click Edit Dashboard button to create dashboard or click Options -> Preferences to update path 

Accessing the portlet via another browser (Internet Explorer) works as expected. 
Environment:
- UIM 8.51 
- cabi (bundled probe) v3.20 
- ump_cabi v3.20
- uim_aws_dashboards v2.40 
- uim_cabi_health_reports v1.20 
- uim_unified_reporter v1.02 
Resolution:
1. Open the Chrome browser, go to Settings -> Advanced -> Content Settings. 

2. Select Cookies and add the cabijs URL as an allowed site under the "Allow" section. 

3. Select Flash and add the cabijs URL as an allowed site under the "Allow" section. 

Note: You can find the cabijs URL via the UMP CABI portlet -> Preferences -> CABI URL (full). 

4. Once the above changes have been made, relaunch the Chrome browser and clear browser cache. 

 
Additional Information:
- If this still fails, within Chrome go to More tools -> Developer tools -> Within the developer tools section select Console, reproduce the issue and review the developer tools output. 

- If you receive the following error: 

No dashboard found with path: /public/ca/UIM/dashboards/common/uim_summary 
Click Edit Dashboard button to create dashboard or click Options -> Preferences to update path 

Notice the UIM is in uppercase, this is a known case-sensitivity issue, the path to the dashboard as shipped out of the box contains /public/ca/UIM and should be /public/ca/uim. Select the CABI portlet preferences -> Wait for the Dashboard Path drop-down to be available -> Open the drop-down menu and select: UIM Summary (/public/ca/uim/dashboards/common/uim_summary). Save the changes and retest the issue.