Skip to main content

Creating a file share

Creating a file share or shared folder is a necessary prerequisite before you install Qlik Sense. The file share is used to store all the Qlik application data and must be accessible to all nodes in your Qlik Sense site. You can create a file share either on the same server as the central node or on a separate server. If you have a large multi-node site we recommend that you configure the file share on a dedicated server for better resilience and performance.

If you create the file share on a separate server then you can follow the same steps as for a central node but you must ensure that the same Windows domain user that you use to run the Qlik services has read and write access to the file share folder.

To create a file share and share the folder with specific users:

  1. Create a local folder on your server computer. For example, create a folder called QlikShare on the C:\ drive.
  2. Right click the folder, and then click Properties.
  3. Click the Sharing tab, and then click Share.
  4. Enter the name of your Windows user, and click Add.
  5. In the Permission level column, select Read/Write, then click Share.
Information noteMake a note of the network path shown in the confirmation screen as you use this later during setup of your shared persistence storage folders. The network path will be in the following format: \\server-name\QlikShare

Ensure that permissions on the folder, subfolders, and files are set to full control for the user account you selected.

To do this:

  1. Click the Security tab.
  2. Select the user account you want to use for the installation.
  3. Click Advanced and check that your user has full control and that this permission applies to the folder, subfolders, and files.
  4. Click the Effective Access tab and then click Select a user and enter your user account name.
  5. Click View effective access and check in the Permission column that your user has full control.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!