Wondering how much support there might be for those of use using PDFCreator as a companywide server solution?
The lack of native 'Windows Service' support really causes problem. I don’t understand why pdfforge has not put more development emphasis on supporting their product as a server solution?
I am running W2K8R2SP1 with PDFCreator 1.2.0 (putting off upgrading to 1.2.3 due to the known uninstallation bug). I have multiple PDFCreator 'printers' all configured to directly save the files to a standard folder on the users desktop. This solution is very robust and works great.
However every few days/weeks PDFCreator will stop printing. Logging into the server Taskmgr will show hundreds of hours of CPU time on the PDFCreator process and show the CPU currently pegged at 50%. At this moment I have no recourse except to restart the service. It would be nice if I could open the management console to see what job it is stuck on, if it is even stuck on a job, or what is going on. Unfortunately when I open the PDFCreator management console it just creates a second PDFCreator instance.
In addition having to perform the whole srvany trick to get it to run as a service is time consuming and lame.
I would really appreciate an official response to this question and am wondering how many others would like one too?
Why pdfforge has not put more development emphasis on supporting their product as a server solution?
-mark