Using temporary license causes same as evaluation copy, Aspose.Total for Java

<?xml version="1.0"?> xxx xxx Developer Small Business 1 Developer And 1 Deployment Location 250131135912 1137374 This is not a redistributable license Aspose.Total for Java Professional 64a49c9e-be92-4828-95a1-2ae6a3241d56 20260203 20250303 This is a temporary license for non-commercial use only and it will expire on 2025-03-03 3.0 https://purchase.aspose.com/policies/use-license xxx

Created with an evaluation copy of Aspose.Words. To remove all limitations, you can use Free
Temporary License Purchase Temporary License - aspose.com

sales@aspose.com can/want not help (… I think whether to buy or not ), but

" While we are happy to assist with any inquiries about pricing or licensing, please note that for in-depth technical assistance, we recommend visiting our Free Support Forum "

We have thousands of files and we don’t know how to filter these incorrect files.
I wonder if this bug can occur RANDOMLY even with a paid license, because it is random even with a temporal license.

@jouko.tiihonen,

If you are encountering evaluation watermarks in documents while using Aspose.Words for Java with a 30-day Temporary License, ensure the license is properly set at the beginning of your program and before invoking any other Aspose APIs. Refer to the documentation on applying or setting the license for guidance. Additionally, always use fully qualified naming (e.g., com.aspose.words.License) when invoking/working with the “License” class, as all Java APIs in the Aspose.Total for Java package include this class. For multi-threaded applications, consider moving the licensing code to the application level, such as, within a static application class constructor or relevant place. This ensures the licensing code is executed at the start and once during the application’s lifecycle, preventing issues with license initialization.

No, the bug does not occur with the paid (professional) license. Aspose’s licensing module operates smoothly and without issues. In most cases, the problem originates on the client’s side and should be resolved accordingly on client’s end.

Let us know if you still find the issue.

Since the conversion of html to pdf was successful by exporting the contents of the license file to class com.aspose.pdf.License, I had no doubt that other conversions would work as well, because the product is Aspose.Total.

Now the information in the license file is also exported to the License categories of the following “sub-applications”:
com.aspose.cells.License, com.aspose.imaging.License, com.aspose.html.License

Works now. Thank you for your help!

@jouko.tiihonen,

It seems your issue is sorted out now. Please feel free to write us back if you still find any issue or have further queries or comments. We will be happy to assist you soon.