Known Upgrade Issues




Although the CloudShell Pro installer should leave all of your current configurations intact, it does overwrite your existing applications. This may inadvertently affect some of your current settings. It is therefore imperative to back up your databases before upgrading.

TestShell API

Updating drivers using TestShell API assets:

  • After upgrading to CloudShell Pro, you need to manually update the TestShell API asset in Authoring, and then recompile any drivers using the API methods.
  • Drivers using the API to update values in the Quali Server only require updating of the asset.

Check in all libraries prior to upgrading

Verify that all the libraries are checked in. Checked out libraries are indicated by a different color icon. The parent folder also indicates if the folder contains a checked-out library.


Upgrading to CloudShell Version: 2020.2 GA is supported from any GA or patch version starting with 6.x GA.

If you need to upgrade from an earlier version, contact Quali Support.

Note: Patches must be installed on GA versions only. Installing a patch on a non-GA version will result in unexpected behavior which may corrupt the database.


Real-time virus protection may affect performance.

All CloudShell upgrade overrides custom configuration files, including customer.config, webconfig.xml, Quali.vbs, WebPortal.vbs, httpd.conf and LanguagePortal.Override.xml. Therefore, copies of the latest files need to be saved and applied after upgrade.
Sisense Starting with CloudShell 2020.2, Sisense server and Quali Server cannot be installed on the same machine. In version 2020.2, Quali Server uses a dedicated RabbitMQ installation, resulting in a coexistence clash with the Sisense server's RabbitMQ.