Known issues and limitations

This topic describes the known issues and limitations for Dimensions CM.

Dimensions CM known issues

Take into account the following known issues when working with Dimensions CM:

  • java.lang.NullPointerException when installing or upgrading to version 14.5.3 on UNIX

    On UNIX, when you install or upgrade to Dimensions CM 14.5.3 in console mode, and do not specify the host name for the remote Git or Vault server, the installer may respond with the following message:


    Solution: Specify the Git or Vault server host name and continue with the installation.

  • Upgrading to 14.5.3 in console mode on UNIX

    On UNIX, when you upgrade Dimensions CM in console mode, and choose not to install a local Git or Vault server, the installer doesn't let you configure the remote Git or Vault server connection.


    1. After the upgrade, navigate to the PulseUno data directory, for example:

      C:\ProgramData\Micro Focus\Dimensions CM\Pulse

    2. Edit the file by adding the following lines:

      Copy code
    3. Restart Common Tomcat.

  • Auto update on Solaris

    Auto update is not supported on Solaris.

  • Eclipse integration

    • The Uninstall button is not enabled when the Eclipse plugin was set up by a standalone installer (Defect 156112).

    • Eclipse 2021+: When you assign users during delegating a request, you may get the following error:

      SWTException: Graphic is disposed.

      Solution: Use another client to delegate requests.

  • Auto update not supported with SSO

    Auto update is not supported when Dimensions CM is configured to use Single Sign-On (SSO).

  • SBM 11.7 SSO support

    SBM 11.7 Single Sign-On is not supported by default, but you can configure it to work.

    The following files are included with Dimensions CM:

    File Location
    sts.pem.SBM.11.7 \dfs
    truststore.jks.SBM.11.7 \common\tomcat\8.5\alfssogatekeeper\conf

    To configure Dimensions CM to work with SBM 11.7 SSO:

    1. Stop Common Tomcat and the Dimensions CM listener.

    2. Rename dfs\sts.pem.SBM.11.7 to dfs\sts.pem.

    3. Rename common\tomcat\8.5\alfssogatekeeper\conf\truststore.jks.SBM.11.7

      to common\tomcat\8.5\alfssogatekeeper\conf\truststore.jks

    4. Start Common Tomcat and the Dimensions CM listener.

  • Installing PulseUno agents on UNIX

    On UNIX, you cannot install PulseUno agents into locations that contain spaces, for example:

    /var/opt/Micro Focus/Pulse Agent/bin

  • Rebasing part of a stream

    If you are working with selected files or folders in a stream, and then rebase the stream, we recommend that you do the following after the rebase:

    1. Delete the local work area.

    2. Get a fresh copy of the stream to the work area.

  • Rehoming a topic stream from a project

    You cannot rehome a topic stream work area back to a project, only to another stream.

    Workaround: Delete your work area contents and refetch the project.

  • dmpmcli on Solaris

    dmpmcli on Solaris doesn't work, as the installer doesn't provide a JRE.

    Workaround: In the file $DM_ROOT/dmpmcli update the path in jre/bin/java to the correct value for your system.

  • Dimensions CM/RM Integration

    If you are using the Dimensions CM and RM integration, the length of the User login id field in RM is limited to 25 characters.

    If Dimensions CM is installed on the same machine as RM Manager, you must use the Dimensions CM client 14.4 or earlier.

  • Deployment Automation

    • If you installed Deployment Automation as part of a CM agent installation on Windows, uninstalling CM may not delete the Deployment Automation directory.

    • Deployment Automation can prevent the shutdown of Common Tomcat. If the Tomcat process persists after you attempt to shut down, you can safely end the process manually.

  • Reverting and editing deleted files

    If you revert a change to a work area and restore a file, before editing the file you must deliver it to CM. If you modify the file locally before committing the undo, the deliver operation reports a conflict.

  • Upgrade dmpmcli

    Dimensions CM 14.5.1 and earlier versions of dmpmcli do not work with a Dimensions CM 14.5.3 server.

    Solution: Use dmpmcli version 14.5.2 or later.

  • Installing on AIX

    If you run an installation on a heavily loaded AIX system, the installation wizard may not finish cleanly and may stop responding while displaying this message:

    The Install Shield Wizard has successfully installed Dimensions CM 14.5.2. Choose Finish to exit the wizard. Press 3 to Finish or 5 to Redisplay [3]

    If this happens, Dimensions CM has been installed successfully, and you can safely abort the installer.

  • Eclipse Integration Installer

    The Eclipse integration installer on Windows Server 2012 R2 may fail with the following error:

    Installer User Interface Mode Not Supported

    Solution: Run the installer in compatibility mode:

    1. Right-click the executable and select Troubleshoot compatibility.

    2. Select Try recommended settings and accept the settings.

    On Windows Server 2012 R2 and Windows 8.x or later, the installer may still fail when run in compatibility mode, and display this message:

    ZeroGu6: Windows DLL failed to load.

    This is caused by an incompatibility between the Java runtime embedded in the integration installers and recent versions of Windows. To resolve the issue, install a 32-bit Java 7 or 8 runtime.

  • Araxis Merge not Registered

    If you installed and uninstalled a trial version of Araxis Merge, the Dimensions CM instance of Araxis Merge may not be registered. Remove the expired license in the Windows registry by deleting the SerialNumber value under:


    The registration information provided by Dimensions CM will be used instead.

Back to top

PulseUno known issues

For a list of known issues and limitations in PulseUno, see the PulseUno online help.

Back to top


The following features and functionality are not supported in the latest version of Dimensions CM:

  • The PulseUno Git and Vault servers are not supported when using Serena SSO.

  • File encryption using DM_FILE_ENCRYPTION. Use SSL Secured SDP (SSDP) instead.

  • HTTP connector when the server is configured for SSL using the SSDP protocol.

  • SBM 11.2 attributes URL and File.


  • DM_USE_OLD_CRB server symbol.

  • SCC plugin with Microsoft Visual Studio 2013 and later. Earlier versions of Microsoft Visual Studio may work with the DM_SCC_ENABLE configuration variable.

  • UPDATE command /NOEXECUTE qualifier.

  • Developer dm command-line client: Updating a work area from a specific stream version (the tip is always used).

Back to top

See also: