Instances of Printer are not deleted
Posted: Thu Dec 19, 2019 7:52 pm
We are using the Printer SDK to created new Printers and e.g. print to a specific filename or add an overlay to PDF files.
In the moment we call CPXCControlEx.get_Printer(...) a kind of copy of the printer is created, which then is named "PDF-XChange Standard V7 (1)". So far so good.
Our Problem now is, that this instance is not deleted at a specific time. Some of our customers have to Restart the Spooler Service, than all instances are gone and only the main/original instance is left.
Especially on a terminal Server (which normally wont get restartet) many Printers are then in the list of Printers e.g. when you want to print a word document. That is Kind of anoying for our customers.
In the software we know exact the moment when we do not need the printer anymore. Is there a specific call to the api we can make so that the instance will be deleted?
We tried this with the latest release we could download today from your website. We also used the sample app you are providing and it also happens there. Even if the process already has shut down, the printers still are left in the system.
Happens on several windows versions, desktop or client.
We are using C# and COM objects to access printers.
Best Regards
Andreas
In the moment we call CPXCControlEx.get_Printer(...) a kind of copy of the printer is created, which then is named "PDF-XChange Standard V7 (1)". So far so good.
Our Problem now is, that this instance is not deleted at a specific time. Some of our customers have to Restart the Spooler Service, than all instances are gone and only the main/original instance is left.
Especially on a terminal Server (which normally wont get restartet) many Printers are then in the list of Printers e.g. when you want to print a word document. That is Kind of anoying for our customers.
In the software we know exact the moment when we do not need the printer anymore. Is there a specific call to the api we can make so that the instance will be deleted?
We tried this with the latest release we could download today from your website. We also used the sample app you are providing and it also happens there. Even if the process already has shut down, the printers still are left in the system.
Happens on several windows versions, desktop or client.
We are using C# and COM objects to access printers.
Best Regards
Andreas