Spire.Doc is a professional Word .NET library specifically designed for developers to create, read, write, convert and print Word document files. Get free and professional technical support for Spire.Doc for .NET, Java, Android, C++, Python.

Thu Oct 15, 2026 3:33 pm

I am trying out Spire.Doc 14.3 in Python 3.14.6 on Windows 10. The following is a code fragment:

doc = Document()
doc.LoadFromFile(filepath)
text = doc.GetText()

For one document (.doc format) the call to GetText() raises an exception, the details of which are as follows:

'Arg_NullReferenceException: at spr넊.spr䉞(IParagraph) + 0xd5\r\n at spr넊.spr䉞(IBody) + 0xd6\r\n at spr넊.
spr䉞() + 0x79\r\n at Spire.Doc.Document.GetText() + 0x62\r\n at Spire.Doc.AOT.NLDocument.Document_GetText(IntP
tr, IntPtr) + 0x4e'

The first of the exotic characters appears to be Unicode U+B10A, which is a Hangul character. There are no Hangul or Chinese characters in the Word document. I can open it in Word, and there is no sign that is is corrupted.

Is there any way round this, or do I just have to accept that some documents will fail to load?

amillington
 
Posts: 1
Joined: Wed Oct 14, 2026 2:32 pm

Fri Oct 16, 2026 4:00 am

Hello,

Thank you for reaching out and for the detailed report.

To help us reproduce and investigate the issue, could you please provide the sample .doc file that triggers the exception when calling GetText()? If you have encountered similar issues with other documents, please feel free to share those files as well, as this would help us better understand the scope of the problem.

You can send the document(s) to us via email at [email protected].

Once we have the sample(s), our team will look into it and get back to you with further findings. Thank you for your assistance.

Sincerely,
Amy
E-iceblue support team
User avatar

amy.zhao
 
Posts: 3046
Joined: Wed Jun 27, 2012 8:50 am

Fri Oct 16, 2026 10:42 am

Hello,

I have received the document you sent via email. Thank you for sharing it.

By testing your DOC file, I was indeed able to reproduce the issue regarding the text extraction failure. I apologize for any inconvenience this may have caused. I have logged this issue in our tracking system under the ticket number SPIREDOC-12120. We will keep you updated on the progress.

If you have any further questions, please feel free to contact us.

Sincerely,
Amy
E-iceblue support team
User avatar

amy.zhao
 
Posts: 3046
Joined: Wed Jun 27, 2012 8:50 am

Return to Spire.Doc

cron