Issues and error messages in CMDB Portal and solutions
If the CMDB Portal displays error messages or shows unexpected behavior, the following solutions may help you address them.
Issues and possible solutions
Error message or Issue | Action | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ERROR (525): File is not allowed to be uploaded. | If any of your custom applications use the NE or NOE APIs, you must upgrade the API JAR files to BMC Helix CMDB 21.05 compatible version. Download the following JAR files from BMC Electronic Product Distribution (EPD) site:
| |||||||||||||
You are not able to launch the CMDB Portal through Mid Tier. | You must check whether the redirect URL is as described in Configuring-the-URL-to-access-CMDB-Portal-through-Mid-Tier. | |||||||||||||
You are not able to access CMDB Portal through BMC Helix Single Sign-On. | You must check whether the BMC Helix Single Sign-On configuration settings are correct. In BMC Helix Single Sign-On, select OAuth2 and ensure that the redirect URI for CMDB is in the following format: http://<host:port>/_rsso/oauth/callback. For more information about configuration settings for BMC Helix Single Sign-On, see Configuring BMC Helix SSO for applications hosted on different domains and Realms | |||||||||||||
You enter credentials to access CMDB Portal through Mid Tier and you see the CMDB login page. | You must ensure that BMC Helix Single Sign-On is configured correctly to the Jetty. For information, see Manually integrating BMC Helix Single Sign-On with Jetty server. | |||||||||||||
You enter credentials to access CMDB Portal through Mid Tier and you see the BMC Helix Single Sign-On login page. | You must check your BMC Helix Single Sign-On configuration settings to make sure the domain name is set correctly in the realm settings in the BMC Helix Single Sign-On adminstration console. For information, see Manually integrating BMC Helix Single Sign-On with Jetty server | |||||||||||||
The following error message is displayed: Something went wrong. | 1. In your browser developer tools, open the Console tab by following keyboard shortcuts or menu paths.
2. In the developer tools of your browser, click the Network tab to view the network activity and REST API calls. 3. View the API requests and responses in the network activity. 4. Check for the following:
5. Share your findings with BMC Support. | |||||||||||||
The following error message is displayed: Unknown http error. |
If none of these have a problem, then contact Support. | |||||||||||||
When editing an instance, you cannot see links or edit relationships | Check the default web path and server name as mentioned in Configuring-the-URL-to-access-CMDB-Portal-through-Mid-Tier. | |||||||||||||
Health and Integrity on the dashboard are not displayed. | The administrator must collect the dashboard utility logs and then contact Support. | |||||||||||||
Some screens such as statistics RE, NE jobs, data sources, and CI, show errors in status. | Check whether the datasource utility is running, and match the count with the rest API. | |||||||||||||
The following error message is displayed: | Check the default web path settings as described in Configuring-the-URL-to-access-CMDB-Portal-through-Mid-Tier. | |||||||||||||
If you click a CI, CMDB displays a URL instead of opening it in CMDB Explorer. | Copy the URL and share it with Support. | |||||||||||||
The following error message is displayed: | Occurs when you run the dashboard utility manually on CentOS. Workaround: Set the | |||||||||||||
The following error message is displayed: this.config is undefined. | Occurs sometimes on the Create Query for Dynamic Service Modeling page, when you refresh the page while creating a query. This error does not affect functionality. However, do not refresh the page while creating a query. | |||||||||||||
Newly configured CMDB Portal does not load and gives error: HTTP Status 404 - Not Found. | Occurs because the active link CMDB:LaunchCMDBConsole has a hardcoded URL that includes default Mid Tier context /arsys. Workaround: Modify the active link manually with the correct Mid Tier context. |
Related topics
Configuring-the-URL-to-access-CMDB-Portal-through-Mid-Tier