Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

jblomqvist
Contributor II

Help: Unable to make a Local QlikView app connection in NPrinting 2017 version

Hello all,

I have a QlikView app that I am trying to connect to with NPrinting June 2017 version but it is unable to find the QVW file.

To confirm:

  • I have specified the path that contains the QVW file using the \\computername\c$\folders\QlikViewApp.qvw format
  • Specified the QVW file name as it is named exactly and added the .qvw extension at the end of the name
  • Ticked "Connection requires authentication" and entered my local laptop login ID
  • Ticked "Change password" and entered my personal account password

When I Run Verification it says it comes up with a X next to "The document exists". Everything else is green.

What am I doing incorrectly? Please help

7 Replies
ogster1974
Honored Contributor II

Re: Help: Unable to make a Local QlikView app connection in NPrinting 2017 version

I've not tried connecting to qlikview Apps on np17 but I note I cannot reference networked locations for folder locations for example.

Have you tried moving your app onto the local machine to connect or using the sever connection.  qvp: etc...

jblomqvist
Contributor II

Re: Help: Unable to make a Local QlikView app connection in NPrinting 2017 version

Hi Andy,

The app is on my laptop.

This is what I already tried:

1) At first I simply did a local path like C:\NPrintingServer\QlikViewDocuments\Samples\Sales Demo.qvw

However this did not work. It produced the same error message as my original post.

2) So then I did \\computername\c$\folders\QlikViewApp.qvw format

But also this did not work.

I am not sure what the issue is.

QVP connection works but this slows down my development because I have to reload the QlikView app through QlikView Server first and then reload metadata in NPrinting to reflect changes in the QVW app. This is a much slower development process because the app is quite large.

This is why I want to do a local connection and develop that way but am having problems connecting.

ogster1974
Honored Contributor II

Re: Help: Unable to make a Local QlikView app connection in NPrinting 2017 version

If it's possible to connect that way could it be a permissions issue.   the nprinting user not having access to the app?

I've heard a lot of people using the qvp method and getting a successful connection but having to manually reload each refresh although I believe the latest version now has a scheduled task to handle this.

jblomqvist
Contributor II

Re: Help: Unable to make a Local QlikView app connection in NPrinting 2017 version

Hi Andy,

Do you mean the NPrinting user unable to access the laptop where the app is?

ogster1974
Honored Contributor II

Re: Help: Unable to make a Local QlikView app connection in NPrinting 2017 version

Yes as it needs permission to access that location to access the app.  

I still have this feeling that the local connection to the app needs to be on the same machine as nprinting as I've noticed you can't create folders to store report output on other networked machines I think this may be the restriction here too.

jblomqvist
Contributor II

Re: Help: Unable to make a Local QlikView app connection in NPrinting 2017 version

Hi Andy,

Thanks for your response.

Few things to clarify:

  • "I still have this feeling that the local connection to the app needs to be on the same machine as nprinting"

Do you mean same machine where NPrinting Designer is installed or same machine where NPrinting is installed on a server? I.e. The local connection needs to refer to some folder in the server where NPrinting is installed?

  • I will check if the NPrinting account has the ability to access my laptop.
ogster1974
Honored Contributor II

Re: Help: Unable to make a Local QlikView app connection in NPrinting 2017 version

I think the local connection needs to be on the same server as nprinting server if you are connecting that way.   use the qvp connection if on another server.  

That's what I think based on the fact you cannot store import user files or export report folders on remote locations.

Community Browser