It looks like you're new here. If you want to get involved, click one of these buttons!
PDFCreator 1.4.3 (server)
Windows XP SP3
I got the problem on one of our "server" but I tested it on a new machine.
I just installed PDFCreator then launch a print. The assigned handles are increasing without stopping.
I uninstalled it, rebooted the OS then reinstalled PDFCreator and the issue stills occur.
Is this issue known?
Don't hesitate to ask for more information.
Thanks in advance
We are having the same issue and it actually appeared for us with 1.4.2. I updated to 1.4.3, but no luck. This is on a 2008 R2 server.
I tested installing 1.4.2 on a Windows 7 x64 computer. It didn't have the issue with handles, but then I uninstalled pdfcreator, then re-installed it and the handles issue appeared.
So it is possilbe that this issue appears ONLY if you are installing on top of an existing version? I tried to do a full cleanup of PDFCreator on our server, then install 1.4.3, but handles still continued to increase. (used revo uninstaller and also deleted all registry entries for PDFCreator)
My current work around is to have a scheduled task restart the PDFCreator service each day, but it restarted at 6 AM and in two hours, it is at 14,000 handles. Doesn't seem to be causing any major issues, as it was at over 1.5 Million handles, before I noticed this issue.
Anyone else seeing this issue?
Tested on Windows XP x86 and had the same issue with the ever increasing handles. This appeared on the very first install on a clean computer. I uninstalled 1.4.3 and installed 1.3.1 and that version runs clean, without the handles bug. I then puth 1.4.3 back on it it, and the handle bug returned.
I tested this 1.4.3 version on a Windows XP computer and it had the Handle leak as well. I uninstalled and installed 1.3.2 and there was no handle leak.
To still get the last version and fixe the problem, I'm using a scheduled task with a batch script.
The script closes PDFCreator.exe and launch it 30 second after. It's launched everynight so we can reinit handles.
It's a solution but it doesn't solve the issue.
Here the batch:
@ECHO OFFtaskkill /IM PDFCreator.exe /Fping -n 30 127.0.0.1 > nul"c:\Program Files\PDFCreator\PDFCreator.exe"
version 1.5.0 was released today, please try to see if it fixes your problem.
I tested it and I obtained the same result.
I'm not doing anything on the computer and handles are still increasing.
Version 1.5 has the same handles issue. I just installed it on a Windows 7 64-bit computer and after 5 or 10 mins, it is at 1,000 handles and rising.
I uninstalled version 1.5.0, because it still has the handle leak and installed version 1.2.3 and it is holding steady at 122 handles.
Installed version 1.5.0 on a Windows 7 64-bit computer and the handles issue continued. The 1.2.3 version works perfectly on this same machne.
I ran into this issue while troubleshooting 2 Server 2003 R2 32-bit with pdfcreator 1.4.3 running as a service that ran out of 'pool memory' (event id 2020). In my lab I had an installation of 1.4.0 on Server 2008 R2 64-bit that didn't show this weird behaviour.
I can confirm that updating to 1.5.0 didn't solve the problem & even worse introduced it to the 2008 server as well.
Me too - as a workaround - restarts the service by a scheduled task every 4 hours ...
Regards & thankx for your ongoing effort
I'm dealing with a client with similar issues. The last time we did an update the PDF Creator service stopped working and we had to have a user logged onto the server with the program opened in order for it to work. Also the auto-save path wouldn't keep so if it got closed we would have to re-enter the path every time. We are currently running version 1.4.3, but I don't think we will be upgrading unless there is a known fix because of the past issues. I do want to post a second option if you are needing to quickly cycle the PDF creator services. It should work on all windows system, but was only tested and verified on 2003. I justed create a batch file with the following lines in it. We scheduled it to run once daily for now, but you might adjust as needed.
net stop "PDFCreator"
net start "PDFCreator"
Any comment on when the next version is set to be released?
I really like what this product has to offer and I hope to expand our usage of it, after this minor bug is corrected. PDFCreator has the potential to save us a lot of money in printing costs, which I plan to prusuade my boss to donate to help the continued developent of this great product.
Has there ever been discussion of making a paid version of PDFCreator?