After years of loyal service, PDFCreator doesn't create PDFs anymore

Hello Community,

I have used PDFCreator for years without any
problem. Then an IT provider ran diverse clean-ups, malware searches etc
on the computer a few days ago and since I have the following propblem:

OS: Microsoft Windows 7 Family Premium
6.1.7601 Service Pack 1 Build 7601
Version of PDFCreator: 1.7.2 Downloaded and installed today

When
I want to print, prompts indicating that the software is preparing the
file for printing appears, in Window 7’s Launch bar a printer icon
appears and then nothing.
- If I right click PDFCreator in Windows’ “Devices and printers” there are no pending printing tasks.
-
If I open PDFCreator for Windows’ Start Menu, the lists of files is
empty. If I want to drag and drop a file into the list of files, the
software defined as default software for that type of file (i.e. Word
for a .doc file) opens, there are the software’s printing prompts and
when the prompts are over, the software remains open. When I close the
software, I’m back to PDFCreator but the file list is still empty.

Did I try to uninstall PDFCreator and reinstall it? - Yes. Multiple times.
Did I try to uninstall PDFCreator 1.7.2 and install an older version? - Yes. I installed 1.7.0. Same result.
Did
I ask the IT provider to find the problem? - Yes. But they refuse to
help without payment as they say it’s not their fault and they can’t
give waranty.

SetupLog.txt is hereafter.

Any ideas where the problem might be are very welcome. Thanks for your help!

Frank

----- Setup - Start: 2014-02-09 15:46:42 -----
Install PDFCreator: 1.7.2
InstallerDirectory: C:\Users\Frank Seidel\Downloads
X64: yes

Start AnalyzeCommandlineParameters
 Parameter /VERYSILENT: false
 Parameter /SILENT: false
 Parameter /FORCEINSTALL: false
 Parameter /REMOVEOPTIONS: false
 Parameter /DONTINSTALLPRINTERS: false
 Parameter /EXPERT: false
 No Parameter /LoadInf
 No Parameter /SaveInf
 No Parameter /REGFile
 No Parameter /PPDFile
 No Parameter /Printername
End AnalyzeCommandlineParameters

WindowsVersionNumber: 6.1.7601
Silent installation: false
GUITS (7000, 50): 11
PreviousApplicationPath: C:\Program Files (x86)\PDFCreator
Update: 1
Installed PDFCreator version: 1.7.0
Installed PDFCreator version is lower 1.5.1 = false
nationCode: 84
InstallPDFCreatorPrinter = false
OS: 2
IMC:
AppPath: C:\Program Files (x86)\PDFCreator
InstalledPDFCreatorVersion: 1.7.0
DontInstallPrinters: true
SPT: false

IC:1|1.7.2|1|fr|b4|d0

— Systeminformation - Start —
Windowsversion: 6.01.7601
WinDir: C:\windows
Win64: true
ProcessorArchitecture: X64
.Net 2.0: true
.Net 2.0 regasm.exe:C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe
SystemDir: C:\windows\system32
TempDir: C:\Users\FRANKS~1\AppData\Local\Temp\
CurrentDir: C:\windows\system32
Computername: FRANKSEIDEL-HP
Username: Frank Seidel
UILanguage: 1036
Internet Explorer version: 9.11.9600.16428
Path:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program
Files (x86)\Common Files\Microsoft Shared\Windows
Live;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Program
Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Pinnacle\Shared
Files\;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program
Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files
(x86)\QuickTime\QTSystem\
C:\windows\system32\Wbem\framedyn.dll: NOT found
framedyn.dll: found in path
— Systeminformation - End —

— Environment - Start —
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\Frank Seidel\AppData\Roaming
CLASSPATH=.;C:\Program Files (x86)\Java\jre7\lib\ext\QTJava.zip
CommonProgramFiles=C:\Program Files (x86)\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=FRANKSEIDEL-HP
ComSpec=C:\windows\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Users\Frank Seidel
LOCALAPPDATA=C:\Users\Frank Seidel\AppData\Local
LOGONSERVER=\\FRANKSEIDEL-HP
NUMBER_OF_PROCESSORS=2
OnlineServices=Online Services
OS=Windows_NT
Path=C:\Program
Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files
(x86)\Common Files\Microsoft Shared\Windows
Live;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\Program
Files (x86)\Windows Live\Shared;C:\Program Files (x86)\Pinnacle\Shared
Files\;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program
Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files
(x86)\QuickTime\QTSystem\
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PCBRAND=s
Platform=BNB
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_ARCHITEW6432=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 42 Stepping 7, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=2a07
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files (x86)
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PSModulePath=C:\windows\system32\WindowsPowerShell\v1.0\Modules\
PTSMInstallPath_X86=c:\Program Files (x86)\Hewlett-Packard\HP ProtectTools Security Manager\
PUBLIC=C:\Users\Public
QTJAVA=C:\Program Files (x86)\Java\jre7\lib\ext\QTJava.zip
SystemDrive=C:
SystemRoot=C:\windows
TEMP=C:\Users\FRANKS~1\AppData\Local\Temp
TMP=C:\Users\FRANKS~1\AppData\Local\Temp
USERDOMAIN=FrankSeidel-HP
USERNAME=Frank Seidel
USERPROFILE=C:\Users\Frank Seidel
windir=C:\windows
windows_tracing_flags=3
windows_tracing_logfile=C:\BVTBin\Tests\installpackage\csilogfile.log
— Environment - End —

----- Setup - End:   2014-02-09 15:48:15 -----

Hi,


please try the following: unistall PDFCreator-> (I know you tried reinstalling allready but there will be a twist), reboot your computer-> check for pdfcmon.dll in windows\system32, if it is still there delete it (you need to stop your spooler to be able to delete it, by typing “net stop spooler” into CMD(with admin rights). Afterwards PDFCreator can be reinstalled and should work again.

Another possible problem could be PDFCreator not having access to it’s temporary spool folder anymore, you can check this by enabling logging on the PDFCreator print monitor and restarting the PDFCreator once, the log will then contain a line  “PDFCreator spool directory (Write access: true): C:\Users\ROBIN~1.WER\AppData\Local\Temp\PDFCreator\Spool”. If it is false go to the folder and give the user running PDFCreator full access to it.

regards,

Robin

Hello Robin,

Thank you for your kind answer!

I did uninstall PDFCreator and rebooted the computer.

No pdfcmon.dll was to be found in windows\system32.

I also looked in C:\Users\ME\AppData\Local\Temp\ and there still was a PDFCreator folder which I moved to the desktop (still there if needed).

I then reinstalled PDFCreator 1.7.2. Unfortunately the situation hasn’t changed.

In order to try the other potential source of error, please advise how I can enable logging in the PDFCreator print monitor. I don’t know how to do this.

Thanks a lot for you help!

Frank


Hi,


to enable the logging, run the pdfcreator.exe and select “Printer->Logging” from the menu of the “PDF Print monitor” . You can also directly check the properties (security settings, writing permission) of the C:\Users\ME\AppData\Local\Temp\PDFCreator folder and make sure your system and the user starting the PDFCreator have full writing access to it and its “spool” subfolder.

regards,

Robin

Hello Robin,

Thank you for the quick answer.

So I went to “Imprimante > Journal” (is it important that the program is installed in French?) and when I then wanted to close PDFCreator I got the error message

----------------------------------------------------------------------
PDFCreator - www.pdfforge.org
----------------------------------------------------------------------
Errorprotocol
----------------------------------------------------------------------
PDFCreator 1.7.2 - Error message
----------------------------------------------------------------------
ERROR DESCRIPTION:
          Error-Nr:    75 (Erreur dans le chemin d’accès)
          Modul:    modPDFCreator
          Procedure:    IfLoggingWriteLogfile
          Line:         50250
          Date/Time:    02-12-2014 / 11:22:55
----------------------------------------------------------------------
CALLSTACK:
----------------------------------------------------------------------
SYSTEMINFO:
 Windows 7
  [6.1 Build 7601 (Service Pack 1)]
----------------------------------------------------------------------

When I clicked on “Next Command”, I got the following error message

----------------------------------------------------------------------
PDFCreator - www.pdfforge.org
----------------------------------------------------------------------
Errorprotocol
----------------------------------------------------------------------
PDFCreator 1.7.2 - Error message
----------------------------------------------------------------------
ERROR DESCRIPTION:
          Error-Nr:    52 (Nom ou numéro de fichier incorrect)
          Modul:    modPDFCreator
          Procedure:    IfLoggingWriteLogfile
          Line:         50420
          Date/Time:    02-12-2014 / 11:23:10
----------------------------------------------------------------------
CALLSTACK:
----------------------------------------------------------------------
SYSTEMINFO:
 Windows 7
  [6.1 Build 7601 (Service Pack 1)]
----------------------------------------------------------------------

From there, the two error messages alternate every time I click on “Next command”.

The same think also happens if I try to print something with PDFCreator.

Does this help to identify the problem?

Kind regards

Frank

Hi,

yes it will most likely help to find a solution, but it might take a liitle as the developers might need to have a look at it. It doesn’t matter what language is set.
Did you check the permissions for C:\Users\ME\AppData\Local\Temp\PDFCreator ?
It looks like PDFCreator can’t write to that folder.


regards,

Robin

Hello Robin,

I’m not sure where I need to check the permissions of the folder. When I open the properties of the folder there are a lot of different tabs, options and advanced options.

Please advise what property I need to check and change if appropriate.

Thanks and regards

Frank

Hi,


I found you a detailed description: http://www.wikihow.com/Change-File-Permissions-on-Windows-7

make sure your user and system account have full access (read,write) to the folder and its “spool” subfolder.

regards,

Robin

Hello Robin,

Thank you for finding this wiki, but what I see on my computer doesn’t correspond to what I see in the tutorial. Is there a possible to send screenshots so that you can guide me?

For example I have an additional dialogue if I really want to continue and after that dialogue the options are not entirely the same. And as a matter of fact, the first tries did not result in PDFCreator working again.

Thanks again for continued help!

Frank

Hi,


I am afraid my Windows is in german, so it will most likely not be very helpfull.
The additional dialogue is normal, it is asking you if you want to use admin rights to modify the permissions of the folder. There is some additional information about file and folder permissions in the Windows help and on the web, the main thing is your user account and your system account have full access to the C:\Users\ME\AppData\Local\Temp\PDFCreator and C:\Users\ME\AppData\Local\Temp\PDFCreator\spool folders.

regards,

Robin

Hello Robin,

So I discovered that PDFCreator did actually create a log file which produced the following error.

18/02/2014 18:34:38: MyAppData: C:\Users\Frank Seidel\AppData\Roaming
18/02/2014 18:34:38: PDFCreator spool directory (Write access: false): C:\Users\FRANKS~1\AppData\Local\Temp\PDFCreator\Spool\
18/02/2014 18:34:39: PDFCreator Program End

So I understood that the problem was actually that I didn’t have the write access to the Spool directory. But the problem was that first \Frank Seidel\ was not in the list of users that I could give access to the folder, than when I tried to add the user I encountered multiple error messages. I eventually clicked a little bit everywhere and now it works.

Thanks a lot for your patience and help!

Frank

Hi,


you are welcome, I am glad it is working again.

regards,

Robin