"Buy" watermarks showing up sporadically

[codeJockey]

We are using the registered version of the V4 print drivers. We send crystal reports to the virtual printers and everything works fine most of the time. However, every once in a while the "buy" watermarks will show up on the created PDF. We are at a loss to explain this, as the same exact report, same code path, always handing in dev keys, etc will sometimes result in watermarks. Any tips or information as to how we might be able to better diagnose this problem would be greatly appreciated.

[John - Tracker Supp]

Hi,

Can you please provide a little more info on how your application interacts with Crystal Reports and the output is sent to PDF-XChange - perhaps a code snippet with your dev keys integrated (please email - dont post here) to support@pdf-xchange.com with a link back to this forum post for reference and we will try and offer some suggestions - also the enviroment in which this is operating OS, PDFX Version etc) - thanks

[Paul - Tracker Supp]

hi codeJockey,

thanks for the email and code snippet. I will be passing tis on to the dev team and will keep you abreast of developments. Would you like to be notified by email or on this forum thread?

regards

[Paul - Tracker Supp]

Hi again codeJockey,

It looks like, from what we can see, that sometimes your application may be calling the 'wrong' printer. Do you have an end user PDF-XChange Print Driver installed in trial mode? Also what printer do you have set as default? If you make sure it is a physical printer there should be no inadvertently calling the PDF-XChange end user printer as the default.

let us know how that works

[codeJockey]

Hi Paul -

I do not believe that ther is an end-user version of PDF-XChange installed, but I will verify with our QA team. I'm not sure how it could call the "wrong" printer, as we are using the name of the printer returned via printer initialization that is done using the key? We have also tried sending the registration keys to the printer before every single print job (SetRegInfo) but that doesn't fix the problem either.

Thanks,
Scott

[John - Tracker Supp]

Hi Scott,

could I ask you to send us a screenshot of their installed printers - to be sure that there is just one PDFX printer and also not varying versions ...

Thanks

[codeJockey]

Hi -

When our application was not processing a document, we would not see a PDF-XChange printer in the list of installed printers. When we are processing a doc, we see our "Delphi"- named printer as created via the SDK and that printer goes away once the doc processing has been completed.

To ensure we are using a clean system, we have un-installed all PDF-XChange software from the machine (Windows 2008 Terminal Server). We then intstalled the driver via PDFX4SA_sm.exe (newest one, just downloaded from the Tracker site). After having done that, we are now seeing a PDF-XChange printer showing up in the installed printers area. When our application processes docs, we are still seeing the "Delphi" printer being added to the list and the PDF is still exhibiting the same behavior.

We have found a duplicatable pattern that involves sending several crystal reports to the PDF printer, with the final report containing an image (JPG) as part of the report data. The 1st time this pattern is executed, all reports render correctly. The second time the pattern is executed, the watermarks show up. If the report containing the image is anything but the last report, the watermarks never show up.

I have attached the requested screen shots of the installed printers; one before creating PDFs and another during.

Thanks,
Scott

[Ivan - Tracker Software]

Does your application exit immediately after printing? Or release printer's AX object?

[codeJockey]

Our application releases the printer and continues to execute.

We have discovered that if we add a small delay (~ 0.5 sec) between sending the last report (containing the image) to the PDFX printer & releasing the printer, we no longer experience the problem. We are hypothesizing that the PDF driver is still processing the final document when our app release the printer. This somehow puts the driver into an unstable state so that the next print job is rendered with the watermarks...?

[John - Tracker Supp]

Thanks - we now understand the issue and agree that the problem is as described - due to your app closing the connection to the printer as is normal, and thus removing the ability to print without re-establishing licensed access correctly.

we will consider alternative ways to handle this process and advise just as soon as we have found a mutually acceptable way to manage the process.

Thanks for your patience.

[mpatel]

Hello

Have your found the solution yet.

I am facing the same problem.

Thanks

[Tracker Supp-Stefan]

Hello mpatel,

Seems like there is no obvious solution so far

Regards,
Stefan

[rostg]

Hello,

Just checking if there is some progress on this issue.

Thanks.

[Tracker Supp-Stefan]

Hello rostg,

We have a ticket for this case (#422) so I will now speak with the dev guys to check if there are any updates, and will come back to you with any news on the subject.

Best,
Stefan

[Paul - Tracker Supp]

Hi Rostg,

the issue has been resolved for the V5 SDK. We are anticipating a release Friday the 18th of this month for the SDK. Please test this when it is available.