Upgrade and Migration

Note: For a detailed list of changes and issues when upgrading from QlikView Server 11.20, read the following Qlik Support article: QlikView 11.20 End of Life Upgrade: Known Issues and changes in product behaviour.
Note: When you upgrade from QlikView Server 11.20 to QlikView Server 12.10 or later, your installation might encounter a variety issues due to backend file system. QlikView Server 12.10 and later versions are more disk intense and require bigger file server than QlikView 11.20. When planning your QlikView deployment, it is important to keep in mind the type of storage and resource capacity. For more information, read the following Qlik Support article: QlikView and its backend File Share System.

For a successful upgrade of QlikView Server, take the following basic practices into account:

  • Back up the current QlikView data directory, which includes most of the log and some of the configuration files as well as the document folders. The files are typically located in %ProgramData%\QlikTech.
  • Perform the upgrade during a scheduled downtime – QlikView Server must be stopped for the upgrade to be successful.
  • Licensing information and settings are saved by default when QlikView Server is removed. They are applied to any subsequent installation of QlikView Server on the system.
  • If Digital Certificate Authentication is used for QlikView Service communication, the new certificates that are created during the upgrade must be installed. See Update certificates.

Note: The installation does not support upgrade from beta or release candidate versions of QlikView Server.

To install QlikView Server, proceed as follows:

  1. Verify that backup media exists for the current release of QlikView Server and back up all current files associated with QlikView Server (HTML pages, QlikView documents, licensing file, QlikView Server .shared files, and so on).
  2. Install QlikView Server.

Multi-machine Preparation

When upgrading an installation that is spread over multiple machines, extra planning is required, since versions cannot be mixed arbitrarily.

Simple Upgrade

This procedure requires no special planning and involves the smallest risk, but causes the system to be down for some time.

Proceed as follows to perform a straight-forward upgrade:

  1. Perform a backup.
  2. See: Upgrade and Migration

  3. Stop all services running on all machines.
  4. Upgrade the services on each machine (in any order).
  5. Start all services on all machines.

Update certificates

The new certificates that are created during an upgrade must be installed on machines running QlikView services. Certificates do not need to be installed on the machine running the QlikView Management Service.

Proceed as follows:

  1. Open the QMC.
  2. Click the Status tab, and then click Services.
  3. Note any services that are disconnected.
  4. Click the System tab, and then click Setup.
  5. Select a service, and then click the General tab for the service.
  6. Click the Apply button in the bottom right of the window, and then follow the instructions to install the certificate.
  7. When you are done, navigate back to Services on the Status tab to verify that the service is now running.

Maximize Uptime

This procedure requires more planning, but the system uptime (from an end user point of view) is maximized.

Proceed as follows to perform the upgrade:

  1. Perform a backup.
  2. See: Upgrade and Migration

  3. Stop QMS (which means QMC becomes unavailable).
  4. Upgrade in the following order (let the installer restart the services):
    1. Web servers
    2. Directory Service Connector (DSC)
    3. QlikView Server (QVS)
    4. QlikView Distribution Service (QDS)
    5. QMS
  5. Start QMS (which means QMC becomes available again).

Migration to a New Machine

Note: This procedure is specific for migrating QlikView Publisher Repository (QVPR) only.

An alternative way is to build the new environment on new servers.

Proceed as follows to perform a migration to a new machine:

  1. On the new machine, install a running, licensed version of QlikView Server.
  2. On both machines, stop all QlikView services.
  3. On the new machine, remove or rename the %ProgramData%\QlikTech\ManagementService\QVPR folder.
  4. On the new machine, remove or rename the %ProgramData%\QlikTech\ManagementService\qvpr_<NewMachineName>.ini file.
  5. Copy the QVPR folder and the .ini file “as is” from the old machine to the new one (that is, keep the folder name).
Note: All QlikView servers must have the same regional settings. Different regional setting may cause errors when loading QlikViewXML reference files.
  1. Rename the .ini file (that is, change qvpr_<OldMachineName>.ini to qvpr_<NewMachineName>.ini).
  2. Change all references from <OldMachineName> to <NewMachineName> in the QVPR .xml files.
  3. Start the QlikView services on the new machine.
  4. In QMC, change the source folder path to the correct folder (or the tasks cannot be edited).
  5. Shut down the old machine.

Did this information help you?

Thanks for letting us know. Is there anything you'd like to tell us about this topic?

Can you tell us why it did not help you and how we can improve it?