I’ve already done some searching into this exception and all the suggestions say to use the latest version of Aspose.Words to fix it. I believe I’ve just downloaded the newest version as of today (15.7.0) and I’m still receiving the exception.
I’ve attached the document throwing the exception to this post.
Thanks for your inquiry. I have tested the scenario and have managed to reproduce the same issue at my side. For the sake of correction, I have logged this problem in our issue tracking system as WORDSNET-12306. I have linked this forum thread to the same issue and you will be notified via this forum thread once this issue is resolved.