Release notes > Known issues, limitations, and workarounds

Known issues, limitations, and workarounds

This release has the following known issues and limitations.

Important This list of known issues was created on November 09, 2017. For the most up-to-date list, always refer to UCMDB Browser 4.15.1 Release Notes.

UCMDB Browser

ID Issue
QCCR1H118730 Currently, UCMDB Browser 4.15.1 FIPS mode is supported only with one of the following web browsers: Microsoft Internet Explorer 11 or later versions, and Mozilla Firefox latest versions.
N/A

(UCMDB Browser embedded version only) UCMDB Browser version 4.15.1 can be embedded only in the UCMDB server version 10.33.

Workaround If you do not want to upgrade the UCMDB server to version 10.33, move the UCMDB Browser embedded to UCMDB Browser Standalone.

N/A

UCMDB 10.33 Admin UI cannot be accessed with embedded UCMDB Browser 4.15.1.

Workaround To fix the issue, follow these steps:

  • Single tenant environment

    1. Go to JMX Console > UCMDB:service=Settings Services > getInternalSetting.
    2. In the key field, enter mam.common.secure.communication.
    3. Click Invoke.
    4. Set the value of the mam.common.secure.communication setting to False.
    5. Go to JMX Console > UCMDB:service=Settings Services > getInternalSettings.
    6. Click Invoke.
    7. Go to the mam.common.secure.communication setting, and make sure that the value is False.
    8. Restart the UCMDB server.
  • Multi tenant environment

    1. Go to JMX Console > UCMDB:service=Settings Services > getInternalSetting.
    2. In the key field, enter mam.common.secure.communication.
    3. Click Invoke.
    4. Set the value of the mam.common.secure.communication setting to False.
    5. Go to JMX Console > UCMDB:service=Settings Services > getInternalSettings.
    6. Click Invoke.
    7. Go to the mam.common.secure.communication setting, and make sure that the value is False.
    8. Go to JMX Console > UCMDB:service=Packaging Services >undeployPackages.

    9. In the packagesNames field, enter dynamicSettings.zip.
    10. Click Invoke.
    11. Restart the UCMDB server.

QCCR1H119209

UCMDB Browser cannot be installed on the JBOSS server.

Workaround To fix the issue, follow these steps:

  1. Open the ucmdb-browser.war > WEB-INF > web.xml file in a text editor.
  2. In the following lines, identify the sections similar with the ones that are highlighted in red, and replace each of them with four spaces (press the Spacebar four times).

            <init-param>
                <param-name>mode</param-name>
                <param-value>SAMEORIGIN</param-value>
            </init-param>
        </filter>
        <filter-mapping>
                <filter-name>ClickjackingFilterSameOrigin</filter-name>
                <url-pattern>/*</url-pattern>
        </filter-mapping>
  3. Save the file.
  4. Connect to the UCMDB server using HTTP protocol.

  5. Start the JBOSS server.

Note If the above steps do not fix the issue, delete the following .JAR files from the ucmdb-browser.war > WEB-INF > lib folder, and then start the JBOSS server:

  • jetty-continuation-9.2.10.v20150310

  • jetty-http-9.2.10.v20150310

  • jetty-io-9.2.10.v20150310

  • jetty-servlets-9.2.10.v20150310

  • jetty-util-9.2.10.v20150310

N/A

(UCMDB Browser embedded version only) UCMDB Browser version 4.14 can be embedded only in the UCMDB server version 10.33.

Workaround If you do not want to upgrade the UCMDB server to version 10.33, move the UCMDB Browser embedded to UCMDB Browser Standalone.

N/A

(UCMDB Browser embedded version only) UCMDB server version 10.33 does not support embedded UCMDB Browser versions older than the UCMDB Browser 4.14.

Workaround Upgrade the UCMDB Browser embedded to version 4.14.

N/A

(UCMDB Browser embedded version only) UCMDB Browser version 4.13 can be embedded only in the UCMDB server version 10.32.

Workaround If you do not want to upgrade the UCMDB server to version 10.32, move the UCMDB Browser embedded to UCMDB Browser Standalone.

N/A

(UCMDB Browser embedded version only) UCMDB server version 10.32 does not support embedded UCMDB Browser versions older than the UCMDB Browser 4.13.

Workaround Upgrade the UCMDB Browser embedded to version 4.13.

QCCR1H113157

The language of the system categories is the one used when the UCMDB Browser is deployed. This is because the system categories are deployed only once, on the first login, using the current locale. On subsequent logins, the system categories are not re-deployed, so the name is not updated either.

Workaround To change the language of the system categories:

  1. Stop the Tomcat.
  2. Change the locale.
  3. Restart the Tomcat.

Note If you change the language, all the users that are connected to the same UCMDB Browser instance will view the system categories with the updated language.

QCCR1H114520

LW-SSO fails to work with the new-ui dashboard when UCMDB Browser is accessed.

Workaround If you deploy UCMDB Browser in your own Tomcat, for Tomcat 8 the following line should be added to the <Tomcat_installation_folder>/conf/context.xml file:

<CookieProcessor className="org.apache.tomcat.
util.http.LegacyCookieProcessor" />
QCCR1H111354

(Safari only) The export of reports/CIs/widgets in the PDF format does not work on Safari.

Workaround Check the address bar and if it is marked with Pop-ups blocked, allow the pop-ups for this site.

QCCR1H112827

When a UCMDB server is reconfigured to use a new schema, the new schema has the OOTB packages deployed at the UCMDB server startup. If a standalone UCMDB Browser is already connected to the UCMDB server, the Browser's packages are not present in the new schema.

Workaround Restart the UCMDB Browser Tomcat in order for the Browser's packages to be redeployed on the new schema.

QCCR1H113171

Sometimes, when SSL is configured and OpenJDK is used, the UCMDB Browser may become unresponsive. This is because the hand shake between the UCMDB Browser server and the browser client fails due to unnamed elliptic curve algorithm.

Workaround Follow these steps to resolve the issue:

  • If Tomcat is started by invoking .\ucmdbbrowser\bin\startup.bat:

    1. Create the setenv.bat file (if one has not already been created).
    2. Add the set CATALINA_OPTS="–Dcom.sun.net.ssl.enableECC=false" line to the setenv.bat file.

      Note If the variable CATALINA_OPTS already exists, just append the –Dcom.sun.net.ssl.enableECC=false value to the variable.

    3. Restart the Tomcat server.

  • If Tomcat is started as a service:

    1. Run the CMS-Browserw.exe file (or the tomcat7w.exe file).

    2. In the dialog box that opens, go to the Java tab, and add –Dcom.sun.net.ssl.enableECC=false in the Java Options container.

    3. Restart the Tomcat server.

QCCR1H106108 (UCMDB Browser embedded version only) The UCMDB Browser version 4.10 can be embedded only in the UCMDB server version 10.30.
QCCR1H113343 (UCMDB Browser embedded version only) The UCMDB Browser version 4.12 can be embedded only in the UCMDB server version 10.31.
QCCR1H106107

(UCMDB Browser embedded version only) The UCMDB server version 10.30 does not support embedded UCMDB Browser versions older than the UCMDB Browser 4.10.

Workaround Move the UCMDB Browser embedded to UCMDB Browser Standalone.

QCCR1H106107

(UCMDB Browser embedded version only) The UCMDB server version 10.31 does not support embedded UCMDB Browser versions older than the UCMDB Browser 4.12.

Workaround Move the UCMDB Browser embedded to UCMDB Browser Standalone.

QCCR1H107689 Currently it is not possible to load the federated CITs' icons from the remote server.
QCCR1H110354

On Internet Explorer 11, sometimes the loading animations get stuck.

Workaround Restart Internet Explorer.

QCCR1H111026

The port number of UCMDB Browser URL changes to 8143 when Configuration Manager 10.22 is connected to UCMDB Server 10.30, resulting that the UCMDB Browser is no longer available.

After Configuration Manager is installed, UCMDB Browser URL becomes https://<server name or IP address>.<domain name>:8143/ucmdb-browser/, which is the URL of the UCMDB Browser embedded in CM.

Workaround After Configuration Manager is installed, make sure you change the port number of UCMDB Browser URL from 8143 back to 8443 (go to UCMDB UI > Administration > Infrastructure Settings Manager, locate the UCMDB Browser URL setting by searching Name with a keyword Browser, and then change the port number from 8143 to 8443 and save the change.

QCCR1H111352

Sometimes, the export of a report fails with the following error message: "Cannot initialize class net.sf.jasperreports.engine.util.JRStyledTextParser".

Workaround Restart the UCMDB Browser server.

QCCR1H110609

The View Discovery Log action in the Discovery Progress Widget is supported only with one of the following web browsers: Microsoft Internet Explorer 11 or later versions, Google Chrome latest versions, and Mozilla Firefox latest versions. This is because Grommet does not provide support for other web browsers.

QCCR1H111482

UCMDB Browser does not support the Platform for Privacy Preferences Project (P3P) header in Internet Explorer for the widgets that can be directly embedded into Service Manager.

Workaround Follow these steps to open in the Internet Explorer the widgets that can be directly embedded into Service Manager:

  1. Assign the UCMDB Browser and the Service Manager to the same domain.
  2. Add the UCMDB Browser and the Service Manager in the hosts file.
  3. Configure the UCMDB Browser URL with a fully qualified domain name (FQDN ).
QCCR1H106412

Currently, in the Get Related Map, the double relations between two related CIs are displayed as a single relation.

QCCR1H108187 Currently, when more than 1000 CIs are displayed in the Get Related Map, you might encounter a performance issue.
QCCR1H107420 To view the TQLs for SM widgets (Defects widget, Incidents widget, and Change Request widget) in UCMDB, go to the JMX console, set the value of the ucmdb_browser.query_services JMX method to true, and then restart the UCMDB Browser.
QCCR1H104887 To view the error messages related to probe's issues under Probe Errors discovery issues type in UCMDB Browser, after upgrading UCMDB to version 10.22, manually redeploy the AutoDiscoveryInfra package located in the <Universal CMDB root directory>\UCMDBServer\content\basic_packages directory.
QCCR1H104553 There are times when a CI that is not visible in the Service Modeling map, has a Discovery Indicator. When this happens, the indicator appears on all the CIs that are in the map and have a direct or indirect link to the CI that is not visible.
N/A Currently it is not possible to create two service models with the same name in the UCMDB Browser, even if different tenants are used. This is because the Views that the service models use as resources must have a unique name.
QCCR1H99251 If accessing the UCMDB Browser from Configuration Manager, you might not be able to use a lot of features like Notification and Reports.
QCCR1H92299

For exporting the Stakeholder widget, when the Person CIT has an avatar image set and the UCMDB Browser is behind a proxy, the exported document will not contain the avatar image, instead the default image is used for that person.

This is because the Java Environment on which the server runs cannot access the image. On the Web Browser, the configurations are set inside the LAN Settings, so the link can be accessed.

QCCR1H99461

UCMDB Browser 4 may not load on Internet Explorer 9 or 10 when Check for newer versions of stored pages is set.

Workaround In case you use Internet Explorer 9 or 10, set Check for newer versions of stored pages to Automatically. To do that, in the Internet Explorer window, go to Tools > Internet Options > General, and then in the Browsing history section, go to Settings.

QCCR1H94718 Browser CI Access Control permissions only apply when a user is connected in Actual state.
N/A

If many users run reports simultaneously, and those reports contain many results, there will be increased memory usage on the UCMDB Browser web server (Tomcat or Jetty).

Workaround To decrease the load on the web server, do one of the following:

  • Increase the maximum heap memory size on the web server.
  • Decrease the session timeout specified in the web.xml file.
  • Set up high availability to spread the load over multiple UCMDB Browser instances. For more information, see "Configure High Availability Mode" in the (missing or bad snippet).
  • Instruct users to log out after finishing to work with the UCMDB Browser.

UCMDB Home

ID Issue
QCCR1H118728

(UCMDB Browser embedded only) UCMDB Home is not accessible from UCMDB Browser embedded, and the following error messages appear in the <UCMDB installation folder>\runtime\log\ucmdb-browser-warn.log file: "Attempt to add unsafe data to cookie”, and “ValidationException: cookie value: Invalid input” .

Workaround Follow these steps to resolve the issue:

  1. Open the <UCMDB installation folder>\conf\esapi\ESAPI.properties file.
  2. Add the % character to the following validators:

    Validator.HTTPCookieValue
    Validator.HTTPHeaderValue  
  3. Restart the UCMDB server.

N/A

(Internet Explorer only) When accessing UCMDB Home on Internet Explorer, a blank page is displayed, and the URL is <protocol>://<server_name>:<port_number>/ucmdb-browser/ui/home.

Workaround Follow these steps to resolve the issue:

  1. Go to Internet Explorer, click the Tools button on the right side of the Address bar, and choose Compatibility View Settings.
  2. Disable the Display intranet sites in Compatibility View option, then click Close.
QCCR1H116886 In certain non-English environments of UCMDB Browser 4.14, some strings on the UCMDB Home UI are not translated into proper languages.
N/A

Sometimes, when accessing UCMDB Home, the following error message appears:

Something went wrong. You're probably using a self signed
certificate. Please click 'OK' to visit the UCMDB URL, then
add it as an exception in your browser and refresh this page. 

Workaround Ensure that the URL is similar to the following: <https>://<server_name>:<port_number>/ucmdb-browser/ui/index.html?wp&ucmdbURL=<ucmdb_server_protocol>%3A%2F%2F<ucmdb_server_name>%3A<server_port_number>&username=..., and then follow the steps in How to Configure Access to UCMDB Home to resolve the issue.

Related topics

What's new in Universal CMDB Browser 4.15.1

Enhancements

Fixed defects