Problem using COM object in Windows Server 2008 R2 (pdfcreator 1.3.2)

Hi,

I'm trying use COM object of pdfcreator in php. bellow code:

 

$PDFCreator = New COM("PDFCreator.clsPDFCreator") or die("Couldn\\' start the COM-object");

$PDFCreator->cStart("/NoProcessingAtStartup");

$options = $PDFCreator->cOptions;

$options->UseAutosave = 1;

$options->UseAutosaveDirectory = 1;

$options->AutosaveFormat = 0;

$options->AutosaveDirectory = $output_dir;

$options->AutosaveFilename = $nomearquivo . ".pdf";

$PDFCreator->cOptions = $options;

$PDFCreator->cSaveOptions();

$PDFCreator->cDefaultprinter = "PDFCreator";

$PDFCreator->cClearcache();

$PDFCreator->cPrintfile($ifname);

$PDFCreator->cPrinterStop = false;

$PDFCreator->cClose();

 

In Windows 7 works ok. But in Windows 2008 Server the pdfcreator is called but nothing happens. The .exe does not crash, it remains there but with no action and If I open Word and send a doc to print, then pdfcreator opens with all files I send before on the list.

I searched forum and found some messages about Windows DEP but did not work for me.

Any ideias ?

Hi,

 

this is probably a temp path related problem, which we couldn´t reproduce yet.

Next week, version 1.4.0 will be released which will have more advanced logging and we will get back to you and hopefully find a solution.

 

regards,

 

Robin

 Maybe the language?

I'm using Windows Server 2008 in portuguese and notice that when I open the cmd prompt the directory name for programs is "Program Files (x86)" but in Windows Explorer appears "Arquivos de Programas (x86)". 

The Same principle aplies to Users folder, all subfolder appear in english in cmd prompt and portuguese in Windows Explorer.

Hi,

 

it would be very helpfull, if you could install version 1.4.0 and enable logging by adding the following DWORD value to HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Print\\Monitors\\pdfcmon in your registry: name : Logging, value :1. This will cause PDFCreator to create an advanced logfile at %Windir%\\Temp\\_pdfcmonLog.txt, please send it to us (support@pdfforge.org). It will help us to identify and solve the problem.

 

regards,

 

Robin