We have just upgraded our Qlik on-prem instance from May 2024 to November 2025 P2 and everything seems to be working fine with the exception of downloading charts as image or PDF.
When attempting to download as PDF, it generates a blank PDF. When attempting to download as an image, it gives me the error "An error occurred during export. Please try again"
Looking in C:\ProgramData\Qlik\Sense\Log\Printing\System\HOST_Service_Printing.txt shows the following error.
9 15.52.3.0 20260126T133054.579+0000 ERROR HOST 90996f90-e655-4395-8139-820c5e67bfd5 Command=Store exported object;Result=1;ResultText=Error: Empty result c0dee17f-94bd-c915-55b6-a7e8b362637c fcb51914-e76a-422b-9036-ad0897c3a945 fe46f8bf-bdf7-4280-9af0-ecd824a238e9 DOMAIN USER 0 Not available Printing Not available Not available Store exported object 1 Export request with id 'fe46f8bf-bdf7-4280-9af0-ecd824a238e9' and owner 'DOMAIN\USER' failed: Empty result 90996f90-e655-4395-8139-820c5e67bfd5
I have followed the two support articles below with no success.
Adding "<add key="webrenderer-args" value="-l=trace" />" to the printing.exe.txt causes the following lines to appear in C:\ProgramData\Qlik\Sense\Log\Printing\Trace\HOST_System_Printing_rwr.txt
[2026-01-26 13:18:03.705112] Initializing file logger...
[2026-01-26 13:18:03.745214] CEF exited message loop
[2026-01-26 13:18:03.747496] GRPC server listening at server_address=127.0.0.1:52051
But nothing appears in the log file after this.
The server is running Windows Server 2022 and so the following article is not applicable
And I now have image generation working again. I'll give it a couple days to verify, but that seems to have done the trick.
Obviously there's a reason I'm having to set those args, which would suggest an issue with a certificate.
I got the --disable-web-security and --allow-running-insecure-content from that thread you posted earlier, but looking in C:\Program Files\Qlik\Sense\Printing\lib\rwr\x64\debug.log showed an error stating that you can't disable web security without setting the --user-data-dir
In the end, I had to restore my VM from backup and upgrade again. Not sure what went wrong the first time, but a restore and upgrade sems to have fixed the issue.
So turns out the restore and upgrade didn't work. Everything was fine for 1 day, but it has started failing to export any images again. So something isn't happy after Qlik was running for a day.
We have the exact same issue, and nothing to fix it so far. What is your status on this now? Have you found anything on this yet? We tried to repair, as was suggested by qlik support, but no succes with that either.
No luck so far unfortunately. I have tried a repair also but was unsuccessful. I'm currently awaiting a response from Qlik support on other things to try.
What's odd is that it was fine for a day, then suddenly stopped working again.
does it happen for any specific big charts or all charts in Qlik sense? Also you can try exporting from remote server where Qlik sense is installed to rule out if its problem with your network.
Regards, Vighnesh Gawad Connect with me on LinkedIn | GitHub
in that case, as per first support article, it maybe because The default timeout is 10 seconds, which may not be long enough on a less powerful server or when the server workload is very high. Did server has enough space or RAM etc?
Also if it was working on first day, maybe something else is blocking it. Does windows server have any kind of antivirus software that gets installed in your Organisation?
Regards, Vighnesh Gawad Connect with me on LinkedIn | GitHub
I have already attempted to increase the timeout to 30 seconds, which causes the first request for image export to take 30 seconds before erroring, subsequent errors only take a couple seconds.
The server did not have issues exporting images prior to the update. CPU usage never goes above 20% and usage does not increase during attempted exports. Same for RAM usage, the server has 64GB of RAM and only 24GB are in use which does not increase during attempted image exports.
As for AV, the server is running ESET Server Security. Disabling this has made no difference either.
