@harshit Could you please attach the problematic document along with code that will allow us to reproduce the problem? We will check the issue and provide you more information.
@harshit Thank you for additional information. Unfortunately, it is impossible to analyze the issue without the problematic document. According to the provided stack trace the exception occurs upon rendering some shape while converting the document most likely to HTML. But it is impossible to provide more information without the problematic document.
Please note, it is safe to attach the documents in the forum, only you and Aspose staff can download the files.
@harshit Thank you for additional information. Unfortunately, I was unable to reproduce the problem on my side using the latest 22.11 version of Aspose.Words. The document is properly converted to HTML without any exceptions on my side. Could you please create a simple console application that will allow us to reproduce the problem? We will check the issue and provide you more information.
@harshit Unfortunately, I cannot reproduce the problem on my side using your test application. Also, 13.10 version is quite old, it was released about 9 years ago. So I would suggest you to update to the latest version of Aspose.Words.
We are not able to replicate it however following things can help us
Can you check the template and let us know what item might cause this issue so that we can work on that?
What shapes are there which might result in this?
Can you run this template through performance testing in your R&D?
Any previous similar issues you got around this area? If yes, how you have resolved those?
Upgrading it to the latest version is a long process of approval and it will increase the testing scope. As of now, we are trying to understand the root cause so that we can create a workaround and keep our customers up and running.
@harshit I have checked your document. There are 3 shapes in it. Two of them are regular images and one shape is line shape with zero height. Probably this shape causes the problem on your customers side:
Document doc = new Document(@"C:\Temp\in.doc");
NodeCollection shapes = doc.GetChildNodes(NodeType.Shape, true);
foreach (Shape s in shapes)
{
Console.WriteLine(s.ShapeType);
Console.WriteLine(s.SizeInPoints);
}
Here is output of this code:
Image
{Width=468.05, Height=65.75}
Line
{Width=108, Height=0}
Image
{Width=206.2, Height=62.25}
But, unfortunately, it is hard to say for sure without ability to reproduce the problem.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
Enables storage, such as cookies, related to analytics.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.