Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

dwqlik82
New Contributor II

Server Connection to Mounted Folder

Hi All,

I'm having a bit of a problem creating a Qlikview server connection to a mounted folder, when connecting to a qvw in the root folder it works fine but any mounted folder i get a red x next to document exists (everything else is green).

Steps taken so far:

  • Folders in QMC are set as browsable
  • Nprinting user has access to the folders in windows
  • Nprinting user in in Qlik Admins and local Admin security groups on server
  • Connection path exactly matches the header when using Open in Server.. on the nprinting server logged on with nprinting user
  • This occurs both on qvw's with and without spaces in the names

Any help/ideas greatly appreciated.

Dale

1 Solution

Accepted Solutions
Employee
Employee

Re: Server Connection to Mounted Folder

Hi,

You can:

- open a .qvw stored on a shared folder as a QlikView Local connection in Qlik NPrinting. In this case you must use the Universal Naming Convention (UNC) path (\\ServerName\Foldername\...\FileName.qvw). This is a local connection, not a server connection. You must be able to open the document from the Qlik NPrinting Engine computer by using QlikView Desktop runned by the same Windows user that runs the Engine service.

- create a QlikView server connection by specifying the QVP address. In this case you don't need to use the folder path where the .qvw is stored because it is delivered by the QlikView server. Before to create the connection log into the NPrinting Engine computer, run the QlikView Desktop with the Windows user that runs the NPrinting Engine and select Open on Server. You must be able to open the source .qvw.

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

2 Replies
Employee
Employee

Re: Server Connection to Mounted Folder

Hi,

You can:

- open a .qvw stored on a shared folder as a QlikView Local connection in Qlik NPrinting. In this case you must use the Universal Naming Convention (UNC) path (\\ServerName\Foldername\...\FileName.qvw). This is a local connection, not a server connection. You must be able to open the document from the Qlik NPrinting Engine computer by using QlikView Desktop runned by the same Windows user that runs the Engine service.

- create a QlikView server connection by specifying the QVP address. In this case you don't need to use the folder path where the .qvw is stored because it is delivered by the QlikView server. Before to create the connection log into the NPrinting Engine computer, run the QlikView Desktop with the Windows user that runs the NPrinting Engine and select Open on Server. You must be able to open the source .qvw.

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

dwqlik82
New Contributor II

Re: Server Connection to Mounted Folder

Hi Ruggero,

I'm not sure how but it seems to have resolved itself, the connection that was previously saying the document doesn't exist has now started working this morning, the only thing I can think of that might have changed was whether any windows updates were applied to the server which restarted the services, either way it can now find the document

Thanks

Dale

Community Browser