Aspose.Words licensing issue

Hi @Amjad_Sahi

could you also help us with an Aspose license issue, although we have a valid Aspose.Total for .NET with LicenseType Site OEM (OrderID: 220401133737).

When we deploy our Microservice that uses Aspose.Words locally it works just fine with Aspose.Words version “22.10” and the new license, as soon as I deploy the service in one of our Azure AKS Cloud environments we get the error: “Build with a trial version of Aspose.Words. To discover the full version of our APIs, please visit Professional On-Premise and Cloud-based solutions for working with Word document formats


See screenshots.

Have we reached any limit for this license?
In the last years we used the same license type and had no problems. Could you check the reason for this? I can also provide a Google session to show the problem.

Using the same license for an older Aspose Version from 2021 works also just fine :thinking:

@pwcagde 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.Words licensing code. For example, Aspose.Words will throw if it cannot find the license.
  • Make sure the input documents do not already have the evaluation message. Aspose.Words does not delete existing evaluation messages.
  • Make sure SetLicense is executed before you instantiate any Document object.

Also, please make sure your license allows free upgrade to 22.10 version of Aspose.Words. Every Aspose license provides one year subscription for free upgrade to any version released during this time. You can open the license file in Notepad (but take care not to modify and save the license file or it will no longer work) and see the SubscriptionExpiry field.

<SubscriptionExpiry>20220218</SubscriptionExpiry>

It means that you can free upgrade to version of Aspose.Words published before 02/18/2022.

Hi Alexey,

we have found the problem. It was a helm/Kubernetes permission issue when using the license secret on our side. After we fixed the issue, our new license seems to work in all environments. Thanks for the quick response

1 Like