Verify connection errors when setting up a connection to Qlik Sense in Qlik NPrinting

Possible cause  

When you are setting up a connection to Qlik Sense in Qlik NPrinting, use the Verify connection button to ensure that all of the information that you have entered to connect to Qlik Sense is correct. A list of checks performed and their status will appear in the Details, if any of the information is incorrect, you will see a red X next to that item in the list indicating that the test failed on that item.

Failed test Proposed action
The connection parameters are valid. One or more connection parameters are wrong or missing.
The Identity is a Windows domain user.

The user in the Identity field must be a Windows domain user, and it must be enabled in Active Directory.

Qlik NPrinting and Qlik Sense must be installed on the same domain.
The Qlik Sense Repository Service can be reached on port 4242 of the proxy address. Verify that the Qlik Sense proxy address is correct and no firewalls are preventing the Qlik NPrinting Engine from reaching the Qlik Sense Repository Service on port 4242.
Installed certificates are valid to connect to Qlik Sense.

Certificates must be exported from Qlik Sense using the Qlik Management Console on the Qlik Sense Server, and installed on the Qlik NPrinting Engine computers.

To install the Qlik Sense certificates, use the QmcCertificatesInstaller.exe located in %ProgramFiles%\NPrintingServer\Tools\QmcCertificatesInstaller.

Ensure that the correct Qlik Sense certificates for the server and version that you are connecting to are installed.

Ensure that the correct user account was used to install the Qlik Sense certificates. See, Installing Qlik Sense certificates.
Get the version from Qlik Sense Repository Service on the proxy address.

Verify that the Qlik Sense proxy address is correct and no firewalls are preventing the Qlik NPrinting Engine from reaching the Qlik Sense Repository Service on port 4242.

TLS 1.2 must be enabled on both the Qlik NPrinting Engine client and the Qlik Sense server.
Get ProxyId from Qlik Sense Repository Service on the proxy address. Verify that the Qlik Sense proxy address is correct and no firewalls are preventing the Qlik NPrinting Engine from reaching the Qlik Sense Repository Service on port 4242.
Get app information from Qlik Sense Repository Service on the proxy address for the Sense App ID. Verify that the user in the Identity field is authorized in Qlik Sense to access the app. Also verify that the Qlik Sense proxy address is correct and no firewalls are preventing the Qlik NPrinting Engine from reaching the Qlik Sense Repository Service on port 4242.
The user running the Qlik NPrinting Engine service is a Qlik Sense RootAdmin. Use the Qlik Management Console (QMC) on the Qlik Sense computer to verify that the user running the Qlik NPrinting Engine service is in the RootAdmin group.
The Proxy Address, Sense App ID and Identity can be used for a connection to a Qlik Sense Engine.

Verify that there are no rules in the Qlik Management Console (QMC) preventing the Windows user running the Qlik NPrinting Engine service, and the user specified in the Identity field, from accessing the specified app.

In the Qlik Management Console (QMC), the Virtual Proxy used in the Qlik NPrinting connection to Qlik Sense must have at least one Load balancing node.

In the Qlik Management Console (QMC), the Virtual Proxy used in the Qlik NPrinting connection to Qlik Sense must have the node that is used in Qlik NPrinting in its Proxy list.

Verify that in Active Directory the user defined as the Identity is enabled.

You might need to manually synchronize Active Directory users.

Qlik NPrinting and Qlik Sense must be installed in the same domain.

Verify in the Qlik Sense Qlik Management Console (QMC) that the user who is running the Qlik NPrinting Engine service is in the RootAdmin group.
All Qlik Sense Engines are reachable from the Qlik NPrinting Engine computers.

Verify that the Qlik Sense proxy address is correct and no firewalls are preventing the Qlik NPrinting Engine from reaching the Qlik Sense Engine service. This Qlik Sense Engine service usually uses port 4747 (either on the Qlik Sense central node, or on dedicated Qlik Sense Engine nodes). This port can be configured in the Qlik Management Console (QMC).

Qlik NPrinting and Qlik Sense must be installed in the same domain. Verify in Qlik Sense Qlik Management Console (QMC) that the user who is running the Qlik NPrinting Engine service is in the RootAdmin group.
Get a list of all apps from Qlik Sense Repository Service on the proxy address. Verify that the Qlik Sense user specified in the Identity field is allowed to retrieve the apps list.
Look up the Qlik Sense proxy port from Qlik Sense Repository Service on the proxy address. Verify that the Qlik Sense user in the Identity field is allowed to look up the Qlik Sense proxy address.
The Qlik Sense proxy port is reachable on the proxy address. Verify that the Qlik Sense proxy address is correct and no firewalls are preventing the Qlik NPrinting Engine from reaching the Qlik Sense Proxy Service. The Qlik Sense Proxy Service usually uses port 4243 (usually on the Qlik Sense central node). This port can be configured in the Qlik Management Console (QMC).
Perform a GetTicket request to the Qlik Sense proxy on the proxy address. Verify that user in the Identity field is valid, the Qlik Sense proxy address is correct, and no firewalls are preventing the Qlik NPrinting Engine from reaching the Qlik Sense Proxy Service. The Qlik Sense Proxy Service usually uses port 4243 (usually on the Qlik Sense central node). This port can be configured in the Qlik Management Console (QMC).

Did this information help you?

Thanks for letting us know. Is there anything you'd like to tell us about this topic?

Can you tell us why it did not help you and how we can improve it?