Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
erhardt_dekock
Contributor III
Contributor III

Multiple node - Invalid path

Hello

QlikSense has recently been installed on 2 nodes for us. We did not perform the installation ourselves, limiting my knowledge of how it was done exactly.

Every second app (literally every second app) that we import shows Invalid path, while every other shows the path as being valid.

qs_invalid_path.jpg

The folder QlikShare_qs02 is on the secondary node and shared with the user running the services on both nodes.

Is there anything we should consider? Check? Any suggestions are welcome.

Working on possible solution with consultants that did installation.

Regards

1 Solution

Accepted Solutions
Levi_Turner
Employee
Employee

Hey Erhardt,

So the main core concept that is needed to understand here is that Engine resources are loaded locally by the Engine delivering the app. This goes for Folder data connections as well as pointers against connectors or DSNs.

What likely is happening is that the D:\... path exists on one node but not the other.

The best practice for a multi-node site is to only use UNC shares for folder data connections to ensure access to the files across the N number of nodes.

To resolve:

  • Share the local path (D:\...\)
    • Output path will be something like \\SERVER\QlikData
  • QMC > Data connections > Edit the Connection String and change the path
  • Validate in the Hub

Hope that helps

View solution in original post

2 Replies
Levi_Turner
Employee
Employee

Hey Erhardt,

So the main core concept that is needed to understand here is that Engine resources are loaded locally by the Engine delivering the app. This goes for Folder data connections as well as pointers against connectors or DSNs.

What likely is happening is that the D:\... path exists on one node but not the other.

The best practice for a multi-node site is to only use UNC shares for folder data connections to ensure access to the files across the N number of nodes.

To resolve:

  • Share the local path (D:\...\)
    • Output path will be something like \\SERVER\QlikData
  • QMC > Data connections > Edit the Connection String and change the path
  • Validate in the Hub

Hope that helps

erhardt_dekock
Contributor III
Contributor III
Author

Hi Levi

That solved our issue. We changed the Connection String to

\\server_name\QlikShare_qs02\QlikData\Human Resources\

The QVDs will then only live on this one server.

Only concern for this approach is that the apps reload QVDs via network (same building/room, still network),

Should be fine... Touch wood

Thank you