Search:     Advanced search

Migrating from the 32-bit Helix ALM License Server to the 64-bit License Server on the Same Computer

Article ID: 282  |  Last updated: 30 May, 2017

This article explains how to migrate data from the 32-bit Helix ALM License Server to the 64-bit server for the same license server version on the same computer.

If you need to upgrade the license server when you upgrade Helix ALM or Surround SCM, we recommend upgrading all 32-bit client and server components first to make sure the upgrade is successful before migrating to the 64-bit server. See the Helix ALM or Surround SCM help for information about upgrading.

Migrating to the 64-bit license server

  1. Make sure the computer you are installing the 64-bit license server on meets the minimum system requirements.
  2. Stop the Helix ALM License Server and any other Helix ALM or Surround SCM servers if they are running.
  3. Back up the license server database.
  4. If you use a license server 2011.0 or earlier native database, make sure it is converted to native SQLite format (LSServer.db). The database is automatically converted to SQLite when upgrading to the 32-bit license server 2011.1 or later.
  5. If you use SQL Server, create a unique 64-bit ODBC DSN to replace the existing 32-bit DSN configured for the license server.
  6. To determine which installer to run if you use both Helix ALM and Surround SCM, check the Helix ALM and Surround SCM release notes for the versions you use to see which license server version each installer includes.

    Use the installer that includes the more recent license server version to install the 64-bit license server. Check license server version compatibility to make sure the version you will install is compatible with the Helix ALM and Surround SCM versions you use.

  7. Install the 64-bit license server.
  8. If you use an Oracle database, install the 64-bit Oracle OCI Client.
  9. Check the license server database location.

Installing the 64-bit license server

Note: In Helix ALM (and TestTrack 2015.1 - 2016.1) and Surround SCM 2014.1 and later, the 32-bit and 64-bit server components are bundled in the same installer. Run the installer you used to install the 32-bit components again and select to install 64-bit applications. For Surround SCM 2014.0 and earlier and TestTrack 2015.0.2 and earlier, 32-bit and 64-bit components are in separate installers.


  1. Run the Helix ALM or Surround SCM installer and select the license server components to install.

    Make sure to install the 64-bit license server components in a different directory than the 32-bit components.

    Note: Select ‘Do not start the Helix ALM License Server’ when prompted so you can move your existing database before starting the 64-bit server.

  2. If you use a SQLite native database, copy the LicenseServDb directory from the 32-bit license server application directory to the 64-bit directory. By default, the 32-bit license server application directory is C:\Program Files (x86)\Perforce\License Server and the 64-bit directory is C:\Program Files\Perforce\License Server.


  1. Run the Helix ALM or Surround SCM installer and select the license server components to install.
    The 32-bit and 64-bit servers are installed in the same directory. The default application directory is /var/lib/splicsvr.

Back to migrating steps

Installing the 64-bit Oracle OCI Client

If you use Oracle, download and install the 64-bit Oracle OCI Client. The required Oracle libraries must be installed in the 64-bit license server application directory.

Back to migrating steps

Checking the license server database location

  1. Start the Helix ALM License Server.
  2. Start the Helix ALM License Server Admin Utility.
  3. Check the server database location in the server options to make sure the correct database is used.

    If you use a SQLite native database, make sure the database in the 64-bit directory is selected. If you use Oracle, PostgreSQL, or SQL Server, you may need to change the database connection information.

Back to migrating steps

Article ID: 282  |   Last updated: 30 May, 2017
move 64-bit migrate

Prev   Next
Setting SQL Server Unicode Options     Oracle Native RDBMS Connection Not Open Error