PDF contains sometimes Demo Stamps

[Chris444]

Hi,
our app uses an OLE-Connection to PXCComLib7.CPXCControlEx and creates a printer with .Printer using our license key.
Some option are being set and than our document is printed using the printer name of the creates printer to create the pdf.
It works without problem.
But very very rarely the created pdf contains the demo stamps.
There is no pattern nor any recognizable circumstances.
It all runs on the same PC with same environment. Everything works fine, but once in a while, it happens. Next PDF is good again.
Our app can run multiple times simultaneously, but we can not force the problem to happen.

Do you have an idea, what could cause this and how we can find the reason?

[Tracker Supp-Stefan]

Hello Chris444,

Are you starting a new driver instance if you are printing more than one file at the same time or do they all go to the same instance that you have created once?

Kind regards,
Stefan

[Chris444]

Hi Stefan,

yes, we are starting a new driver instance, if we are printing more than one file at the same time.
As I said, our application just generates one pdf at the same time:
App is started, connect to printer driver, creates new printer, print our stuff to a new pdf, disconnects from driver and app will be closed.
It can happen, that our app is started multiple times at the same time.
BUT the problem seems not to depend on creating multiple pdf files at the same time. Some customers said, they got the demo stamps while creating just one pdf file at that time.
Because the error only occurs every now and then, we don't have any precise details about the circumstances.
So it would be nice to know, under which conditions the demo stamps might be visible.
Perhaps this could help locating the problem.

[Chris444]

Hi,
any new information about this? Or things we could try out?
Regards,

[TrackerSupp-Daniel]

Hello, Chris444

At the moment, I am afraid that we do not have any advice to pass on, the Dev team is looking into things from this end, and trying to work out a solution, but I cannot offer a timeline.
In the meantime, we do have a ticket made for tracking this issue internally. While there is not much in there at the moment, you can ask us for updates by referencing the ticket number in the future:

RT#6848: Bug: DriversAPI - sometimes unlicensed

Kind regards,