PDF XChange Forum

My company is seeing an uptick in reports from our customers who are using Windows 10 that PDF generation is not working at all. When digging into this a bit we've noticed that drivers are being orphaned. See the attachment below for a screenshot of an extreme example of this.

We are calling the "RemoveOrphanPrinters" function on the COM object but it just doesn't seem to do anything. We are aware that we're using an older version of the PDF-XChange driver (4.0 build 195) but we're hopeful we can find a solution that doesn't involve upgrading to a newer version of the tool.

Thanks

Hello sooprcow,
I notice that all except one of the print queues in your list there are from competitors products.
Can you confirm that ours is also causing this problem?

The "RcApiPDFDriver" and the "UltramatePDFDriver" are the orphaned instances of your "PDF-XChange 4.0" driver that we instantiate programmatically via the CPXCControlEx's GetPrinter(..) function. Both are from the same the same application but use different workflows.

Hi again sooprcow,
Can you validate that you have used the "RemoveOrphanPrinters" function as detailed in this article?
https://www.pdf-xchange.com/knowle ... pplication
It seems that iPXCC.RemoveOrphanPrinters('') needs to be called before iPXCC.Get_Printer in order for it to work.
Waiting patiently for your response
~

Yes, I can confirm that is the function we're calling and that we're calling it before the GetPrinter call.

Hi sooprcow,
We will try to reproduce the issue and figure out further steps on this.

Any status update on this one?

Hello sooprcow,

Roman is in our Canadian office, and it's currently the middle of the night there, but I will leave him a note and ask him to post an update here as soon as he can later today!

Cheers,
Stefan

Hello sooprcow,
Can we arrange a remote debug session on one of your machines that has this issue?
See here for details.