Use License.SetLicense to License Aspose.Words for .NET API

Aspose.Words Product Family
1

Hi, we recently updated our aspose pdf and words platform license.
After raising issues with the pdf library and the license we have those issues resolved, HOWEVER we are also having issue with the words license.

The following exception is being raised:

Set license for aspose word conversion error:System.InvalidOperationException: The subscription included in this license allows free upgrades until 26 May 2017, but this version of the product was released on 01 Dec 2019. Please renew the subscription or use a previous version of the product.
at ?.(Object )
at ?.()
at ?.(Boolean )
at ?.(Object )
at ?. ()
at ?.(Object , UInt32 )
at ?.(Boolean )
at ?.(Object[] , Type[] , Type[] , Object[] )
at Aspose.Words.License.SetLicense(Stream stream)
at …AsposeWordConversions.AsposeWordConversionsModule.Activated()

Our license file should be valid (some items removed for privacy):

License
Data
…
LicenseType: Developer OEM
LicenseNote: Limited to 1 developer, unlimited physical locations
…
OEM: This is a redistributable license
Products:
Product: Aspose.Words Product Family
EditionType: Enterprise
…
SubscriptionExpiry: 20201212
LicenseVersion: 3.0
LicenseInstructions: Using Your License - Purchase - aspose.com

2

Use License.SetLicense to License Aspose.Words for .NET API

@damong,

It seems that the License.SetLicense method is still picking the old license in your application. Can you please double check if you are providing correct path to new license file?

In case the problem still remains, please post your license file via private message. In order to send a private message with attachment, please click on my name and find “Message” button.

Fix System.InvalidOperationException Error upon Setting Aspose.Words License

We will then investigate the issue with your license file on our end and provide you more information. Please do not share your license file publicly in this forum thread.

3

Thank you and sorry for raising something that was in the end our issue. Unlike the PDF library which read the license from a file, the processing for the Words library ignored the license file and had a hard coded license :frowning:

Thanks to your help asking us to re-verify the case on our end, we have found the issue.

4

@damong,

It is great that you were able to resolve the Aspose.Words licensing problem on your end.
Please let us know any time you have any further queries in future.