Importing a Qlik Sense App (.qvf) in the Qlik Sense Management Console fails. There are various causes for this issue and this article will help in identifying the most common root causes. 

In the process of importing an App one must access the Sense QMC, Start-> Apps -> Import 
 - Select a QVF (App) to import using the Browse, and select <Import>.

This process will result in one of the following:

• The import fails with Failed to import app. Please check the log file.
• Or the Process remains at the Import stage until aborted. 

Resolution:

What does the log file say?

Review the log file for more detailed errors to assist in further troubleshooting.  For basic log file information, see Logging Storage.

Locate the logs in the following locations:

C:\ProgramData\Qlik\Sense\Log\Repository\Trace\SERVERNAME_System_Repository.txt
C:\ProgramData\Qlik\Sense\Log\Engine\trace\SERVERNAME_System_Engine.txt
 

Note: If you are running a multi node environment, each node will have its own local copy. Review all of them. In addition, if the logs have been archived since the issue occurred, review the location of the archived log, which by default is in the configured Service Cluster location. 

Service Account permissions 

Verify that the account running the Qlik Sense Services has the correct permissions: It requires Read/Write permissions.

• To locate your Apps folder, open the QMC: https://<QPS server name>/qmc
• Select Service cluster on the QMC start page to display the service cluster page.
• This will list your App folder.
• To verify permissions, navigate to the App folder share location in a Windows Explorer.
• Right-click the folder and verify both Sharing and Security for the service account permissions.

Disk space

In the case of large Apps, verify that enough disk space is available. Check the available space on the central node's C:\ disk. Even if Sense is installed on another drive, C:\ (and its temporary folder) will be used for the calculation.

At least 2 times the App size need to be available for the import to succeed. 

Example: If the app is 8 GB then a minimum of 16 GB free disk space is required to Import the app.

Related content:

Qlik Sense shows error when importing an app - log files read "request entity too large"
Cannot import App (qvf) to the QMC "Failed to import app. Please check the log file"
Import of apps in Qlik Sense failed when FIPS is enabled
 

All users with the Automation Creator role can create automations. 

To add or remove the Automations Creator role:

1. Open the Qlik Cloud Management Console
2. Navigate to Users and select the User you wish to modify
3. Check or uncheck the Automations Creator role

Automations at large can be enabled or disabled as a feature in Qlik Cloud. See Managing automations for more information on how to manage automations.

Also see a related video posted on Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly  

This option is available in Qlik Sense June 2018 Patch 1 and later releases.   

Description of related problem:

Getting errors "Connection to the Qlik Sense engine failed for unspecified reasons. Refresh your browser or contact our system administrator" for external users on other browsers except for IE when they open the Qlik sense app and leave it inactive until it exceeds the Firewall session idle timeout. This is followed by a connection reset for the TCP WebSocket session.

For Qlik Sense Enterprise for Business (Cloud), see Loading of an app is hanging when using QlikSense Cloud.

 Cause:

TCP WebSocket connection is terminated by the firewall because the firewall is not receiving any TCP traffic such as keep-alive packets from client browser (e.g. Firefox, older Chrome versions).  Specific web browsers have their own tcp keep-alive behavior. 

This issue may be found with less frequency with IE because it sends the TCP Websocket keep-alive more frequent than any other main stream browser. Here are the default intervals for the three main browsers latest releases as of September 2020:

Default TCP-Keep-Alive intervals:

• Chrome: 45 sec
• Edge: 45 sec
• Internet Explorer: 30 sec (see IE: Change Keep-Alive timeout)
• FireFox 81.0: 10sec for ~2 minutes (115sec) period, then a keep-alive packet every 10 minutes; More details under Mozilla Networking Preferences.

General info

This functionality is by default switched off not to affect any existing customers. Customers who do not experience any issues with web sockets terminated by the network due to inactive SHOULD NOT switch this feature ON since it will send unnecessary traffic on the network. See How are WebSockets used in QlikSense ? for more information.

How to configure?

1. Stop the Qlik Sense Proxy Service
2. Edit the file C:\Program Files\Qlik\Sense\Proxy\Proxy.exe.config This location may not be available if Qlik Sense was not installed in the default location.
3. Add the configuration key:
   

   <add key="WebSocketPingInterval" value="0"/>   <!-- Interval in seconds for the web socket ping to the client (a value of "0" is disabling the ping)–>

   Where value is a suitable positive number depending on the inactive web socket timeout setting in the network. The effective interval that the Qlik Sense Proxy server will send keep-alive messages towards the client my oscillate between 2 x value and 1 x value, since it also takes into account backend inter-process socket activity. Eg: setting the value of WebSocketPingInterval to 30 may lead to keep-alive messages sent to the client every 30 or 60 seconds.
   
   Note: The Qlik Sense Proxy service may not send keep-alive packets if it detects activity on that client's Websocket tcp session.
   
   Recommended is 60-300 second range, shorter interval generates more load on Proxy CPU and network. It should be set as high as possible, meaning it's best to identify at which interval an intermediate proxy cuts the connection when it perceives it as idle, and then set the ping interval to a slightly smaller value.
   
   A too small number (e.g. less than 30) will load the proxy and the network and IS NOT recommended. Suitable numbers could be 60 to 300 (i.e. 1 minute to 5 minutes), but it all depends on the network configuration (if the network removes web sockets that have been inactive for more than 5 minutes then, of course, the value must be set something less than 5 minutes (i.e. less than 300)). If a lower value is required, it is recommended to investigate the components involved in the connection, such as third party proxies and network load balancers to configure them with less restrictive timeouts. 
   
   

         It is possible that the same WebSocketPingInterval value has different behaviors in each Qlik Sense Hub                    section due to various network device. The value may keep the connection live in Dashboard but still lose                  connection in Data Load Editor. You may test with a lower  WebSocketPingInterval value until the proper                      value is found to keep connection in all sections. For example, when connecting CloudFlare as web                                application firewall, the WebSocketPingInterval value may need to set to 10 seconds otherwise "connection              lost" may still be received in Data Load Editor even the rest of Qlik Sense Hub keeps connected. 

          4. Restart the Qlik Sense Proxy Service.

Related content:

• Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly  
• How are WebSockets used in QlikSense ?
• Loading of an app is hanging when using QlikSense Cloud
• Browser Timeout
• Qlik Sense HUB timeout even with session timeouts configured correctly
• Increase session timeout in QlikSense

Setting sensitivity in Qlik Catalog allows you to mark certain fields as sensitive, indicating that they require extra care to maintain security and privacy.

When exporting data, the chosen obfuscation method is automatically applied to sensitive fields to ensure confidentiality. Users are prompted to select the obfuscation method during the export process.

In more detail, administrators can configure sensitivity settings for individual fields, deciding which ones should be considered sensitive. Sensitivity enforcement applies obfuscation to sensitive fields upon export, hiding or transforming the data. Administrators can choose from different obfuscation methods like CharClassObfuscator, DigestObfuscator, NumericObfuscator, ConstantValueObfuscator, and DictionaryObfuscator.

Each method has its own way of transforming or masking the data. By selecting a specific obfuscation rule for sensitive fields, administrators can control how the data will be transformed when exported.

Examples of obfuscation methods include replacing digits and letters, converting values into hash codes, modifying numeric values, returning constant values, or mapping data to different values using a dictionary.

Overall, Qlik Catalog provides a way to manage sensitivity and apply obfuscation methods to protect sensitive data when published, ensuring that it remains secure and confidential.

To use the sensitivity feature for source fields:

1. Navigate to the source, entity and then the field
2. Click Edit (pencil icon)
   
   
   
   
3. Enable Sensitive and choose the obfuscation method
   
   
   
4. Follow the same steps to configure sensitivity for other fields as necessary
5. Shop for the entity and publish to a location of choice
   
   

Note: 

The sensitivity feature for fields only applies when you publish to a target location using the Publish option in Catalog.

Environment

Qlik Catalog

After upgrading QlikView to May 2023 IR, charts may show as blank objects in Qlik NPrinting.

Qlik NPrinting Designer displays the images correctly in preview mode.

Environment

Qlik NPrinting Any version
QlikView May 2023 IR
Nprinting Reports: Excel, PowerPoint, PDF

Resolution

This is currently being investigated.

The issue is found to be with QlikView May 2023 IR not with any Qlik NPrinting versions. It works perfectly fine with QlikView May 2022 SR2 and earlier supported QlikView versions.

Also, the problem occurs when Qlik View Server Connection is used in Qlik NPrinting connections.

Workaround:

Internal Investigation ID(s)

QV-24977

Information on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes with the ID QV-24977 for reference.

Attempting to start the Data Movement server on Linux (service repagent start) fails with the following error:

Failed to start service

Symptom

One of following  error messages can be seen in the repsrv.log file in such scenarios.

Failed to write file

Failed to write entire file

Resolution

The root cause is likely a lack of storage. See the Data Movement system requirements for details: Recommended hardware. Either free up storage by removing unnecessary files or directories, or increase the available capacity. 

To verify current capacity run df -h from the root ( / ) directory.

To review which directories take up the most space run the following from root:

sudo du -h --max-depth=1 | sort -rh

To find files larger than 100MB which may clutter the storage, run: 

sudo find / -type f -size +100M -exec ls -lh {} \;

Cause

Directory has reached 100% capacity and has consumed all of the storage that was available.

Environment:

Qlik Data Movement

Opening the Qlik Enterprise Manager Analytics tab fails with the following error:

SYS-E-JSERVNAVAIL, Java service 'AnalyticsCtlClient' not yet available 
SYS,JAVA_SERVICE_NOT_AVAILABLE,AnalyticsCtlClient(statusCode: 500

Reviewing the service log files indicates:

Failed to start jetty server. Failed to bind to /127.0.0.1:3102

Resolution

After upgrading to QlikView 12.70 SR2 users cannot open documents from the AccessPoint once the session timeout is reached. The following error is displayed:

Failed to open document, You don't have access to this document

Environment

QlikView May 2022 (12.70) IR to SR2
QlikView May 2023 (12.80) IR

Resolution

This is caused by QV-24743 and QV-24830.

Fix Version

Fix scheduled to be released in:

• QlikView 12.80 SR1
• QlikView 12.70 SR3

Upgrade to the appropriate version when it has become available. Refer to the QlikView Release Notes for details once the versions have been released.

Internal Investigation ID(s) 

QV-24743 and QV-24830

Introduction

In this article, we will outline steps listed in the user guide with the addition of screenshots for Windows installations for replacing self-signed certificates.  We take these steps to ensure a secure connection to Replicate. 

Steps 

1. Stop the Replicate UI and Server services

2.  As administrator, from the following location, C:\Program Files\Qlik\Replicate\bin, run

RepUiCtl.exe certificate clean

3. Create a new private key file (note this will be generated in the current working directory):

openssl genpkey -algorithm RSA -out private.key -outform PEM

4.  Create the cert.crt file based on the private key file created earlier:

openssl req -new -addext "subjectAltName = DNS:SSL-TEST.exampledomain.com" -key private.key -x509 -days 365 -out cert.crt

5.  Create the cert.pfx file based on previous info:

openssl pkcs12 -export -certpbe PBE-SHA1-3DES -keypbe PBE-SHA1-3DES -nomac -inkey private.key -in cert.crt -out cert.pfx

6.  Import the newly created certificate, by double clicking on the cert.pfx file generated in previous step. This will open the 'Certificate Import Wizard.'

Select, 'Local Machine' and click next.

7.  Specify the cert.pfx file you want to import. Click 'Next' and then enter the password from step #3. 

8. Select 'Automatically select the certificate store based on the type of certificate', then click 'Finish'.

9. Open up Windows MMC for Certificates on Local Computer. 

10. Place the newly imported certificate in the 'Trusted Certificates' folder

11.  Run the command to delete anything current

netsh http del sslcert ipport=0.0.0.0:443

12. Double click on the certificate in trusted certs folder to find the certificate thumbprint under the details tab

13. Use this thumbprint in the certhash of following command:

netsh http add sslcert ipport=0.0.0.0:443 certhash=b26fae671d12ab9afcc82cd93321f7e00dc300d6 appid={4dc3e181-e14b-4a21-b022-59fc669b0914}

Restart the services and check if you have the lock icon on your Replicate URL. 

Note: For chrome, you may need to also add the certificate to chrome://settings/security -> 'Manage device certificates' -> Trusted Root Certificate Authorities. 

Environment

• Qlik Replicate 

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.

The following error can occur when using SAP BW Connector to extract data from InfoProvider/CompositeProvider.
--------
[ERR] [QVX] RfcAbapException:JOB_CANCELLED
Job aborted, check log for Job /QTQVC/READ_MPDATA in Job Overview (transaction SM37)
---------

Environment

• Qlik SAP Connector

Resolution

Reported bug QB-18952 was closed by R&D as WAD(working as designed) .

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

Workaround

From the SAP System,

1. Go to transaction SE37 and execute function module /QTQVC/GET_METADATA. 
2. Check the concerned INFOPROVIDER

The allowed maximum width  is 8192 characters.

From the INFOPROVIDER, if the field is of, for example 15282 characters wide, a simple workaround would be to split the extraction into two or more extractions. Then in Qlik Sense or QlikView, depending on your data model, use JOIN / CONCATENATE.

Cause

Product Defect ID: QB-18952

The native Qlik PostgreSql connector (ODBC package) does not import strings with more of 255 characters. Such strings are just cut off, the following characters are not shown in the applications. No warnings are thrown during the script execution.

The problem affects the Qlik connector but not all the DNS drivers.

Environment

Qlik Sense February 2023 and higher versions
Qlik Cloud

Resolution

When setting up the PostgreSQL connection, set the parameter TextAsLongVarchar  with value 1 in the connector Advanced settings.

When TextAsLongVarchar is set, and the Max String Length is set to 4096, 4096 characters are loaded. 

Notice that there still are limitations to this functionality related to the datatype used in the database. Data types like text[] are currently not supported by Simba and they are affected by the 255 characters limitation even when the TextAsLongVarchar parameter is applied.

Qlik has opened an improvement request to Simba to support them.

As workaround, it is possible to test a custom connector using a DSN driver to deal with these data types.

Internal Investigation ID

QB-21497

Qlik Replicate can read SQL Server backup transaction logs stored in Rubrik.

The setup requires the Rubik administration team to use the attached script and to modify it accordingly to guarantee compatibility with your deployment.

This script is provided as is. Qlik Support cannot provide continued support or maintenance of the solution. For assistance, contact our Professional Services.

Environment

Qlik Replicate 

Creating a subscription based on a visualization or a sheet in Qlik Cloud, the following error is displayed: 

An SMTP server must be configured if you want to receive subscription emails. Please contact an administrator

Verifying the subscription in the Management Console shows:

There was a problem sending your email. please review your settings.

Resolution

• Verify if the email password is correct or if it has expired
• Verify your internal or 3rd Party SMTP Server connection configuration

Related Content

Creating a subscription | Qlik Cloud Help 

Environment

Qlik Cloud 

Sometimes it might be necessary to deallocate licenses using the Qlik Command Line Interface, for instance in case of licenses allocated to users no longer in the system.

Environment

• Qlik Cloud 

Resolution

1. Download and configure the Qlik-cli 
   
   
2. run "qlik license assignment ls" in the Powershell  or UNIX shell to see currently assigned licenses. You will get something like this:
   
   

   [                     
     {
       "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"
     },
   ]
   ​

    

3. identify any user that should not have a license assigned. There is a higher probability that you'll find them among the users who have no "name:" and "userid:" fields
   
   
4. for each of this user contruct the string
   
   

   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"}]'
   
   For instance, in the case of the final user in the list above it will be  '[{"subject":"22232425","type":"analyzer"}]'
   
   
   

5.  feed the string into this command:

   qlik license assignment delete --delete STRING
   
   With the example above you will run:
   qlik license assignment delete --delete '[{"subject":"22232425","type":"analyzer"}]'
   
   

6. Run the command and wait for the result.
   A "200" will confirm that the removal worked
   
   
   

   % qlik license assignment delete --delete '[{"subject":"22232425","type":"analyzer"}]'
   [                    
     {
       "status": 200,
       "subject": "22232425",
       "type": "analyzer"
     }
   ]
   

    

7. Check the "Home" section of the management console to confirm that the allocation was removed

    

Related Content

If Oracle is configured with a Physical Standby, and the Oracle LOG_ARCHIVE_DEST_n initialization parameter is configured with the DELAY option, running a Full Load and Apply Changes task on an Oracle Physical Standby instance may result in missing or erroneous data in the target database.

The following warning may be thrown in the log files: 

Using standby database could have caused the missing events problem during Full Load and CDC synchronization.

If you do not have the DELAY parameter configured and there is no data loss, this warning message can be ignored. Please check with your DBA if the DELAY parameter is set.

Resolution:

This issue can be resolved using an internal parameter: standbyDelayTime, which should be set to a value little bit bigger than the Delay parameter of LOG_ARCHIVE_DEST_n initialization parameter. Units are in minutes.

For information on how to set internal parameters, see Qlik Replicate: How to set Internal Parameters and what are they for?

This solution may lead to redundant records for a table without PK/UI if there were INSERT operations during that period. Example - LOG_ARCHIVE_DEST_2 = 'DELAY=10'

Environment

Qlik Replicate

Related Content:

Supported standby configurations | Qlik Replicate Help

Reloading the Qlik Sense Connector in Qlik Lineage Connector Client Managed may fail with:

Connector of type 'QlikSense' not included in license. Canceling execution

You will also see an "Invalid License" error on the Cloud link.

Resolution

1. Verify that you have a valid License in Qlik Cloud
2. Verify if the API key is expired or deleted in Qlik Cloud (Extracting lineage data with Qlik Lineage Connectors)

Environment

#Qlik Lineage Connector

It may be necessary to remove line feeds (LF) and carriage returns (CR) from BLOB or CLOB datatype fields. However, Qlik Replicate tasks have a limitation on LOB fields preventing functions from being used on them.

Workaround:

Use a source lookup to retrieve the field value, bypassing the inherent data type.

The general form of the function is as follows:

source_lookup(TTL,'SCHM','TBL','EXP','COND',COND_PARAMS)

Use of the standard replace chars function:

replaceChars(X,Y,Z)

Combined usage for both functions for the transformation expression:

ReplaceChars(source_lookup(1,'DBO','table','field','id=?',$id),X'0A','|')

Related Content

Qlik Replicate Transformation: Source Lookup - CLOB datatype - limitations on string functions
Data Enrichment functions 

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.

SAML is not supported by default in QlikView but can be implemented by creating a custom authentication module that will convert SAML requests/responses to QlikView Ticket to log the user in.

This customization is provided as is. Qlik Support cannot provide continued support of the solution. For assistance, contact our Professional Services or engage in our QlikView Integrations forum.

Currently, this solution only works for SP initiated authentication. Making it work for IDP-initiated authentication might require further code changes in the library/module source code.

This has been tested with QlikView 12.10 SR7.

Requirements:

• IIS installed with asp .net development language
• .NET framework 4.0
• Copy and unzip qvsaml.zip in the root of your IIS website. Make sure to edit the bindings of your website and set up https.

Configuration on the QlikView side:

1. Edit the file C:\ProgramData\QlikTech\WebServer\config.xml to include the IP address of the machine where the authentication module is hosted.
   
   You will need to change the line:
   

   <GetWebTicket url="/QvAjaxZfc/GetWebTicket.aspx"/>​

   to
   

   <GetWebTicket url="/QvAjaxZfc/GetWebTicket.aspx">
   	<TrustedIP>fe80::b178:730a:5c2a:86d2%11</TrustedIP>
       </GetWebTicket>​

    

2. If you are unsure if the request is sent over IPv4 or IPv6, you can just use: ping servername in a command prompt and see which IP address is returned.

Configuration of the authentication module:

1. Copy your authentication module code in your IIS site folder. The site needs to be run over HTTPS.
   
   The sample is built using "CodeBehind" so you will need to compile the source code and place the compiled binary in the bin folder for the sample to work.
   
   A compiled version "QlikViewSamlAuthentication.dll" is provided as is.
   
   The sample also uses the third party library OIOSAML.NET (version 2.0.1):  https://www.digitaliser.dk/resource/3868871
   
   A compiled version that works with OneLogin (dk.nita.saml20.dll) is provided as is.
   
   If you choose to compile the source code yourself for use with OneLogin, you will need to comment out the statement to check that the name is an URI as this attribute is an email address in OneLogin:
   
   File: DKSaml20AttributeValidator.cs 
   
   
2. Before:
   

   public void ValidateAttribute(SamlAttribute samlAttribute)
           {     
   
               if (!Uri.IsWellFormedUriString(samlAttribute.Name, UriKind.Absolute))
                   throw new DKSaml20FormatException("The DK-SAML 2.0 profile requires that an attribute's \"Name\" is an URI.");​

   after

   public void ValidateAttribute(SamlAttribute samlAttribute)
           {     
               /*
               if (!Uri.IsWellFormedUriString(samlAttribute.Name, UriKind.Absolute))
                   throw new DKSaml20FormatException("The DK-SAML 2.0 profile requires that an attribute's \"Name\" is an URI.");
                   */

3.  Settings for QlikView in the module web.config:
   

   <QlikViewSaml
       accessPointUrl="https://qlikserver1.domain.local/"
       authenticatePage="QvAjaxZfc/Authenticate.aspx"
       webTicketPage="QvAjaxZfc/GetWebTicket.aspx"
       tryPage="https://qlikserver1.domain.local/qlikview/"
       backUrl="https://qlikserver1.domain.local/webticketerror.html" />

   Replace https://qlikserver1.domain.local/ by your qlikview server URL in the above code.
4. Settings for the Audience:
   

   <AllowedAudienceUris>
         <Audience>https://qlikserver1.domain.local</Audience>
       </AllowedAudienceUris>​

   
   *It must exactly match the setting you have in Onelogin.
   
   
5. Settings for the certificate used to sign the SAML request:
   

   <Federation xmlns="urn:dk.nita.saml20.configuration">
       <SigningCertificate findValue="CN=qlikserver1" storeLocation="LocalMachine" storeName="My" x509FindType="FindBySubjectDistinguishedName"/>

   *In this case, we use a certificate that has "CN=qlikserver1" as its distinguished name.
   *You need to install the certificate in Windows first. It must have a private key.
   
   
6. Settings for the folder for the IDP metadata:
   

   <IDPEndPoints metadata="C:\idpdata\">
   ...​

   
   *In this example, the folder is C:\idpdata, once Onelogin is set up, download the metadata from Onelogin and copy it in this folder.

Configuration of OneLogin

1. Create a new company app using the template "SAML Test Connector (IdP w/attr)". Below, you can find the settings used in this example:
   
   
   
   
2. Make sure that the audience set here matches what you have in the web.config of the module
3. In saml_login.aspx (file that handles the SAML request in the module), make sure the URL is correct.
   
   
   
   
   Other tabs are left at default values.

Test the solution and log in:

1. Open the URL of your module (In this case, the module is hosted in IIS on the same server as QlikView):
   
   
   
   
2. Click on "Go to QlikView" and you should get to the Onelogin login page:
   
   
   
   
3. Once you're logged in, you should be redirected to the Access point, notice your user name in the upper right corner:
   
   

Qlik Sense or QlikView may not load all data from a CSV file.

Resolution

Sometimes a special character is used to mark the end of the file. If this character is found in the middle of a text file (for example, enclosed by quotation marks), the file may not load correctly. In this instance, we can modify how Qlik Sense and QlikView read data. 

Qlik Sense:

1. Select the .csv file you want to load in the File Wizard
2. Set Quoting to None 
3. Check Ignore End-Of-File character? 
   
   
   

QlikView

1. Select the .csv file you want to load in the File Wizard
2. Set Quoting to None 
3. Check Ignore EOF
   
    

Cause

Due to a problem with quotes or special characters in the file. See Help Site File Wizard: Type

Environment

Qlik Sense all supported versions, including Qlik Cloud
QlikView all supported versions

Previewing Qlik NPrinting report templates in the Qlik NPrinting Designer leads to the error:

An error occurred while elaborating the entity tags.
Please check if the entities are properly placed inside their level tags.
Error message:
TemplateEntities list does not contain this column
Parameter name: templateEntities

Environment

Qlik NPrinting Designer May 2023 IR, May 2023 SR 1

Resolution

Upgrade to Qlik NPrinting May 2023 SR 2.

Information on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes with the ID OP-95892 for reference.

Workaround:

Replace the current Qlik.Reporting.Adapters.dll file in C:\Program Files (x86)\NPrinting\Designer\libs.

For this workaround to function, the installed Qlik NPrinting designer version must be May 2023 SR1.

1. Take a backup of the current Qlik.Reporting.Adapters.dll file
2. Download the attached Qlik.Reporting.Adapters.zip file
3. Extract the .dll.
4. Replace the Qlik.Reporting.Adapters.dll file

Upgrade to May 2023 SR2 when released.

Fix Version:

Qlik NPrinting May 2023 SR 2

Cause

OP-95892