QlikView task list empty after applying Unified Signed License Key (SLK) in a non-Publisher environment

[Maria_Halley]

If you were previously running a QlikView environment without a Publisher license and have now swapped to an SLK (Signed License Key), all document reload tasks will be cleared. The same applies to moving a QlikView environment from a non-Publisher to a Publisher with a legacy serial number, as both instances enable Publisher and discard all existing document tasks. 

Always back up your QVPR before applying a new license or replacing an existing license. See QVPR database files.

The instructions in this article only apply to non-Publisher environments. If you already have an active QlikView Publisher, applying an SLK will not affect your tasks.

Before applying the SLK

A QlikView Server-only environment (no licensed Publisher) has the following configuration and user interface available in the QlikView Management Console (QMC) :

• The QlikView Server License tab and Client Access License (CALs) tab
  
  
• A list of existing Tasks (Document Tasks)
  
  
• The User Documents tab listing all available documents (apps); any documents with a reload task will be indicated with an alarm clock icon
  
  

After the SLK has been applied

All Publisher functionality is enabled as soon as an SLK has been applied. The following configuration and user interface will be available:

• The Signed License Key tab and the Professional and Analyzer access tab 
  
  
• All pre-existing tasks (User Document tasks) are removed
  
  
• The Documents tab now includes a Source Documents sub-tab
  
  

As a side effect, all Document Tasks are lost.

How to recover pre-existing tasks

To recover pre-existing tasks and revert to a non-Publisher environment while retaining the SLK license, including Professional and Analyzer license management, follow these steps:

1. Stop all QlikView services
   
   
2. Restore the previously backed-up QVPR (see How To restore the QVPR from a backup or how to recreate the QVPR)
   
   This reverts QlikView to the previous state, removing the Professional and Analyzer management tab.  
   
   
3. Within the restored QVPR folder, open the QlikViewServerResource.xml file in a text editor
   
   The upcoming modifications re-enable the Professional and Analyzer management tab, which is crucial for managing your QlikView environment.
   
   
4. Modify the LicenseModel value from “Legacy” (A) to “New” (B)
   
   
5. Save the changes
   
   
6. Restart all services

Following this change, your QlikView environment will function as if it does not have a Publisher license, though you will retain the User Interface:

• The Professional and Analyzer access tab remains in place, allowing for license management
  
  You need this tab to manage your license and user assignments.
  
  
• Source Documents remains in place but is empty and offers no functionality
  
  
• User Documents do not retain the alarm clock icons for documents (apps) with existing tasks, but the tasks are now visible in the Tasks overview and run as expected
  
  Tasks can still be added and edited in the User Documents view, but can also be managed from the Tasks list.
  
  

Initially, after changing LicenseModel from Legacy to New, or if the Service Dispatcher has not been restarted, the tasks may appear as Unrunnable.

Restart the services to clear this, specifically the Service Dispatcher.

Related Content

• How to remove Publisher License from QlikView Environment 

Environment

• QlikView

[NZFei]

The problem is that after applying SLK and all the reload tasks disappeared, I am not allowed to create any reload tasks. And also I am not allowed to assigned any licenses!

[peter_turner]

This can be quite an issue, especially now when renewing subscriptions/licences, as QlikView can get included as an 'Add-On' to Qlik Sense Client Managed or Qlik Cloud.

The unified key can be used on multiple products, and includes QV Publisher - but this is not documented or mentioned anywhere.

As a result a customer may apply the unified key to their QV server, which automatically and silently also unlocks QV Publisher. All existing tasks are removed as part of that unlock and there are no confirmations or prompts to warn you.

You have a couple of options at that point.
1. Use QV Publisher and re-create the tasks (there are some community guides on this)
2. Try to restore the tasks and keep Publisher (again an article on the community for this)
3. Restore a backup of the ProgramData\QlikTech folder to revert the licence change. Then raise a case with Qlik to remove Publisher from your licence, then reapply the key.

There have been multiple instances where option 3 has been the quickest of those bad options. Hopefully Qlik will make changes to QV and documentation to at least warn customers before a licence update breaks their entire environment.