I have a client that the end users are using both web browser and QV desktop client.
Every morning, the end users cannot print report in the web client (the error message is time out). I can see there is a pdfsaver3 process in the server but it doesn't look working. Then if I try using the local client to open the same application in server, make the same selection and print the same report, it can be printed without any problem. I can see another pdfsaver3 is running so I have two pdfsaver3 in the process list. (If I open notepad and print something using pdf-xchange 3.0 I have the same result - another pdfsaver3 that is working).
After that I go back to web browser, I can print the same report. And from then the web browser will work for the rest of the day until next morning. Note: the next morning there is only one pdfsaver3 in the process list and it is not working for web browser.
Qlik support asked me to delete all the printers in the server but I am not allowed to do it because uses are using other printers too.
Does anyone have any clue about this? What will make a working pdfsaver3 process not working for web client?
The client is using QV 11 SR15 in a Windows 2008 R2 server. I have tried both Google Chrome and IE...
My case is different. During installing QV, the printer spooler was running. The printer is found and working. The pdfSave3.exe just stops printing sometimes. After restart the QV service or kill the pdfSaver3.exe, it will work again.
I have reinstalled the pdf-xchange 3.0 twice by the way. We have also upgraded QV from QV11 SR12 to SR15 but we are still having some problem for example this morning, the web client was working but desktop client did not work. I killed the pdfSaver3.exe and re-tried printing, the desktop worked again.
I start to think if it is caused by the NPrinting daily pdf report in the morning. If pdf-xchange 3.0 printer is working in QV at the end of previous day but not the next morning and if NPrinting was the only thing that has exported some pdf reports during this time, wouldn't it caused by it?
The NPrinting is version 16.2.0.0. I can see its printer is called "QlikView NPrinting PDF Printer". I think it use pdf-xchange 2012 to print. The NPrinting is working well without any problem.
Do you mean you are generating reports from nprinting. If so, those reports generated default in the morning of everyday.
So, and then problem is not the nprinting. Though, I also tried few months ago to achieve this. That time client recommend me to upgrade the nprinting server. So that, I've tried that way to. Finally I got this and again I've started bit thinking on earlier concern and version. Finally, I didn't find any solution asi I expected.
Hope this helps you
Best Anil, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful
I don't use NPrinting and therefore don't know if there is a problem with it - but your description directed to a conflicting of the PDF-XChange and NPrinting and/or between them and the OS respectively the filesystem - maybe a look within the event-logs give any hint.
