Known issues

For a complete and up-to-date list of defects and fixes found in the latest release of Deployment Automation, see the Knowledge Base.

Here are the issues known to exist at the time of release:

  • AIX: installation wizard stops responding when finished.

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

    The InstallShield Wizard has successfully installed Deployment Automation. Choose Finish to exit the wizard. Press 3 to Finish or 5 to Redisplay [3]

    If this happens, you can safely abort the installer. Your server installation is complete.

  • Version import for Nexus Sonatype components is no longer working.

    Starting from Deployment Automation 6.3.2, Nexus Sonatype no longer cuts off parts of the server URL. If you have used a URL with a relative path, the relative part now remains intact.

    For example, in version 6.3.1, Nexus Sonatype converted the http://localhost:8080/nexus path into http://localhost:8080.

    After the upgrade, you might need to reconfigure the components that use Nexus Sonatype as a source config type.

  • Connecting a 4.5.1 agent to the DA 6.3.2 server through HTTPS.

    To connect a 4.5.1 agent to a 6.3.2 server through HTTPS, you must first manually upgrade the agent's JRE to version 1.8.

    If the agent was installed with the bundled JRE, open the /jvm directory on your agent and replace all its contents with JRE 1.8 files.

  • Replication import fails on Oracle.

    If replication import fails on Oracle with the error ORA-01000, the maximum open cursors limit has been exceeded. To change the limit on the database side, run this SQL query:

    alter system set open_cursors = <limit_number>;

  • Importing secure properties and property definitions, and passwords.

    Deployment Automation 6.3 and earlier: secure properties and property definitions, and passwords, are not resolved if they are imported from servers version 6.3.1 or later.

  • Importing replication data.

    Deployment Automation 6.3 and earlier: importing data from servers version 6.3.1 or later is not supported.

  • AIX: uninstaller does not work.

    The DA server uninstaller does not work on AIX.

    Workaround: Remove directories /opt/MicroFocus/da and /var/opt/serena/inventory.

  • uBuild source configuration type.

    uBuild is no longer supported.

    Workaround: Use the Deployment Automation API to develop your own plugin to support uBuild.

  • OpenJDK

    Deployment Automation 6.3.1 and later uses OpenJDK. A server installation cannot be completed if the glibc dependency is missing.

    Solution: Install the glib dependency for your operating system, for example:

    CentOS: yum install glibc.i686

    Ubuntu: apt-get install libc6.i686

  • Running DA installer on CentOS.

    To run the DA installer on a minimal CentOS, run this command in a terminal: yum install bc

  • z/OS agent cannot be upgraded from server.

    The z/OS agent cannot be upgraded from the Deployment Automation server.

  • Pending approvals not completed before upgrade are revoked.

    Any pending approvals at the time of upgrade cannot be completed properly in the updated version due to architectural changes. You should complete them before upgrading if possible. Otherwise, after upgrading, you must rerun or reschedule the associated requests to initiate a new set of approvals.

  • Deployment Automation has limited support for IPv6 IP addresses.

    If you are using IPv6 IP addresses on your network, you must use hostname instead of IP address in Deployment Automation agent or agent relay configuration.

    Here are the known issues for IPv6 addresses:

    • If you use IPv6 IP addresses in agent or agent relay configurations, you must use brackets around the address and with the colon character (:) escaped with a backward slash (\), for example, [fc00\:\:a1f\:2007].

      If you do not do this, the agent or relay does not connect and an error similar to the following is displayed in the log:

      java.lang.IllegalArgumentException: hostname can't be null

    • If you run a process using the agent or agent relay configured using an IPv6 address, the process fails.
  • Chrome web browser HTTPS connection fails on HPUX server.

    You cannot connect to Deployment Automation through HTTPS in a Chrome web browser if your Deployment Automation server is installed on HPUX. You can connect through other web browsers, such as Internet Explorer or Firefox, if you add an exception to the browser.


    1. In the in the server.xml file, find the commented out connector block that contains cipher attributes by searching for the word ciphers. The default directory for the file is

      C:\Program Files\Micro Focus\common\tomcat\8.5\conf

    2. Insert the entire ciphers= attribute into the connector block that is being used for HTTPS and save your changes.
    3. Restart Common Tomcat.
  • The client now requests a WebSocket connection upon initial connection to the server. If you receive a WebSocket error, you may need to configure your proxy server to support the WebSocket connection. In some cases, the proxy server may need to be upgraded. For more information, see Knowledge Base item S141934.

  • Agents may not come back online after server upgrade.

    Due to changes to supported security protocols starting in version 6.1.1, Deployment Automation agents using earlier versions of Java, such as Java 6, may not be allowed to connect to the server after the upgrade. If your agents do not come online after the server upgrade, upgrade them by following the instructions in Knowledge Base item S141622.

  • When a large number of agents are moved from one unidirectional agent relay to another, agents of versions prior to 6.1.2 may not automatically appear online.

    When a large number of agents are changed to point to a different unidirectional agent relay, agents of versions prior to 6.1.2 may not automatically come online. They may be listed as CONNECTED or OFFLINE.

    Solution: To bring them online, click the Test icon in the Agents / Pools pane, or restart the agents.

  • Installer page disappears when installing the agent on RedHat 7.3 that uses the Adwaita theme.

    If you are using the RedHat 7.3 with the Adwaita theme and try to install the Deployment Automation agent, the installer page disappears and you cannot complete the installation. This is due to the fact that the Adwaita theme is missing some objects used by installer. This works fine with other themes, such as Oxygen. For details on changing the theme, see Knowledge Base item S142064.

  • Error configuring the ALM Solutions Connector 6.1.3 services when running encrypt.cmd to encrypt the almsernet properties.

    When configuring the ALM Solutions Connector almsernet service, if you run encrypt.cmd to encrypt the files, the following error occurs:

    Could not find or load main class com.serena.sernet.httpserver.util.Encrypt

    Workaround: Edit the ..\webapps\almsernet\WEB-INF\encrypt.cmd file and change almsernet-8.1.0.jar to almsernet-8.1.2.jar.

    Back to top

    See also: