PDF files not created on one workstation

[trumpetinc]

This seems to be my day for running into problems

I have one customer with one workstation that is exhibiting the following behavior:

1. Open a text document
2. Print to our application's print driver
3. Our application receives the appropriate driver events without problems, including DOCUMENTEVENT_STARTPAGE and DOCUMENTEVENT_ENDPAGE, ending up with DOCUMENTEVENT_ENDDOCPOST.
4. The PDF file is never created

We call SetDefaultFileName to specify the output name, and we do have the UseFileName option specified via SetFileNameOptions.

We call EnablePrinter immediately after calling SetDefaultFileName, and initiate the print job immedately after the call to EnablePrinter.


Any ideas on what could be causing the PDF to not be generated at all?

I've already confirmed that I can create a file with the specified name by hand - so it's not something odd with file sysetm permissions...

Thanks in advance,

- Kevin

[trumpetinc]

It would also probably help if I explained that the above test procedure works perfectly on many, many other workstations...

Thanks!

- K

[Joan]

Hello,

Please tell me which version of the PDF Converter you are using and how precisely you are printing to the PDF Printer, so I can try to see what might be going wrong.

Thanks.

[trumpetinc]

Hello,

Please tell me which version of the PDF Converter you are using and how precisely you are printing to the PDF Printer, so I can try to see what might be going wrong.

Thanks.

CDIntf210.dll is the DLL. Version on the DLL is 2.1.0.8.

Right now, I'm just working in a test application that has one button: Load.

Load calls DriverInit and sets the parameters I described in my above post - and we set up a window that receives OnPDFEvent messages from the driver. We only click this once per run of the application.

In the OnPDFEvent handler window, we do the following:

- During the DOCUMENTEVENT_ENABLEDPRE event, we call SetDefaultFileName to set the output filename, then we call EnablePrinter

- For all other events, we write the event information to a listbox so we can log what is being sent to it.




On every other workstation I've ever done this with, the events come through and are listed in the log, and a PDF file gets created in the location specified in the SetDefaultFileName call.

On this workstation, the events come through to the log, but the PDF file never gets generated.



Thanks in advance for your help!

- Kevin

[Jose]

Hello,

Can you verify if your customer's problematic system has a FILE: port? Although the PDF Converter does not use this port, it still needs access it to. If you do have a FILE: port then you will just need to create one.

Hope this helps?

[trumpetinc]

How interesting - apparently, this machine has two ports named "FILE:" - I can't even begin to imagine how that might have happened. I've asked the admin to reformat and re-install the operating system - who knows what else is wrong with that computer.

Thanks for the suggestion!

Hello,

Can you verify if your customer's problematic system has a FILE: port? Although the PDF Converter does not use this port, it still needs access it to. If you do have a FILE: port then you will just need to create one.

Hope this helps?

[trumpetinc]

OK - we reformatted the machine, and all is well now. thanks!

[quote="trumpetinc"]How interesting - apparently, this machine has two ports named "FILE:" - I can't even begin to imagine how that might have happened. I've asked the admin to reformat and re-install the operating system - who knows what else is wrong with that computer.

Thanks for the suggestion!