Issue with setting Aspose Total License

Aspose.Total Product Family
1

IMPORTANT: Hello, we have an Aspose.Total license. In testing locally, we are able to get our application to correctly read the license and work with the associated Aspose products we use. However, when we deploy to a development environment, the Aspose license appears to not work correctly, as after converting a file the Aspose watermark is present and the converted file appears to be in trial mode. Is there a particular method we must use to set the Aspose.Total license in a deployed application? This is a time sensitive matter, any help is greatly appreciated. Thank you.

2

@drymers Fir of all please check the following points:

  • Make sure your call to SetLicense gets executed. Step through in the debugger.
  • Make sure your code does not catch an exception thrown by Aspose licensing code. For example, Aspose will throw if it cannot find the license.
  • Make sure the input documents do not already have the evaluation message. Aspose does not delete existing evaluation messages.
  • Make sure SetLicense is executed before you instantiate any Document object.

Also, please make sure the license is applied to every Aspose product you use in your application.

3

Hi Alexey, thanks for getting back to us. There appears to be issues with the setLicense method, or the license we were provided. We even changed our code to manually set each license before any Aspose code is called, and we are still having issues getting the license to set in our dev environment. The licenses are still successfully set in the debugger every time locally, but not in dev. Do you have any other troubleshooting suggestions?

4

@drymers,

I guess, either you are using an older version of Aspose API(s) with the latest license or the licensing code was not processed at all on your development environment (debug the licensing code and set some breakpoints to see if the license code was processed, please confirm). Make sure you are using the latest version of the API with the latest license and use the older license (if you have) with older Aspose API versions.

It’s worth noting that newer licenses are signed with sha256, while older licenses were signed with sha1. Therefore, there is a possibility that you are using an older version of the API with a newer license. If you want to use an older API version with a newer license, kindly contact sales to get an updated license (signed with sha1) to be used with older versions of the Aspose for .NET APIs.

5

Hello, thank you for the reply. Our license is signed with SHA256. What is the most recent version of the Java artifacts that is compatible with this version of the signed license?

6

@drymers,

It is best if you use the latest versions of Aspose for Java APIs with your license (signed with SHA256). Generally, the licensing module was changed/improved two years ago or even longer, but this may vary for different APIs. Therefore, new licenses might not work with older versions of Aspose APIs, and you will need to obtain an updated SHA1 signed license. Could you please provide details about which Aspose for Java APIs you are using? This way, we can inform you about the exact versions in which the licensing module was enhanced.

7

Sure, the dependencies are:
aspose-words: 22.7
aspose-cells: 21.6
aspose-pdf: 20.6
aspose-pdf-kit: 3.7.0
aspose-html: 20.6
aspose-page: 20.6
aspose-email: 20.6

Will these versions cause issues with licensing? If so, should we shoot to upgrade past the most recent major release?

8

@drymers,

I think versions older than 2 or 3 years might cause this issue.
e.g.,

aspose-pdf: 20.6
aspose-pdf-kit: 3.7.0
aspose-html: 20.6
aspose-page: 20.6
aspose-email: 20.6

We recommend to use newer versions of the APIs.

9

A post was split to a new topic: Exception: java.lang.NullPointerException: Cannot invoke “com.aspose.pdf.internal.pcl.parser.PCLParser.getOptions()” because the return value of “com.aspose.pdf.internal.pcl.composer.Composer.getParser()” is null