After applying a valid Signed License Key (SLK), the QlikView Server (QVS) remains Unlicensed in the QlikView Management Console. This occurs while a network proxy is used on the QlikView server host.

Resolution

This solution requires QlikView May 2024.

1. Navigate to %ProgramData%QlikTech\ManagementService\QVPR\ 
   
   
2. Locate LicenseService.xml and open it in an editor (may require administrative permissions)
   
   
3. Find the <LicenseService> section and modify the following parameter values to localhost:
   
   (A) ServerAddress="https://localhost:9200/"
   (B) ServerName="LicenseService@localhost"
   
   
   
   
4. Save the changes to LicenseService.xml
   
   
5. Navigate to %ProgramData%QlikTech\QlikviewServer\
   
6. Locate Settings.ini and open it in an editor (may require administrative permissions)
   
   
7. Find the [Authentication] section and change the following parameter's value to localhost:
   
   (C) NxServiceConnectionString=http://localhost:9200
   
   
   
   
8. Find the [Settings 7] section and change the following parameter's value to localhost:
   
   (D) LicenseServiceUrl=http://localhost:9200
   
   
   
   
9. Still in the [Settings 7] section, add the following parameter:
   
   CustomLicenseServiceUrl=http://localhost:9200
   
   The CustomLicenseServiceUrl parameter is required to prevent the QlikView server from reverting to default license service settings. 
   
   For details, see How to Modify the QlikView Server Settings.ini file.
   
   
10. Restart all QlikView services

Cause

QlikView cannot reach the license server when a network proxy is configured on the host machine. 

Internal Investigation ID(s)

SUPPORT-6241, QV-23738, QV-23918

Environment

• QlikView all versions

With a Unified license (formerly called Dual Use License) the legacy QlikView license is complemented with a Qlik Sense license that can be applied to the QlikView server as it includes QlikView entitlement license attributes. Such license needs to be activated with the Signed License Key (SLK). When a customer enters an Analytics Modernization Program (AMP, formerly known as Dual Use program), QlikView CALs (e.g. Named User CALs, Document CALS, Session CALs and Usage CALs) are converted into Professional User, Analyzer User,  and Analyzer Capacity User allocations based on the Analytics Modernization Program conversion ratios.

Here are two scenarios:

I. If a customer transitions to AMP with on-premise (client-managed) Qlik software (e.g. converts to the perpetual estate or convert to subscription Qlik Sense Enterprise on Windows), a Unified License containing the converted quantity of Professional Users, Analyzer Users and Analyzer Capacity would be delivered. This license contains a customized Qlik Sense Enterprise Signed License Key (SLK) which can also be deployed on QlikView Server and/or QlikView Publisher. If a user is assigned a Professional or Analyzer user license, this assignment information is synchronized to all Qlik Sense and QlikView deployments activated using this Unified License key. As such one user just needs one license to access the entire Qlik software platform (regardless if it is Qlik Sense or QlikView).

In this scenario, as long as the QlikView Server and Qlik Sense edition use the same Identity Provider (IdP) the user can access apps on both environments consuming only one user license allocation.

If the user license is reallocated in any of the systems to a different user, the same will occur across both QlikView and Qlik Sense environments.

II. If a customer transitions to AMP with Qlik Sense Enterprise SaaS add-on, a Qlik Sense Enterprise SaaS tenant may use a Unified License  for the on-premise deployment. The customer is able to upload QlikView document prepared by the on-premise QlikView software directly into Qlik Sense Enterprise SaaS for distribution.

A QlikView Server or a Qlik Publisher software can be activated in two ways:

1) Using a legacy method with 16-digit QlikView license key and the corresponding control number

2) Using a modern Unified License with Signed License Key containing needed QlikView Server and Publisher Service attribute(s). In this latter scenario, user license assignment (Professional/Analyzer) and analyzer capacity would be synchronized with other deployments using the same Signed License Key as it is done in the Unified License model

If the customer opts to remain in Perpetual licensing, the existing QlikView license model can be retained. Otherwise, if the customer opts for conversion into Subscription licensing model, a set of QlikView subscription license attributes mirroring the existing QlikView perpetual license key setup would be delivered such that the customer switch to the subscription QlikView keys without the need for an immediate migration project towards using Unified licensing.

Note: Please note that Qlik is no longer starting clients on the Perpetual license model. See End of Perpetual License Sales 

Environment:

• QlikView 
• Qlik Cloud 
• Qlik Sense Enterprise on Windows 
   

Related Content:

• How to Apply an unified Signed License Key for QlikView and Qlik Sense
• Qlik Multi-Cloud Frequently Asked Questions (FAQ)

A Professional or Full entitlement was removed without any action from the tenant administrators.

Going to the Administration activity center and reviewing Events by filtering for the Event Type "com.qlik.license.assignment.deleted" or "com.qlik.license.assignment.updated" shows no activity.

Resolution

Always align entitlements between your environments.

Cause

If the same Signed License Key is also used by another tenant or on a version of Qlik Sense Enterprise for Windows, any change from those other environments will be synchronized to your tenant.

Because the action was not performed on the tenant itself, the tenant's Events section (or the Audit APIs) won't show them.

Environment

• Qlik Cloud Analytics

This template was released on September 29, 2025.

Many customers rely on the Capacity Consumption Report in Qlik Cloud to understand usage and billing patterns. Until now, deploying and refreshing this app required repetitive manual steps: downloading from the admin console, publishing it into a managed space, and re-publishing every time a new version was needed.

This approach made monitoring difficult and often left customers with out-of-date insights.

What's new

A new Qlik Automate template automates the end-to-end deployment of the consumption app into a managed space of your choice. Once set up, the app is refreshed daily - ready for admins or billing users to work with.

With this in place, you can:

• Stay current – The app refreshes once per day (morning CET), so your analytics reflect the latest usage data.

• Collaborate easily – Place the app directly into a managed space for shared access.

• Enable subscriptions and alerts – Users can subscribe to sheets or KPIs, or create alerts on thresholds that matter to them.

• Maintain governance – The template creates/uses the right spaces and applies roles automatically.

• Eliminate manual work – No more re-publishing or searching through personal space copies.

How it works

• The automation checks that you are on a capacity-based subscription (your app size must be 100MB or less; larger data sets still need to be deployed manually or via script).

• It ensures you are a TenantAdmin (required for license and app access).

• It creates a staging space (for imports) and a managed space (for sharing).

• It imports the latest version of the app into staging, then publishes it to the managed space.

• You can configure how many historic versions you want to keep in the shared space. By default, no staged apps are kept.

Scheduling

Since the underlying data is refreshed once per day in the morning CET, we recommend scheduling this automation to run around midday CET. This ensures that your managed space always holds the latest daily version of the app.

Requirements

• TenantAdmin role

• Capacity-based subscription

• Report size ≤100MB (larger reports cannot currently be deployed with Qlik Automate)

Get Started

1. Create a new automation, navigate to the App Installer category, and select the Capacity consumption app deployer template.

2. Update the variables (space names, versions to keep).

3. Test manually once.

4. Schedule it to run daily (around midday CET).

Once enabled, you’ll have a single source of truth for consumption reporting - ready to drive alerts, subscriptions, and collaborative analysis across your admins.

Related Content

• Review the Help documentation on the capacity report to understand its metrics and counters.

Environment

• Qlik Cloud

Before you can start using Qlik Sense Desktop, you need to authenticate yourself against a Qlik Sense Enterprise server. You need to have a working network connection to enable authentication.

The following requirements need to be met:

• A functioning network connection to the Qlik Sense Enterprise Client-Managed Server or Enterprise SaaS/Business tenant.
• Use of a Professional license. Analyzer licenses do not support Desktop Authentication
  For legacy token license: User and Login Passes allow Desktop Authentication
• No TEST license. Test licenses disallow the use of authentication links 
• Compatibility must be met. See Qlik Sense Desktop patch process and compatibility with on-premise installs and Qlik Cloud .

After you have been authenticated once, internet access is not required to continue using Qlik Sense Desktop. However, you have to re-authenticate yourself if thirty days have passed since you last authenticated.

Environment

Qlik Sense Desktop 
Qlik Cloud 
Qlik Sense Enterprise on Windows 
Qlik Sense Business 

Related Content 

Starting Qlik Sense Desktop | Qlik Sense on Windows Help 
Starting Qlik Sense Desktop | Qlik Cloud Help
Configuring Qlik Sense Desktop authentication link 
How to authenticate Qlik Sense Desktop against SaaS editions 
How to authenticate Qlik Sense Desktop against a Qlik Sense Enterprise on Windows server  

Q: When does the Qlik Talend Administration Console license information update?

A: Adding a license to the Qlik Talend Administration Console will update it immediately.

When using a High Availability (HA) setup, the license cache remains for 60 minutes, and it takes 60 minutes for the recheck of the license from the database (licenses table) to take place. In a scenario where the first license was only just applied to the primary Talend Administration Console, the second Talend Administration Console will check the database after 60 minutes.

If a license check should be forced, restart the Talend Administration Console service(s) that need their license updated, or manually add the license in the server, which will write over the license in the database.

Environment

• Qlik Talend Administration Console (TAC)

After otherwise successfully restoring a Qlik NPrinting backup, the license information remains blank. This information is expected to be restored as well.

Resolution

This has been addressed as defect QCB-31631.

Workaround:

Activate the Qlik NPrinting license manually.

Fix Version:

Qlik NPrinting February 2024 SR5 and later releases. See the Release Notes for details.

Environment

• Qlik NPrinting May 2023 SR6 and SR7
• Qlik NPrinting February 2024 SR3 and SR4

Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes or contact support with the ID QCB-31631 for reference.

Beginning on the 30th of January, Qlik introduced the concept of 3rd party runs in Qlik Automate. This is the first step towards a shift in our packaging that will focus on third-party runs only, while standard runs become free of charge.

This shift will happen over the course of a couple of months, giving you sufficient time to analyze your usage and make adjustments if necessary. Please reach out to your account manager if you have any questions.

Contents

• Timeline
• Standard run vs third-party run
• Standard runs
• Third-party runs
• Possible third-party runs
• Transition of existing entitlements
• Introduction of third-party runs (Jan 30th)
• Switch to new packaging (April 2nd)
• Enforcement of overages (May 6th)
• Packaging details
• FAQ

Timeline

The timeline below illustrates how the various stages of this packaging update will happen. In between each stage should be sufficient time to analyze your usage and prepare for the enforcement.

• January 30th: Introduction of third-party runs
• April 2nd: New third-party packaging is available for purchase 
• May 6th: Enforcement
  • Third-party limits for seat-based licenses
  • Third-party overages for capacity licenses

Standard run vs third-party run

Standard runs

An automation run is considered a standard run if it only executes blocks from the following categories:

• All Qlik connectors (Qlik Cloud Services, Qlik Reporting, Qlik AutoML, Qlik …)
• Base blocks (excluding Call URL & Cloud Storage)
• Mail & Microsoft Outlook

Example:

Third-party runs

An automation run is considered a third-party run if it executes any blocks that are not in the standard connector categories.

As a rule of thumb, a standard run will execute one or more blocks from third-party connectors. Among others, third-party connectors are connectors like Slack, Amazon S3, Microsoft Excel, Call URL. A full overview of all automation connectors if available here.

Example:

Every run of this automation will execute the Send Message (Slack) block.
This will make every run a third-party run as the Slack connector is a third-party connector.
The “Contains third-party blocks” label indicates that the automation contains an active third-party block.

Possible third-party runs

For a run to be considered a third-party run, we only evaluate executed blocks. If the third-party blocks in the automation were not executed, the run will not count as a third-party run. A block not being executed could be caused by many factors like Condition blocks, Filter List blocks, deactivated third-party blocks, ...

This illustrates that an automation with a “Contains third-party blocks” label will not necessarily generate third-party runs on every run.

Example:

This automation will only execute the Send Message (Slack) block if the reload fails (from the Do Reload block). This means it will only generate third-party runs depending on the state of the Condition block.

Transition of existing entitlements

Introduction of third-party runs (Jan 30th)

1. Customers who are entitled to included runs will get these as third-party runs
2. Purchased runs will be converted to third-party runs
3. Renewals before the end of March will maintain the same included third-party runs until next renewal.

Switch to new packaging (April 2nd)

1. Every new purchase will be using the new packaging
2. Renewals will revert third-party runs to the edition included quantity of the new packaging + any purchase of third-party runs using the new packaging

Enforcement of overages (May 6th)

1. When your monthly third-party runs are exhausted, overages will be enforced.
   1. For Capacity licenses with included third-party runs only, automations with active third-party blocks will no longer start and an overage status will be displayed. 
   2. For Capacity licenses with purchased third-party runs, overages will be charged according to your contract and configuration.
   3. For User based licenses with included or purchased third-party runs, automations with active third-party blocks will no longer start and an overage status will be displayed. 
2. Automations without active third-party blocks will continue to run (since they cannot generate third-party runs).

Packaging details 

The below table provides an overview of the new packaging for automations that will come in effect on April 2, 2025. Please reach out to your account manager for quotes and pricing related questions. 

FAQ

1. Will max concurrency be shared across run types?
Yes, both run types will count towards the same max concurrency.

2. Will usage of Qlik APIs through the Call URL block or other generic connectors count towards third-party runs?
Yes, when these blocks and connectors are used to make API requests to Qlik APIs, they will still count towards third-party runs. If you are missing blocks or functionality in a Qlik connector, please create an improvement request on our Ideation portal or support an existing request.

3. Will the new packaging have an included amount of third-party runs?
Yes, the new packaging will continue to provide some third-party runs for most editions of Qlik Cloud. Details are available in the above section "Packaging details".

4. Why are some automations with third-party blocks missing the label "Contains third-party blocks"?
An automation will only receive the label when someone performs a manual run or saves it in the editor. We are planning a new update that will apply this label to all automations with active third-party blocks regardless of someone saving them or not.
Please note that regardless of this label being on an automation or not, automation runs will still be evaluated and receive a correct billable yes/no label.

The video above demonstrates how to convert Qlik Sense Enterprise servers with Tokens to the Professional and Analyzer capacity licensing model.

The conversion breaks down like this:

• User Access Passes -> Professional
• Everyone else into Analyzer Capacity

Steps

1. Copy and Save existing User Access rules, storing for future reference.
2. Do the same for Login Access rules
3. Paste the Signed License Key (SLK) in the signed license box, and hit Apply
4. Recreate the Professional Access rules from scratch or copy and paste from the User Access Rule.
5. Validate the rule and click Apply
6. Recreate the Analyzer Capacity access rule from scratch or copy the Login Access rule
7. Validate the rule and click Apply

Environment

• Qlik Sense Enterpise

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Related Content 

Please refer to the Qlik Sense® License Conversion Policy dated March 2021 for details.

Transcript

Hello and welcome to this short video guide on upgrading a Qlik Sense token server to a Qlik Sense Professional and Analyzer subscription license.

Our starting point for this upgrade guide is a very simple Qlik Sense Enterprise server, which is using the token style license. That means users gain access using either a User Access or a Login Access pass. Token style Qlik Sense uses the legacy LEF license with a serial and control number activation. This will be replaced in the Professional and Analyzer model license with a Signed License Key (SLK).

Make sure that you copy or save the existing user access rules storing the rules for future reference. We will do the same for the login access rules. Copy and save the rule conditions for future reference.

When you're issued with your new Qlik Sense Enterprise Professional and Analyzer subscription license, you will be issued a new license key or a new tenant. You may continue to use the old Qlik Sense Enterprise token license for up to four months. This will allow you to stand up a new Qlik Sense Enterprise site with Professional Analyzer users in parallel, and transition over time; or do it in one big go.

In this example, we are going to upgrade an existing Qlik Sense token server using the Signed License Key to move it to the Professional and Analyzer user model. Paste the Signed License Key in the signed license box and hit apply. When the license is successfully applied, you will see the license number as well as a license summary on the summary page. In this example, we have 4 Professional Users, as well as 8,000 minutes of Analyzer Capacity per month. There are no user allocations carried over from the old token model.

We need to recreate the Professional access rules. You can create rules from scratch or copy and paste the old token rules to a new Professional allocation rule, like so. Make sure you validate the rule and then hit apply.

We will do the same thing for the Analyze Capacity access rule. Copy the old token access rule for login access and paste it in the analyze capacity access rule. Validate the rule and hit apply. A quick test will validate that the Professional user access rules are functioning correctly. And here we can see that a Professional user was successfully allocated according to the rule we've set up.

Now we will check that the Analyzer capacity allocation rule is also working as expected. Click on the license usage summary tab; and here you can see that 6 minutes of analyzing capacity have been consumed. Everything is working as expected.

Thank you for watching. We hope you found this video useful.

If you would like more information, take advantage of the expertise of peers, product experts, and technical support engineers by asking a question in the Qlik product forums on Qlik community; or check out the support program space. Here you can search for answers in the support knowledge base, learn directly from Qlik experts via support webinar like Techspert Thursdays, and don't forget to subscribe to the support update blog. Thanks for watching.

You are a prospective customer and are looking to purchase a Qlik Cloud subscription.

• See How to purchase Qlik Sense SaaS digital subscription.
• If you are looking to manage an active subscription, see Managing Your Subscription in My Qlik.

You are a prospective customer, having never purchased Qlik licenses before and are interested in learning more about Qlik products and making a purchase:

• Go to Qlik.com to browse our available offerings and engage in our Live Chat if you have questions.
• Or contact Sales directly.

You are an existing Customer, having previously purchased a license directly from Qlik and wish to purchase additional licenses or CALs:

• Please contact your Account Manager. If you are unsure who the Account Manager is for your company, contact Support using Live Chat.

You are an existing Customer and purchased your licenses through a third party (not directly from Qlik) and wish to purchase additional licenses or CALs:

• Please contact your Responsible Partner from which you previously purchased licenses. If you are unsure who your Responsible Partner is, contact Support using Live Chat.

Users can view all licenses by navigating between the Active and Expired tab.

1. Login to the legacy Support Portal by following this link or
   
   
   1. Login to Community (https://community.qlik.com) and click Support in the navigational ribbon
   2. Then click Licenses & Archived Cases 
   3. And choose View Licenses and Archived Cases to be redirected
      
      
      
      
2. On the Legacy Portal, click on View License Information or Archived Cases at the top of the page and select View My Licenses.
   
   
   
   
3. You will be redirected to the License List page or Legacy Cases list.
   
   Select Active (1) to view Active License.
   Select Expired (2) to view Expired Maintenance Licenses
   
   
   
   
   

1. If you would like to see a particular license, you can filter the list with the license key.
   
   

As a benefit of our Analytics Modernisation Program (AMP), a signed license key is issued as a unified license key. This enables the use of one license across Qlik Sense Enterprise on Windows and QlikView, granted the license has the required QlikView infrastructure attributes (QV_NODES for QVS, QDS_NODES for Publisher).

This allows for analyzer capacity to be shared across all systems using the same license.

Environment

QlikView 
Qlik Sense Enterprise on Windows 
With a Signed License Key (SLK) applied as a unified license across multiple environments 

Here is an example:

A QlikView server currently shows 18 minutes of consumption in the QlikView Management Console (Fig 1.) 

This can be accessed through: System (A) > Licenses (B) > Choose the License (C) > Professional and Analyzer access (D)

Fig 1

If a user accesses and consumes on a linked Qlik Sense Enterprise Server, the Qlik Sense Enterprise Management Console will show the up-to-date consumption. See Fig 2. Note the 24 minutes, an increase from the 18 we have seen in QlikView.

This can be accessed in the Qlik Sense Management Console > License Management > License usage summary

Fig 2

The usage on the server will be synchronized and shown on the other linked servers within approximately 10 minutes. See Fig 3 and note the 24 minutes, which matches the value in Qlik Sense.

Fig 3

For local consumption data, each server will store its own consumption and user information.   

For Qlik Sense Enterprise on Windows, the License Monitor app will show capacity consumption.

For the QlikView Server, the capacity consumption is shown and stored in the local session log file, with the CAL consumed being Analyzer Capacity, with a log entry like this:

RLS64 12.50.20200.0 20210412T132942.000+0200 20210412T133617.000+0200 C:/ProgramData/QlikTech/Documents/retail store performance.qvw 20190220T113522.000+0200 Socket closed by client 20210412T133601.000+0200 00:00:16 0.000000 10228 1303493 31 2 QTSEL\ghd 1718e2e6-5b1c-4b9e-87a9-d9200f55e37a Ajax QvWS 12.50.20200.0 browser.msie illa/5.0 (windows nt 10.0 On 4747 fe80::df3:cd38:b86f:50bd 58495 Analyzer Capacity 6 315dcfab-7448-4f4b-8209-ef34742b1abe

! Note: Do NOT modify the NPrinting Database for any reason using PG Admin postres query or any other execution tools as this will damage your NPrinting Deployment and prevent successful NPrinting Database backup and restore operations.

! Note: Do NOT restore an older version of an NPrinting Database to a New NPrinting server or restore a newer version of the NPrinting database to an older version of NPrinting Server.

Examples: 

• NP 21.0.0.0 to NP 21.0.0.0  This is OK
• NP 20.29.7.0 to NP 20.39.6.0 NOT OK  This will compromise your deployment of NPrinting
• NP 20.39.6.0 to NP 20.29.7.0 NOT OK  This will compromise your deployment of NPrinting

These rules apply to general releases and service releases: The point version of the NPrinting Database being restored must match the point version of NPrinting Server being restored to (see Backup and restore Qlik NPrinting).

• How to Identify an incorrectly/unnecessarily restored database: Identify NPrinting Server restored with incorrect NPrinting database version

! Note:  From NPrinting February 2020 and later versions, it is NOT necessary to enter a superuser database password

! Note: If you are making a backup for the Qlik Support team, please add the following NPrinting user information so that we can log onto the NPrinting Web Console following the local restore of the database (also ensure that NPrinting Authentication is enabled. Go to Admin > Settings > Authentication

This procedure is meant to backup and restore (partial backup and restore of these individual items is not possible*):

NP Web Console Items:

• NPrinting apps
• Tasks
• Connections
• Filters
• Schedules
• *Reports (can separately be exportable/importable however only and exclusively between identical versions of NPrinting. See Related Content section link below)
• Conditions and most settings applied to an existing system 

NP Backup zip File Contents (do NOT open and modify the contents of this file):

• A dump of the NPrinting database repository
• All files used by report templates
• All files related to reports published on the NewsStand
• All files related to On Demand reports
• The backup file size can be 'roughly' estimated by enumerating the size of the folder "c:\programdata\nprinting\apps"

Resolution:

NOTE:

• Do not unzip the backup file (np_backup.zip), simply copy it to

  c:\nprintingbackups​

Before Proceeding: Please log on as the NPrinting service account used to run the NPrinting Web Engine and Scheduler services before proceeding

• The video below makes no mention of the Qlik NPrinting License Service which was included on newer versions. It also needs to be stopped as documented below.
• If restoring to a different NPrinting server environment, see step 7 below for additional consideration not covered in the video below.

1. Stop only the following Qlik NPrinting services (do NOT stop any other services)

Open the Windows Service Manager (services.msc), and stop the following services (by right-clicking them, and then clicking Stop). This will ensure any manual or scheduled NPrinting Publish Tasks are not executed during the backup or restore process:

• Qlik NPrinting Engine Service (NOTE:  Stop all NP Engines connected to your NP server before proceeding)
• Qlik NPrinting Scheduler Service
• Qlik NPrinting WebEngine Service
• Qlik NPrinting Audit Service
• Qlik NPrinting License Service

2. Create a folder for the backup in:

C:\NPrintingBackups

3. Open Command prompt and change directory path

Do NOT modify any syntax or add any additional unnecessary spaces
Open the command prompt making sure to run cmd.exe as Administrator and change directory as follows:

cd C:\Program Files\NPrintingServer\Tools\Manager

4. Backup

Copy and paste the following backup syntax to the command prompt console. Replace superuserDBpassword with your password first used when installing NPrinting.

Qlik.Nprinting.Manager.exe backup -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin" --pg-password YourSuperuserDBpasswordHere​

Qlik.Nprinting.Manager.exe backup -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin"

Qlik.Nprinting.Manager.exe restore -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin" --pg-password YourSuperuserDBpasswordHere​

Qlik.Nprinting.Manager.exe restore -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin"

File C:\Users\domainuser\AppData\Local\Temp\2\nprintingrestore_20201203082300\files\xxxxxxxxxxxxxxxxxxxxxxxxxxxx does not exist in the source backup package. 

• These are references to NPrinting Apps/Connections/Reports that once existed and have been subsequently deleted from the NPrinting Web Console.
• For example, A report/connection/NP App may have been deemed retired, then manually deleted by a user with appropriate NP role permissions since it no longer served any specific purpose.
  

6. Start all NPrinting server services that were stopped earlier.

Restoring to a Different Environment

! Note:  If re-installing on existing or restoring to a different NPrinting server environment, ensure that the destination NPrinting server license is enabled/activated before restoring the NP database.

If restoring to a different NPrinting server environment (same NP database version as the NP server version that you have restored to),

Note that once the restore to the Target/Destination server is complete you will need to update the following applicable settings in the NP Web Console on the Target/destination server that the NP database has been restored to:

NPrinting Engine:

• Sept 2019 and earlier NPrinting versions: Update the NP Engine in the Engine Manager via the NPrinting Web Console. Add the name of the new NP Engine Computer name here and disable or delete the original NP Engine entry.
• November 2019 and later versions, you will need to follow the Resend Certificate section of the following article New Engine Certificate Installation Process and Resolving NP Engine Offline in order to resend the NPrinting Engine certificates

NP Connections:

• QlikView NP Connection paths if local QVW or QVP connection paths have changed
• Sense connections: if the Sense IDs, Proxy address and NP Identity (NP service account used on the target NP server) has changed at the time of the NP database restore

Qlik Sense Certificates (if using NPrinting Qlik Sense connections)

• April 2019 and earlier NPrinting versions: you will need to re-import the Qlik Sense certificates to the new NPrinting server
• If June 2019 and later NPrinting versions: you may simply copy the previously exported client.pfx file to the following folder and Restart all NPrinting server services
  

  C:\Program Files\NPrintingServer\Settings\SenseCertificates​

  
  
  • How to Connect NPrinting to Single or Multiple Qlik Sense servers (NP June 2019 and later versions only)
• NPrinting May 2023 and Newer: If working exclusively with May 2023 and later NPrinting versions, use this certificates help page: https://help.qlik.com/en-US/nprinting/Content/NPrinting/DeployingQVNprinting/NPrinting-with-Sense.htm

Related Content:

Other helpful information about the NP Backup and Restore tool and process:

• NPrinting Manual Backups creates (the following is also true for the programmatic backups performed during the NPrinting Upgrade process)
  
  • a temp file and folder backup that uses up c:drive space
  • This temp backup folder is removed once the manual backup is completed
  • Note: The temp folder backup location cannot be modified
• NPrinting performs Three Automated Backups of the NPrinting Database during the upgrade process only. The c:\drive where NPrinting Server is installed must have sufficient space to allow the upgrade process to proceed without failure. The upgrade process creates:
  • a pre-upgrade backup of the NP database (pre-upgrade backup of the NP Database)
  • a post upgrade backup (upgraded version of the NP database).
  • a temp file and folder backup (which is removed once the upgrade is completed)

• The pre and post upgrade backup files can be found here: 

  C:\ProgramData\NPrinting​

  Note:The pre and post upgrade backup files are appended with the NP version number and backup date
• Backup and restore log history is found here: 

  C:\ProgramData\nprinting\logs\nprinting_manager.log​

• The automated NP backup contains the same file and folder structure as the manual NP backup process. (these files and folders must NOT be modified).
• The NP backup/restore tools and process cannot be used to backup and/or restore individual NPrinting reports.
• To 'Backup/Export' and or Restore/Import individual reports, please visit Moving reports between environments 

*NOTE:

• This article applies to Supported Versions of NPrinting only

• NPrinting Server: Disk space optimization
• Qlik NPrinting Upgrade Install from NPrinting 17.3.x or higher
• Exporting and installing Qlik Sense certificates 
• Backup and restore Qlik NPrinting
• Backing up the Qlik NPrinting audit trail
• Restoring Qlik NPrinting audit trail data from a backup
• Identify wrong NPrinting database version restored to NPrinting Server

Analyzer Capacity Licenses can be assigned automatically based on Analyzer Capacity License Rules. These rules can be set up to provide Analyzer Capacity to users, groups, or anonymous users.

This article covers what function the license type has, how to assign it, and how to track usage. 

Index:

• What is an Analyzer Capacity license?
• How to assign Analyzer Capacity Licenses
• Assigning Analyzer Capacity in Qlik Sense Enterprise SaaS:
• Create an Analyzer Capacity License Rule in Qlik Sense Client-Managed:
• How to monitor Analyzer Capacity usage
• Qlik Cloud
• Qlik Sense Enterprise on Windows Client Managed
• In QlikView
• How Qlik Sense Analyzer Capacity Works (video)
• Related Content
• Environment

What is an Analyzer Capacity license?

The Qlik Sense Analyzer Capacity license type is automatically assigned to users not assigned a Professional or Analyzer license and consumes time during an active session with the minimum session length set to 6 minutes.

Overview:

• An Analyzer Capacity license type would typically be used by users not assigned to any of the available named user types (Professional or Analyzer).
• The capabilities for the Analyzer Capacity license type are similar to the current Analyzer user type and supports the same features. 
• Analyzer Capacity is available for:
  • Qlik Cloud 
  • Qlik Sense Enterprise on Windows
  • QlikView.
• Analyzer Capacity works with Both Signed License Key and Signed License Definition.

Details:

• The minutes are based on a monthly subscription, which resets at 0:00 UTC time on the first day of the calendar month.
• Consumption is in 6-minute blocks. No consumption during idleness.
• Overage can be added to the subscription. See How to manage Overage for Analyzer Capacity.

How to assign Analyzer Capacity Licenses

Assigning Analyzer Capacity in Qlik Sense Enterprise SaaS:

No setup is required. If no Professional or Analyzer License was assigned, Analyzer Capacity is automatically allocated. 

See Enabling dynamic license assignment for details. 

Create an Analyzer Capacity License Rule in Qlik Sense Client-Managed:

1. Open the Qlik Sense Management Console
2. Go to Licenses Management
3. Open Analyzer Capacity Rules in the right-hand menu (See fig 1)
4. Click Create new 
   
   Fig 1
   
   
5. Provide details for your rule. In our example, we are enabling users in the group capacity to receive Analyzer Capacity Licenses. 
   
   Name: Name of your rule
   Description: Description of your rule
   Actions: Allow access 
   
   Populate the conditions accordingly. See Fig 2.
   
   Fig 2
   
   If you are looking to provide access for anonymous users, see How to allow Anonymous Hub access in Qlik Sense Enterprise on Windows.
   
   
6. Click Apply
7. All users in the defined group will now receive an Analyzer Capacity License. 
   
   
   

How to monitor Analyzer Capacity usage

Qlik Cloud

The Entitlement Analyzer for Qlik Cloud provides detailed usage data for Analyzer Capacity, but a tenant admin can gain an overview through the Management Console at any time:

1. Open the Qlik Cloud Management Console
2. Open the User allocation tab
3. Open the Overview tab
4. Review the current Analyzer capacity usage 
   
   
   
   

The Entitlement Analyzer is only available for Qlik Cloud.

Qlik Sense Enterprise on Windows Client Managed

The bundled License Monitoring app provides usage data for Analyzer Capacity, but an administrator can gain an overview through the Qlik Sense Management Console at any time:

1. Open the Qlik Sense Enterprise on Windows Management Console
2. Go to License Management
3. The License usage summary tab (a) lists the current Analyzer capacity usage (b)
   
   
   
   

In QlikView

1. Open the QlikView Management Console and go to System
2. Open the Licenses tab
3. Select License 
4. Switch to the Professional and Analyzer access tab.
5. The General tab lists the current Analyzer Capacity usage 
   
   

How Qlik Sense Analyzer Capacity Works (video)

Related Content

Analyzer capacity license and monitoring (Client Managed)
Qlik Licensing Service Reference Guide 
Assigning user allocation (Qlik Cloud)
Analyzer capacity license (Qlik Cloud)
Top 5 things to know about modern Qlik Licensing

Environment

QlikView 
Qlik Sense Enterprise on Windows 
Qlik Cloud 

If you need to resend a license email along with license installer links and the license key to a customer/user, follow the steps outlined below.

This guide will help you understand the process and the necessary details you need to provide.

Steps to Resend a License Email:

1. Gather Necessary Information:

   • New User Email ID: Ensure you have the email address of the person who needs the license email resent.
   • Product Name and Version: Identify the specific product name and version that need to be resent.
   • PO Number: Include the purchase order number associated with the license.
   • Existing Email ID: Provide the email address to which the license was originally sent.
   • License Type: Indicate if it is a test migration license or a definitive license.
   • Deployment Type: Specify if it is a cloud or on-premises license.
   • Description of Request: Provide a brief description of why you need to resend the license email.

2. Send an Email Request:

   • For users, send your request to customercare@qlik.com.

Email Template for Requesting to Resend a License Email

Use the following template to structure your email request:

Subject: Resend License Email Request

Dear Support Team,

I hope this email finds you well.

I am writing to request that a license email be resent. Below are the details:

• New User Email ID: [Insert User Email] (new user email ID to which the license email needs to be sent)
• Product Name and Version: [Insert Product Name and Version]
• PO Number: [Insert PO Number]
• Existing Email ID: [Insert Existing Email ID] (who it was already sent to)
• License Type: [Test Migration License or Definitive License]
• Deployment Type: [Cloud or On-Premises License]
• Description: [Provide a brief description of your request]

I would greatly appreciate your assistance in resending the license email. Thank you for your support and consideration.

Best regards,

[Your Name]

Example of a Detailed Request

Subject: Resend License Email Request for Talend Data Integration

Dear Support Team,

I hope this email finds you well.

I am writing to request that the license email for Talend Data Integration be resent. Below are the details:

• New User Email ID: Sam@xyz.com
• Product Name and Version: Talend Data Integration Version 8.0
• PO Number: PO-23451
• Existing Email ID: original.recipient@xyz.com
• License Type: Test Migration License
• Deployment Type: Cloud License
• Description: Due to unforeseen circumstances, the original license email was not received. I would be grateful if you could assist me by resending it.

I would greatly appreciate your assistance in resending the license email. Thank you for your support and consideration.

Best regards,

Sam

Important Notes

• Ensure all details are accurate and complete before sending your request.
• Use the appropriate email address based on your user type (general user or Qlik partner).

Following these steps will help you effectively resend a license email to your customer.

If you have any further questions, feel free to reach out to the respective teams.

Introduction

As a Talend Test Migration License is generated for a period of 60 days (2 months) at a time, how to extend your Talend Test Migration License when it is expiring or already expired in Talend Studio/Talend Administration Center?

Resolution

Please create a new case in Qlik Customer Support Portal so that our Support can generate a new test migration license for you. As long as there is a current subscription of the account, a test migration license will be provided.

Please keep in mind that a Talend Test Migration License is valid for 60 days(2 months) a time.

If you are looking to obtain a Test Migration license, see How to Request and Utilize a Talend Test Migration License.

If you are looking for Qlik Support Case Portal, see How to contact Qlik Support 

Environments

Talend Studio 

Talend Administration Center