Verify connection error

[slogue1234]

Hi

NPrinting can no longer generate meta data following Qlik upgrades (hardware and software).

Qlikview version - May 2024 SR1

NPrinting version - February 2025 SR1

NPrinting Designer version - 25.5.5.0

I am receiving the error: "The account used to run Qlik NPrinting Engine belongs to the QlikView Administrators Windows group on the QlikView Server."

I have checked all permissions and admin rights, all match the old server which had no issues. The only thing different between old and new servers is the 'Qlikview Management API' group - this is ticked on the old server, not on the new. Could this be causing a problem?

Thanks

[Lech_Miszkiewicz]

HI @slogue1234 

This may matter if you are using Claster connection and is documented 

https://help.qlik.com/en-US/nprinting/February2025/Content/NPrinting/DeployingQVNprinting/NPrinting-...

cheers

[David_Friend]

yes for sure if a cluster

[slogue1234]

This is not part of a cluster, just single node. Would that change the advice?

I have created the QlikView Management API group and added the user to it, however I am still getting the same error when trying to create connections?

Thanks

[Andrea_Bertazzo]

hi @slogue1234 
Please, connect to the NP Engine machine as the Engine user, open QV desktop and try to open the QlikView document in Server. Does this work?
Verify that the account used to run Qlik NPrinting Engine and the account in the QlikView Administrators Windows group  is exactly the same.  Ensure that this account has a token in QlikView.

[Andrea_Bertazzo]

hi @slogue1234 

Do you have any news? Didi you try the tests suggested?

Kindly, let us know if the problem is still there.

[slogue1234]

Hi

Yes I finally got it working.

I added the NPrint user to the Qlikview API Management Group but still received the error. 

Then the services Qlikview were restarted and the Qlikview servers were rebooted in response to unrelated service issues.

After this, the Nprinting errors cleared. So unfortunately I am not entirely clear what combination of steps resolved the issue