Free Support Forum - aspose.com

WordML save issue

We are having a problem with saving a WordML document. Saving it as docx works fine but doc creates a corrupted file and pdf throws an ArgumentOutOfRangeException. I tried with the latest version and still getting the error. Here is the stack trace:


at System.Collections.ArrayList.RemoveAt(Int32 index)
at x4adf554d20d941a6.x3a43ccb489970add.xd34fbbc45789217c()
at x4adf554d20d941a6.x3a43ccb489970add.xbc13914359462815(x56410a8dd70087c5 x5906905c888d3d98)
at x4adf554d20d941a6.x3c81b884cf5d3405.xef8721f06e48b9f3()
at x4adf554d20d941a6.x3c81b884cf5d3405.x408f4b7efc86fd49()
at x4adf554d20d941a6.xa268fdb9ca040dde.x408f4b7efc86fd49()
at x4adf554d20d941a6.xa268fdb9ca040dde.xc3819e13f60dd8e6(Boolean xfad304b5f8f3bb5b)
at x4adf554d20d941a6.x4e2f8bff72d83f71.xc3819e13f60dd8e6()
at x59d6a4fc5007b7a4.xcde671c53995c411.xd9db07500873ae98(Document x3664041d21d73fdc, xdeb77ea37ad74c56 xdfde339da46db651)
at Aspose.Words.Document.UpdatePageLayout()
at Aspose.Words.Document.x410db0f4a89a6ef1(Boolean x24af0daafcd8fb8c)
at Aspose.Words.Document.get_xcde671c53995c411()
at Aspose.Words.Document.get_PageCount()
at xf989f31a236ff98c.x6c74398bceb133f8.xa2e0b7f7da663553(x8556eed81191af11 x5ac1382edb7bf2c2)
at Aspose.Words.Document.xf381a641001e6830(Stream xcf18e5243f8d5fd3, String xafe2f3653ee64ebc, SaveOptions xc27f01f21f67608c)
at Aspose.Words.Document.Save(String fileName, SaveOptions saveOptions)
at Aspose.Words.Document.Save(String fileName, SaveFormat saveFormat)

I was able to shorten the file while still getting the same exception. You should be able to reproduce by saving the attached file as PDF.

Hi Recep,


Thanks for your inquiry. I have managed to reproduce the same issues at my side. I have logged these issues as WORDSNET-7640 and WORDSNET-7641 in our issue tracking system. I have linked this forum thread to the same issue and you will be notified via this forum thread once these issues are resolved.

WORDSNET-7640 : Exception while conversion from WordML to PDF
WORDSNET-7641 : WordML to Doc conversion issue. I have faced the Office file validation message in output Doc file. Please confirm this issue. Are you facing the same issue?

We apologize for your inconvenience.

Hi,

Is there an ETA for the fix of these issues?

This is a very critical issue for us as our client cannot print their bills. If we knew what in the WordML is causing the issue, we can possibly alter WordML to work around this problem until you provide a fix. Is there any chance you can provide us what is in the WordML causing the exception?

Thanks,

-Harun

We have Aspose.Total Site OEM license and we are in the process of getting enterprise support. Can you please escalate these issues as they are very critical for our clients? If you can at least tell us what in the wordml is causing the exception, we can modify that to work around the problem until we get a fix.

Thank you,

-Harun

Hi Harun,

Thanks for your inquiry and sorry for the delayed response.
Harun:
Is there an ETA for the fix of these issues?
This is a very critical issue for us as our client cannot print their bills. If we knew what in the WordML is causing the issue, we can possibly alter WordML to work around this problem until you provide a fix. Is there any chance you can provide us what is in the WordML causing the exception?
Regarding WORDSNET-7641, we have a good news for you that is this issue has now been resolved and its fix will be included in the next version of Aspose.Words (13.1) which is planned to be released by the end of this month. We will inform you via this forum thread as soon as the new release is published.

Secondly, our development team has planned the fix of WORDSNET-7640 to be integrated in Aspose.Words 13.2. This issue is currently in development. We will inform you as soon as this issue is resolved. We apologize for any inconvenience.

Moreover, the issue (WORDSNET-7640) occurs because there are stranded field characters in the document. When you look at your source xml, you will see that the first field start occurs an line 1926 in the header. Then there seems to be a couple of correctly formed fields. And then a field separator happens at line 3386 and a field end at line 4419.
If you remove those field separator and field end from the source xml, no exception occurs on conversion. The field is incorrectly formed, because the field start is in the header, and field separator elsewhere. Re-saving via Microsoft Word probably removes the incorrect field.

Best regards,

Hi Harun,


Thanks for your request. Please see my answer in the Enterprise Support forum here. This thread may not be accessible by the user ‘recep’; so, please use your ‘harundiri’ account for further proceedings.

Many thanks,

The issues you have found earlier (filed as WORDSNET-7641) have been fixed in this .NET update and this Java update.


This message was posted using Notification2Forum from Downloads module by aspose.notifier.
(3)

The issues you have found earlier (filed as WORDSNET-7640) have been fixed in this .NET update and this Java update.


This message was posted using Notification2Forum from Downloads module by aspose.notifier.
(1)

While the latest version fixes the issue in the document I sent earlier, it does not fix the issue completely as I encountered the same exception again when I did some tests with the newest release.


I am attaching a document which leads to the same exception when I try to save it as PDF.

Hi Recep,


Thanks for your inquiry. While using the latest version of Aspose.Words i.e. 13.2.0, I managed to reproduce System.ArgumentOutOfRangeException on my side. I have logged this issue in our bug tracking system. The issue ID is WORDSNET-7910. Your request has also been linked to this issue and you will be notified as soon as it is resolved. Sorry for the inconvenience.

Best regards,
Hi,
Is there any update on this issue? When can we expect a fix?

Thanks
Hi Recep,

Thanks for your inquiry. We have a good news for you that is WORDSNET-7910 has now been resolved and its fix will be included in the next release of Aspose.Words (13.3.0) which is planned to be released within next 1~2 days. We will inform you via this forum thread as soon as the new release is published.

Best regards,

The issues you have found earlier (filed as WORDSNET-7910) have been fixed in this .NET update and this Java update.


This message was posted using Notification2Forum from Downloads module by aspose.notifier.