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.
Dimensions CM server, agent, and clients:
|UNIX/Linux: Delta libraries issue during upgrade
On UNIX/Linux, if you use delta libraries, you may get the following message after upgrading Dimensions CM when you attempt to perform an item operation:
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.
On Solaris, if the solution doesn't resolve the issue, remove the libstdc++.so.6 and libgcc_s.so.1 files located in the following folder:
|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:
|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.
|Reverting and editing deleted files
|If you revert a change to a work area and restore a file, you must deliver the file to Dimensions CM before editing it. If you modify the file locally before committing the undo, the deliver operation reports a conflict.
On Solaris, dmpmcli is not supported, 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 14.5.1 and earlier versions of dmpmcli do not work with a Dimensions CM server 14.6 or later.
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 
If this happens, Dimensions CM has been installed successfully, and you can safely close the installer.
|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 is used instead.
|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.
For details about the agent auto update, see Administration.
|Solaris: Auto update not supported
|Auto update is not supported on Solaris.
|Auto update not supported with SSO
|Auto update is not supported when Dimensions CM is configured to use Single Sign-On (SSO).
Dimensions CM integrations:
|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:
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.
|The Uninstall button is not enabled when the Eclipse plugin was set up by a standalone installer (Defect 156112).
|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.
PulseUno known issues
For a list of known issues and limitations in PulseUno, see the PulseUno help.
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 attribute types URL and File for the SBM synchronizer.
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.
Developer dm command-line client: Updating a work area from a specific stream version (the tip is always used).