This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

This video demonstrates how to activate the Qlik SAP Connector or update the license in use.

Here is a link to more information in the Support Knowledge Base:

Qlik SAP Connector: Activating/updating license 

Video Transcript:

Hi and Welcome to Qlik Fix
This video demonstrates how to activate the Qlik SAP Connector or update the license in use.
After installing the SAP Connector either in a Qlik Sense or QlikView environment, the connector executable files are placed in this location. (C:\Program Files\Common Files\QlikTech\Custom Data\)
In order to activate the SAP Connector, under the QvSAPSqlConnector folder, run the QvSAPSqlConnector.exe file.
Under the Help drop down button, click on Update license.
If internet connection is available use the first option. Otherwise, select second option "Enter license text" and used full LEF information.
If the LEF content is unknown it can be retrieved via the Support Portal. See the knowledge base article "How to request a control number and LEF" in Qlik Community.
Fill in the 16-digit License key, Control number, and remaining fields, then click Update. If successful it will be indicated with this message.
The LEF information is retrieved and stored in the Lef.txt file under this location. (C:\ProgramData\QlikTech\Custom Data\QvSAPConnector)
If licensing for use with QlikView the license update may be triggered via QlikView Desktop by selecting one of the SAP connector options, and clicking Connect.
If the QvSAPSqlConnector.exe option is selected, the same interface mentioned is displayed where the license can be updated under Help, Update License.
If you’d like more information,
search for answers using the unified search tool on the Support Portal.
It searches across the support knowledge base, Qlik Community, Qlik Help site, and Qlik YouTube channels.
Take advantage of the expertise of peers, product experts, and technical support engineers by asking a question in a Qlik Product Forum on Qlik Community.
And don’t forget to subscribe to the Support Updates Blog.
Thanks for watching.
Nailed it!

Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.

#QlikSupport

 This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

This video will demonstrate how to use Qlik-CLI for SaaS to migrate Apps from your on-premises Qlik Sense environment to your Qlik Sense SaaS edition. Qlik-CLI makes it possible for scripting and automating App migration.

Here is a link to the Support Knowledge Base article which contains links to mentioned documentation.

How to use Qlik-CLI to Migrate Apps to Qlik Sense SaaS 

Video Transcript:

Hi and welcome to Qlik Fix!
This video will demonstrate how to use Qlik-CLI for SaaS to migrate Apps from your on-premises Qlik Sense environment to your Qlik Sense SaaS edition.
Qlik-CLI makes it possible for scripting and automating App migration.
The tool may be installed and connected to you Qlik Sense SaaS tenant following the steps mentioned in this Community knowledge base article. (https://community.qlik.com/t5/Knowledge-Base/How-to-install-and-start-using-Qlik-CLI-for-SaaS-editions-of/ta-p/1796143)
Qlik-CLI can also be used to connecting to Qlik Sense on Windows via the QRS API.
As with SaaS Editions of Qlik Sense, the connection to Qlik Sense on Windows also requires a API Key for authentication. (qlik context get andresostizzo.us.qlikcloud.com)
The API key is essentially a JSON Web Token, or JWT, usually pronounced as jot.
So the first step is to have a new Virtual Proxy configured to accept JWT Authentication.
This will allow for qlik-cli to establish a trusted connection with the Qlik Sense server.
For detailed steps with enabling and testing JWT Authentication, take a look at this knowledge base article in community on how to set it up.
(https://community.qlik.com/t5/Knowledge-Base/Qlik-Sense-How-to-set-up-JWT-authentication/ta-p/1716226)
In this video's example however, we use the openssl commands found in this qlik.dev page to create a certificate and private key that are used for signing the JWT. (https://qlik.dev/tutorials/using-qlik-sense-on-windows-repository-api-qrs-with-qlik-cli#create-a-public--private-key-pair-for-signing-jwts)
Then, we create the JWT with the code sample found in this section, using Node. (https://qlik.dev/tutorials/using-qlik-sense-on-windows-repository-api-qrs-with-qlik-cli/#tokenjs-code-sample)
NodeJS can be downloaded from the Nodejs.org website. (https://nodejs.org/en/download/)
After installing it, the jsonwebtoken module needs to be installed with the following node package management (NPM) command. (npm install jsonwebtoken)
Now we can edit the provided Token.js javascript code for creating the token.
Note that the userid and userdirectory attributes names as well as the value specified for the audience (aud) attribute are all case sensitive, and need to match what is configured in the Virtual Proxy.
Also make sure to indicate an existing licensed user for the userid and userdirectory.
For jwtEncryptionKey, fill in the location for the private key file generated previously with openssl.
Now we can run this code with the following node command. (node token.js)
The token should be created and displayed.
Next, we need to create the context for the connection with the Qlik Sense server.
Run the following command with values for the context name, URL for the Virtual Proxy, server type as Windows, and the api-key which is the new JWT created. (qlik context create QSEoW --server https://192.168.254.243/jwt --server-type windows --api-key)
Note that if an IP or alias is used in the URL, it needs to be added to the Virtual Proxy's list of allowed hosts.
Now we switch to the newly created context with the context use command, and we are ready to run qlik qrs commands.
For example, the following command will retrieve a list of Apps and their IDs in JSON format. (qlik qrs app ls --insecure | jq -r '.[] | {"name":.name,"id":.id}')
Notice that the --insecure flag allows for the command to be run from outside the Qlik Sense server itself.
Also note that we are piping the output to a JSON processing tool called JQ.
JQ can be downloaded from the following web page. (https://stedolan.github.io/jq/)
Another example would be the need to retrieve App IDs for a specific Stream.
Adding the stream name object in the JQ command, and then piping it to the select-string command can help listing the App names and ids that were published to the specified stream.
(qlik qrs app ls --insecure | jq -r '.[] | {"name":.name,"id":.id,"stream":.stream.name}' | select-string "Monitoring apps" -context 2,0)
Next we can export one of these apps. Let's first set the variables for the App ID, the exported filepath, and new filename.
Now we can use these variables in the following command for exporting the App.
Note that the --skipdata flag exports the App without data.
This is beneficial with larger Apps since there is an upload size limit of 1GB when importing Apps to Qlik Sense SaaS editions.
More information on app sizing is available in the following article. (https://community.qlik.com/t5/Knowledge-Base/Qlik-Sense-Business-and-Enterprise-SaaS-App-Size-Storage-Size/ta-p/1710690)
We will also add the flag -v to enable verbose mode and display more result information.
We can see that a 200 OK is returned, and that the app is successfully exported.
The next step is to import the App into the Qlik Sense SaaS instance.
First we need to switch to the context used for your Qlik Sense SaaS tenant.
Review the values stored in our variables.
Then use the following command to import the App, and store its ID to the "SaaSApiID" powershell variable.
The App should now show in Cloud Hub under Explore.
Keep in mind that exported apps do not contain original private sheets and have the public sheets and stories set as private as seen here.
You may publish the sheets manually via Cloud Hub, or use qlik-cli as in the following example.
First review the imported App ID variable created previously.
With the following command obtain a list of sheets in the app.
Then, set all of them to public.
We can see the result in cloud hub and then notice the App is still found under the user's personal space.
The app may be assigned to a specific space, and many other tasks are available as well via Qlik-CLI.
Examples for Space assignment and owner changes can be found in the qlik.dev page shown here. (https://qlik.dev/tutorials/migrate-apps-from-qlik-sense-on-windows-to-qlik-sense-saas#place-the-app-in-a-shared-space)
If you’d like more information,
Take advantage of the expertise of peers, product experts, and technical support engineers
by asking a question in a Qlik Product Forum on Qlik Community.
Or search for answers using the new SearchUnify tool.
It searches across our Knowledge Base, Qlik Help, Qlik Community, Qlik YouTube channels and more, all from one place.
Also check out the Support Programs space.
Here you can learn directly from Qlik experts via a Support webinar, like Techspert Thursdays.
And don’t forget to subscribe to the Support Updates Blog.
Thanks for watching.
Nailed it!

Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.

#QlikSupport

This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos. 

Take your bookmarks to the next level! This video will demonstrate how to use Dynamic Bookmarks, such as a "Max Year" bookmark that will always return the most recent year in the field.

Transcript

This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos. 

This video covers the scenarios in which the "too many sessions active in parallel" error message is expected to occur, and how to prevent it.

For more information see knowledge base article via the link below:

Troubleshoot no access pass or too many sessions active in parallel on Qlik Sense hub 

Video Transcript:

Hi and welcome to Qlik Fix!
This video covers the scenarios in which the "too many sessions active in parallel" error message is expected to occur, and how to prevent it.
Starting on the June 2019 release of Qlik Sense, the error message displayed here became a common occurrence.
Prior to the June 2019 release and since April 2018 when Professional and Analyzer licensing model was released, the error message indicating "you have no access pass" was expected to be displayed instead, which was misdleading.
The issue is due to the maximum allowed five authentication sessions that can be active at any time in Qlik Sense. See Access Assignment in Qlik Help site. (https://help.qlik.com/en-US/sense-admin/November2020/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Common/Server-Licensing-Access-Types.htm)
The maximum of five allowed sessions applies to authenticated licensed users, so after opening multiple authentication sessions from different browsers or computers, we see the error message displayed to the client after attempting to open the sixth session.
In this storage location we can review the Qlik Sense repository audit security logs which will have lines registered indicating that the SessionCount has reached a value of five, so it logs UsageDenied in reference to this issue.
Note that different tabs on the same browser normally use the same authentication session and do not lead to the same issue.
This issue is more commonly observed when an administrator uses the Qlik Sense service account to manage and develop Apps via the Hub.
This occurs because the service account has been assigned a professional or analyzer license, and the number of sessions limit is imposed not just for client connections, but also internal system connections to the Qlik Sense Proxy API, such as for Monitoring app reload tasks, which use the service account by default.
In order to prevent this issue, administrators should not use the service account for developing and managing apps via the Qlik Sense hub.
Instead, use another licensed account, and do not allocate a license to the Qlik Sense service account.
If the issue is reported with a regular user account, make sure the maximum number of sessions is not being reached for the user.
For more information on how to count the number of sessions, see the knowledge base article "How to count sessions in Qlik Sense". (https://community.qlik.com/t5/Support-Knowledge-Base/How-to-count-sessions-in-Qlik-Sense/ta-p/1714209)
Note that when allocating the legacy User Access Pass to the service account, this issue may also delay or prevent Monitoring app reload tasks from being performed successfully.
This happens because the Qlik Sense service account is used to create sessions with the Qlik Sense Proxy API during the reload.
In order to prevent reload task issues, the recommendation is again to leave the Qlik Sense service account as a RootAdmin, without any license allocated to it.
An alternative would be to use another RootAdmin for the monitoring apps Data Connections that is not used in App development, and has no license allocated.
If you’d like more information,
search for answers using the unified search tool on the Support Portal.
It searches across the support knowledge base, Qlik Community, Qlik Help site, and Qlik YouTube channels.
Take advantage of the expertise of peers, product experts, and technical support engineers by asking a question in a Qlik Product Forum on Qlik Community.
And don’t forget to subscribe to the Support Updates Blog.
Thanks for watching!

Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.

#QlikSupport

This video will demonstrate how to schedule a reload in Qlik cloud. Schedule a reload for any of your charts by day, time, and/or occurrence.

Check out more Qlik Fix Videos.

Transcript

This video demonstrates to how to use automated log cleanup on Replicate. Automated cleanup simplifies the process of purging outdated logs in Replicate, requiring just a few simple steps.

Transcript

This video demonstrates to publish a sheet. A publish sheet can be viewed by the collaborators who has access to it.

Transcript

This video will demonstrate how to Monitor a Chart. Monitoring charts facilitate quick and effortless viewing of one's charts.

Transcript

This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

This video demonstrates how to install Qlik Replicate.

Video Transcript:

Hi and Welcome to Qlik Fix
This video will demonstrate how to install Qlik Replicate.
First, you can download the installer file by logging into the Qlik Product download site of Qlik Community.
Expand the compressed file, right-click the installer and Run as Administrator.
The installer requires Microsoft .NET 4.8, so the wizard will install that first.
Click Next on the Qlik Replicate Install wizard
Read and agree to the customer agreement.
Set the location for program files. This location must be a local drive.
Now the location for the data files. This will be the location for all of the task information and log files It’s recommended that this be a large location and CAN be a network drive.
Here you have the option to install a local Replicate Server or if you had already installed Replicate on a Linux box, you could set this up to connect to that Linux based Replicate server.
We’re doing a fresh installation on this Windows machine.
Review the current settings and start to install.
Now, once it’s finished, I’ll check those newly installed Windows services:
The Qlik Replicate Server and Qlik Replicate UI server services. Both are running.
These services are by default set to run as Local System, but if you require that the services be run by a user account, that account must be a local administrator on this machine.
One tip, the data folder locations that we set during the installation for both the program files and the data files can be reviewed here.
To access the Qlik Replicate console, it can be found from the start menu.
This server has a self signed certificate, that why we’re seeing this warning.
Login using the service account that we used during the installation.
The first thing to do is to click on Register to enter the license for activation.
This should be a text file that was sent from Qlik. You can Open that text file and copy the contents and paste it in here OR
You can click on Load and navigate to that same file, and click on Register License.
That creates a communication with the Qlik licensing server, and now the Replicate server is registered.
To review the registered license from the Replicate console,
Click on the drop down menu, select Server
Click on License on the left, that here you can see the details of the registered license, like the expiration date. If you have an update to the license, you can always click on the Register License button from here and register a new or updated license.
Now Qlik Replicate is ready and you can begin to setup the specific end points you want to use.

I hope this helps.

This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

Environment

• Qlik Enterprise Manager
• Qlik Replicate

This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

Environment

• Qlik Compose

This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

Environment

• Qlik Cloud

This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

Environment

• Qlik Replicate

This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

Environment

• Qlik Replicate

This video demonstrates how to Restart a Qlik Replicate task from the Log Sequence Number or LSN for a Postgres source.

Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.

Transcript

This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

This video demonstrates how to publish an app from Qlik Sense Enterprise on Windows to Qlik Cloud as a part of Qlik’s multi-cloud SaaS offering.

For more information:

https://help.qlik.com/en-US/sense-admin/May2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/Multi-Cloud/distributing-apps-QSEoW-to-QCS.htm

Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.

Transcript:

Hi and Welcome to Qlik Fix.
This video will demonstrate how to publish an app from Qlik Sense Enterprise on Windows
to Qlik Cloud as a part of Qlik’s multi-cloud SaaS offering.
Start by verifying that the license being used in Qlik Sense Enterprise on Windows
is a Signed License Key. License Key plus control number method of licensing is not compatible with Multi-Cloud deployments.
This Signed License Key should also be the same one applied to our Tennant in Qlik Cloud.
To check, go to this license overview address.
And verify that the license key being used here is the same as on Qlik Sense on Windows.
Now to set up the Multi-Cloud Deployment
Go to the Cloud Distribution settings
And click on Set Up New Deployment at the bottom
We’ll give it a name. This will be referenced again later.
The API end point is your Tenant URL
Copy that
I’m going to use a local token to connect Qlik Sense on Windows with the Cloud deployment
And with the Qlik Cloud Services Format checked, copy the token
Now back to the Cloud Management Console
Identity Provider at the bottom
And Create New
Select – Multi-Cloud
And paste in the Local Bearer Token that we just copied from Qlik Sense on Windows.
And Create
To test the connection, go to Cloud Distribution in the QMC,
Deployment Setup, and click on Test Connection.
Now we need to create a custom property that will be used when publishing apps from Windows to the Cloud deployment.
This will be attached to applications that will be pushed to the cloud.
Click on Apps
And the value should match the deployment name that we entered before in the Multi-Cloud Setup Console.
Now for the apps that we want to publish,
Go into the app,
Edit,
and in Customer Properties
Specify the deployment we just setup, so that the setting is added to the app
The next step is to create a distribution policy
Create new
Let’s use a template for distribution
Add a name
Set the value to use the custom property
And Apply
Now let’s verify that the distribution happened by
Going back to the Cloud Hub
Refresh
And there it is. That has just been published from Qlik Sense Enterprise on Windows to the Qlik Cloud Hub.
This app is currently only accessible by one person.
To change this, go into Administration
Notice the alert about some apps in Staging Mode
Select the app
Click “Set Space”
And assign the app to a managed space so that other users can use the app.
Now back to the hub, in the details,
we can verify that the app is in the managed space.
Access to this space can be adjusted in the space settings.
Now let’s do this with a new app,
Let’s Import and example app to Qlik Sense on Windows.
Select the app, edit
Add the customer property
Apply
Now let’s publish the app.
Let’s publish it to a Stream on Windows
The publishing task applies the distribution policy
and the app will appear in both the Windows Hub Stream
and the Cloud Hub as a staged app.

I hope this helped.
If you'd like more information

Take advantage of the expertise of peers, product experts, Community MVPs and technical support engineers
by asking a question in a Qlik Product Forum.

Hiding in plain sight is the Search tool.
This engine allows you to search Qlik Knowledge Base Articles,
Qlik Community forums,
Help dot Qlik dot com, Qlik Gallery,
multiple Qlik YouTube channels and more, all from one place.

There’s also the Support space.
We recommend you subscribe to the Support Updates Blog,
And learn from Qlik experts via a webinar, like Techspert Talks or Q&A with Qlik.
Thanks for watching.
(music)
Nailed it!

 This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

This video explains where to find the reload script logs depending on where the reload was triggered.

Here is a link to more information in the Support Knowledge Base:

How to find the Script (Reload) logs in Qlik Sense Enterprise 

 Video Transcript:

Hi and welcome to Qlik Fix!
This video explains where to find the reload script logs depending on where the reload was triggered.
When the app reload is triggered via the Hub from the Qlik Sense Data load editor (DLE), reload logs are placed on the server running the Qlik Sense Engine that is currently in use by the client.
This means that in a multi-node environment, each RIM node with an Engine service used by the specific Virtual Proxy needs to be checked for the new reload script log file.
One common way to know before hand which RIM node Engine service has been used is to use the function computername(), as seen in this example with a Text object.
It outputs the hostname of the server hosting the Engine service that is currently being used by the client.
In this case qlikserver2 is in use. We see here the reload task was saved in this location on qlikserver2 itself.
The log file name will contain the App ID as reference.
Note that unlike some other logs, script logs generated via the Hub do not get archived in the Share persistence location.
The share persistence storage location is used to store the reload script logs for reloads triggered by Tasks. This includes tasks triggered manually, or by being scheduled.
These script logs get archived in the Share as soon as the reload task is concluded.
In order to check the share location see Service cluster in QMC, under Archived logs root folder.
In that share location we see the log file created by the last reload task under the folder created for that RIM node, under the Script sub-folder.
Here the App ID is also used in the file naming convention for reference.
Note that by default only 4 script log files per App will be kept by Qlik Sense in the ArchivedLogs location.
The RIM node's host name can be retrieved at the same place that the most recent reload log can be retrieved via QMC.
Under the Status column when clicking on the Information icon the host name will be at the top, and the most recent log file can be downloaded by clicking on the "Download script log" button.
If you’d like more information,
Take advantage of the expertise of peers, product experts, and technical support engineers
by asking a question in a Qlik Product Forum on Qlik Community.
Or check out the Support Programs space.
Here you can search for answers in the Support Knowledge Base,
Learn directly from Qlik experts via a Support webinar, like Techspert Thursdays.
And don’t forget to subscribe to the Support Updates Blog.
Thanks for watching.
Nailed it!

Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.

#QlikSupport

This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

This video demonstrates how to download Qlik Products.

Here is a link to more information in the Support Knowledge Base:

https://community.qlik.com/t5/Knowledge/How-to-download-Qlik-Products/ta-p/1906869

Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.

Click here for video transcript

This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

This video demonstrates how to create a new O-auth data source connection so that you are redirected to the login page of the system you’re connecting to.

Sometimes while trying to add a new connection that uses OAuth authentication flow(for eg: Quickbooks connector) within an automation having multiple connections, it gets automatically connected to the previously linked user instead of redirecting it to the login page of the system.

A possible solution for this would be to log out from one account before logging into the other account if we want to add multiple connections of the same system. Please refer below video which shows up how to manually logout from a quickbooks account and then retry adding up a new connection for quickbooks within an automation.

Transcript

This video demonstrates how to create a new O-auth data source connection so that you are redirected to the login page of the system you’re connecting to.
Let’s try connecting a new data source for quick books.
Assume we have multiple data sources already connected
If we click on add Link Connection,
it will automatically get connected to a previously signed in QuickBooks account
instead of redirecting to the login page of QuickBooks
In order to connect multiple data sources of QuickBooks using different accounts
First, Manually log out from QuickBooks
Retry adding up a new connection for QuickBooks by clicking on
add another QuickBooks connection
This will redirect to the login page of quick books
Where you can sign in with a different account
And now the new connection is made
I hope this helped.
If you'd like more information
Take advantage of the expertise of peers, product experts, Community MVPs and technical support engineers
by asking a question in a Qlik Product Forum.
Hiding in plain sight is the Search tool.
This engine allows you to search Qlik Knowledge Base Articles,
Qlik Community forums,
Help dot Qlik dot com, Qlik Gallery,
multiple Qlik YouTube channels and more, all from one place.
There’s also the Support space.
We recommend you subscribe to the Support Updates Blog,
And learn from Qlik experts via a webinar, like Techspert Talks or Q&A with Qlik.
Thanks for watching.
(music)
Nailed it!