Some script logs are not transferred to Archive log Folder.

Storage Locations:

Qlik Sense log folder:

C:\ProgramData\Qlik\Sense\Log\Script
Log names consist out of the AppID and a year, date, and timestamp.

Archived log Folder:

 \\SERVICECLUSTER-SHARE\ArchivedLogs\NodeName\Script
Log names consist out of the AppID and a year, date, and timestamp.

Environment:

• Qlik Sense Enterprise on Windows, all versions

Resolution:

By design, not all script logs are transferred to the Archived logs folder. Reloads executed from the hub are not transferred. 

1. When reloading data in app via hub, Script log will be left in Script log folder C:\ProgramData\Qlik\Sense\Log\Script

2. When reloading data via QMC/task, Script log will be transferred to Archived logs folder \\SERVICECLUSTER-SHARE\ArchivedLogs\NodeName\Script

Related Content:

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

Question

When using the unattended installer to install Talend on-prem products, such as TAC (Talend Administration Center), there is no visible log. Where can you find the log, and how can you determine if the products have been successfully installed?

The installation log is located in /tmp for Linux and %TEMP% for Windows. The file name will be "installbuilderinstaller.log". To locate the correct install log, please refer to the timestamp at the end, as multiple installation logs may exist in the temp directory.

To confirm successful installation, it is best to inspect the installation folder. Upon successful completion, a file named uninstall (for Linux) or uninstall.exe (for Windows) will be generated at the root of the installation folder. With default settings, the file will be located at /opt/Talend-8.0.1/uninstall or C:\Talend\8.0.1\uninstall.exe.

Can deleted Qlik Cloud apps or sheets be recovered? Can apps, sheets, or automations owned by a deleted user be recovered?

Once an app or sheet has been deleted it cannot be recovered.

What about deleted users and their orphaned objects?

Orphaned apps (created when the user has been deleted) can be reassigned. See Qlik Cloud Analytics: Can the owner of orphaned Apps be changed after the owner is deleted? for instructions.

For more information about what to consider before deleting a user, see Deleting users.

The following cannot be recovered:

• A deleted app
• A deleted sheet
• Personal objects belonging to a deleted user
• Automations belonging to a deleted user

Qlik suggests the following techniques to ensure no work is lost:

• Duplicate the app to the same or different 'Shared' or 'Personal' space
• Setup a test or 'recycle bin' space where duplicated apps are kept until it has been verified that the app can be fully deleted
• If space is a concern, export the app without data and re-import it to the 'recycle bin' space. This will allow you to keep an empty master copy of the app

Qlik has received feedback in the past to implement a recovery feature: Recycle bin for SaaS editions of Qlik Sense (#279017) (Log in to Qlik Ideation to leave comments and vote.)

It is not possible to set up a Microsoft Office 365 email provider with OAuth 2.0 authentication.
The HAR file shows this message in Network:

{connectionFailed: true, message: "Error during email request", success: false}
connectionFailed: true
message: "Error during email request"
success: false

Resolution

Configure the Mail.Send permission as it is described in Configuring a Microsoft 365 email provider using OAuth2.

Cause

This problem occurs when the Mail.Send permission has not been configured in the app registration.

Related Content

More information about the  Mail.Send permission can be found in Application permission to Microsoft Graph (learn.microsoft.com).

Environment

• Qlik Tabular reporting
• Qlik Cloud

Information about app and storage size for Qlik Cloud for Qlik Sense Enterprise SaaS and Qlik Sense Business can be found in Qlik Sense capacity.  

Note: An app on disk is typically 4-6 times bigger in memory, although this is a rule of thumb and exceptions can and do occur, and an app within the "on-disk" size limit may balloon past the "in memory" limit.  

App Objects have a memory limit of 10 GB, except when run on dedicated capacity.

If you are looking to compare other features between Qlik Sense Business and Qlik Sense Enterprise SaaS, see Compare product features 

For more information about capacity, see:

Qlik Sense specifications and capacity 
Pricing | Qlik Sense

This can help in the troubleshooting process to find out what App/User was active and accessed an application right before an error/issue in the environment.
 
The entries are color coded for the name of the App in the Hub/QMC along with the APP ID and Session ID
 
Note: Session ID will change for different users and different browsers, this includes closing the browser and reopening it (which is a new session, but will be the same App ID). In this test there's only one session and two accesses of the app, but a user can open the app in another browser which will show it as the same user in two different sessions for the same app at the same time.
 

Environment: 

Qlik Sense Enterprise on Windows , version 3.2.1 and newer, single node

Windows 2012 R2

App Name: Load Test APP ID
Published APP ID?: c3ed4e49-dc98-4ff8-b140-f3d945236197 - Load Test APP ID
Session ID?: fe87b122-8979-45d4-9c37-3c39ce704045 - Load Test APP ID

C:\ProgramData\Qlik\Sense\Log\Engine\Trace\QLIKSERVER1_System_Engine.txt
 
First Open (loaded into memory):
 
16           20170321T215743.565+0100       INFO      QlikServer1         System.Engine.Engine   46           6f40f67b-47aa-406f-bb78-947e90cd9ff3         DOMAIN\qvservice         QvSocket: Connected to server as user: 'UserDirectory=DOMAIN; UserId=qvservice' for document: '/app/c3ed4e49-dc98-4ff8-b140-f3d945236197' on socket fe80::743e:6e47:b9f:acb5:4747 <-> fe80::743e:6e47:b9f:acb5:62282         0              Internal Engine                20170321T215743.566+0100       3136       3176       20170321T215516.000+0100       6f40f67b-47aa-406f-bb78-947e90cd9ff3
17           20170321T215743.573+0100       INFO      QlikServer1         System.Engine.Engine   46           31b65464-36b3-48c1-8dc8-f7b5c2ecbb9b              DOMAIN\qvservice         Server: Document Load: Beginning open of document                fe87b122-8979-45d4-9c37-3c39ce704045              DOMAIN              qvservice             20170321T215743.573+0100                3132       3176       20170321T215516.000+0100       31b65464-36b3-48c1-8dc8-f7b5c2ecbb9b
18           20170321T215743.597+0100       INFO      QlikServer1         System.Engine.Engine   46           610de372-ad42-4975-863b-93f5d9fbcbec              DOMAIN\qvservice         DOC loading: Beginning load of document C3ED4E49-DC98-4FF8-B140-F3D945236197.           fe87b122-8979-45d4-9c37-3c39ce704045              DOMAIN              qvservice                20170321T215743.597+0100       3756       3176       20170321T215516.000+0100       610de372-ad42-4975-863b-93f5d9fbcbec
19           20170321T215744.640+0100       INFO      QlikServer1         System.Engine.Engine   46           f15e84d0-f8d9-44d1-a8e1-3095b41e4a0d        DOMAIN\qvservice         Document Load: The document c3ed4e49-dc98-4ff8-b140-f3d945236197 was loaded.          fe87b122-8979-45d4-9c37-3c39ce704045              DOMAIN              qvservice                20170321T215744.641+0100       4468       3176       20170321T215516.000+0100       f15e84d0-f8d9-44d1-a8e1-3095b41e4a0d
 
Second Open (already loaded in memory):
 
20           20170321T220052.937+0100       INFO      QlikServer1         System.Engine.Engine   47           34b26c68-67e8-4be1-9439-6026c0c59f9e          DOMAIN\qvservice         QvSocket: Connected to server as user: 'UserDirectory=DOMAIN; UserId=qvservice' for document: '/app/c3ed4e49-dc98-4ff8-b140-f3d945236197' on socket fe80::743e:6e47:b9f:acb5:4747 <-> fe80::743e:6e47:b9f:acb5:62296         0              Internal Engine                20170321T220052.937+0100       3136       3176       20170321T215516.000+0100       34b26c68-67e8-4be1-9439-6026c0c59f9e
21           20170321T220052.960+0100       INFO      QlikServer1         System.Engine.Engine   47           cc981161-bbfd-42ec-aa5c-b512e0602283         DOMAIN\qvservice         Server: Document Load: Beginning open of document     fe87b122-8979-45d4-9c37-3c39ce704045   DOMAIN              qvservice             20170321T220052.960+0100       3132       3176                20170321T215516.000+0100       cc981161-bbfd-42ec-aa5c-b512e0602283
 
Notice the first load will state what Session ID initiated the load into memory. The second attempt only gives the App ID in the first log line and then the Session ID is in an entry afterwards. While these entries should be right after each other, depending on what’s happening, they might be broken up by other entries. It’s unlikely, but does make it more difficult to troubleshoot a heavily trafficked environment without access to the Proxy logs.
 
Note: The First Open is only triggered when the QVF is not in memory, so the initial load in memory might be in another log file depending on when the log files are archived.
 
C:\ProgramData\Qlik\Sense\Log\Proxy\Audit\QLIKSERVER1_AuditSecurity_Proxy.txt
 
First Open (loaded into memory):
 
3              11.11.0.0              20170321T215732.019+0100       QlikServer1         738f0e4c-85bc-44ab-accb-18825ec407a5                Command=Login;Result=0;ResultText=Success   fe87b122-8979-45d4-9c37-3c39ce704045              c8d0eb48-fe7a-47da-bbca-0eab11340b92  0              DOMAIN              qvservice             0              Not available      Security                ::ffff:172.16.16.100          Proxy    AppAccess          /hub/stream/e4f1e040-75cf-4db0-afbd-baaf90cab8f8    Login                0              User authenticated. User 'DOMAIN\qvservice' used authentication method 'ticket' and got session 'fe87b122-8979-45d4-9c37-3c39ce704045'            1dc02c31e1779346144cbcc4b75a81a55f466159
4              11.11.0.0              20170321T215742.970+0100       QlikServer1         97ab24cb-edb8-4930-a343-69e044ec7dd0                Command=Add app privileges;Result=0;ResultText=Success         fe87b122-8979-45d4-9c37-3c39ce704045                0e6278ad-ffff-4d6c-9d66-af84a1596d78                 0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Security                ::ffff:172.16.16.100          Proxy    AppAccess                /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197            Add app privileges:ProcessRequestAccessResult 0                Access to app 'c3ed4e49-dc98-4ff8-b140-f3d945236197' allowed with access type 'UserAccessType', result code 'Ok'              94d89f25a8faad2ea59837ded7b6a1603a4607da

Second Open (already loaded in memory):
 
20           20170321T220052.937+0100       INFO      QlikServer1         System.Engine.Engine   47           34b26c68-67e8-4be1-9439-6026c0c59f9e          DOMAIN\qvservice         QvSocket: Connected to server as user: 'UserDirectory=DOMAIN; UserId=qvservice' for document: '/app/c3ed4e49-dc98-4ff8-b140-f3d945236197' on socket fe80::743e:6e47:b9f:acb5:4747 <-> fe80::743e:6e47:b9f:acb5:62296         0              Internal Engine                20170321T220052.937+0100       3136       3176       20170321T215516.000+0100       34b26c68-67e8-4be1-9439-6026c0c59f9e
21           20170321T220052.960+0100       INFO      QlikServer1         System.Engine.Engine   47           cc981161-bbfd-42ec-aa5c-b512e0602283         DOMAIN\qvservice         Server: Document Load: Beginning open of document     fe87b122-8979-45d4-9c37-3c39ce704045   DOMAIN              qvservice             20170321T220052.960+0100       3132       3176                20170321T215516.000+0100       cc981161-bbfd-42ec-aa5c-b512e0602283
 
As you can see the first load will state what Session ID initiated the load into memory. The second attempt only gives the App ID in the first log line and then the Session ID is in an entry afterwards. While these entries should be right after each other, depending on what’s happening, they might be broken up by other entries. It’s unlikely, but does make it more difficult to troubleshoot a heavily trafficked environment without access to the Proxy logs.
 
Note: The First Open is only triggered when the QVF is not in memory, so the initial load in memory might be in another log file depending on when the log files are archived.

C:\ProgramData\Qlik\Sense\Log\Proxy\Audit\QLIKSERVER1_AuditSecurity_Proxy.txt
 
First Open (loaded into memory):
 
3              11.11.0.0              20170321T215732.019+0100       QlikServer1         738f0e4c-85bc-44ab-accb-18825ec407a5                Command=Login;Result=0;ResultText=Success   fe87b122-8979-45d4-9c37-3c39ce704045              c8d0eb48-fe7a-47da-bbca-0eab11340b92  0              DOMAIN              qvservice             0              Not available      Security                ::ffff:172.16.16.100          Proxy    AppAccess          /hub/stream/e4f1e040-75cf-4db0-afbd-baaf90cab8f8    Login                0              User authenticated. User 'DOMAIN\qvservice' used authentication method 'ticket' and got session 'fe87b122-8979-45d4-9c37-3c39ce704045'            1dc02c31e1779346144cbcc4b75a81a55f466159
4              11.11.0.0              20170321T215742.970+0100       QlikServer1         97ab24cb-edb8-4930-a343-69e044ec7dd0                Command=Add app privileges;Result=0;ResultText=Success         fe87b122-8979-45d4-9c37-3c39ce704045                0e6278ad-ffff-4d6c-9d66-af84a1596d78                 0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Security                ::ffff:172.16.16.100          Proxy    AppAccess                /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197            Add app privileges:ProcessRequestAccessResult 0                Access to app 'c3ed4e49-dc98-4ff8-b140-f3d945236197' allowed with access type 'UserAccessType', result code 'Ok'              94d89f25a8faad2ea59837ded7b6a1603a4607da
 
Second Open (already loaded in memory):
 
5              11.11.0.0              20170321T220052.910+0100       QlikServer1         881a8f23-f3a2-4f2b-ae45-969dc9c0c2e3                Command=Add app privileges;Result=0;ResultText=Success         fe87b122-8979-45d4-9c37-3c39ce704045                a057e326-6123-406a-8ee2-e82a46efe367             0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Security                ::ffff:172.16.16.100          Proxy    AppAccess                /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197            Add app privileges:ProcessRequestAccessResult 0                Access to app 'c3ed4e49-dc98-4ff8-b140-f3d945236197' allowed with access type 'UserAccessType', result code 'Ok'              0649a45ad43ccfcf97b82a1cd8d14dd2fa0cfe3b
6              11.11.0.0              20170321T220553.102+0100       QlikServer1         a5462a59-cf10-494e-b021-fc1c26bad82c                Command=Add app privileges;Result=0;ResultText=Success         fe87b122-8979-45d4-9c37-3c39ce704045                a057e326-6123-406a-8ee2-e82a46efe367             0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Security                ::ffff:172.16.16.100          Proxy    AppAccess                /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197            Add app privileges:ProcessRequestAccessResult 0                Access to app 'c3ed4e49-dc98-4ff8-b140-f3d945236197' allowed with access type 'UserAccessType', result code 'Ok'              11c238cbc3edf8e921ebf0e0d8f71b199497a880
 
There’s a few logs listed here that will give other information along with the Session and App ID, but with the Proxy logs we can verify the Session ID that links to the App ID. This can point you to a time, user and app accessed giving you an idea of what users/apps were active and open at the time.

C:\ProgramData\Qlik\Sense\Log\Engine\Audit\QLIKSERVER1_AuditActivity_Engine.txt

First Open (loaded into memory):
 
1              12.16.1.0              20170321T215745.019+0100       QlikServer1         48345a91-0cef-4f54-adce-e1137ab27acd                20170321T215745.007+0100       12.2.2.0                Command=Open app;Result=0;ResultText=Success                fe87b122-8979-45d4-9c37-3c39ce704045              0e6278ad-ffff-4d6c-9d66-af84a1596d78                 1                DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197               Not available      Engine  Not available              Global::OpenApp             Open app            0              Success 48345a91-0cef-4f54-adce-e1137ab27acd
 
Second Open (already loaded in memory):
 
2              12.16.1.0              20170321T220053.193+0100       QlikServer1         ea7e3197-3651-4a87-9c56-a4d51872f01f                20170321T220053.193+0100       12.2.2.0                Command=Open app;Result=0;ResultText=Success                fe87b122-8979-45d4-9c37-3c39ce704045              a057e326-6123-406a-8ee2-e82a46efe367             1                DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197               Not available      Engine  Not available              Global::OpenApp             Open app            0              Success ea7e3197-3651-4a87-9c56-a4d51872f01f
 
This log gives the information on the app being opened with its Session ID.
 
C:\ProgramData\Qlik\Sense\Log\Engine\Trace\QLIKSERVER1_Session_Engine.txt
 
First Open (Closed browser tab):
 
1              20170321T220016.240+0100       INFO      QlikServer1         Session.Engine.Engine   53           6f637615-237c-4716-87d1-4a3f06ed81be        DOMAIN\qvservice                         fe87b122-8979-45d4-9c37-3c39ce704045              DOMAIN                qvservice             20170321T220016.238+0100       3132       3176       12.2.50504.0409.10                20170321T215516.000+0100       0e6278ad-ffff-4d6c-9d66-af84a1596d78                 c3ed4e49-dc98-4ff8-b140-f3d945236197    Load Test APP ID              20170320T195542.497Z                 Socket closed by client                20170321T215743.000+0100       0.001771              0.006285              1902       5619       13           0                UserDirectory=DOMAIN; UserId=qvservice           Off         6f637615-237c-4716-87d1-4a3f06ed81be
 
This has one entry for when tab in the browser was closed (but maintained the actual Session ID since the browser was still active) and you can see by the time stamp of 20170321T220016 is before the Second Open of 20170321T220053. If you had closed the Second Open session you would have a similar entry.
 
C:\ProgramData\Qlik\Sense\Log\Proxy\Audit\QLIKSERVER1_AuditActivity_Proxy.txt
 
First Open (No Session established until now):
 
1              11.11.0.0              20170321T215731.469+0100       QlikServer1         201ee217-3713-44cb-9277-d374799a84fb                Command=Get ticket;Result=0;ResultText=Success          0              0              0              INTERNAL            sa_proxy                0              Not available      Proxy    Not available      /hub/stream/e4f1e040-75cf-4db0-afbd-baaf90cab8f8    Get ticket:ConsumeIncomingTicket  0              User claimed ticket: 'ewXLiJDk6xM1Q0TH'. Session will be etablished                201ee217-3713-44cb-9277-d374799a84fb
2              11.11.0.0              20170321T215731.512+0100       QlikServer1         7042d186-3f1d-4759-9d87-663b73522766                Command=Start session;Result=0;ResultText=Success    fe87b122-8979-45d4-9c37-3c39ce704045              0                0              DOMAIN              qvservice             0              DOMAIN\qvservice         Proxy    Not available                /qps/sessionstart/qvservice        Start session      0              Start session for user: 'DOMAIN\qvservice'                7042d186-3f1d-4759-9d87-663b73522766
3              11.11.0.0              20170321T215731.892+0100       QlikServer1         2e9f0d03-aabe-403a-b282-ec01a47283a0                Command=Add session;Result=0;ResultText=Success      fe87b122-8979-45d4-9c37-3c39ce704045                c8d0eb48-fe7a-47da-bbca-0eab11340b92             0              DOMAIN              qvservice             0              Not available                Proxy    Not available      /hub/stream/e4f1e040-75cf-4db0-afbd-baaf90cab8f8    Add session:NotifyOfPostSession       0              Syncing user attributes for user 'DOMAIN\qvservice'        2e9f0d03-aabe-403a-b282-ec01a47283a0
4              11.11.0.0              20170321T215736.774+0100       QlikServer1         4f3ec3ce-604b-4fad-930c-6c5d3c417112                Command=Get session;Result=200;ResultText=Success  fe87b122-8979-45d4-9c37-3c39ce704045                bcce5b5b-a2e5-455c-9a36-f3fe076b03e3              0              DOMAIN              qvservice             0              Not available                Proxy    AppAccess          /qps/user?targeturi=http:%2f%2fqlikserver1.domain.local%2fhub%2f     Get session:HandleRequest 200         Handle connection request         4f3ec3ce-604b-4fad-930c-6c5d3c417112
5              11.11.0.0              20170321T215743.567+0100       QlikServer1         1fcb5c5c-15f5-40a6-bd54-0819643cd197                Command=Open connection;Result=0;ResultText=Success           fe87b122-8979-45d4-9c37-3c39ce704045                0e6278ad-ffff-4d6c-9d66-af84a1596d78                 0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Proxy    AppAccess          /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197                Open connection             0              Backend web socket connection Opened for session 'fe87b122-8979-45d4-9c37-3c39ce704045'. App id: 'c3ed4e49-dc98-4ff8-b140-f3d945236197'. UserAgent: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36'           1fcb5c5c-15f5-40a6-bd54-0819643cd197
 
First Open (Closed tab)
 
6              11.11.0.0              20170321T220016.242+0100       QlikServer1         12a1b6ff-d000-4f56-a58c-8ca1bd36a567                Command=Close connection;Result=0;ResultText=Success            fe87b122-8979-45d4-9c37-3c39ce704045                0e6278ad-ffff-4d6c-9d66-af84a1596d78                 0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Proxy    AppAccess          /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197                Close connection              0              Backend web socket connection Closed for session 'fe87b122-8979-45d4-9c37-3c39ce704045'. App id: 'c3ed4e49-dc98-4ff8-b140-f3d945236197. UserAgent: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36'           12a1b6ff-d000-4f56-a58c-8ca1bd36a567
 
Second Open:
 
7              11.11.0.0              20170321T220052.937+0100       QlikServer1         f1f1350f-0b00-4cf1-b30c-51ddbfecb6bb                Command=Open connection;Result=0;ResultText=Success           fe87b122-8979-45d4-9c37-3c39ce704045                a057e326-6123-406a-8ee2-e82a46efe367             0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Proxy    AppAccess          /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197                Open connection             0              Backend web socket connection Opened for session 'fe87b122-8979-45d4-9c37-3c39ce704045'. App id: 'c3ed4e49-dc98-4ff8-b140-f3d945236197'. UserAgent: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36'           f1f1350f-0b00-4cf1-b30c-51ddbfecb6bb

 
Notice in this log the user gets a Ticket and Session in the first open to kick off the Session ID. You can then see that web socket connection is closed to the application for that session and then reopened right after it.
 
Note: The Syncing of attributes in the First Open that gets the ticket, it only does that the start of the session and will not be triggered until a new session is established.

C:\ProgramData\Qlik\Sense\Log\Proxy\Audit\QLIKSERVER1_AuditActivity_Proxy.txt
 
First Open (No Session established until now):
 
1              11.11.0.0              20170321T215731.469+0100       QlikServer1         201ee217-3713-44cb-9277-d374799a84fb                Command=Get ticket;Result=0;ResultText=Success          0              0              0              INTERNAL            sa_proxy                0              Not available      Proxy    Not available      /hub/stream/e4f1e040-75cf-4db0-afbd-baaf90cab8f8    Get ticket:ConsumeIncomingTicket  0              User claimed ticket: 'ewXLiJDk6xM1Q0TH'. Session will be etablished                201ee217-3713-44cb-9277-d374799a84fb
2              11.11.0.0              20170321T215731.512+0100       QlikServer1         7042d186-3f1d-4759-9d87-663b73522766                Command=Start session;Result=0;ResultText=Success    fe87b122-8979-45d4-9c37-3c39ce704045              0                0              DOMAIN              qvservice             0              DOMAIN\qvservice         Proxy    Not available                /qps/sessionstart/qvservice        Start session      0              Start session for user: 'DOMAIN\qvservice'                7042d186-3f1d-4759-9d87-663b73522766
3              11.11.0.0              20170321T215731.892+0100       QlikServer1         2e9f0d03-aabe-403a-b282-ec01a47283a0                Command=Add session;Result=0;ResultText=Success      fe87b122-8979-45d4-9c37-3c39ce704045                c8d0eb48-fe7a-47da-bbca-0eab11340b92             0              DOMAIN              qvservice             0              Not available                Proxy    Not available      /hub/stream/e4f1e040-75cf-4db0-afbd-baaf90cab8f8    Add session:NotifyOfPostSession       0              Syncing user attributes for user 'DOMAIN\qvservice'        2e9f0d03-aabe-403a-b282-ec01a47283a0
4              11.11.0.0              20170321T215736.774+0100       QlikServer1         4f3ec3ce-604b-4fad-930c-6c5d3c417112                Command=Get session;Result=200;ResultText=Success  fe87b122-8979-45d4-9c37-3c39ce704045                bcce5b5b-a2e5-455c-9a36-f3fe076b03e3              0              DOMAIN              qvservice             0              Not available                Proxy    AppAccess          /qps/user?targeturi=http:%2f%2fqlikserver1.domain.local%2fhub%2f     Get session:HandleRequest 200         Handle connection request         4f3ec3ce-604b-4fad-930c-6c5d3c417112
5              11.11.0.0              20170321T215743.567+0100       QlikServer1         1fcb5c5c-15f5-40a6-bd54-0819643cd197                Command=Open connection;Result=0;ResultText=Success           fe87b122-8979-45d4-9c37-3c39ce704045                0e6278ad-ffff-4d6c-9d66-af84a1596d78                 0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Proxy    AppAccess          /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197                Open connection             0              Backend web socket connection Opened for session 'fe87b122-8979-45d4-9c37-3c39ce704045'. App id: 'c3ed4e49-dc98-4ff8-b140-f3d945236197'. UserAgent: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36'           1fcb5c5c-15f5-40a6-bd54-0819643cd197

First Open (Closed tab)
 
6              11.11.0.0              20170321T220016.242+0100       QlikServer1         12a1b6ff-d000-4f56-a58c-8ca1bd36a567                Command=Close connection;Result=0;ResultText=Success            fe87b122-8979-45d4-9c37-3c39ce704045                0e6278ad-ffff-4d6c-9d66-af84a1596d78                 0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Proxy    AppAccess          /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197                Close connection              0              Backend web socket connection Closed for session 'fe87b122-8979-45d4-9c37-3c39ce704045'. App id: 'c3ed4e49-dc98-4ff8-b140-f3d945236197. UserAgent: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36'           12a1b6ff-d000-4f56-a58c-8ca1bd36a567
 
Second Open:
 
7              11.11.0.0              20170321T220052.937+0100       QlikServer1         f1f1350f-0b00-4cf1-b30c-51ddbfecb6bb                Command=Open connection;Result=0;ResultText=Success           fe87b122-8979-45d4-9c37-3c39ce704045                a057e326-6123-406a-8ee2-e82a46efe367             0              DOMAIN              qvservice             c3ed4e49-dc98-4ff8-b140-f3d945236197         Not available      Proxy    AppAccess          /app/c3ed4e49-dc98-4ff8-b140-f3d945236197?reloaduri=http%3a%2f%2fqlikserver1.domain.local%2fsense%2fapp%2fc3ed4e49-dc98-4ff8-b140-f3d945236197                Open connection             0              Backend web socket connection Opened for session 'fe87b122-8979-45d4-9c37-3c39ce704045'. App id: 'c3ed4e49-dc98-4ff8-b140-f3d945236197'. UserAgent: 'Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36'           f1f1350f-0b00-4cf1-b30c-51ddbfecb6bb
 
Notice in this log the user gets a Ticket and Session in the first open to kick off the Session ID. You can then see that web socket connection is closed to the application for that session and then reopened right after it.
 
Note: The Syncing of attributes in the First Open that gets the ticket, it only does that the start of the session and will not be triggered until a new session is established.

C:\ProgramData\Qlik\Sense\Log\Proxy\Trace\QLIKSERVER1_Audit_Proxy.txt
 
First Open (loaded into memory):
  
1              20170321T215731.134+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.Authentication.AuthenticationHandler 14           384a5be2-8c1f-4569-8b17-a6fa747b8f2f          DOMAIN\qvservice         Session 'a0ee67d2-581b-47db-9514-443ac4a008b1' is invalid (possibly timed out or logged out)            0              45b4435a-3e05-47c4-b78b-0e5311154a91                                                             ::ffff:172.16.16.100                                          {}             1650cb4421d90c3f0e3af23e1f5e2c8176219ad8
2              20170321T215731.188+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.RedirectionHandler       14           17bed8a0-b6ec-4316-9dfd-ff062b4b1c79     DOMAIN\qvservice         Authentication required, redirecting client@http://[::ffff:172.16.16.100]:62230/  to http://qlikserver1.domain.local:4248/windows_authentication/?targetId=6b07f3fb-5d9e-462f-b424-bb389054e645            0              45b4435a-3e05-47c4-b78b-0e5311154a91                                                             ::ffff:172.16.16.100                                          {}                8da259cac80248a0b1258dffa22a0bc5585c668b
3              20170321T215731.444+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.Authentication.TicketValidator 14           ab854bb8-5c99-4a1c-8b76-00a443e94684    DOMAIN\qvservice         Issued ticket 'ewXLiJDk6xM1Q0TH' for user, valid for 1 minute(s)               0                                DOMAIN              qvservice             ewXLiJDk6xM1Q0TH                                                                       7f97ce8a8282eb9ed7aa0b61722b2504241e0e09
4              20170321T215731.470+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.Authentication.AuthenticationHandler 14           f27f9ebc-4ad4-4d5a-968d-13e910e1efab        DOMAIN\qvservice         User claimed ticket: 'ewXLiJDk6xM1Q0TH'            0              583a2b2e-5aeb-4292-9d02-d1c4e5a1cd0b DOMAIN              qvservice             ewXLiJDk6xM1Q0TH       ::ffff:172.16.16.100                                          {}             e025a74e13bb4c759fe5ad99787ad5589381b7bf
5              20170321T215731.891+0100       INFO      QlikServer1                Audit.Proxy.Proxy.DefaultModules.Session.SessionClientHandler               8              8dfacde2-3963-432b-af75-22d5122b5fea    DOMAIN\qvservice         Syncing user attributes for user DOMAIN\qvservice was successful                fe87b122-8979-45d4-9c37-3c39ce704045              583a2b2e-5aeb-4292-9d02-d1c4e5a1cd0b            DOMAIN                qvservice             ewXLiJDk6xM1Q0TH       ::ffff:172.16.16.100                                          {}                df162a32bfed4ae4c37531b6f1ad4e7cb18b708e
6              20170321T215732.018+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.Authentication.AuthenticationHandler 14           711c200a-60e9-457a-be6c-89f1ce11bf82          DOMAIN\qvservice         User 'qvservice' used 'ticket' authentication, got session: 'fe87b122-8979-45d4-9c37-3c39ce704045'                  fe87b122-8979-45d4-9c37-3c39ce704045              583a2b2e-5aeb-4292-9d02-d1c4e5a1cd0b   DOMAIN              qvservice             ewXLiJDk6xM1Q0TH       ::ffff:172.16.16.100                                          {}                7fa218f968005afa6c0e635058e1e6c290e90d76
7              20170321T215735.128+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies     8              11c49eb7-4ce8-45be-98d1-76a10f34562c          DOMAIN\qvservice         Retrieved 1 engine(s) from repository, result code Ok, app: __hub                fe87b122-8979-45d4-9c37-3c39ce704045              355bcda7-26f1-4a41-94d5-c5c88499abb8              DOMAIN                qvservice                             ::ffff:172.16.16.100                          qlikserver1.domain.local:4242    {}                7b0262f7f34c583b38c13639692a495540079d74
8              20170321T215735.144+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies     8              29022811-cbe3-4f9d-ba19-b3bb50f37e0e        DOMAIN\qvservice         Cached 1 prioritised Engine(s), app: __hub           fe87b122-8979-45d4-9c37-3c39ce704045          355bcda7-26f1-4a41-94d5-c5c88499abb8              DOMAIN              qvservice                             ::ffff:172.16.16.100                          qlikserver1.domain.local:4242    {}                5ff601a6ada967d7d6c9990a1bddbe25e7bbc1cf
9              20170321T215735.186+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies     24           dbf6cd5b-735e-4112-94c3-4db366bbe4b2       DOMAIN\qvservice         New target uri chosen: https://qlikserver1.domain.local:4900/ , app: __hub   fe87b122-8979-45d4-9c37-3c39ce704045              355bcda7-26f1-4a41-94d5-c5c88499abb8              DOMAIN                qvservice                             ::ffff:172.16.16.100                          qlikserver1.domain.local:4900    {}                ba0e44b68b214c47fea575e93244c3c5f159c281
10           20170321T215743.535+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies     8              7bcf1a03-6cfe-45ea-a06b-d1a780528be0        DOMAIN\qvservice         Retrieved 1 engine(s) from repository, result code Ok, app: c3ed4e49-dc98-4ff8-b140-f3d945236197    fe87b122-8979-45d4-9c37-3c39ce704045              79705676-f6f7-4396-8771-9f9f2a57f711      DOMAIN              qvservice                             ::ffff:172.16.16.100          c3ed4e49-dc98-4ff8-b140-f3d945236197                    {}             fe793ff3d692d1992e38f7be35c3a15d93ada65d
11           20170321T215743.535+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies     8              425b5b86-579e-410f-8721-a816841bc16a         DOMAIN\qvservice         Cached 1 prioritised Engine(s), app: c3ed4e49-dc98-4ff8-b140-f3d945236197    fe87b122-8979-45d4-9c37-3c39ce704045              79705676-f6f7-4396-8771-9f9f2a57f711                DOMAIN              qvservice                             ::ffff:172.16.16.100          c3ed4e49-dc98-4ff8-b140-f3d945236197                                {}             ab51d2ad92cef8fff57fb15b1d5b115eeabedecb
12           20170321T215743.563+0100       INFO      QlikServer1                Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies     24           4c8e93c3-b3c9-475b-aa03-b8290f196014         DOMAIN\qvservice         New target uri chosen: wss://qlikserver1.domain.local:4747/, app: c3ed4e49-dc98-4ff8-b140-f3d945236197               fe87b122-8979-45d4-9c37-3c39ce704045              79705676-f6f7-4396-8771-9f9f2a57f711           DOMAIN              qvservice                             ::ffff:172.16.16.100          c3ed4e49-dc98-4ff8-b140-f3d945236197    qlikserver1.domain.local:4747    {}             f27c34ac0b7976a062ef3ea21d129acf451b0e65

This log only tracks the initial Session from the first Open, since the session is already established for the User. Further opening of the same app will not trigger a new entry for this Session/App ID
  
Final Note: There were no tests and review of entries for any new user sessions, different App IDs or for when the session times out or is forcible closed (closing the browser).  

What is legacy mode?
Legacy mode in Qlik Sense allows users who have access to the data load editor to write load statements which reference file paths rather than through LIB statements.

Simple example:
Standard Mode:
LOAD * 
FROM [lib://data/data.csv]
(txt, codepage is 28591, embedded labels, delimiter is ',', msq);

Legacy Mode:
LOAD * 
FROM C:\data\data.csv
(txt, codepage is 28591, embedded labels, delimiter is ',', msq);

What are the security considerations when using legacy mode?

Out of the box, for a user to do development in Qlik Sense, they need some combination of two types of access:

1. An ability to create a data connection
2. An ability to read (or see) a data connection

This security model is the intermediary between the user inside of Qlik Sense and the data sources.

When using legacy mode, any user who has access to the Data Load Editor can now access the file system of the local Qlik Sense server as well as any network file shares that the Qlik Sense service account independent of the security rules configured on the Qlik Sense deployment. In this example, the user has access to AttachedFiles, which all users would out of the box, as well as a Salesforce data connection, yet they are still able to load from the data.csv:

This means that the traditional mechanism for ensuring governance and security over data access inside of the Data Load Editor will no longer apply and the user(s) will be accessing the files as the Qlik Sense Service account

What are the benefits of using Legacy Mode?

This is difficult to answer in an exhaustive manner, but generally the benefits are narrowly scoped to deployments where app development, self-service capabilities are disabled or where this level of access is restricted to a vetted set of administrators. Some benefits include:

• The ability to use relative paths in load scripts (e.g. LOAD * FROM ..\..\Customer1\sales.csv). Often used in conjunction with include scripts which allow easy deployment to multiple customers or tenants.
• The ability to use the EXECUTE function (in conjunction with an additional Settings.ini change) to directly call external processes during script execution
• The ability to re-use load statements from QlikView documents in Qlik Sense
• And others

Is legacy mode recommended by Qlik?
For most deployments, no, legacy mode is not recommended. It can be useful in some deployment scenarios where the security concerns are mitigated.

How do I switch to Legacy mode / disable standard mode?
Disabling standard mode - Enabling Legacy Mode - Qlik Sense on Windows

Qlik Sense Legacy mode

Qlik Sense Legacy Mode - Qlik Design Blog

This is a recording of a Support Techspert Thursdays session.

This session addresses:
- What the App Analyzer can do
- How to set it up
- How to improve app performance
- Troubleshooting issues

Chapters:

00:00 – Intro

 01:26 - App Analyzer Overview

 02:39 - When the App Analyzer is Useful

 03:43 - SaaS Standard Tier Capabilities

 06:23 - How Qlik Sense Stores Data

 07:32 - App Analyzer Dashboard demo

 08:58 - Example App Optimization

 10:54 - Best Practice thresholds

 12:02 - Threshold Analysis Sheet Demo

 12:32 - App RAM to Quota Sheet Demo

13:19 - Example App

 13:47 - App Analysis Sheet Demo

14:39 - Rolling Analysis Sheet Demo

16:28 - Reload Time

17:06 - Setting it up

 18:11 - TIP: Relative Path

 18:47 - Creating a REST Connection

 20:34 - The right space to use

 21:16 - Troubleshooting: SET ErrorMode

 22:13 - TroubleShooting: API Key

 23:29 - App Analyzer on Qlik Community

 24:41 - Qlik Diagnostic Toolkit

 25:41 - Qlik Sense Admin Playbook

 26:13 - Q&A

Environment

• Qlik Sense Enterprise SaaS - Standard Tier

Related Content 

App Analyzer on Qlik Community

Qlik Dignostic Toolkit

Qlik Sense Admin Playbook

STT - Optimizing Qlik Sense SaaS Apps with App Analyzer

Q&A:

Q: I noticed sheets supposedly in my app according to the App MetaData Analyser that are not part of my app. Is the presented data reliable?

A: Neither the App Analyzer for Qlik Sense Enterprise SaaS or the App Metadata Analyzer for Qlik Sense Enterprise on Windows track sheets – they only gather data model and reload metadata. That said, there was a bug in the App Metadata Analyzer for Qlik Sense Enterprise on Windows that did associate some fields/tables to the wrong apps that has since been addressed. You can always grab the latest version of the App Metadata Analyzer for Windows here.

Q: Hi, super interesting stuff!  is the very same App Analyzer available to non-SaaS customers?

A: The application that the App Analyzer was modeled off of is the App Metadata Analyzer for Qlik Sense Enterprise on Windows that ships with the product. You can find the most recent version of that application here.

Q: The configuration of REST Connector is throwing error "cannot connect"...are there any setup needed on the tenant level?

A: Please refer to the installation guide for the App Analyzer and if you are still having issues, please post on the Qlik Community entry here.

Q: Can we setup Qlik Alerting to inform us as we get closer to threshholds?

A: Absolutely, yes. This is a great way to stay on top of monitoring your applications. In addition, you can also monitor one of the charts from the app in the Hub to have a quick look at where everything stands each time you login to the tenant.

Transcript

Currently, there is no available feature to delete (or update) existing tags in Qlik Sense SaaS.

Environment

Qlik Cloud 

Resolution

Qlik has previously received feedback on this feature. For up to date information and to express your interest in this feature, review https://community.qlik.com/t5/Suggest-an-Idea/Enable-Deletion-Update-of-Tags-in-Qlik-Sense-SaaS/idi-p/1831354 

When accessing the QlikSense Hub with an iOS device (iPad/iPhone) Apps are not loaded or cannot be opened. HTTPS access is used.

The user tries to open the Qlik Sense Hub on an iOS device (iOS 8 and above) using the address https://servername/hub

When attempting to open an App they are presented with an endless loading screen or "Connection to the Qlik Sense engine failed for unspecified reasons"
 

A review of the QlikSense Proxy logs (Folder Trace\ and  SERVER_Audit_Proxy) might show SslNoClientValidation WARN entries. 

Environment: 

Qlik Sense Mobile  on iOS

Cause:

Apple has removed the ability of users to ignore certificate warnings on devices iOS 8 and above. On laptops or desktops you would have the option to ignore the SSL warning, but this option is not possible with iOS devices.

Resolution:

1) Since the "Connection Lost" message or endless "bubble" loading screen are typically indicative of an allowed url/host problem, be sure that the Domain that the user is accessing the Hub has been allowed through firewalls and proxies. See article Error Message "Connection lost" When Connecting To Qlik Sense Hub for more clarity on this. If users on laptops / desktops do not receive this message then proceed to step 2.

2) Access https://sense-demo.qlik.com/hub using the iOS device. If this works then proceed to step 3.

• If the demo link does not work, you have a possible browser, network, or internet connectivity issue at the device level.

3) Apple requires an SSL cert from a trusted CA when accessing websites via HTTPS (check their knowledge base for a list of providers). You can either acquire a certificate from one of the vetted list of providers or the user(s) can access the Hub using HTTP. For guidance on applying a third party certificate, see article How to change certificate for the Proxy.  

4) If no certificate from a trusted CA can be acquired, it will be necessary to install the current one.  See Apple and it's Apple Configurator for details. 

The Qlik Sense Mobile app allows you to securely connect to your Qlik Sense Enterprise deployment from your supported mobile device. This is the process of configuring Qlik Sense to function with the mobile app on iPad  / iPhone.

This article applies to the Qlik Sense Mobile app used with Qlik Sense Enterprise on Windows. For information regarding the Qlik Cloud Mobile app, see Setting up Qlik Sense Mobile SaaS. 

Content:

• Pre-requirements (Client-side)
• Configuration (Server-side)
• Update the Host White List in the proxy
• Configuration (Client side)

Pre-requirements (Client-side)

See the requirements for your mobile app version on the official Qlik Online Help > Planning your Qlik Sense Enterprise deployment > System requirements for Qlik Sense Enterprise > Qlik Sense Mobile app

Configuration (Server-side)

Acquire a signed and trusted Certificate.

Out of the box, Qlik Sense is installed with HTTPS enabled on the hub and HTTP disabled. Due to iOS specific certificate requirements, a signed and trusted certificate is required when connecting from an iOS device. If using HTTPS, make sure to use a certificate issued by an Apple-approved Certification Authority.
Also check Qlik Sense Mobile on iOS: cannot open apps on the HUB  for issues related to Qlik Sense Mobile on iOS and certificates.

For testing purposes, it is possible to enable port 80.

(Optional) Enable HTTP (port 80).

1. Open the Qlik Sense Management Console and navigate to Proxies.
2. Select the Proxy you wish to use and click Edit Proxy.  
3. Check Allow HTTP 

Update the Host White List in the proxy 

If not already done, add an address to the White List:

1. In Qlik Management Console, go to CONFIGURE SYSTEM -> Virtual Proxies
2. Select the proxy and click Edit
3. Select Advanced in Properties list on the right pane
   
   

    

4. Scroll to Advanced section in the middle pane
5. Locate "Allow list"
   
   

    

6. Click "Add new value" and add the addresses being used when connecting to the Qlik Sense Hub from a client. See How to configure the WebSocket origin allow list and best practices for details. 
   
   

Generate the authentication link:

An authentication link is required for the Qlik Sense Mobile App.

1. Navigate to Virtual Proxies in the Qlik Sense Management Console and edit the proxy used for mobile App access
2. Enable the Client authentication link menu in the far right menu.
3. Generate the link.

NOTE: In the client authentication link host URI, you may need to remove the "/" from the end of the URL, such as http://10.76.193.52/ would be http://10.76.193.52 

Associate User access pass

Users connecting to Qlik Sense Enterprise need a valid license available. See the Qlik Sense Online Help for more information on how to assign available access types.
Qlik Sense Enterprise on Windows > Administer Qlik Sense Enterprise on Windows > Managing a Qlik Sense Enterprise on Windows site > Managing QMC resource > Managing licenses

• Managing professional access
• Managing analyzer access
• Managing user access
• Creating login access rules

Configuration (Client side)

1. Install Qlik Sense mobile app from AppStore.
2. Provide authentication link generated in QMC
   • Open the link from your device (this can be also done by going to the Hub, clicking on the menu icon at the top right and selecting "Client Authentication"), the installed application will be triggered automatically, and the configuration parameters will be applied.
   •  Enter user credentials for QS server

The TAC configuration page's Artifact section displays an error for JFrog access check：

error unauthorized : https://<JFROG_PLATFORM_URL>:<PORT>/access/api/v1/system/ping

Cause

$ curl -u "admin:password" "https://<JFROG_PLATFORM_URL>:<PORT>/access/api/v1/system/ping"
{
"errors" : [ {
"code" : "UNAUTHORIZED",
"message" : "Unsupported authentication method Basic"
} ]
}

Resolution

For every Access-related API, you must use an admin-scoped Access Token or an Admin Identity Token. For further details, please refer to How to generate access token from JFrog admin UI.

Environment

• Talend Administration Center 8.0.1

Qlik Sense Enterprise Client-Managed offers a range of Monitoring Applications that come pre-installed with the product.

Qlik Cloud offers the Data Capacity Reporting App for customers on a capacity subscription, and additionally customers can opt to leverage the Qlik Cloud Monitoring apps.

This article provides information on available apps for each platform.

Content:

• Qlik Cloud
• Data Capacity Reporting App
• Access Evaluator for Qlik Cloud
• Answers Analyzer for Qlik Cloud
• App Analyzer for Qlik Cloud
• Automation Analyzer for Qlik Cloud
• Entitlement Analyzer for Qlik Cloud
• Reload Analyzer for Qlik Cloud
• Report Analyzer for Qlik Cloud
• How to automate the Qlik Cloud Monitoring Apps
• Other Qlik Cloud Monitoring Apps
• OEM Dashboard for Qlik Cloud
• Monitoring Apps for Qlik Sense Enterprise on Windows
• Operations Monitor and License Monitor
• App Metadata Analyzer
• The Monitoring & Administration Topic Group
• Other Apps

Qlik Cloud

Data Capacity Reporting App

The Data Capacity Reporting App is a fully supported app distributed within the product. For more information, see Qlik Help.

Access Evaluator for Qlik Cloud

For more information, see Qlik Cloud Access Evaluator.

Answers Analyzer for Qlik Cloud

For more information, see Qlik Cloud Answers Analyzer.

App Analyzer for Qlik Cloud

For more information, see Qlik Cloud App Analyzer.

Automation Analyzer for Qlik Cloud

For more information, see Qlik Cloud Automation Analyzer.

Entitlement Analyzer for Qlik Cloud

The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant for user-based subscriptions.

The app provides:

• Which users are accessing which apps
• Consumption of Professional, Analyzer and Analyzer Capacity entitlements
• Whether you have the correct entitlements assigned to each of your users
• Where your Analyzer Capacity entitlements are being consumed, and forecasted usage

For more information, see The Entitlement Analyzer.

Reload Analyzer for Qlik Cloud

For more information, see Qlik Cloud Reload Analyzer.

Report Analyzer for Qlik Cloud

For more information, see Qlik Cloud Report Analyzer.

How to automate the Qlik Cloud Monitoring Apps

Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:

1. Install/update the apps with a fully guided, click-through installer using an out-of-the-box Qlik Application Automation template. 
2. Programmatically rotate the API key that is required for the data connection on a schedule using an out-of-the-box Qlik Application Automation template. This ensures that the data connection is always operational. 
3. Get alerted whenever a new version of a monitoring app is available using Qlik Data Alerts. 

For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.

Other Qlik Cloud Monitoring Apps

OEM Dashboard for Qlik Cloud

For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.

With the exception of the Data Capacity Reporting App, all Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.

If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.

Monitoring Apps for Qlik Sense Enterprise on Windows

Operations Monitor and License Monitor

The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.

The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.

For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.

Basic information can be found here:

The License Monitor 
The Operations Monitor 

Both apps come pre-installed with Qlik Sense. 

If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows. 

App Metadata Analyzer

The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.

Basic information can be found here: 

App Metadata Analyzer (help.qlik.com)

For more details and best practices, see: 

App Metadata Analyzer (Admin Playbook)

The app comes pre-installed with Qlik Sense.

The Monitoring & Administration Topic Group

Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.

Monitoring & Administration 

Other Apps

LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs 
Sessions Monitor, Reloads-Monitor, Log-Monitor 
Connectors Log Analyzer 

All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.

The following steps are only applicable to Qlik Sense deployments originally installed with versions prior to the June 2019 release. For any Qlik Sense deployments installed with later versions, follow standard steps for patching Qlik Sense and do not perform the steps in this article.

In these steps we will occasionally ask you to run Powershell code.

Executing PowerShell code:

1. Copy the code and save it in a ps1 file, in example: certificates_backup.ps1
2. Open elevated command line and navigate to the location where the script was saved.
3. Start PowerShell by executing following command: Powershell
4. Run the script by executing following command: .\<name_of_the_script>.ps1 in example: .\certificates_backup.ps1

Environment

• Qlik Sense Enterprise on Windows, June 2019 thru November 2019

Resolution

1. After upgrading to June 2019 or above, check the Root certificate by running the C2 Validator tool on ALL NODES. If CA and Critical display 'Missing', please follow the instructions below.
2. Stop all services on ALL NODES in the Qlik Sense cluster.
3. Back up all current Qlik Sense certificates from the CENTRAL NODE by executing the following PowerShell code:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

function ExportCertificatesFromStore(
    [string] $name,
    [string] $location)
{
    $success = 1
    $oid = "1.3.6.1.5.5.7.13.3"
    
    $localStore = new-object System.Security.Cryptography.X509Certificates.X509Store $name, $location
    $localStore.Open("MaxAllowed")

    $mypwd = ConvertTo-SecureString -String "MyPassword" -Force -AsPlainText

    try
    {
        $certs = $localStore.Certificates
        foreach ($cert in $certs)
        {
            $extensions = $cert.Extensions
            foreach($extension in $extensions)
            {
                if ($extension.Oid.Value.Equals($oid))
                {
                    Get-ChildItem -Path cert:\$($localStore.Location)\$($localStore.Name) | Where-Object { $_.PrivateKey.CspKeyContainerInfo.Exportable } | Export-PfxCertificate -FilePath "$($localStore.Name)_$($localStore.Location).pfx" -Password $mypwd
                    break;
                }
            }
        }
    }

    catch
    {
        write-host "An error occurred while removing certificates" -ForegroundColor Red
        write-host $_.Exception.GetType().FullName -ForegroundColor Red
        write-host $_.Exception.Message -ForegroundColor Red
        $success = 0
    }

    finally
    {
        $localStore.Close()
    }
    
    if ($success -ne 1)
    {
        exit 20
    }
}

function ExportCertificates()
{
    ExportCertificatesFromStore "Root" "LocalMachine"
    ExportCertificatesFromStore "My" "LocalMachine"
    ExportCertificatesFromStore "My" "CurrentUser"
}

ExportCertificates
write-host "Done."
exit 0

NOTE: For information on how to execute above code please refer to “Executing PowerShell code” section at the top. Modify $mypwd variable to define custom password. Make sure certificates were backed up after running the script:

• Root_LocalMachine.pfx – root CA
• My_LocalMachine.pfx – server
• My_CurrentUser – client

NOTE: If you happen to have more certificates with the same values in Issued To, Issued By and Friendly Name columns and you are unable to identify the correct certificate, please refer to Identifying Qlik Sense root CA and server certificates in certificate store.

1. Remove current Qlik Sense root CA certificate from CENTRAL NODE by executing the following PowerShell code:
   

   Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
   
   function RemoveCertificatesFromStore(
   [string] $name,
   [string] $location)
   {
       $success = 1
       $oid = "1.3.6.1.5.5.7.13.3"
   
       $localStore = new-object System.Security.Cryptography.X509Certificates.X509Store $name, $location
       $localStore.Open("MaxAllowed")
       try
       {
           $certs = $localStore.Certificates
           foreach ($cert in $certs)
           {
               $extensions = $cert.Extensions
               foreach($extension in $extensions)
               {
                   if ($extension.Oid.Value.Equals($oid))
                   {
                       write-host "Deleting certificate from" $localStore.Name $localStore.Location
                       write-host " Subject:"$cert.Subject
                       write-host " Issuer:"$cert.Issuer
                       write-host " Serial:"$cert.SerialNumber
                       $localStore.Remove($cert)
                       break;
                   }
               }
           }
       }
       catch
       {
           write-host "An error occurred while removing certificates" -ForegroundColor Red
           write-host $_.Exception.GetType().FullName -ForegroundColor Red
           write-host $_.Exception.Message -ForegroundColor Red
           $success = 0
       }
       finally
       {
           $localStore.Close()
       }
   
       if ($success -ne 1)
       {
           exit 20
       }
   }
   
   function CleanCertificates()
   {
       RemoveCertificatesFromStore "Root" "LocalMachine"
   }
   
   CleanCertificates
   write-host "Done."
   exit 0​

2. Make sure script completes without any errors. Otherwise remove Qlik Sense root CA certificate manually (please see Recreating Qlik Sense root CA certificate (manual back-up and removal of existing certificates).
3. Remove all current Qlik Sense certificates from NON-CENTRAL NODES by executing the following PowerShell code:
   

   Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass
   
   function RemoveCertificatesFromStore(
       [string] $name,
       [string] $location)
   {
       $success = 1
       $oid = "1.3.6.1.5.5.7.13.3"
   
       $localStore = new-object System.Security.Cryptography.X509Certificates.X509Store $name, $location
       $localStore.Open("MaxAllowed")
   
       try
       {
           $certs = $localStore.Certificates
           foreach ($cert in $certs)
           {
               $extensions = $cert.Extensions
               foreach($extension in $extensions)
               {
                   if ($extension.Oid.Value.Equals($oid))
                   {
                       write-host "Deleting certificate from" $localStore.Name $localStore.Location
                       write-host " Subject:"$cert.Subject
                       write-host " Issuer:"$cert.Issuer
                       write-host " Serial:"$cert.SerialNumber
                       $localStore.Remove($cert)
                       break;
                   }
               }
           }
       }
   
       catch
       {
           write-host "An error occurred while removing certificates" -ForegroundColor Red
           write-host $_.Exception.GetType().FullName -ForegroundColor Red
           write-host $_.Exception.Message -ForegroundColor Red
           $success = 0
       }
   
       finally
       {
           $localStore.Close()
       }
   
       if ($success -ne 1)
       {
           exit 20
       }
   }
   
   function CleanCertificates()
   {
       RemoveCertificatesFromStore "Root" "LocalMachine"
       RemoveCertificatesFromStore "My" "LocalMachine"
       RemoveCertificatesFromStore "My" "CurrentUser"
   }
   
   CleanCertificates
   write-host "Done."
   exit 0​

4. Make sure script completes without any errors. Otherwise remove certificates manually (please see Recreating Qlik Sense root CA certificate (manual back-up and removal of existing certificates).
5. Remove all current Qlik Sense certificates from NON-CENTRAL NODES stored locally by deleting all files from following location:
   
   C:\ProgramData\Qlik\Sense\Repository\Exported Certificates\.Local Certificates
   
   
6. On ALL NODES navigate to C:\Program Files\Qlik\Sense\Repository (or corresponding nondefault location) and open Repository.exe.config file.
7. Make sure Certificates.SelfSignedRoot.BasicConstraintsCA key has value set to true, in example:
   
   <add key="Certificates.SelfSignedRoot.BasicConstraintsCA" value="true" />
   
   If the above key is not present, add it within <appSettings> section, in example:
   

   (…)
   <add key="BackgroundWork.CountLimit" value="3" />
   <add key="Certificates.SelfSignedRoot.BasicConstraintsCA" value="true" />
   <add key="DatabaseCommandTimeout" value="00:01:30" />
   (…)​

   
   NOTE: If you are installing a patch on November 2018 track, name of the key is: <add key="CertificatesSelfSignedRootBasicConstraintsCA" value="true" />
   
8. On the CENTRAL NODE, start Qlik Sense Repository Database service.
9. On CENTRAL NODE, from an elevated command line navigate to C:\Program Files\Qlik\Sense\Repository (or corresponding nondefault location) and run:
   

   repository.exe -bootstrap -iscentral​

10. When bootstrap mode has reached Entering main startup phase.., start Qlik Sense Service Dispatcher service and make sure that the Bootstrap mode has terminated. Press ENTER to exit.. final message is shown

Note: If this message is not shown, open Windows Task Manager, find Qlik Sense Repository Service in the Processes tab and end it by right-clicking on it and selecting End task.

1. To make sure new certificate is in use, run the C2 Validator tool,
2. On CENTRAL NODE restart Qlik Sense Service Dispatcher and start all remaining services.
3. On the NON-CENTRAL NODES, depending on the setup, perform either step a) or b) below:
   • Account running the Qlik Sense services has administrator privileges:
     1. [Applicable ONLY for April 2019 track]: Delete host.cfg file from C:\ProgramData\Qlik\Sense\ 
     2. Start Qlik Sense Repository Service.
     3. Open the Qlik Management Console (QMC) and redistribute the certificates according to Redistributing a certificate
     4. Restart Qlik Sense Repository Service and start all remaining services on the node to make sure they are using the newly distributed certificates.
   • Account running the Qlik Sense service does not have administrator privileges:
     1. [Applicable ONLY for April 2019 track]: Delete host.cfg file from C:\ProgramData\Qlik\Sense\ 
     2. At the command line, navigate to C:\Program Files\Qlik\Sense\Repository (or corresponding nondefault location), and run:
        repository.exe -bootstrap
     3. When the Waiting for certificates to be installed.. message is displayed, redistribute the certificates according to Redistributing a certificate
4. Once the bootstrap mode has terminated, start the Qlik Sense Service Dispatcher, then start the Qlik Sense Repository Service, and finally the remaining Qlik Sense services.

Access Denied

Or

You will not see any files/folders

Resolution

• Make sure the path you are accessing has proper Read rights and permissions are granted. Please read here to check effective permissions, Effective Permission.
• If it is a multi-node environment, ensure that the path is accessible from all the Qlik Sense Windows machines (RIM nodes).
• Make sure to use UNC paths. Please read more about UNC Paths here, File Path Formats 
• Qlik Sense Service account must have access to the path you are connecting to. Please read more about Service Account here,
  • Qlik Sense Service Account requirements 
  • What is the Service Account for Qlik Sense Enterprise on Windows? 
• The Network Shared folder must be on the same domain as the Qlik Sense Windows machine.
• If it is a network path, ensure that the users' credentials of those who do not have access to Qlik Sense are not saved. If the users' credentials are saved, accessing the network path may result in the following warning:

The username or password is incorrect

Cause

• Qlik Sense Service Account does not have proper rights and permissions to access the path.
• The Network Shared path is not accessible from the other Qlik Sense Windows machines (RIM nodes) in a multi-node environment.
• The Path provided is a Mapped drive. Please read here as the mapped drives are not supported, Cannot use mapped network drives for Qlik Sense folder connections
• Network share is Password protected and not accessible to the Qlik Sense Service account.
  
  

When the network share is password-protected, even if the service account has access to it, you must first enter the network share from the Qlik Sense Windows machine/s with credentials to access it.

Note that for every reboot, the password-protected folder will prompt for credentials, causing the Folder Data Connection to fail since Folder Data Connection does not have an option to save user credentials.

Environment

• Qlik Sense Enterprise on Windows 

Introduction

"This prediction failed to run successfully due to schema errors"  can occur during the prediction phase if there is a mismatch in the table schema between training and prediction datasets.

In this example, we will show how a column in the prediction dataset was profiled as a categorical rather than numeric because it contained dashes '-' for empty values.

Steps

1. Upload test_dash_training.csv and test_dash_prediction.csv to Qlik Cloud. See attachments on the article if you would like to download.

Training dataset:

Prediction sample:

2. Create a new ML experiment and choose test_dash_training.csv, and click 'Run Experiment'

3. Deploy the top model

5. Create a new prediction and select test_dash_prediction.csv as the apply dataset

You will encounter a warning message, "Feature type does not match the required model schema."

If you continue, you will encounter another message after clicking 'Save and predict now'.

6. If you click 'Save configuration', the prediction will attempt to run but will not produce prediction dataset and will display an error.

Resolution

Clean up dashes from 'chats' column in test_dash_prediction.csv. Either remove them from the prediction dataset or transform to a numeric value such as zero.

Environment

• Qlik AutoML 

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.

Your Qlik Sense Enterprise on Windows environment suddenly stopped working. When checking the Qlik Sense windows services, you are observing Qlik Sense Repository is stopped whilst the other is running fine. You try to start the Qlik Sense Repository service but it keeps on stopping after a few seconds. 

The System_Repository log (%ProgramData%\Qlik\Sense\Log\Repository\Trace\YourServerName_System_Repository.txt) shows the following error:

115 20220302T083819.725+0100 ERROR qlikserver1.domain.local System.Repository.Repository.QRSMain 6 3266cf81-5a37-4d34-b74f-70a6fc225764 domain\qvservice Fatal exception during startup Attempted to perform an unauthorized operation.   at System.Security.Cryptography.Utils.SetKeySetSecurityInfo(SafeProvHandle hProv, CryptoKeySecurity cryptoKeySecurity, AccessControlSections accessControlSections)↵↓   at System.Security.Cryptography.Utils.GetKeyPairHelper(CspAlgorithmType keyType, CspParameters parameters, Boolean randomKeyContainer, Int32 dwKeySize, SafeProvHandle& safeProvHandle, SafeKeyHandle& safeKeyHandle)↵↓   at System.Security.Cryptography.RSACryptoServiceProvider.GetKeyPair()↵↓   at System.Security.Cryptography.RSACryptoServiceProvider..ctor(Int32 dwKeySize, CspParameters parameters, Boolean useDefaultKeySize)↵↓   at Qlik.Sense.Communication.Security.Certificates.DotNetCert.SetPrivateKeyAccess(IdentityReference identityReference)↵↓   at Repository.Core.Bootstrap.RepositoryBootstrapper.Install(BootstrapState bootstrapState)↵↓   at Repository.Core.Bootstrap.BootstrapHandler.Install(BootstrapState bootstrapState)↵↓   at Repository.Core.Bootstrap.BootstrapHandler.Bootstrap(BootstrapState bootstrapState)↵↓   at Repository.QRSMain.Bootstrap()↵↓   at Repository.QRSMain.Main()↵↓   at Repository.QRSMain.Run(String[] args, Action`1 terminate) 3266cf81-5a37-4d34-b74f-70a6fc225764

The Windows Application log also prints this McAfee error at the same time you try starting the repository service: 

Event: 3  McAfee Endpoint security

EventID= 18060 

Domain\qvservice ran Qlik\sense\repository\repository.exe, which tried to access C:\programdata\microsoft\crypto\RSA\MachineKeys\<Some GUID> , violating the rule "Malware Behavior: Windows EFS abuse", and was blocked. For information about how to respond to this event, see KB85494

Environment

Qlik Sense Enterprise on Windows 

Resolution

To mitigate the problem as soon as possible,  please reach out to your Internal IT team in charge of administering McAfee and request them to disable the exploit prevention on McAfee - You could set up a new container in McAfee, add all your Qlik Sense servers, and set a policy to disable the exploit prevention. 

A longer-term solution is to investigate with the vendor why this error suddenly came in and make sure all Qlik Services (processes) are excluded from any security software scan. 

Cause

Qlik Sense repository.exe is no longer able to access to local computer personal certificate store, which prevents the service to start.

Related Content 

Complete list of event IDs for Endpoint Security
Malware Behavior: Windows EFS Abuse

Accessing and managing your Data Spaces varies depending on your active subscription.

Without an active Qlik Cloud Data Integration subscription:

Data Spaces cannot be managed from the Management Console or the Analytics Services hub. To manage your Data Spaces, use the Data Integration section.

Note: A professional license is required.

1. Click the main Qlik Cloud menu button next to your profile icon
2. Open Data Integration
   
   Note: If you cannot see Data Integration, add /qdi to your tenant URL. Example: https://TENANTNAME.REGION.qlikcloud.com/qdi
   
   
   

To add a new space:

1. Select the Getting started or Home tab
2. Click Add new
3. Click Create space
   
   
   

To edit a space:

1. While still in Data Integration select Data projects
2. Open the Spaces drop down
3. Select your space
   
   
   
   
4. Click Manage space
   
   

With an active Qlik Cloud Data Integration subscription:

You can manage your Data Spaces directly from the Management Console and through Qlik Data Integration.

See Managing data spaces for details on how to manage spaces using the Management Console. For steps on how to use Qlik Data Integrations, see the instructions above.

Environment

Qlik Cloud 

Related Content:

Users previously assigned a Basic User entitlement have unexpectedly been promoted to Full User entitlement. 

This is working as expected and will happen when a Basic User is granted any additional permissions. Source: Types of user entitlements.

An exception is the Collaboration Platform role, see Qlik Cloud Analytics: Assigning the Collaboration Platform User role to a Basic User does not promote it to full.

Resolution

To avoid users being promoted to Full Users, remove any assignment, both in single spaces and at a global level.

Spaces

Verify the users are not assigned any roles other than than Has restricted view. 

Be careful when using the Anyone group, since assigning any other role to this group will promote all users to Full.

This includes the default data space: Default_Data_Space created on tenant setup. Remove the Anyone member:

1. Go to Spaces
2. Click the ellipses menu (...) and choose Manage members
3. Remove Anyone by through the ellipses menu (...) and clicking Remove
   
   
   

Global

Turn off Auto assign for all Security roles in the Administration Center.

1. Open the Administration Center
2. Open Users
3. Switch to the Permissions tab
4. Switch Auto assign to Off on all Security roles:
   
   

Specific users

If a user was manually assigned a role, the role has to be removed again manually.

1. Open the Administration Center
2. Open Users
3. Switch All Users tab if not already selected
4. Locate the user and click the ... menu (a), then choose Edit roles (b) and remove all previously assigned roles
   
   

Environment

• Qlik Cloud Analytics