Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
It is possible to export the list of tenatnt users to a .json file using the "user ls" command from the Qlik Command Line Interface (qlik-cli).
The scripts provided in this article are provided as they are and they are for guidance only.
As a tenant admin, download and configure the Qlik-cli
qlik user ls --limit 1000 > tenantusers.json
[
{
"assignedGroups": [],
"assignedRoles": [
{
"id": "608050f7634644db3678b1a2",
"level": "user",
"name": "Developer",
"type": "default"
},
{
"id": "608050f7634644db3678b17f",
"level": "admin",
"name": "TenantAdmin",
"type": "default"
},
{
"id": "605a1c2151382ffc836af862",
"level": "user",
"name": "SharedSpaceCreator",
"type": "default"
},
{
"id": "605a1c2151382ffc836af866",
"level": "user",
"name": "ManagedSpaceCreator",
"type": "default"
},
{
"id": "605a1c2151382ffc836af86b",
"level": "user",
"name": "DataSpaceCreator",
"type": "default"
},
{
"id": "605a1c2151382ffc836af85d",
"level": "admin",
"name": "AnalyticsAdmin",
"type": "default"
},
{
"id": "605a1c2151382ffc836af85f",
"level": "admin",
"name": "DataAdmin",
"type": "default"
},
{
"id": "63580b8d5cf9728f19217be0",
"level": "user",
"name": "PrivateAnalyticsContentCreator",
"type": "default"
},
{
"id": "6356f0425cf9728f1962b942",
"level": "user",
"name": "DataServicesContributor",
"type": "default"
}
],
"created": "2020-05-18T09:38:29.214Z",
"createdAt": "2020-05-18T09:38:29.214Z",
"email": "martina.testoni@dkdaklaldkdaklladaaddddl.com",
"id": "USERID1",
"lastUpdated": "2023-04-04T07:32:00.756Z",
"lastUpdatedAt": "2023-04-04T07:32:00.756Z",
"name": "Martina Testoni",
"picture": "https://s.gravatar.com/avatar/gravatarimage=pg\u0026d=https%3A%2F%2Fcdn.auth0.com%2Favatars%2Fdp.png",
"preferredLocale": "",
"preferredZoneinfo": "Europe/Copenhagen",
"roles": [
"Developer",
"TenantAdmin",
"SharedSpaceCreator",
"ManagedSpaceCreator",
"DataSpaceCreator",
"AnalyticsAdmin",
"DataAdmin",
"PrivateAnalyticsContentCreator",
"DataServicesContributor"
],
"status": "active",
"subject": "auth0|SUBJECTID2",
"tenantId": "TENANTID"
},
{
"assignedGroups": [],
"assignedRoles": [
{
"id": "608050f7634644db3678b17f",
"level": "admin",
"name": "TenantAdmin",
"type": "default"
},
{
"id": "605a1c2151382ffc836af86b",
"level": "user",
"name": "DataSpaceCreator",
"type": "default"
},
{
"id": "608050f7634644db3678b1a2",
"level": "user",
"name": "Developer",
"type": "default"
},
{
"id": "605a1c2151382ffc836af866",
"level": "user",
"name": "ManagedSpaceCreator",
"type": "default"
},
{
"id": "63580b8d5cf9728f19217be0",
"level": "user",
"name": "PrivateAnalyticsContentCreator",
"type": "default"
},
{
"id": "605a1c2151382ffc836af862",
"level": "user",
"name": "SharedSpaceCreator",
"type": "default"
},
{
"id": "6356f0425cf9728f1962b95c",
"level": "user",
"name": "Steward",
"type": "default"
},
{
"id": "605a1c2151382ffc836af85d",
"level": "admin",
"name": "AnalyticsAdmin",
"type": "default"
},
{
"id": "62bb165356d1879582c1b468",
"level": "admin",
"name": "AuditAdmin",
"type": "default"
},
{
"id": "605a1c2151382ffc836af85f",
"level": "admin",
"name": "DataAdmin",
"type": "default"
}
],
"created": "2023-03-31T08:44:37.332Z",
"createdAt": "2023-03-31T08:44:37.332Z",
"email": "Gentile.Faccenda@dkdaklaldkdaklladaaddddl.com",
"id": "USERID2",
"lastUpdated": "2023-04-03T11:24:35.037Z",
"lastUpdatedAt": "2023-04-03T11:24:35.037Z",
"name": "Gentile Faccenda",
"picture": "https://s.gravatar.com/avatar/randomurl=https%3A%2F%2Fcdn.auth0.com%2Favatars%2Fdp.png",
"roles": [
"TenantAdmin",
"DataSpaceCreator",
"Developer",
"ManagedSpaceCreator",
"PrivateAnalyticsContentCreator",
"SharedSpaceCreator",
"Steward",
"AnalyticsAdmin",
"AuditAdmin",
"DataAdmin"
],
"status": "active",
"subject": "auth0|IDPSUBJECT2",
"tenantId": "TENANTID"
}
]
qlik user ls --limit 1000 | ConvertFrom-Json | ConvertTo-Csv > tenantusers.csv
This article shows you how to locate your Qlik Cloud license number (Subscription ID) as well as your Tenant Hostname, your Tenant ID, and your Recovery Address.
Only the Tenant Admin can see the Qlik Cloud Subscription ID and Tenant Hostname / ID.
If you are looking to change your Tenant Alias or Display name, see Assigning a hostname Alias to a Qlik Cloud Tenant and changing the Display Name.
Qlik NPrinting and Qlik Sense are installed on Azure cloud machines. The configuration respects all the requirements. in particular, the NPrinting Engine user is present on both the NPrinting and Sense servers with the same domain and SSID.
The Metadata reload test fails with a "Not a domain user" message. On the other side, the Metadata reload is successful when launched (ignoring the Test error) even if the NPrinting Engine logs show these error and warning messages:
Engine.Navigator.QlikSense.SDK.QlikSenseDiagnose 20231128T103337.642+01:00 ERROR NP-SERVER _NAME 0 0 0 0 0 0 0 0 PerformDiagnosis found a problem. ERROR: System.Exception: Not a domain User : Domain\NPUser↓↓ at Engine.Navigator.QlikSense.SDK.QlikSenseDiagnose.<>c__DisplayClass8_0.<PerformDiagnosis>b__3() in C:\Jws\release-may2023-SwCB9Sd4b\server\NPrinting\src\Engine.Navigator.QlikSense.SDK\QlikSenseDiagnose.cs:line 90↓↓ at Engine.Navigator.QlikSense.SDK.QlikSenseDiagnose.GetStep(DiagnoseStep step, Action stepCode) in C:\Jws\release-may2023-SwCB9Sd4b\server\NPrinting\src\Engine.Navigator.QlikSense.SDK\QlikSenseDiagnose.cs:line 40
Engine.Navigator.QlikSense.SDK 23.20.5.0 Engine.Navigator.QlikSense.SDK.QRSApi
20231128T103350.840+01:00 WARN NP-SERVER _NAME 0 0 0 0 0 0 0 0 Domain user check failed for Domain\NPUser. ERROR: System.Runtime.InteropServices.COMException (0x8007200A): The specified directory service attribute or value does not exist.↓↓↓↓ at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)↓↓ at System.DirectoryServices.DirectoryEntry.Bind()↓↓ at System.DirectoryServices.DirectoryEntry.get_SchemaEntry()↓↓
Ignore the error message and proceed with the metadata reload.
According to the current analysis, the error message is shown because Azure does not organize users and permissions as on-premise Windows servers do. NPrinting does not receive the expected answers from Azure AD Connect and interprets this as missing access levels in Azure during the connection tests.
On the other side, when the environment is correctly configured, the NPrinting Engine user has access to the Qlik Sense applications, so the metadata reload and the tasks executions are completed successfully at the end.
You can change or reset the password of your Qlik Account on either Qlik.com or MyQlik.
Choose your option:
Related Article: How to Register for a Qlik Account
If at any point you do not receive a password or an email, see No Activation or Password Reset Email arrives or contact our support representatives.
Below error will appear when you execute the "Bootstrap" command to generate/regenerate the Certificates while you are migrating or upgrading the Qlik Sense Environment,
[ERROR] Fatal exception during bootstrap: There is no RSA private key associated with this certificate
Note: Please take assistance from your Admin/IT Team if you are not aware of the Certificates issued to your Qlik Sense site.
Tip:
After regenerating the certificates, if your UDC and Data Connections are failing, you must re-enter the passwords to all data connections and UDCs, since those encrypted passwords have a hash reference back to those certificates, once you remove the Certificates and create new ones, that reference gets broken, a new hash needs to in place, and to do so, you must re-enter the password.
[ERROR] Fatal exception during bootstrap: Keyset does not exist
Creating 40 permanent worker threads for connection handler
Qlik Sense works normally, but a huge quantity Repository logs is generated. These following messages are continuously repeated (not necessarily both of them are present).
In System logs:
INFO SERVERNODE System.Repository.Repository.Core.Repository.Common.ModelRepository`1[[Repository.Domain.Model.UserDirectorySettings, Repository.Domain, Version=xx.xx.x.0, Culture=neutral, PublicKeyToken=...]]
..... Database object has newer timestamp than object being modified; ....
.... ERROR SERVERNODE System.Repository.Repository.Core.Repository.Common.TransactionUtility
..... Error when committing
In User Management logs:
WARN SERVERNODE UserManagement.Repository.Repository.Users.SyncUsersWorker ........
Conflict when trying to do database operation; retrying... at Repository.Core.Repository.Common.AbstractModelRepository.CheckConflicts(IRepositoryObject persistedItem, DateTime itemModifiedDate)↵
The quantity of messages generated is very high and several GB of memory can be occupied in disk in few hours.
In order to avoid a complete filling of the disk, it is necessary to restart the node where the problem occurs. Generally, this resolves the issue.
To avoid this problem, we have introduced an improvement in the latest Qlik Sense releases that avoids potential conflicts. This improvement is present in Qlik Sense February 2021 Patch 6 and in Qlik Sense May 2021 SR1 or higher releases. An upgrade is recommended to ultimately fix the problem.
The problem is due to an incorrect synchronization between the Database and one of the nodes.
SHEND-509
Assigned Qlik Cloud licenses and entitlements can be deallocated using the Qlik Command Line Interface. This method is specifically useful when the user with the allocated entitlement or license is no longer visible in the system and can therefore not be configured in the Management Console.
[
{
"created": "2023-04-03T11:24:05.101Z",
"excess": false,
"name": “Enzo Bearzot”,
"subject": "auth0|12345678”,
"type": "professional",
"userId": “userid1”
},
{
"created": "2022-08-17T11:50:04.647Z",
"excess": false,
"name": “Vittorio Pozzo”,
"subject": "auth0|910111213”,
"type": “analyzer”,
"userId": “userid2”
},
{
"created": "2022-08-17T11:50:04.647Z",
"excess": false,
"name": “Ferruccio Valcareggi”,
"subject": "auth0|14151617”,
"type": "professional",
"userId": “userid3”
},
{
"created": "2022-06-07T11:36:15.704Z",
"excess": false,
"subject": “18192021”,
"type": “professional”
},
{
"created": "2022-06-03T13:50:14.105Z",
"excess": false,
"subject": “22232425”,
"type": "analyzer"
},
]
The syntax below is for Unix shells. For usage in Windows Powershell add a "backslash" before each "doublequote" sign. '[{"subject"... will have to become '[{\"subject\"...
'[{"subject":"USERSUBJECT","type":"ASSIGNEDLICENSE"}]'
Example: Using the last user in the list provided above, the string would be:
'[{"subject":"22232425","type":"analyzer"}]'
Feed the string into this command:
.\qlik.exe license assignment delete --delete STRING
With the example above you will run:
Example using the last user in the list above:
.\qlik.exe license assignment delete --delete '[{"subject":"22232425","type":"analyzer"}]'
Run the command and wait for the result.
A status returned as 200 will confirm the removal worked:
% qlik license assignment delete --delete '[{"subject":"22232425","type":"analyzer"}]'
[
{
"status": 200,
"subject": "22232425",
"type": "analyzer"
}
]
Verify the allocation was removed by navigating to the Qlik Cloud Management Console's Home section.
Multi-Factor Authentication (MFA) adds additional security for logging into Qlik Cloud Services. Qlik recommends enabling MFA on your Qlik account.
If the device used for MFA is bein replaced, or if MFA needs to be disabled temporarily, this can be achieved in your My Qlik Portal.
Not able to create a connection to Azure Blob Storage from Qlik Azure connector in Qlik Sense SaaS
Qlik Sense throws the below error while connecting to the "Azure Storage" Connector:
HttpStatusCode: Unauthorized, StatusCode: 401, StatusDescription: Server failed to authenticate the request.
A good walkthrough of configuring Azure Blob Storage for access by Qlik Cloud can be found here:
Configuring Azure Blob Storage in Qlik SaaS (Qlik Cloud Services, Qlik Sense Business)
Relevant resources:
How to Access My Qlik Portal
Managing Your Subscription in My Qlik
Please do the following before requesting the change:
Areas that are particularly sensitive when you remove a user:
When synchronizing Qlik Sense with Active Directory, you may encounter an error message saying "the User Directory Connector (UDC) is not configured, because the following error occurred: Setting up connection to LDAP root node failed. Check log file"
This often indicates a log on failure, i.e. the username and/or password is wrong.
A common cause for this is wrong username and/or password.
Every Qlik Cloud user is assigned a unique UserID. A tenant admin can locate the UserID in the Management Console.
How to quickly get a user's details in the Cloud Management Console?
When users try login for the first time via 3rd party Identity Provider, they see the error message below:
"{"errors":[{"title":"Multiple active users detected with the same e-mail, please contact your administrator","code":"LOGIN-12","status":"400"}],"traceId":"000000000000000081ed1151407942ba".
If some time has passed since the user was invited at the time Qlik ID was still in use, the following error may appear instead:
"{"errors":[{"title":"User invitation expired","code":"USER_INVITE_EXPIRED","status":"403"}],"traceId":"000000000000000081ed1151407942bc".
The user likely has a pending invite. We need to temporarily disable the identity provide affected and delete the user's pending invite. Invites only show up when no Identity Provider is active on the system. We will need to temporarily disable the current IDP. During that brief time, users won't be able to login, but users that are already in the system will be able to work.
You can use Qlik CLI to automate the process or to simply carry it out in a command line rather than in the Management Console.
To get started with Qlik CLI, see: qlik-cli | Qlik Developer Portal.
For information about the commands used, see:
qlik context | Qlik Developer Portal
user ls | Qlik Developer Portal
user rm | Qlik Developer Portal
The issue occurs to users who had received the invite to access the tenant via Qlik SSO or default identity provider Qlik ID and haven't actioned on the invite email. Once the invite is deleted, the issue will be resolved.
Your Qlik Account may be locked out after multiple consecutive (unsuccessful) login attempts.
The following message will be printed:
YOUR ACCOUNT HAS BEEN BLOCKED AFTER MULTIPLE CONSECUTIVE LOGIN ATTEMPTS.
When the account is blocked, you need to reset the password. Please follow the steps below.
If you are unable to access your account still, please contact Qlik Support.
Users can view all licenses by navigating between the Active and Expired tab.
Create a new Source Endpoint for Teradata but when trying to do a Test Connection you get the below error:
SYS-E-HTTPFAIL, No Teradata driver were found.
SYS,GENERAL_EXCEPTION,No Teradata driver were found
Qlik Replicate 2022.5
Qlik Replicate 2021.5
The Teradata ODBC Driver that was installed is 17.10 or 17.20 you will need to set the below internal parameter on the Teradata Source Endpoint under the Advanced Setting Internal Settings. You will need to set the driver to the ODBC Name as its shown in the 64 ODBC Manager for Windows.
64 ODBC Manager Teradata ODBC Driver Name: Teradata Database ODBC Driver 17.10
The Teradata Source Endpoint Change Processing internal parameters:
driver value Teradata Database ODBC Driver 17.10
driver value Teradata Database ODBC Driver 17.20
The cause is due to the default Teradata ODBC Driver you have installed as if this is not listed you could get this type of error trying to connect.
If the Endpoint is changed the Task should be Stopped and Resumed.
Replicate Target Endpoint Teradata Version 15 or higher ODBC requirements
Setting up Google OAuth (or another identity provider) may fail with:
Authorization Error
Error 400: redirect_uri_mismatch
Do not use the Alias Tenant URL for the callback URL. Use the original Tenant URL.
See Creating a new identity provider configuration.