Free Support Forum - aspose.com

Aspose.word.dll error "unclosed literal string" / "out of memory"

Hi
I tried to open attached docx file using below methods, but latest aspose.word.dll (18.5.0.0) thrown ‘out of memory error’ and version “16.7.0.0” thrown error “There is an unclosed literal string. Line 1, position 268434684.”
Can you please check whats wrong with doc file / dll ?

Document doc = null;
using (Stream stream = new FileStream(@“D:\Federal–Sec-tempPath.docx”, FileMode.Open, FileAccess.Read, FileShare.ReadWrite))
{
doc = new Document(stream);
}

        Document report = new Aspose.Words.Document(@"D:\Federal--Sec-tempPath.docx");

Thank you.

below is the link for zip file of docx file
https://thedigitalgroupsharangpatil.sharefile.com/d-sae2a739a3794614b

Hi
https://thedigitalgroupsharangpatil.sharefile.com/d-sae2a739a3794614b
I tried to open above docx file using below methods, but latest aspose.word.dll (18.5.0.0) thrown ‘out of memory error’ and version “16.7.0.0” thrown error “There is an unclosed literal string. Line 1, position 268434684.”
Can you please check whats wrong with doc file / dll ?

Document doc = null;
using (Stream stream = new FileStream(@“D:\Federal–Sec-tempPath.docx”, FileMode.Open, FileAccess.Read, FileShare.ReadWrite))
{
doc = new Document(stream);
}

    Document report = new Aspose.Words.Document(@"D:\Federal--Sec-tempPath.docx")

Thank you,

@sharang,

Thanks for your inquiry. We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-16820. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

@sharang,

Could you please share your working environment e.g. operating system, architecture (32 / 64 bit), .NET Framework? Thanks for your cooperation.

OS- Windows 7 Enterprise (Service Pack 1). 64 bit OS.
.net framework - 4.5.1
RAM- 16 GB

@sharang,

Thanks for sharing the detail. We will inform you via this forum thread once there is any update available on this issue.

@sharang,

Thanks for your patience. Could you please share what is your application project properties? It seems that you are using x86 target platform. Please use x64 to avoid the shared exception.