QlikView: Task list empty after applying Unified Signed License Key (SLK)

[Maria_Halley]

If you were previously running a QlikView environment without a Publisher license and have now swapped to an SLK which includes a Distribution Service/Publisher license, all document reload tasks will be cleared. 

The same applies to moving a QlikView environment from a non-Publisher to a Publisher legacy serial number.

All existing document tasks are discarded when a Publisher is enabled. 

Before activating the SLK:

1. Verify if you have a licensed publisher
   
   In the QlikView Management Console, go to System, then switch to Licenses and verify if you have a Publisher listed and licensed. 
   
   Alternatively, review the System and Setup tab to see if you have a Distribution Service listed. 
   
   
2. Document your existing tasks, so they can be recreated.
3. Backup your QlikView Server(s) Backup Help Page 
4. Make a snapshot of the server to allow for quick recovery.
5. Apply the SLK
6. Recreate your tasks

If you already have a publisher license, you can apply the Signed License Key, without any effect on the tasks.

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.