We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

License.setLicense Throws InvalidOperationException: License Parsing Error

I have the EXACT same problem. When I use the aspose-slides-22.6-jdk16.jar EVERYTHING WORKS. Usign the same code and aspose-slides-22.8-jdk16.jar I get the error

"com.aspose.slides.exceptions.InvalidOperationException: License parsing error --->
java.lang.IllegalArgumentException: 
Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized"

All other 22.8 aspose libs work great when updating. Please advise when a fix from Aspose is available.

We are using Java Version 17.0.3

@dfplive,
To investigate the case on our end, we need more details. Please share the following additional data and information:

I will see when we can find some time to prepare this for you. Our licenses is good yall made some change to ad in looking at the source compare on maven. it appears there is a bad reference to an xml parser.

to recap 22.6 works but 22.8 generates the error. so this is NOT our issue but yalls.

thank you

Here is the relevant part of the stack dump. We get NO such error in 22.6
in 22.8 we get
at com.aspose.slides.internal.oh.final.do(Unknown Source)
at com.aspose.slides.internal.oh.return.if(Unknown Source)
at com.aspose.slides.internal.oh.return.do(Unknown Source)
at com.aspose.slides.License.setLicense(Unknown Source)

@dfplive,
We will wait for the data and information mentioned above. Without this, we will not be able to check the problem. Thank you.

We are using Aspose.Total.Java license and just now ran into same kind of problem when updating Aspose libraries. We have confirmed the problem on Aspose.Slides v22.8 and v22.7 while v22.6 is OK. The error we get comes from AsposeLicenseLoader:

class com.aspose.slides.exceptions.InvalidOperationException: 
License parsing error ---> java.lang.IllegalArgumentException: 
Property 'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.

@dfplive, @tommyR,
It seems to be the issue is the same as described here:


This issue is related to the Linux configuration and can be resolved with the following commands:

yum install -y fontconfig
fc-cache --force

Please let us know if this helps you.