We are using Aspose 21.1
We have a docx openxml file,that we have to insert a docx file to header,
after inserting the file, if we use word to open the file,
there are dialogs warning us there is an error about header,
but we can conitnue, and word can ignore the error and load the file properly.
in code, if we set word application invisible, word application can bypass these warnings and works properly.
but in aspose, it throws an exception, we can not bypass this error.
Is there any flags in aspose, so we can just ignore the error, or aspose can fix the issue automatically, or something Aspose can get a fix for to handle this without prompts?
The document appears to be corrupted and cannot be loaded.
Cannot find part ''.
Stack Trace:
at .(String )
at .( , String , ImportFormatMode )
at . β( )
at . β( )
at .(CompositeNode )
at .( )
at .( , )
at .(DocumentBase )
at .()
at . β()
at .()
at .()
at .()
at Aspose.Words.Document.(Stream , LoadOptions
@cdiggidydot
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): WORDSNET-25065
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
Please note MS Word also shows an error while opening your document but can recover the document. So it looks like the document is really corrupted.
Hi Alexey,
Thanks for quick response but our request was more around asking if there was an api call or something we can do to ignore the prompt and have it just try to create the PDF.
In our automation we can hide the prompt and get Word > PDF via Print to PDF option.
We were hoping for some similar option in Aspose which gives better quality pdf images etc. We think if we can programmatically ignore the prompt that Aspose could be able to as well. If it needs a fix in some new version to do this that would be helpful.
@cdiggidydot No, unfortunately, there is no option to bypass such problems in the file. Aspose.Words need to recover the file to read it. This is what is supposed to be done in WORDSNET-25065.
Is the notifyer accurate, before the comment seemed like the issue would not be addressed but the automated message says itβs fixed in latest version?