Nprinting service account qlikview named cal issue

[stevelord]

Hi All, I'm using Nprinting 16.5 and Qlikview 12.20.20400 that were deployed in our new server environment and working well since June 2, 2018.  Last week, nprinting jobs began failing for unknown reasons. A colleague of mine was able to run the nprinting jobs manually while I was on pto as a workaround.  I'm back from PTO troubleshooting now.

When I sign in as the nprinting service account to see things from its perspective and open a document, it gives me that message about the document being made by someone else and asks if I want to recover it.  I push abort/cancel to get out of that, and it says failed to load etc, but then the document opens anyway.  It lets me reload the document, but not resave it, then freezes when I try to just close it out.  When I subsequently login as myself, I can open the document without any prompts/issues, but when I reload it fails to open the related qvds in write mode.  This makes me think the nprinting service account has a phantom open on them still, but I can delete the qvds from my own user account and reload the document without issue repeatedly after that.  If I try to reload it from the nprinting service account again, the above cycle is repeated.

I've done the file->open in server bit from the nprinting service account, and it opens documents without issues that way and qvmc shows that it last used its license at that time.  I even had a daily nprinting job to do that to keep its qlikview named cal active which worked for years prior to setting up on the new server (NP 16.0 and QV 11.2 SR12 prior to June 2 2018).  But when I just try to open the document directly, I'm back to the error message about it being created by another user...

So I'm stumped.  Please advise on how I can get the named cal to stick to my nprinting service account.  NP 16.5, QV 12.20.20400 last updated June 2 2018.

[Eva_B]

Hello,

I saw your post didn't receive any responses so I wanted to provide some information concerning Qlik NPrinting and the Account requirements.

A great article was created by one of my colleagues which is found here:

https://support.qlik.com/articles/000033911

Please review and let us know if you have any further questions.

Also if this post answered your question please mark it as a "Solution."

Regards,

Eva

[Lech_Miszkiewicz]

Hi,

I am quite surprised that out of nowhere it stopped sticking the license to the service account user.

Just make sure that:

• this service account is not used anywhere else,
• you have QlikView desktop and server running the same version on NPrinting and Qlik servers
• make sure that after QlikView upgrade the "Allow lease licenses from server" is still checked in QlikView QMC.
• stop NPrinting service (server) and re-type username and password and start again
• see if you can create a dummy qvw using NPrinting service account and run dummy report out of it - since it will be created by service account it should not ask for user name and password
• maybe enable session 0 preview to see what is happening whe service account tries to run task/job https://kb.firedaemon.com/support/solutions/articles/4000086228-what-is-session-0-isolation-what-do-...

Is there section access used in this application?

or maybe group policies overwrote admin privileges - so service account cannot save document anymore? 

or maybe the folder / or qvw file owner left company so account got locked and therefore no changes can be done on the folder where qvw is stored. I had this odd behaviour once when for some reason folder and file policies were constantly overwritten.

The response from the other user probably does not apply to your case as it only touches requirements for NPrinting 17 and above service account user, when i looked at the document she pointed you to there was nothing really relevant to your case, so you probably will not find there anything useful unfortunately

If nothing from the above works i suggest you open support ticket with Qlik - it is quite odd situation with license not sticking and support might have to step in to solve it quicker.

cheers

Lech