Upgrading from Qlik Sense 3.1 SR2 or later to Qlik Sense June 2017 or later

Before you upgrade, if your Qlik Sense 3.1 SR2 or later installation is running services using a Local System account, you need to change this to use a service user account (local or domain) before upgrading to Qlik Sense June 2017 or later. If you continue to use a Local System account to run the services when upgrading you will get an error.

Changing the user account type to run the Qlik Sense services on a central node

Выполните следующие действия.

  1. In Windows, either create a new or use an existing domain or local user account to run the Qlik Sense services.
  2. If the service account user does not have administrator privileges, you must add the user to the following groups in Computer Management > System Tools > Local Users and Groups > Groups.

    • Qlik Sense Service Users
    • Performance Monitor Users
  3. Open the Control Panel and then select System and Security>Administrative Tools>Services.
  4. Stop all services except the Repository Database.
  5. Assign Full control permission for the dedicated service account to the folder %ProgramData%\Qlik\Sense.
  6. As an administrator, open an elevated command prompt.
  7. Navigate to the Program Files\Qlik\Sense\Proxy folder and run Proxy.exe -bootstrap.

    Qlik Sense proxy service

  8. Navigate to the Program Files\Qlik\Sense\Scheduler folder and run Scheduler.exe -bootstrap.

    Qlik Sense scheduler service

  9. Navigate to the Program Files\Qlik\Sense\Repository folder and run Repository.exe -bootstrap.

    If you are changing the user account on your primary or central node, run Repository.exe -bootstrap -iscentral.

    Qlik Sense repository service

  10. Close the elevated command prompt.
  11. Change the log on credentials for each of the Qlik Sense services as follows:
    1. Right-click the service and select Properties.
    2. Select the Log On tab and then This account.
    3. Enter the credentials for the dedicated service account and click OK.

    The services are as follows:

    • Qlik Sense Engine Service
    • Qlik Sense Printing Service
    • Qlik Sense Proxy Service
    • Qlik Sense Repository Service
    • Qlik Sense Scheduler Service
    • Qlik Sense Service Dispatcher
    Примечание: If you are using a user account with administrative privileges, keep the Qlik Sense Repository Database running under the Local System account. Do not change the account.
    Примечание: Depending on your setup some of the services may not be available.
  12. Start the Qlik Sense Service Dispatcher, and then the Qlik Sense Repository Service (QRS).
  13. Start the rest of the Qlik Sense services.

Upgrading from Qlik Sense 3.1 SR2 or later with a shared persistence model to Qlik Sense June 2017 or later

Выполните следующие действия.

  1. Stop your Qlik Sense services.
  2. Upgrade your central node by launching the Qlik Sense setup file (Qlik_Sense_setup.exe).
  3. Select Upgrade to upgrade your existing shared persistence deployment.
  4. Accept the license agreement and click Next.
  5. On the Service Credentials page, enter the Username and Password for your Windows Qlik Sense service user account.

    If the user is member of a domain, enter the service account as <domain>\<username>. For more information, see User accounts.

  6. On the Ready to upgrade page, select the appropriate check boxes if you want the setup to create desktop shortcuts and automatically start the Qlik Sense services when the setup is complete, and click Upgrade.
  7. Check that all of the Qlik Sense services have started successfully.
  8. Check that all apps have been migrated successfully on the central node. If migration has failed for one or more apps, resolve the issues before continuing.

    Предупреждение: If the node running the app migration goes offline, migration will stop. It will not restart automatically. In a single node environment, all apps will have Migration status set to Unknown. See: Migrating apps. In a multi-node environment with failover nodes, the primary node will be replaced by the next available node, but migration will not restart. See: Failover. To resume migration, you will need to restart the following services, in order: Qlik Sense Service Dispatcher (QSD) and Qlik Sense Repository Service (QRS). See: Services.
  9. Deploy the Qlik Sense upgrade with shared persistence on the remaining nodes.
  10. Примечание: Any custom manual configurations that you make to the PostgreSQL database must be manually reproduced after the upgrade.