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:

  • UNIX/Linux: Delta libraries issue during upgrade

    On UNIX/Linux, if you are upgrading Dimensions CM and use delta libraries, you may get the following error during upgrade:

    Error: No delta package available when attempting item operations

    Solution: Copy the libmlclient64.so library from your earlier Dimensions CM installation, or contact Support for a copy of this file.

  • UNIX/Linux: Agent auto update may not work if using an installation package created on Windows

    On UNIX/Linux, if you are running agent auto update using an installation package created on Windows, the agent is not upgraded. This may happen when an installation package is created on a Windows machine and auto update scripts and binaries don't have proper permissions for a UNIX/Linux platform.

    Solution: Create the installation package on UNIX/Linux. Before running the CIP command, change the permissions for installation package files to 755. For details about configuring auto update, see Administration.

  • SBM 11.8 SSO logout error

    When you log out of the Dimensions CM web applications or PulseUno as an SBM 11.8 SSO user, the logout from SBM fails.

    Solution: Upgrade SBM to version 12.0.

  • 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).

  • 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

    • Windows: If you installed Deployment Automation as part of a Dimensions CM agent installation, uninstalling Dimensions 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.6 server.

    Solution: Use dmpmcli version 14.5.2 or later.

  • AIX: Installation wizard stops responding on a heavily loaded system

    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. 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 close 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:

    HKEY_CURRENT_USER\Software\Araxis

    The registration information provided by Dimensions CM is used instead.

Back to top

PulseUno known issues

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

Back to top

Limitations

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

  • 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_CONCURRENT_DELIVER_LOCK_MODE server symbol.

  • 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: