Qlik Sense Troubleshooting – Frustrating Problems & their Solutions

Earlier, we have discussed Qlik Sense Collaboration. Today, we will see Qlik Sense Troubleshooting. So, we will discuss how to troubleshoot for problems that you may encounter during your course of work in Qlik Sense. In this article we will see how to troubleshoot issues related to loading data, creating visualizations, discovering, exporting, deployment, and administering.

So, let’s start Qlik Sense Troubleshooting.

Qlik Sense Troubleshooting

Qlik Sense Troubleshooting – Frustrating Problems & their Solutions

Stay updated with the latest technology trends while you're on the move - Join DataFlair's Telegram Channel

1. Qlik Sense Troubleshooting

i. Qlik Sense Troubleshooting in Loading Data

Discussed below are the problems and their proposed solutions for Qlik Sense Troubleshooting.

  • Data connection is disconnected after restarting the SQL Server?

Close the app or all the apps running at that time and restart the hub or Qlik Sense Desktop.

  • Synthetic key warning when loading data?

Synthetic keys generate when two tables have more than one field in common. Generation of a synthetic key considers bad because it indicates a bad data structure which might cause issues with handling data and conducting a proper analysis. There is no ideal solution to resolve this problem other than preventing the presence of more than one common field between tables.

  • Circular reference warning while loading data?

Circular references or looping happens when we connect one table to the other in more than one way. This causes a logically impaired data model which we can fix by renaming the common fields etc.

  • Unable to select data from an OLE DB connection?

Check the configuration details of the connection, it should be rightly configured or check if the connection string is correctly designed. Also, you may check if you are logging in with the correct details.

  • Unsupported non-ANSI character set?

Sometimes, the data files fetched using an OLE DB connection does not support the characters, does not encod in ANSI. To fix this problem, you must fetch data files via a folder connection as it will handle more character codes.

  • When a connector is not working?

A connector does no work i.e. it is unable to establish a data connection because the connector is not installed properly. Check whether the installed connector is correct or not. In case of a multi-node deployment, the connector must be installed on all the nodes. And, in some cases, the connector has to be made compatible for Qlik Sense for it to work.

Recommended Reading – Qlik Sense Data Model

  • Data does not load even after execution of the data script?

Sometimes even if the script executes without any error detection, the data does not load. To resolve this, activate the debug option and check for any missing semicolons at the end of statements.

  • Showing error for the invalid path?

A file path can return as invalid if it does not found in the system or if the name is bigger than 171 characters as Qlik Sense only supports file names up to 171 characters.

  • If a date field does not recognize as a date field?

If you load a date field in a table but it does not recognize or read as a date field by the system in the sheet view. Then, open the data manager and go to the edit option and edit that table. Change the field type to Date or Timestamp and specify a date-time format.

  • Are tables not showing in the data manager?

If the data manager does not show tables and their data, even if they are loaded into the script. Then go to the data manager and click on Load Data option. This will reload the table, complete the data profiling and preparation and then display the tables in the app.

  • Low disk space?

You might run out of disk space as all the loaded data caches in QVD files. To solve this problem, delete the folder which contains all the QVD files from the source, C:\Users\<username>\Documents\Qlik\Sense\Apps\DataPrepAppCache.

ii. Qlik Sense Troubleshooting in Creating Visualizations

  • Cannot find your fields in the assets panel?

Possibly because you are working in a published app where the publisher must have not allowed access to the fields.

  • Showing error message “The data contains invalid geometries that can not show on the map. Review your data for errors and try again.”?

The geometric data (probably from a KML file) you are using must not be in the correct format or have some errored and unsupported content. Check for the format and errors, correct them and reload the files.

  • Showing error message “The following locations could not be found: <locations>. Review the values in your data and try again.”?

Locations given by the users for use in maps are sometimes not found and shown probably because they are not spelled correctly, or the given location is not found in the Qlik Sense location database. To resolve this, check for any errors in the spellings, or add the coordinated of the location manually if it is not present in the QS database.

Have a look at Qlik Sense Capabilities

  • Showing error message “The following locations had more than one result: <locations>. Set a custom scope to clarify which locations to display.”?

If the location you enter resembles other locations and returns multiple results. Then, you can specify additional details for that particular location to set it apart from others. We call this as setting a scope for the location. Set the Scope for location option to Custom and add additional details like city, state, country etc.

iii. Qlik Sense Troubleshooting in Discovering

  • Does not produce results upon searching?

Possibly this is because the selections whose values you are searching for are locked. Unlock the selections and then search.

  • Showing error message “Incomplete visualization”?

Visualizations are not shown properly if you do not have access to some of the data fields. Request the app administrator to grant you access to the restricted data fields.

iv. Qlik Sense Troubleshooting in Exporting

  • Data cannot export completely?

You may have exceeded the file size limit. Make the file of the supported size and then export it.

  • Cannot export a visualization as an image?

Possibly because the visualization is too large in size to export. The permitted size is 2000 by 2000 pixels. If your image size exceeds this, then resize the image and try to export it again.

Recommended Reading – Qlik Sense Text and Image Visualizations

  • Having blank spaces in place of specific language characters?

Sometimes the characters of the languages like Japanese, Korean, Simplified Chinese, or Traditional Chinese doesn’t support in the fonts of stories. So, if you want to display these fonts of different languages, then you have to download the fonts and then export the PDFs.

  • Data view table changing back to visualization after exporting?

This is because the data view does not support exporting. You can select the Export data option to export the data from each visualization instead.

  • The table does not show the Total field after exporting?

Possibly because only the original fields retain after exporting and so, you have to recreate the calculated Total field again.

v. Qlik Sense Troubleshooting in Deployment

To troubleshoot the issues related to deployment, you must follow a procedure, in order to detect the issue properly. You can either solve the issue by yourself, using the log files or you can call in for professional help. To detect the problem at first, try to figure out things like What kind of a problem is it? Is it a configuration problem, a component problem or a global issue? are there any error messages? Did the system behave abnormally? In which component did the issue is occurring?

After finding answers of these questions, look for the log file respective of the component (engine, repository, proxy, and scheduler) in which the problem occurs. Then, compare the details of a normal log file with the details of the log file which had recorded the data at the time of error or malfunction. From here, you can identify the issue and fix it.

vi. Qlik Sense Troubleshooting in Administering

Troubleshooting the administrative tasks uses the log files which stores system performance related information for all the types of operations going on in Qlik Sense. The log files keep a log of security operations, data loading, load balancing, distribution etc. If there is a problem, which usually shows by error message generation, then you can look for the respective log file and detect the issue in order to further take the best troubleshooting step. All the issues generated, and the troubleshooting methods suggested for them generally categorizes into use case sections. There are three such sections,

  • Procedure: Records the procedure or operation that is being carried out in Qlik Sense.
  • Success: This section has all the names of log files to which the details of the procedures are written.
  • Errors: This section contains the list of all the possible errors associated with different procedures.

You must read Qlik Sense Mathematical Functions

So, this was all in Qlik Sense Troubleshooting. Hope you like our explanation.

2. Conclusion

Thus, in this Qlik Sense Troubleshooting tutorial, we discussed all the common issues that generated while using Qlik Sense. If you come up with any doubts or queries, do drop your comments in the comment box below.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.