PDFCreator tasks not showing up in job queue

Hello,

I’m having the following issue: whenever I click on the “print” button in the usual print pop-up with PDCreator selected, nothing happens. The printer icon shows up in tray but no job is registered and no file is processed. (I am running Windows 7 SP1 and the last version stable version of PDFCreator). Any clue?

Thanks in advance,

N.

Hi,


as a first step, please enable logging (in the “printer” menu of the “PDF Print Monitor”), start a printjob and post the resulting log here.

best regards,

 

Thanks a lot, Robin. I get no output in the log file, but the following screen pop-upS:
1) https://www.dropbox.com/s/nlwt4qinvqof0rc/Capture.JPG
2) https://www.dropbox.com/s/ho5g2net0b6h18g/Capture2.JPG

Hi,

please check the permission for the PDFCreator temp spool folder (%USERPORFILE%\AppData\Temp\PDFCreator\spool. Make sure the user running PDFCreator has full writing access to this folder.

best regards

Thanks for you kind answer, Robin. My permissions over the folder and its content were completely messed up. It’s all fixed now! :slight_smile:

I had the same problem and the answer also worked for me!

What I still don’t know is the reason why this happened suddenly. I’d like to know it but anyway, thanks a lot :wink:

I’ve been having the same problem. When I logged the print job I got this:

6/30/2014 10:13:11 AM: PDFCreator Program End
6/30/2014 10:13:16 AM: PDFCreator Program Start
6/30/2014 10:13:16 AM: Windowsversion: Windows 7 6.1 Build 7601 (Service Pack 1) [TerminalServer IsWinXPPlus IsWinVistaPlus IsWinVistaSP1 IsWindows7]
6/30/2014 10:13:16 AM: InstalledAsServer: False
6/30/2014 10:13:16 AM: MyAppData: C:\Users\trosta\AppData\Roaming
6/30/2014 10:13:18 AM: PDFCreator Program Start
6/30/2014 10:13:18 AM: Windowsversion: Windows 7 6.1 Build 7601 (Service Pack 1) [TerminalServer IsWinXPPlus IsWinVistaPlus IsWinVistaSP1 IsWindows7]
6/30/2014 10:13:18 AM: InstalledAsServer: False
6/30/2014 10:13:18 AM: MyAppData: C:\Users\trosta\AppData\Roaming

Hi,


(edit: @trosama)
did the problem get solved by changing the permissions for the temp/spool folder?

@Robin.W: Yes, the problem get solved via changing permissions on the temp/spool folder.