Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

Not applicable

NPrinting 17 Connection cache-Error Request has been purged due to connection errors

hi experts..

   I installed Qlikview NPrinting 17 after that I add the engine for make a report the engine status shows online

And then I create the app and connection the conection status got ok but the cache status shows connection errors like below

Capture7.JPG

so anyone suggesting me to solve this issue by proper steps..

7 Replies
oknotsen
Honored Contributor III

Re: NPrinting 17 cache status error

Please stick to your own topic.

I rejected and deleted your same question in other topic.

May you live in interesting times!
Employee
Employee

Re: NPrinting 17 cache status error

Hi Sankar,

You should get a clue in the log files. Location: %ProgramData%\NPrinting\Logs

If you find errors check this page for possible cause/resolution: Troubleshooting ‒ QlikView NPrinting

HTH - Daniel.

guruprem
Contributor III

Re: NPrinting 17 Connection cache-Error Request has been purged due to connection errors

Hi,

Today I have also faced the same issue. May I know how it was resolved at your place

Not applicable

Re: NPrinting 17 Connection cache-Error Request has been purged due to connection errors

hi guruprem

            In our place we are using CALs licenses for Qlikview so we have to lease the  licenses to Qlikview server

after that restarting the NP engine cache was generated fine..

Check your Qlikview licenses First

NP (2).PNG

Emmanuelle-Bustos
Valued Contributor

Re: NPrinting 17 Connection cache-Error Request has been purged due to connection errors

same issue somebody has fix this?

Not applicable

Re: NPrinting 17 Connection cache-Error Request has been purged due to connection errors

Hi emmanuelle.bustos ..

          Check That app If it is using any Session access Cache error ll appears

Emmanuelle-Bustos
Valued Contributor

Re: NPrinting 17 Connection cache-Error Request has been purged due to connection errors

Hi Sankar,

We solve the issue by re-exporting Sense Server certificates and reimporting them on the NP Server then it works fine!

Community Browser