Problem with License Watermaking
Problem with License Watermaking
Hi,
We are using NovaPDf SDK v71.1 Build 341.
And we have acquired license for novaPDF OEM Single Application License 7.x
we are using the following code to initialize NovaPDFOptions
myNovaPDFOptions = new NovaPdfOptionsClass();
//Here i pass the license key and other registration information
myNovaPDFOptions.Initialize(PDF_PRINTER_NAME, NOVAPDF_REGISTRATION_NAME, NOVAPDF_LICENSE_KEY, NOVAPDF_APPLICATION_NAME);
myNovaPDFOptions.InitializeOLEUsage("InfoPath.Editor.2");
myNovaPDFOptions.LicenseOLEServer();
After that we set the other profile settings using SetOptionString2 and SetOptionLong2 APIs.
Initializations is done only once, but profile updation before each print job.
The print call is initiated through Infopath form control.
The issue is license information is printed on the footer for some print jobs. We are not able to identify any use case. In some machines this doesnt happen at all, in some, it occurs randomly, and in some other it occurs always.
Is there a problem with the code, or is there anything else to be done.
We are using NovaPDf SDK v71.1 Build 341.
And we have acquired license for novaPDF OEM Single Application License 7.x
we are using the following code to initialize NovaPDFOptions
myNovaPDFOptions = new NovaPdfOptionsClass();
//Here i pass the license key and other registration information
myNovaPDFOptions.Initialize(PDF_PRINTER_NAME, NOVAPDF_REGISTRATION_NAME, NOVAPDF_LICENSE_KEY, NOVAPDF_APPLICATION_NAME);
myNovaPDFOptions.InitializeOLEUsage("InfoPath.Editor.2");
myNovaPDFOptions.LicenseOLEServer();
After that we set the other profile settings using SetOptionString2 and SetOptionLong2 APIs.
Initializations is done only once, but profile updation before each print job.
The print call is initiated through Infopath form control.
The issue is license information is printed on the footer for some print jobs. We are not able to identify any use case. In some machines this doesnt happen at all, in some, it occurs randomly, and in some other it occurs always.
Is there a problem with the code, or is there anything else to be done.
-
- Posts: 286
- Joined: Wed Dec 16, 2009 12:46 pm
Re: Problem with License Watermaking
Hello,
We have tried to search your details on the novaPDF version purchase but did not find any.
Please send us the details of your novPDF transaction along with the exact serial key you have used to [email protected] so we can try to troubleshoot the issue.
Thank you for understanding.
We have tried to search your details on the novaPDF version purchase but did not find any.
Please send us the details of your novPDF transaction along with the exact serial key you have used to [email protected] so we can try to troubleshoot the issue.
Thank you for understanding.
Follow us to stay updated:
- Newsletter (get a discount for subscribing): https://www.novapdf.com/newsletter.html
- Facebook: https://www.facebook.com/novapdf
- Twitter: https://twitter.com/novapdf
- Linkedin: https://www.linkedin.com/showcase/novapdf
Re: Problem with License Watermaking
Hi,
The initialize method throws an exception, if registration key is not proper.
So if initialize call is executed without any issues, that means registration details are fine. Is that right?
And also, as i said, sometimes the watermarking is not coming. So that does mean that the reistration details given through code is proper?
We just received registration key and registraiton name when we purchased the license.
One parameter for initialize method is application name. This application name can be anything.. right?
Another thing is about order of initializing the control which initiates print and Initialize API call.
we are printing a document that is loaded in Infopath Form control, and this control initiates print.
The code in my first post is executed first and then the Infopath Formcontrol is created.
I am using a 64 bit machine.
Thanks and Regards,
Roshni.
The initialize method throws an exception, if registration key is not proper.
So if initialize call is executed without any issues, that means registration details are fine. Is that right?
And also, as i said, sometimes the watermarking is not coming. So that does mean that the reistration details given through code is proper?
We just received registration key and registraiton name when we purchased the license.
One parameter for initialize method is application name. This application name can be anything.. right?
Another thing is about order of initializing the control which initiates print and Initialize API call.
we are printing a document that is loaded in Infopath Form control, and this control initiates print.
The code in my first post is executed first and then the Infopath Formcontrol is created.
I am using a 64 bit machine.
Thanks and Regards,
Roshni.
-
- Posts: 286
- Joined: Wed Dec 16, 2009 12:46 pm
Re: Problem with License Watermaking
Hello,
If your application is build on 32 bit then I suggest you add next call before printing EACH document:
pNova->LicenseApplication(“SPLWOW64.EXE”)
This is a module that converts 32 bit printing calls to 64 bits and needs to be licensed in these situations.
You can leave this call always, don’t have to check if you run on 64 bits.
Thank you.
If your application is build on 32 bit then I suggest you add next call before printing EACH document:
pNova->LicenseApplication(“SPLWOW64.EXE”)
This is a module that converts 32 bit printing calls to 64 bits and needs to be licensed in these situations.
You can leave this call always, don’t have to check if you run on 64 bits.
Thank you.
Follow us to stay updated:
- Newsletter (get a discount for subscribing): https://www.novapdf.com/newsletter.html
- Facebook: https://www.facebook.com/novapdf
- Twitter: https://twitter.com/novapdf
- Linkedin: https://www.linkedin.com/showcase/novapdf
Re: Problem with License Watermaking
Thank you so much.
I went through the following link
http://www.novapdf.com/kb/distributing- ... 4-337.html
The printing module is build in 32 bit environment and run on 64 bit platform.
We will check it out with the solution mentioned in the link.
I went through the following link
http://www.novapdf.com/kb/distributing- ... 4-337.html
The printing module is build in 32 bit environment and run on 64 bit platform.
We will check it out with the solution mentioned in the link.