Release Notes > Known issues

Known issues

CMS 11.0 contains the following known issues.

ID Module Description



DDMI - Inventory Tools


Importing a custom SAI file (for example, User.zsai) into the Software Application Index (SAI) Editor fails with a loading error.

Workaround To import the custom SAI file into the SAI Editor properly,

  1. Close the Software Application Index (SAI) Editor if it is open.
  2. Navigate to the <DataFlowProbe>\runtime\probeManager\
    directory, locate and remove the auto.zsai file.
  3. Launch the Software Application Index (SAI) Editor again.
  4. Import the customer SAI file (in this case, User.zsai).
  Configuration Manager

Configuration Manager adapters (CM KPI Adapter and CM New Policy Adapter) show "can't parse argument number" error. This is related to an authentication issue when checking the logs.

Workaround To resolve the issue, you may use one of the following workarounds:

  • Use the admin or sysadmin user.
  • Go to UCMDB UI and manually set for CM integration user the tenant owner and consumers.

  • Go to the UCMDB server JMX Console,

    1. Locate the listResourceTypes operation in the UCMDB:service=URM Services category.
    2. Provide customer ID (default: 1) and click Invoke.
    3. On the returned page, select Auth_ROLE_ASSIGNMENT, then select the CM user.
    4. In the Resource XML field, add the following tags:

      <xmlSecurityDomainType2Id> <xmlSecurityDomainType2IdAny> <xmlAccessLevel>FULL</xmlAccessLevel> <xmlTenantAssociationType>OWNED_BY</xmlTenantAssociationType> <name>Any Tenant Security Domain with Full permissions on Owned resources</name> </xmlSecurityDomainType2IdAny> <xmlSecurityDomainType2IdAny> <xmlAccessLevel>VIEW</xmlAccessLevel> <xmlTenantAssociationType>USED_BY</xmlTenantAssociationType> <name>Any Tenant Security Domain with View permissions on Used resources</name> </xmlSecurityDomainType2IdAny> </xmlSecurityDomainType2Id>

    5. Click Save resource.
  Configuration Manager

Configuration Manager 10.22 CUP3 (or with a later CUP) cannot connect to UCMDB server 10.30 (or later).

Workaround To resolve the issue, configure Configuration Manager by following the instructions in How to Configure Configuration Manager 10.23 to Connect to UCMDB Server.

  Universal CMDB - General

When you install PostgreSQL 9.6 with UCMDB version 10.30, then upgrade UCMDB to version 10.32, UI login may not be possible. This is because UCMDB version 10.30 does not support PostgreSQL 9.6.

Workaround To use PostgreSQL 9.6 with UCMDB 10.32 (or later), follow the upgrade path below:

  1. Install UCMDB version 10.30 with a supported database (for example, embedded PostgreSQL 9.4.8).

  2. Upgrade UCMDB to version 10.32 (or later).
  3. Reconfigure UCMDB to connect to PostgreSQL 9.6.

    For detailed instructions, see How to Reconfigure UCMDB to Use Another Schema/Database.

  Universal CMDB - General

Aging is not working on populated CIs. Though aging related attributes were set for the CIT, the Is Candidate for Deletion attribute is not changing to true for CIs that were populated.

This is because, when a CI is created, it will populate the Candidate For Deletion Time attribute with the value of the current day plus the number of days defined by the Deletion Candidate Period attribute. If the Deletion Candidate Period attribute is changed later, the Candidate for Deletion Time value will not be changed.

  Universal CMDB - General

When the Data Flow Probe remains connected to the UCMDB Server during server restart, exceptions will be thrown.

Workaround Stop the Data Flow Probe before restarting the UCMDB server. After the server is up, start the Data Flow Probe. The issue will not occur.

  Universal CMDB - General

The shortcut of Uninstall HPE Universal CMDB Server or Uninstall Data Flow Probe may not appear on the Start menu of Windows Server 2016.

Workaround The shortcut problem is a Microsoft issue in Windows Server 2016. If you want to uninstall UCMDB server or Data Flow Probe, go to the UninstallerData folder to uninstall it.

  Universal CMDB - General

If calls are made to an instance that has been removed or is in process of deletion, exceptions will be thrown.

Workaround Restart the UCMDB server and the exceptions will disappear.

QCCR1H106088, QCCR1H100903 Universal CMDB - General

Displaying a specific view may crash the UCMDB server. This is because too many nodes were returned by the view that caused many more number of meta links generation and crashed the system with OutOfMemory error.

Workaround In addition to the fix provided in UCMDB 10.3x, for views with huge number of nodes and relations, you may also increase the memory of the UCMDB server and the applet. For detailed instructions, see How to Increase the Java Heap Memory Used by the UCMDB UI Java Applet.

QCCR1H105575 Universal CMDB - General

There is a wrapper license key support issue for certain time zones, causing UCMDB Probe service unable to start.

Workaround If you encounter such an issue, contact HPE Software Support to obtain new wrapper license keys, and then manually deploy the provided License keys on probe.

QCCR1H106754 Universal CMDB - General

When LDAP is enabled, UCMDB should not require password change anymore. However, after logging into UCMDB, users receive a page with the following message requiring them to change password: "Default or expired password detected. Please change your password."

Workaround When LDAP authentication is enabled, users need to set the Passwords must use default policy infrastructure setting to False.

  Universal CMDB - General

When uninstalling the UCMDB server, in the Uninstall Universal CMDB Server dialog box, the following items cannot be removed:

Unable to remove directory: C:\hp\UCMDB\UCMDBServer\solr\server\logs
Unable to remove directory: C:\hp\UCMDB\UCMDBServer\solr\server
Unable to remove directory: C:\hp\UCMDB\UCMDBServer\solr\bin
Unable to remove directory: C:\hp\UCMDB\UCMDBServer\solr

Workaround Make sure that the Solr process, a Java process that points to <UCMDB_Server_Home>/bin/jre, is stopped before uninstalling the UCMDB server.

To stop the Solr process,

  1. Access http://localhost:<port>/solr.
  2. Go to <UCMDB_Server_Home>/bin, and then run solr.bat on Windows and on Linux to stop the Solr server.
  3. If the Solr process is still available,

    Windows: End the Solr process in Task Manager.

    Linux: Use console/terminal to terminate the SOLR PID.

  Universal CMDB - General

If the Solr index folder is empty at the UCMDB server startup, UCMDB deletes it and Solr will recreate it again with the default files, which causes server errors, such as HttpSolrClient$RemoteSolrException and NoSuchFileException.

Workaround If the problem still appears, manually delete the index folder and restart the server.

  Universal CMDB - General

Saving or updating a perspective based view with several perspectives (for example, seven perspectives), may cause performance issues and it also may get the UCMDB server stuck.

Workaround In case you experience the above behavior and there is no other solution that can be used:

  1. Go to the UCMDB JMX Console, locate the setGlobalSettingValue JMX method in the UCMDB:service=Settings Services category.
  2. Provide the following parameter values:


    value: Specify the number of perspectives used in the perspective based view which crashed the system.

  3. Click Invoke.

  4. Restart the UCMDB Sever.

QCCR1H109216 Universal CMDB - General

When starting Solr manually on a Windows machine by running solr.bat start <port> from the command line using the script <UCMDB_Server_Home>\bin\solr.bat, if the command line from which the Solr was started is closed, the Solr process is stopped.

Workaround This is a Windows OS platform behavior and it is not linked to Solr process or UCMDB. However, you can restart the UCMDB server, which will then start the Solr, and there will be no command line visible in Windows.

QCCR1H104520 Universal CMDB - General

When trying to delete an attribute from a class which is used as key attribute on a descendent class, the Save button from UI shows an error that the action was not able to be performed, but actually the attribute will be removed from the list of key attributes for the descendent class. Clicking Save again will finally delete the attribute from the class.

Workaround When the attribute definition is overwritten in a descendent class, if you want to delete the attribute from the parent class, do the following:

  1. Remove all attribute overriding from the descendent classes.

  2. Delete the attribute from the parent class.

QCCR1H98275, QCCR1H95041 Universal CMDB - General The priority for TQL queries under the pattern-based model are changed from medium on UCMDB 9.05 to inactive on UCMDB 10.xx. The performance might be affected if the TQL queries under the pattern-based model are set to low/medium priority on UCMDB 10.xx. In this case, you might see that the locked gates and calculation for scheduled pattern-based model could take a couple of hours.
QCCR1H98228 Universal CMDB - General

(High Availability environment only) Changes in Global Settings that require the server’s restart to take effect may not take effect without restarting all nodes from a cluster.

Workaround In order for all changes in Global Settings that require the server’s restart to take effect, you must restart all nodes from the cluster (one by one or with the restartCluster JMX method).

QCCR1H101149 Universal CMDB - General

After upgrading UCMDB to version 10.21 (or later) successfully, some times users may encounter an internal error when trying to launch the UCMDB UI.

Workaround In case you encounter an internal error when trying to launch the UCMDB UI, delete the C:\Users\<user>\AppData\Local\Temp\UcmdbAppletJars folder and try to launch the UCMDB UI again.

QCCR1H98834 Universal CMDB - General The testDBConnection JMX method does not support PostgreSQL.
  UCMDB Installation

(Linux only) When installing UCMDB server, the following warning message may pop up even you do not have any PostgreSQL database installed on the concerning machine:

Workaround If you did not install any PostgreSQL database before, you can simply click Ignore to proceed. It is just a warning message that has no impact on the usage of UCMDB server and probes. The UCMDB server and probes can be normally used.

  UCMDB Installation

For machines where Russian, Korean or Japanese is set as the OS language, if users install UCMDB 10.31 or any other previous version, the language options in the installation wizard are English and the OS language. However, when users install UCMDB 10.32 on such machines, the installation wizard provides the following installation language options without Russian, Korean or Japanese:

  • English
  • Brazilian Portuguese
  • French
  • German
  • Italian
  • Netherlands
  • Spanish

Workaround Select English or any other supported language provided in the installation wizard.

QCCR1H103867 UCMDB Installation

The wrapper.log file is created in the bin folder when the log folder is missing.

Workaround If the log folder is missing (for example, it was deleted accidentally), before starting up the UCMDB server, make sure you create the log folder manually.

Note: If you want to delete the logs, delete the content in the log folder only, and never delete the folder itself. Make sure the <UCMDBServer>\runtime\log folder always exists.

N/A UCMDB Upgrade

After upgrading UCMDB to version 11.0, and then restarting the UCMDB server, the UCMDB server fails to start.

Workaround To resolve this issue, follow these steps:

  1. Go to the UCMDB server JMX Console.
  2. Locate the rebuildModelDBSchemaAndViews operation in the UCMDB:service=DAL services category.
  3. Enter the following parameters:

    • customer ID. Enter your customer ID (default: 1).
    • previewMode. Select False.
    • skipIndexRebuild. Select False.
    • skipColumnsUpdate. Select False.
  4. Click Invoke.
QCCR1H117937 UCMDB Upgrade

After upgrading UCMDB from version 10.31 (or earlier) to version 11.0, the search functionality does not work in UCMDB Browser.

Workaround The SOLR version in UCMDB 10.31 is upgraded from 5.2.1 to 6.2.1. When you upgrade UCMDB from version 10.31 (or earlier) to version 11.0, the Solr version used in old UCMDB does not upgrade automatically, and the configuration files do not match anymore. Therefore, to resolve the issue, do one of the following depending on the Solr edition in your environment:

  • Embedded Solr. After the upgrade, make sure you manually remove the search folder under the <UCMDB_server> directory.
  • Standalone Solr.

    1. Upgrade Solr to version 6.2.1.
    2. Manually remove the search folder under the <UCMDB_server> directory.
QCCR1H120120 UCMDB Upgrade

After upgrading UCMDB from version 10.33 (or earlier) to version 11.0, the following Windows services still contain "HP" in their names or descriptions:

  • UCMDB_Probe
  • UCMDB_Probe_DB
  • HP Universal Discovery XML Enricher

Workaround None.

  UCMDB Upgrade

Opening or accessing (for example, accessing through command) any of UCMDB server folders or files during the upgrade may result in upgrade failure. During the upgrade, UCMDB server folders and files will be modified or overwritten by the installer wizard.

Workaround Close all UCMDB Server folders and files before the upgrade, and DO NOT open or access any of those folders and files during the upgrade.

In case of such upgrade failure, to restore the server, copy the entire content of the C:\hp\UCMDB\UCMDBServer\old folder into the C:\hp\UCMDB\UCMDBServer folder. Then you can continue to use the server or perform another upgrade.

QCCR1H104381 UCMDB Upgrade

Resource string files added in the basic package AutoDiscoveryInfra are not updated during UCMDB upgrade.

Workaround After upgrading UCMDB to version 10.22 (or later), manually re-deploy the AutoDiscoveryInfra package.

QCCR1H104015 UCMDB Upgrade

Login fails after recreating a database schema after upgrading UCMDB from version 10.21 to version 10.22.

Workaround After upgrading UCMDB from version 10.21 to 10.22 (or later), and you have created and changed the database schema, perform the following to align the password from the database with the one from the super integration credentials file. This requires calling two JMX methods.

  1. Reset the DB password.

    1. On the UCMDB server, go to JMX console > UCMDB-UI:name=UCMDB Integration > setCMDBSuperIntegrationUser.
    2. In the User Name filed, enter UISysadmin, and in the Password field, enter the desired password value.
    3. Click Invoke
  2. Reset the super integration user credentials file.

    1. Go to JMX console > UCMDB:service=Authorization Services > resetPassword.
    2. In the Value box for customerID enter 1, in User Name field enter UISysadmin, and in the Password field, enter the password value to match the one you entered in step 1.

    3. Click Invoke
QCCR1H91974 UCMDB Upgrade

After upgrading from earlier versions to 10.20 or later, instances of the Tags business service attribute and element may not be searchable.

Workaround In order to find instances of the Tags business service attribute when searching, you must change the indexer and ranking configuration in the JMX console.

  • In UCMDB:Service=Topology Search Services. Method: editIndexerConfiguration, for the business_element class, the Tags attribute must be lower case in order to be searchable.
  • In UCMDB:Service=Topology Search Services. Method: editRankingConfiguration, the Tags element should be tags in order to be searchable.
QCCR1H100431 UCMDB Upgrade

When upgrading from UCMDB version 10.11 with a CP15 update to UCMDB 10.20 (or later), the UCMDB server cannot start after upgrade. This is due to the current CP version deployed on top of version 10.11 which is higher than the CP version bundled in the 10.20 install media. ()

Workaround You can fix this upgrade issue by changing the CP version in the JMX Console manually during the upgrade, and after the upgrade, redeploy the existing CP.

For example, if you are upgrading UCMDB from version 10.11 with CP15 Update 1 [or any other CP version (including updates) higher than CP15 for 10.20 or CP21 for 10.30] to version 10.20, do the following,

  1. Perform the minor upgrade from UCMDB 10.11 with CP15.01.142 to UCMDB10.20.
  2. Check status and wait for the CP deployment to fail with error in error.log:

    [ErrorCode [105005] Content pack downgrade is not allowed]
    Trying to install CP version [15.00.123] which is older than the one already installed [15.01.143] is not support.
  3. Log in to the JMX Console and access UCMDB:service=Settings Services.

  4. Locate the getInternalSettings method.

  5. Enter customer ID and cp.version in the key value field, and then click Invoke.

    The returned value should be 15.01.142.

  6. Replace the value with 15.00.123 and click Set.

  7. After that the CP deployment should finish successfully. You can check the status in mam.packaging.log.

  8. Access UCMDB UI and redeploy CP 15.01.142.

  9. Check the CP version from menu Help > About. It should be 15.01.142.

You may also refer to KM01581489 for details.

QCCR1H96681 UCMDB Upgrade

When upgrading both UCMDB and Content Pack from previous versions to the latest versions, from example, upgrade UCMDB from 10.11 to 10.20 and Content Pack from CP14 to CP15, if you have customized any Content Pack files, deployment of some Content Pack class model files may fail during the upgrade.

Workaround Reinstall the latest Content Pack manually after the upgrade.

QCCR1H97159 UCMDB Upgrade

If you have created custom class models on UCMDB version 9.05, after upgrading UCMDB from version 9.05 to 10.20 or later, you might find that your custom class models are not available. For example, when you create a new activity for a management zone, you might find that the Protocol pane in the Define Credentials tab page is empty.

Workaround Invoke the JMX method updateClassModel to upgrade custom class models. To do so,

  1. Launch the Web browser and enter the following address:

    http://<machine name or IP address>.<domain_name>:1977/

    where <machine name or IP address> is the machine on which the Data Flow Probe is installed. You may have to log in with the user name and password.

  2. In the Search field, type updateClassModel and press Enter.
  3. Locate the updateClassModel method, in the customerID Value field, type 1, and click Invoke.

  UCMDB Upgrade

After upgrading UCMDB to version 10.20 or later, you may encounter some credentials related issues. (97159)

Workaround To resolve the credentials related issues, do the following:

  • key.bin file. Check and make sure that the new probe uses the same key.bin file as the UCMDB server.

  • Time. Check and make sure that the probe time is the same as the UCMDB server time. If the probe time is different, it may cause credentials error.
  • Credentials fail on the upgraded environment.

    Install a new probe and copy specified files to override problematic files. To do this:

    1. Install a clean probe on the same machine of UCMDB server, connect it to UCMDB server. Make sure that the new probe can get credentials normally.
    2. Go to the clean probe, copy the Cmcache.bin and secured_storage.bin files from C:\hp\UCMDB\DataFlowProbe\conf\security directory.

    3. Go to the probe that has get credentials errors, override the two files with yours.

    4. Restart the probe and try to get credentials again.

  • Export credentials from the upgraded environment and import them to the fresh install environment, the JMX operation fails. When the exported credential xml file contains customized class models, or the customized class models are not defined on the UCMDB server that you upgraded, you may encounter credentials import issue.

    • Remove the customized protocol from the exported credential xml file.
    • Add the customized class models on the UCMDB server manually via CIT.

    Note: Make sure that the export CIT or import CIT works well. Otherwise it may cause the workaround not working.

Note: To upgrade customized class models, invoke the JMX method updateClassModel. For details, see Invoke JMX Method updateClassModel.
QCCR1H93868 UCMDB Upgrade

A user with “create user” permissions loses permission after upgrading the UCMDB from version 9.0x.

QCCR1H69931 UCMDB Upgrade During upgrade from a version earlier than UCMDB 10.00, you might get a UNIQUE_INDEX violation exception on the path attribute of discovery modules CIT. In previous versions the column could contain duplications while in the newer version it has a UNIQUE_INDEX qualifier. The message means that there were duplications and that the qualifier is not added.
QCCR1H75574 UCMDB Upgrade When upgrading from a previous version to 10.20 or later, the user preferences of a deleted user are not deleted. Warnings appear in the log and the upgrade completes successfully.
QCCR1H99001 UCMDB Upgrade

After upgrading UCMDB to a newer version (including CUP), the Normalization rules do not work.

Workaround To fix the issue, perform either of the following:

  • Deploy a new Content Pack package.

  • Manually delete the <Data Flow Probe Installation>\runtime\probeGateway\maxupdatetime.txt file and then restart the Data Flow Probe.

  UCMDB Upgrade

(Automated Service Modeling only) When performing ASM service discovery from the UCMDB Browser, all the errors from the ASM service discovery are not assigned to the correct categories. They are assigned to the Other category.

Workaround If you use ASM, to workaround this issue, make sure you upgrade both your UCMDB Server and Content Pack to the latest versions, that is to upgrade UCMDB Server to version 10.21 (or later) and Content Pack to version 16.00 (or later).

QCCR1H104783 UCMDB Downgrade

Automatic upgrade of data flow probes in the following scenario is not supported: Upgrade UCMDB server (for example, from version 10.20 to 10.21), then downgrade UCMDB to the previous version (in this example, from 10.21 to 10.20), and then after that, upgrade UCMDB server back again (in this example, from 10.20 to 10.21).

Workaround Manually upgrade data flow probes using the deployProbePatch JMX method. To do so,

  1. Launch the Web browser and navigate to: https://<server_name>:8443/jmx-console, where <server_name> is the name of the machine on which Universal CMDB is installed.

  2. Go to UCMDB:service=Discovery Manager.

  3. Locate deployProbePatch.

  4. In the Value box for the parameter customerId, enter the <customer id>. The default value is 1.

  5. In the Value box for the parameter filePath, enter the full file path of the patch file.

  6. Click Invoke.

QCCR1H114244 Universal CMDB - Reconciliation

Short leased IP addresses get merged incorrectly.

Workaround If you use Cisco VPN switches, make sure you configure one of the following:

  • Exclude these VPN MACs from the arp_mac attribute of IP Address and connected interface to IP of interface with that MAC in reconciliation auto exclude.
  • Exclude these VPN MACs from the arp_mac attribute of IP Address and connected interface to IP of interface with that MAC in the reconcilation rule of IP Address.

  Universal CMDB - UI

After downloading the localized online help from Micro Focus Software Support site (SSO), and replacing the files under <UCMDB_Server>\deploy\ucmdb-docs\docs\eng\doc_lib folder with the localized version and restarting the UCMDB server, the localized online help does not load properly because of the web browser cache.

Workaround Make sure you clear your web browser cache.

  Universal CMDB - UI In UCMDB UI > Modeling > Reports > Custom Reports > Custom > Compliance, when running Compare Archives Report or Compare Snapshots Report, if the number of CIs from the report is huge, it may require a very long time to generate the report, sometimes more than 10 hours.
  Universal CMDB - UI

(Firefox only) When launching UCMDB UI from Firefox with JNLP enabled, make sure the Firefox version is 52 (or lower), because Firefox support for NPAPI plug-in is removed for version 52 and later.

Workaround Make sure to use Firefox version 51 or lower.

  Universal CMDB - UI

When a TQL is used by both a pattern-based model (PBM) and a view, the PBM becomes inconsistent with the TQL if the TQL is updated from the view. This issue is caused by the fact that Package Manager Resource Selector becomes inaccessible while a new package is being created or an existing package is open. The following error message is displayed in the logs:

"Caused by: java.lang.IllegalStateException: 
ModelName is not synchronized with its pattern. 
Element number 12 does not 
exist in pattern graph."

ModelName and 12 in the error message could be different values.

Workaround Pattern-based models must be created or edited only from the model instead of from the TQL query. The same TQL query cannot be used by both the model and the view.

To fix a corrupted PBM, use one of the following two ways:

  • Delete the model and then recreate it

    1. Log in to UCMDB JMX Console and URM Services.
    2. Run method listResources for Resources of type: Topology_ENRICHMENT_BUSINESS_VIEW.
    3. Locate the EnrichmentBusinessView that is mentioned in the error message and delete it. Then the model is deleted.
    4. Recreate the model from Modeling Studio using the same TQL.
  • Edit the unsynchronized resources of the problematic model

    1. Log in to UCMDB JMX Console and URM Services.
    2. Run method listResources for Resources of type: Topology_ENRICHMENT_BUSINESS_VIEW and Topology_TQL.
    3. Retrieve the xml definition of the Topology_ENRICHMENT_BUSINESS_VIEW and Topology_TQL of the problematic model.
    4. Open the EnrichmentBusinessView and locate the ID that is mentioned in the error message.

    5. Do one of the following:

      • Change the missing ID in the EnrichmentBusinessView with an existing one from the Topology_TQL definition and save the resource.
      • Add the missing ID in the Topology_TQL definition by replacing an existing one and then save the resource.

      Here is an example:

      <tql:node class="node" name="Node" id="19">

      If you do not have id 12 in the TQL query, you can change it in the following way:

      <tql:node class="node" name="Node" id="12">
  Universal CMDB - UI Only HTTP protocol is supported when launching UCMDB UI from any web browser running on Mac OS X with JNLP enabled.
  Universal CMDB - UI

UCMDB UI loads properly with HTTP, but it may not load with Safari on Mac OS when HTTPS is enabled.

Workaround Switch the UCMDB Server back to HTTP protocol by changing the following setting in the \UCMDBServer\conf\ file to true and then restart the UCMDB server:

  Universal CMDB - UI

(Chrome only) UCMDB UI applet cannot work in Chrome version 42 or later, because starting from Chrome 42, NPAPI plugins are disabled by default. Chrome displays a gray screen with the following error message when users try to access the UCMDB UI: This site uses a plugin (Java(TM)) that is unsupported.

Workaround To resolve the issue, you need to enable NPAPI manually and keep Chrome below version 45 to make UCMDB UI client applet work properly. For details, see KM01656540.

To launch UCMDB UI from Chrome version 45 (or later), follow the instructions in How to Launch UCMDB UI from Chrome 43+, Firefox 48+, Microsoft Edge, or Safari 10+.

QCCR1H99579 Universal CMDB - UI

Cannot upload a zip package if the zip file size exceeds the applet available memory.

Workaround You can deploy larger packages using the deployPackages JMX method (go to the JMX Console > UCMDB:service=Packaging Services > deployPackages).

You can also control the maximum size of the packages to be uploaded by setting the value of the infrastructure setting File upload maximum file size for archive type to a larger value (default value: 200 MB).

  Universal CMDB - Server

When importing data packages into UCMDB through Package Manager, some data packages may fail to be imported.

Workaround Check and make sure that the files you import into UCMDB are using the same encoding as defined in the XML. For example, if you export the XML files in UTF-8 encoding, then you should import files encoded in UTF-8 as well. The problem would occur if you import files encoded in UTF-8 BOM and the XML content specifies it is UTF-8.

  Universal CMDB - Server

If the Solr search functionality is not enabled, even when https://localhost:8983/solr can be accessed or started from command line, any search activity from UCMDB Browser or JMX console may fail.

Workaround If UCMDB server cannot start Solr for some reason after the server starts, just stop the UCMDB server, start Solr manually and start the UCMDB server again.

QCCR1H102136 Universal CMDB - Server

(Linux only) OpenJDK may create a wrong server name on the status page if the machine hosting UCMDB Server is in a certain domain environment.

Workaround If the problem appears, modify the wrapper.conf file as follows:

  1. Open the <UCMDB_Server_Home>\bin\wrapper.conf file using a text editor.
  2. Uncomment the line with, and specify a server name or simply use the localhost name.

    To find the localhost name in console, simply enter hostname.

  Universal CMDB - Server

(Linux only) Statistics data collection does not work for Linux (program "ps" cannot run due to too many open files and failed to fetch statistics), which would create a lot of threaddump txt files, and then failed to run other applications, like applying a content pack or running license utility.

Workaround In order to change the Linux Max Open files, you will have to increase the maximum number of open files system-wide and per process of a specific user:

  • System-wide:

    Set system-wide file descriptors (FD) limits by editing the /etc/sysctl.conf file, so that after reboot the setting will remain as it is:

    1. Locate and open the /etc/sysctl.conf file.
    2. Append a config directive as follows:

      fs.file-max = 100000
    3. Save and close the file.

    4. Users need to log out and log back in again for the changes take effect, or just type the following command: # sysctl -p
  • User Level FD Limits:

    After setting system-wide FD limits, you can still limit httpd user (or any other users) to specific limits by editing the /etc/security/limits.conf file.

    1. Set httpd user soft and hard limits as follows:

      httpd soft nofile 4096
      httpd hard nofile 10240
    2. Save and close the file.

To view limits, enter:

# su - httpd
$ ulimit -Hn
$ ulimit -Sn

To check the limits of a process:

  1. Get the PID number by entering:

    - #ps aux | grep <process-name> #
  2. Check the limits of a process:

    - cat /proc/<PID>/limits`
QCCR1H106209 Universal CMDB - Server

After adding a new UCMDB server to an High Availability (HA) cluster that has been reinstalled on a fresh operating system, the new server does not register as a cluster node.

Workaround Manually set the network interface in the wrapper.conf file when you have more than 1 network interface. To do so,

  1. On a UCMDB server instance in the HA cluster, open the c:\hp\UCMDB\UCMDBServer\bin\wrapper.conf file in a text editor.
  2. Add a entry into the file, which looks similar to the following:,server=y,suspend=n,address=5005<ip-address>

    where <ip-address> is the IP of the right interface to be used.

  3. Save the file.
  4. Repeat the above steps on each of the remaining UCMDB servers in the cluster, and use for each the right IP/Interface assigned for that server.
  5. Restart all UCMDB servers.
QCCR1H100329 Universal CMDB - Server

The Writer server becomes unresponsive which schedules a restart of the entire HA infrastructure. This impacts the load balancing URL, causing all probes to disconnect. This is caused by the existing Garbage Collector algorithm used in UCMDB.

Workaround The problem can be resolved by improving the performance of the Garbage Collector by using G1 algorithm for the Garbage Collector. For enterprise environments where you have more than 16 GB of RAM allocated just for UCMDB (see the property value in the ..\UCMDB\UCMDBServer\bin\wrapper-platform.conf file), check and make sure you add the following settings to the wrapper-custom.conf file if they are not present:

#Enable the following parameters for JVM G1 garbage collector in enterprise environments
  Universal CMDB - Server You cannot not use the status page when the URM resources are not deployed at the first time a schema is created or modified.
QCCR1H104733 Universal CMDB - Server

Can not save the enrichment rule when adding the customer relationship. This is caused by the fact that the TQL query behind the enrichment is not connected. When there is no existing relation between two CI types, it is not possible to create an enrichment which will add the relation just by entering enrichment manager and by adding the relation that is needed.

Workaround Create a joinf link in the TQL query between the concerning two CI Types by joining them on an attribute value. This way the enrichment manager will know how to perform correctly the enrichment actions.

  Universal CMDB - Topology

After updating a non-key attribute of a CI with enrichment rule, an unexpected new CI instance is created. This is only happening when populating attributes having a constant part and a dynamic part, in this case CDoc+<node:name>.

Workaround The first time the enrichment is executed, it will have a full TQL query layout. If the enrichment rule is active and it is notified of a change, it will run on a partially TQL query layout. This is designed so for performance reasons.

To workaround the issue, you may take either of the following:

  • Run enrichments on a scheduled notice. Nowadays it is not recommended to have many active enrichments.
  • Split the enrichment into two parts, one does the CREATE of new CIs which will run periodically, one does the UPDATE which is active.

QCCR1H99954 Universal CMDB - Topology Currently the Perspective views are not displayed in the Reports module in UCMDB.
QCCR1H95041 Universal CMDB - Topology The priority for TQL queries under the pattern-based model are changed from medium on UCMDB 9.05 to inactive on UCMDB 10.xx. The performance may be affected if the TQL queries under the pattern-based model are set to low or medium priority on UCMDB 10.xx. In this case, you can see that the locked gates and calculation for scheduled pattern-based model can take a couple of hours.
  Universal Discovery - General The Smart Software Analytics (SSA) server cannot respond to any API calls when processing scan files. Operations on the SSA UI are not supported if SSA server is teaching.
  Universal Discovery - General

When running the JEE Weblogic by JMX job, all the CIs were reported normally; however in the end an error occurs to the job: "Failed to connect to remote process".

Workaround To resolve the issue,

  1. On the probe machine, open the java.policy file (in the <DataFlowProbe>\bin\jre\lib\security directory) using a text editor.
  2. Add the following permission: "register"
  3. Save the file.
  4. Restart the probe.
  Universal Discovery - General

Dispatch might fail when users activate a discovery activity involving a data flow probe that has the same name as a domain.

Workaround For successful dispatch, make sure either of the following:

  • When naming a data flow probe, do not use the same name as that of any domain; or
  • Use the same domain name for a probe under the conditions that:

    • The probe is the only probe contained in the domain
    • The probe does not share the same name with any other domain
  Universal Discovery - General

If there is a Linux probe connected to the UCMDB server, when running ASM, it would try to detect an available probe. If it finds the Linux probe, an ASM dispatch issue could occur, because Linux probe is capable of running integration jobs only.

Workaround Right-click an adapter and select Go to Adapter, then go to the Adapter Configuration tab, in the Trigger Dispatch Options section, select the check box for Override default probe selection, and in the value field specify the target probe you want to use.

  Universal Discovery - General

After upgrading UCMDB server to version 10.31, and setting the setDomainEncrypt JMX method to true, if you start some old version 10.30 probes which were not upgraded to the latest version because they were down before the server upgrade, when they connect to the UCMDB server and you run discovery jobs, the discovery jobs would fail with error. This is because these old probes do not have the updated domainScopeDocument.xml and domainRangesDocument.xml (DSD/DRD) files that contain the new domain_encrypt attribute. The DSD/DRD files were downloaded to probes before server upgrade. After server upgrade, probes would not download the DSD/DRD files again.

Workaround To resolve this issue, the easiest way to modify any IP range or credentials (such as a protocol) from UCMDB server, which will trigger the automatic upgrade process for the probes. As a result, the updated DSD/DRD files as well as the upgrade packages are downloaded to the probes, then the probes are upgraded to the latest version automatically.

QCCR1H112324 Universal Discovery - General

Data Flow Probe JMX Console is fully accessible without providing any credentials.

Workaround To fix this issue, do the following:

  1. Stop Data Flow Probe.
  2. Add into
    <DataFlowProbe_Home>\bin\WrapperGateway.conf and
  3. Restart Data Flow Probe.
  Universal Discovery - General

After upgrading UCMDB to version 10.30 without deploying the latest Content Pack (CP21), when the Content Pack version is CP17 (or earlier), and you upgraded your CP to version CP18, CP19, or CP20 manually, SNMP discovery jobs may fail to run due to the missing of a Sun library.

Workaround If you manually upgrade an older CP to CP18, CP19, or CP20 when UCMDB is already on version 10.30, to enable SNMP discovery jobs to work properly, make sure you deploy an additional package corresponding to your target CP version.

The packages can be found in the <UCMDB_Server_Home>\tools\compatibility_patch folder:

CP version Package


For detailed instructions, see How to Deploy a Package.

  Universal Discovery - General

On a Windows machine where two Data Flow Probes are installed, both with Inventory Tools, after uninstalling one probe, the following three file types (.xsf, .aws, and .awcs files) lose their default opening programs and cannot be opened.

Workaround Manually re-associate default opening programs for the three file types: Inventory Tools Viewer for .xsf files, and Inventory Tools Analysis Workbench for .aws files and .awcs files.

  Universal Discovery - General

When more than 1500 IP ranges are configured on each Data Flow Probe, the following performance issues might occur:

  • Memory usage is huge on the UCMDB server side, which may cause OutOfMemoryError and the writer server restart.
  • Modifying the IP ranges could take a while.

Workaround Do not configure too many IP ranges and always keep the total number of IP ranges below 1500 per probe.

  Universal Discovery - General

When application names of existing records are changed in master.zsai, the records in auto.zsai are not updated automatically.

Workaround Delete the auto.zsai file on all remote servers directly so that it will be automatically regenerated:

  1. Delete the auto.zsai file on all of the remote servers.

  2. Restart the XML Enricher.

QCCR1H107794 Universal Discovery - General

(Universal Discovery protocol only) When running a discovery job that uses the Universal Discovery protocol to push a large amount of CIs into another UCMDB server, the job fails with timeout errors, which causes data inconsistency issue and performance impact.

Workaround The default connection timeout value of the Universal Discovery protocol is 20 seconds. If the command execution in your organization's discovery job takes some time, to ensure that the job runs successfully, increase the timeout value in both of the following places, for example, to 45 seconds:

  • The Connection Timeout parameter value in the Universal Discovery Protocol Parameters dialog (go to UCMDB UI > Data Flow Management > Data Flow Probe Setup > Domains and Probes > DefaultDomain(Default) > Credentials > Universal Discovery Protocol)
  • The shellGlobalCommandTimeout property value in the globalSettings.xml file (go to UCMDB UI > Data Flow Management > Adapter Management module, under Resources > Packages > AutoDiscoveryContent > Configuration Files)

QCCR1H105604, QCCR1H105110 Universal Discovery - General

Version 10.1x (and later) probes appear to corrupt the PostgreSQL database under normal discovery loads. The root cause is that when Anti-Virus is scanning the PostgreSQL data folder, it could cause PostgreSQL tables to corrupt.

Workaround To resolve the issue, perform the following:

  • Always make sure that the PostgreSQL install directory is added into the anti-virus software exclusion list. The exclusion of data files will not introduce any potential security risk.
  • If you need to run weekly-based scan, monitor the probeerror.log file, and if a database error shows up (for example, a database error related to the Discovery_result table), do the following:

    1. Clean the probe log folder.
    2. Run Clear Probe Results Cache from UCMDB UI > Data Flow Management > Universal Discovery > Discovery Modules/Jobs to clean the problematic table.

    This should resolve the issue.

QCCR1H105538 Universal Discovery - General

After upgrading from UCMDB from version 10.11 CUP5 + CP15 to versions higher than 10.21 (with CP17 or later), users are unable to run any discovery job or integration job that uses an external process on the probe. For example,

  • VMware discovery

    • VMware vCenter Connection by VIM

    • VMware vCenter Toplogy by VIM

    • VMware vMotion Monitor by VIM

  • XLS Import

  • NNMi Integration

The discovery or integration job fails with an "Failed to execute remote process" error. This is because version 10.11 file was used in 10.21 probe and the incorrect class path value caused the error.

Workaround To resolve the issue, append the missing ../lib/discovery-content-api.jar to the value for the remoteJVMClasspath adapter parameter.

Note: When upgrade a probe by reinstall, do not copy the old file from the old probe to the upgraded probe directly, because the values of the properties might have been changed during the upgrade.

QCCR1H104758 Universal Discovery - General

After upgrading UCMDB from version 10.21 + CP15 to version 10.22 (or later)+ CP18 (or later), the ASM for BSM functionality does not work anymore.

Workaround Re-deploy the package after upgrade as follows:

  1. Unzip the CP18 package and locate the package in the packages folder.
  2. In UCMDB UI, navigate to Administration > Package Manager, and click the Deploy packages to server button.

  3. Select the package and import it.
QCCR1H101769 Universal Discovery - General

(PostgreSQL only) Some SQL statements are observed running more than 30 minutes, which causes Probe database to crash. The root cause is that the default value of the statement_timeout setting in the postgresql.conf file is 0.

Workaround To workaround the issue, locate and open the hp\UCMDB\DataFlowProbe\pgsql\data\postgresql.conf file in a text editor, and then modify the default value of the statement_timeout setting from 0 to 3600000.

QCCR1H104012 Universal Discovery - General

(Service Discovery) The modified IsofPath parameter value in the ASM template fails to load properly.

Workaround To modify the parameters in the service discovery activity template successfully, select a different row or click Enter to complete the change you made in the Value field of parameters. After that, click OKto save the changes. This ensures that the parameters values are saved successfully and the communication log reflects the change properly, then the new parameter value can be used in discovery jobs correctly.

QCCR1H100855 Universal Discovery - General

When you have many environments, note that it is not supported to update the domainScopeDocument.xml and domainRangesDocument.xml files on all environments by building a package and importing it to all other environments.

Workaround The only way to update these files is to call the editResource JMX method (from the UCMDB:service=Packaging Services or UCMDB:service=URM Services category).

If you want to update IP Ranges and Credentials, you can also use the importCredentialsAndRangesInformation and exportCredentialsAndRangesInformation JMX methods. For details, see Universal CMDB Hardening Guide or Universal CMDB JMX Reference Guide.

  Universal Discovery - General

When changing the LW-SSO initString from UCMDB UI or via JMX, the probe side fails to synchronize the credentials from Configuration Manager. (QCCR1H100746)

Workaround To resolve the issue, do the following:

  • If the value of initString is changed from UCMDB UI, regardless whether the probe is connected to or disconnected from the UCMDB server, you can use the setLWSSOInitString JMX method on the probe side to keep the same initString value as on the UCMDB server side, then credentials from CM can be successfully synchronized.

    To do so,

    1. On the Probe machine, launch the Web browser and enter the following address: https://localhost:8453.

      Note If the Probe Manager and the Probe Gateway are running as separate processes, the address should be entered on the machine that is running the Probe Manager as follows: https://localhost:8454.

    2. Click type=CMClient to open the JMX MBEAN View page.
    3. Locate the setLWSSOInitString method and provide the same init string that was provided for UCMDB's LW-SSO configuration.
    4. Click the setLWSSOInitString button.
  • If the value of initString is changed from JMX on the UCMDB server side, and

    • the probe is disconnected from the UCMDB server, use the setLWSSOInitString JMX method on the probe side to resolve the issue. For detailed instructions, see steps above.
    • the probe is connected to the UCMDB server, invoke the setInitString JMX method on the UCMDB server side to enable automatic synchronization of the initString value.

      For instructions on how to invoke the setInitString JMX method, see Universal CMDB JMX Reference Guide.

QCCR1H104153 Universal Discovery - General

Probe discovery will result in duplicate node CIs (Windows/Unix) if re-imaging the Virtual Machine system with the same template, IP address, and hostname. This is because the unique calculation logic for the node is different between the UCMDB server and the probe.

Workaround Before re-imaging your Virtual Machine system, remove the CI instance of the old Windows/Unix system from UCMDB manually.

  Universal Discovery - General

If a Management Zone inherits the IP range from a bound probe, after the probe is added to or removed from a probe cluster, the Management Zone loses the IP range setting and the following operations have unexpected results:

  • Move this Management Zone from one folder to another folder.

    This operation results in an error message and the Management Zone remains in the original folder.

  • Move the folder that contains this Management Zone to another folder.

    This operation moves the folder to the target folder successfully. However, an error message appears and this Management Zone is moved to the Root folder. If there are other Management Zones after this Management Zone in the tree, these Management Zones are also moved to the Root folder.

  • Rename the folder that contains this Management Zone.

    This operation renames the folder successfully. However, an error message appears and this Management Zone is moved to the Root folder.

Workaround To work around this issue, manually set the IP range for the problematic Management Zone, and then move the Management Zone(s) to the target folder.

QCCR1H97710 Universal Discovery - General

The WebSphere to Web Server Dependencies job is causing OutOfMemoryError on the probe side.

Workaround The probe requires at least 4G memory to run the WebSphere to Web Server Dependencies job. Therefore, allocate at least 4G memory for the probe.

QCCR1H98271 Universal Discovery - General

When the probe is in Separate Mode, the default credentials for basic authentication are not updated automatically.

Workaround Update the default credentials for basic authentication manually. To do so,

  1. Open the JMX Console of the UCMDB Server side, enter changeBasicAuthenticationCredential in the quick search field and click the link that appears.
  2. Specify values for userName and password.

    Note: Password must contain at least six characters.

  3. Click Invoke.
  4. Encrypt the password by using the JMX Console of the probe side as follows:

    1. Open the JMX Console of the probe side, enter getEncryptedKeyPassword in the quick search field and click the link that appears.
    2. Enter the password that you specified.

    3. Click Invoke and then the encrypted password is generated.
  5. Copy the encrypted password.
  6. Edit the file as follows:

    appilog.agent.Probe.BasicAuth.User = <the user name 
    that you specified>
    appilog.agent.Probe.BasicAuth.Pwd = <the encrypted 
    password that you just copied
  7. Save the change and then restart the probe.
  Universal Discovery - General

When working in a High Availability environment, if there is a failover to the other UCMDB Cluster, you must first clear the data of the Integration Service before running it.

Workaround To clear the data, run the following:


  Universal Discovery - General When using the network ping options available in the new Check Network Availability dialog box to troubleshoot network connection issues and/or credential related issues against a node type inventory CI in IT Universe Manager, you selected a different credential in the Choose Credential dialog box but changed your mind and clicked the Cancel button, All credentials show up in the Credential field, instead of keeping the original value in the Credential field unchanged.
QCCR1H101124 Universal Discovery - General

After upgrading UCMDB to version 10.21 and deploying the Content Pack 16.00, the new Check Network Availability permission is not available for the out-of-the-box role Discovery And Integrations Admin. This is caused by the fact that version 10.21 installer does not run in silent mode, therefore the package is not deployed.

Workaround To make the Check Network Availability permission available for the out-of-the-box role Discovery And Integrations Admin, you need to manually deploy the package. To do so,

  1. Copy the package from the <UCMDB_Server_Home>\content\basic_packages directory to the machine from where you will deploy the package.
  2. Launch UCMDB UI and navigate to Administration > Package Manager, and click the Deploy packages to server button.

    In the popup dialog, select, and then click Deploy.

  3. After the deployment is completed, go to Security > Roles Manager, select Discovery and Integration Admin > CIT Menu Items, then select Node CI type, the Check Network Availability action should show up in the Selected Actions pane.
  Universal Discovery - General

After upgrading to version 10.21, some jobs cannot run in JVM 8 because the driver JAR files of these jobs only support JVM 7.

Workaround To work around this issue, you can use a remote process of JVM 7 to run these jobs. For detailed instructions, see KM01746334.

QCCR1H101777 Universal Discovery - General

When the UD probe compiles a list of CIs to be scanned, it does not add CIs that are connected through VPN. This happens when there are two UCMDB servers available handling the discovery of the client environments, but there is only one agent package with the same call home configured.

Workaround Set up a DNS alias, such as UDCallHome, that in each network resolves to a local (for that region) UD probe to receive the agent call home event. This way the same initial agent call home configuration could be used throughout.

QCCR1H105398 Universal Discovery - Probe Framework

Probe database (PostgerSQL) size grows quite big (36 GB). Clearing probe cache resolves the issue, but it reoccur at regular interval. This issue is caused by the biggest table ddm_discovery_results, which is the main table that controls the result of all CIs discovered by the probe, but the table is used by multiple features.

Workaround To resolve the issue, use the C:\hp\UCMDB\DataFlowProbe\pgsql\bin\pgAdmin3.exe GUI to perform DB dump. Just right click the Data Flow Probe DB, and choose backup.

For example, from the C:\hp\UCMDB\DataFlowProbe\pgsql\bin directory, execute the following command:

psql.exe --username=postgres --command 
"VACUUM  full verbose" --dbname=dataflowprobe
QCCR1H98264 Universal Discovery - Probe Framework

When the appilog.collectors.storeDomainScopeDocument property in the file is set to false, some jobs which run in the remote process mode may fail, because the remote process cannot read the probe memory, thus having no access to the domainScopeDocument file stored in the memory. When the setting is false, the file is only stored in the probe memory.

Workaround If some jobs run in the remote process mode, make sure that you set the value of the appilog.collectors.storeDomainScopeDocument property in the file to true.

QCCR1H98262 Universal Discovery - Probe Framework

When using PostgreSQL as your database on the Windows platform, the UCMDB_Probe_DB service is not starting as a non-system user. This is a third-party product limitation, because PostgreSQL is able to "irrevocably give up administrative rights at startup". For details, see this PostgreSQL wiki page.

Workaround In order for the UCMDB_Probe_DB service to start properly, you may configure the Log On options for the UCMDB_Probe_DB service as follows:

  1. Locate the UCMDB_Probe_DB service in the Services window.
  2. Right-click UCMDB_Probe_DB and select Properties.
  3. In the UCMDB_Probe_DB Properties window, go to the Log On tab, and do either of the following:

    • (Recommended) Select the Local System account option.

      Note: This is the recommended option, because the SYSTEM account has access to all necessary folders according to the default settings on Windows.
    • Select This account, and specify the account name and password.

      Note This option is NOT recommended. Even if you specify an administrator account, it will be treated as a common user account by PostgreSQL, because PostgreSQL is able to "irrevocably give up administrative rights at startup".

      If you DO need to specify a different account, make sure that the USERS group on your Windows platform has:

      • Read and Write access to the C:/UCMDB/DataFlowProbe/pgsql folder.
      • Read access to the files in system library (for example, the C:/Windows/System32 folder) that PostgreSQL needs to access.

        For the list of files that PostgreSQL needs to access, see PostgreSQL documentation.

  4. Click OK.
QCCR1H98897 Universal Discovery - Probe Framework Java API setDiscoveryConfigurationXML does not support cluster.
QCCR1H120762 Universal Discovery - Probe Upgrade

After upgrading a probe of version 10.22 (with or without a CUP) to version 10.33, the data in the ddm_discovery_results and ddm_discovery_touch_results tables are reserved.

After upgrading a probe of version 10.22 to version 11.0 (or later), the data in the ddm_discovery_results and ddm_discovery_touch_results tables are removed. This is the designed behavior as the new Universal Discovery licensingmodel is introduced in version 11.0

  Universal Discovery - Probe Upgrade

After the installation, there are two entries in the control panel with the same name for both of Data Flow Probe and UCMDB Server. Both entries refer to the same installation. Uninstall any of them will uninstall the referenced product. They have no impact for your normal use.

Workaround If you want to remove one of the entries,

  1. Go to Start > Run, enter regedit and click OK to open the Registry Editor.
  2. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall, and locate the entry you want to remove.

    Note The registry path may vary with Windows operating systems, make sure you locate the entry for your OS.

  3. Delete the selected entry.
QCCR1H99342 Universal Discovery - Probe Upgrade

Linux does not support automatic upgrade of probes.

Workaround To perform manual upgrade of probes on Linux, run the <DataFlowProbe Installation Folder>/tools/upgrade/ script.

  Universal Discovery - Probe Upgrade

Deploying probe update manually failed with an "Out of memory" error.

Workaround When you deploy a probe update manually via UCMDB UI, the maximum package size allowed is 200 MB. If the package size is greater than 200 MB, deploy it via JMX console using the deployProbePatch JMX method from the UCMDB:service=Discovery Manager category.

Also, note that the UCMDB UI client for applet requires 1280 MB memory at least.

N/A Integrations LW-SSO does not work if you go from HTTPS to HTTP with an integration of UCMDB with another product. For example, when integrating with another product, if UCMDB is configured to work on HTTPS, and the other product is on HTTP (for example BSM), then even if you use the same LW-SSO configuration on both environments, BSM will not open based on LW-SSO, because the LW-SSO cookie was created on UCMDB which is on HTTPS. If you first open BSM which is on HTTP, and then you want to open UCMDB, UCMDB will open with no additional authentication based on LW-SSO.
QCCR1H105818 Integrations SiteMinder with AJP does not work any more starting from UCMDB 10.21, because Jetty does not support it. That is why after upgrading to UCMDB version 10.21, the UCMDB integration with SiteMinder with IIS as front-end will fail.
QCCR1H107699 Integrations Java adapters do not support the remote process feature. An integration job will fail with an error when the "Run as Separate JVM" option with the Java adapter is set to TRUE.
QCCR1H104825 Integrations

After downgrading UCMDB to an earlier version (for example, from version 10.22 to version 10.21 or 10.20), because the version of the adapter is higher than the UCMDB server version, the adapter is not recognized and all integration points based on the adapter can not be loaded from the database.

Workaround After downgrading UCMDB to an earlier version, re-deploy the adapter package from the <UCMDBServer_install_dir>\content\adapters folder and restart the UCMDB server.

QCCR1H101184 Integrations

(UCMDB version 10.20 and later) UCMDB to BSM push integration does not work if attributes sizes is different. In UCMDB version 10.20 and later, the size for some OOTB attributes is 250, but in RTSM or BSM 9.05, the size is 100. Therefore, when trying to push CIs with large value from UCMDB to BSM, the integration does not work.

Workaround Check and make sure that the sizes of attributes between UCMDB and RTSM/BSM are synchronized before pushing CIs with large values.

QCCR1H104603 Integrations

When creating an integration point using the Cmdb 9.x Adapter, the integration point does not work on HTTPS protocol.

Workaround To make the connection work, add the certificate of the remote machine into the cacert file in the \DataFlowProbe\bin\jre\lib\security\cacert directory.

QCCR1H98251 Integrations

After upgrading from 10.20 to 10.21, manually redeploy the UCMDB 9.x integration adapter package located in the C:\hp\UCMDB\UCMDBServer\content\adapters directory.

If the package is not redeployed, the integration adapter still works, but the reconciliation issue fixed in QCCR1H92320 will re-occur.

QCCR1H91379 Integrations

When creating an integration point using the Cmdb 9.x Adapter, after clicking the OK button to save the integration point, the saving operation may fail after working for some time. This is caused by the long-running task DataAccessAdapterQueryGetSupportedClassConfigs.

Workaround Whenever you encounter a similar timeout issue and see DataAccessAdapterQueryGetSupportedClassConfigs in the log, you can go to the JMX console and increase the values for the following two settings:

  • task.DataAccess.Manager.getAdapterClassesConfig.timeOut. Default value for the setting is 20000.

  • configuration.remote.action.timeout. Default value for the setting is 35000.

QCCR1H98068 Integrations

You cannot create one integration point for both data push and population.

Workaround To create an integration point for both data push and population, do the following:

  1. Update the value for Object Root from managed_object to root.

    1. Log in to UCMDB with an administrator account and go to Administration > Infrastructure Settings Manager.
    2. From the Filter by column drop-down list, click Name, type Object Root in the text box and double-click the Object Root entry that is displayed.
    3. In the Properties dialog box, go to the Current Value field, change managed_object to root, and then click Save.
    4. Log out of UCMDB and log in to UCMDB again for the change to take effect.
  2. Add the discoverypattern_mdr_type attribute to Auto Discovery Pattern definition.

    1. Go to Modeling > CI Type Manager > CI Types pane > Root tree > Data > Object > Configuration, and click Auto Discovery Pattern definition.
    2. In the right pane, click the Attributes tab and click the Add button.
    3. In the Add Attribute dialog box, type discoverypattern_mdr_type in the Attribute Name and Display Name fields, and click OK.
  3. If you already create an integration point, delete it and create it again.
  4. Open the Adapter Source Editor dialog box and click Save.

    1. Go to Data Flow Management > Adapter Management > Resources pane, select the adapter that is related to your integration point.
    2. Right-click the adapter, select Edit adapter source.
    3. In the Adapter Source Editor dialog box, click Save.
QCCR1H92081 Integrations

When creating a new inherited CI Type in which the parent has identification based on key attributes, it will be by default inherited by the child CI Type, without the possibility of changing it. For example, creating an inherited CI Type from Person will inherit its identification by key attribute by default. So if you choose to change the identification with reconciliation rule, the whole identification will be the Person identification by key + identification by rule.

Workaround When creating the new CI Type inherited from Person, change first the identification of Person by removing all attributes conditions, so the new identification of the newly created CI Type will be empty.

QCCR1H101639 Integrations

When trying to run a remote process using the Integration Service, the following error is returned: Failed to connect to remote process.

Workaround If you want to use the Integration Service to run a remote process, add the following jars to the basic_discovery_minimal_classpath setting in the <UCMDB_Server_Home>\integrations\conf\ file manually:

QCCR1H102098 Integrations The Integration Service cannot start due to a failure to connect to the database after you change the master key on the UCMDB server.
  Tenant Owner

After switching to Tenant aware reconciliation, the OwnerTenant attribute becomes read-only in the Configuration Item Properties dialog.

Workaround Use Assign Tenants functionality from the CI’s context menu.

  Tenant Owner

After removing the Key Attributes qualifier from the OwnerTenant attribute of the Managed Object, sometime no properties are displayed for the CIs in UI.

Workaround If you want to switch back (to disable Tenant aware reconciliation), do the following:

  1. Remove the ID_ATTRIBUTE qualifier for the TenantOwner attribute on the managed_object CIT.

  2. Remove the value of the reconciliation.tenantaware.citypes setting.

  3. Reload the class model from persistency (go to the JMX console > UCMDB:service=Class Model Services, and invoke the reloadClassModelFromPersistency method).

  4. Go to JMX console > UCMDB:service=Model Services, invoke the recalculateID method with classname field empty.

  5. Go to JMX console > UCMDB:service=Model Services, invoke the updateClasModel method.

  Tenant Owner Enrichment is not invoking the Reconciliation on Update OwnerTenant via Associate Tenant Rule. As a result, you may have duplicated data in the system in case if you update the OwnerTenant's CI to a tenant that already has this CI.
  Tenant Owner CIs with Identification rule would be duplicated in case if the user is updating the OwnerTenant CI to a tenant that already has this CI from Update OwnerTenant in the Assign Tenants module.
  Tenant Owner When adding Consumer Tenants to a CI, the System Default Tenant appears in the list of Consumers after saving, even if it was not selected. This issue occurs only when changing the Owner Tenant or the Consumer Tenant.
  Tenant Owner

When removing all Consumer Tenants from a CI (from the IT Universe), an error is thrown and the Owner Tenant is overwritten with the System Default Tenant.

Workaround To avoid removing the System Default Tenant from the Consumer Tenants list, make sure you set the System Default Tenant as consumer.

Only when the System Default Tenant is not set as consumer, the Owner Tenant will be overwritten with the System Default Tenant when trying to save.

QCCR1H104949 Tenant Owner

Error message received when setting up a tenant aware environment, for the OOTB enrichments which are adding CIs.

Workaround If there are enrichments which are creating new CIs, after setting the environment as tenant aware, the attribute Owner tenant should be set for those CI Types which are being created through enrichments.

QCCR1H116188 Server After you delete some historic tables, there is no history available for nodes which were created before historic tables were deleted, even if they are modified by hand or through a Discovery job.