One of our customers is experiencing an error when opening a certain DOC file using Aspose.Words for .NET 15.7. They inform us that the file can be opened in Microsoft Word without any error messages. Unfortunately the file is confidential, so they can’t send it to us.
Here is the full stack trace:
K:\New folder\Client.Email.01.0015.0183.doc
Aspose.Words.FileCorruptedException: The document appears to be corrupted and cannot be loaded. —> System.InvalidOperationException: Incorrectly read SPRM:D613. Expected 115, but read 48 bytes.
at .(Byte[] )
at .(Byte[] , TableStyle )
at .(Style , Int32 , Int32 )
at .(Int32 , Int32 , Boolean )
at .( , Int32 , Int32 )
at .(BinaryReader , , IWarningCallback )
at .()
at Aspose.Words.Document.(Stream , LoadOptions )
— End of inner exception stack trace —
at Aspose.Words.Document.(Stream , LoadOptions )
at Aspose.Words.Document.(Stream , LoadOptions )
at Aspose.Words.Document…ctor(String fileName, LoadOptions loadOptions)
at eDiscovery.Toolbox.Processor.AsposeTotal.Word.WordDocumentFactory.GetDocument(String filePath, Boolean loadRemoteResources) in D:\EDT\Dev\toolbox\trunk\Source\eDiscovery.Toolbox.Processor\AsposeTotal\Word\WordDocumentFactory.cs:line 20
at eDiscovery.Toolbox.Processor.PdfTiffConverter.PdfTiffConverter.Convert(String sourceFilePath, String destinationFilePath, SaveFormat saveFormat) in D:\EDT\Dev\toolbox\trunk\Source\eDiscovery.Toolbox.Processor\PdfTiffConverter\PdfTiffConverter.cs:line 190
at eDiscovery.Toolbox.Processor.PdfTiffConverter.PdfTiffConverter.ConvertToPdf(String sourceFilePath, String destinationPdfPath) in D:\EDT\Dev\toolbox\trunk\Source\eDiscovery.Toolbox.Processor\PdfTiffConverter\PdfTiffConverter.cs:line 65
at PdfAndTiffConverterGUI.MainForm.StartProcessingButton_Click(Object sender, EventArgs e) in d:\EDT\Temp\PDFConverterAspose\PdfAndTiffConverterGUI\MainForm.cs:line 143
Thanks
Hi Reuben,
Thanks for your inquiry.
We have just released a new version of Aspose.Words (15.9.0) here and I would suggest you please upgrade to the latest version. I hope, this helps.
If the problem still remains, please attach your input Word document here for testing. We will investigate the issue on our end and provide you more information.
Best regards,