I've traced this down to a somewhat invalid footnote or endnote in the document. I mean it does not comply with the way a footnote should be stored in the DOC file according to my knowledge, but now since I've seen how it can be, I've added code that handles this situation successfully. I will publish a hotfix in the next 1-2 days.
This is fixed in Aspose.Word 3.3.1
I still get this issue with the 126.96.36.199 version of aspose. I uninstalled and then re-installed the product.
I have tried to load your document using Aspose.Word 188.8.131.52 and exception appears.
When I use 184.108.40.206 the document loads ok.
Check Version property of Aspose.Word reference in Solution Explorer. It should be 220.127.116.11. If not -remove the reference and add it again.
The new version appears to fix the image problem and both the MailMerge and ProtectDocument calls appear to succeed. However, once the user opens the files on MS Word 2003, and scrolls down to where the images are shown, MS Word throws an exception and indicates that the document must be repaired. Any ideas on this one?
We have been able to reproduce the problem. Please allow several days for working out a fix or workaround.
This problem is caused by images grouped with textboxes into group shapes on page 6 of the document. This is for the both images. Aspose.Word has trouble dealing with textboxes in groups at the moment.
To workaround, click on the image, right click and select Ungroup. Then it would also be a good idea to click on each textbox and pull their anchors to different paragraphs. This will help to avoid Z-order being lost since if several shapes are anchored to one paragraph, Aspose.Word might lose their Z-order and you end up with some textboxes below the image.
All problems with textboxes, groups and z-order will eventually be fixed in Aspose.Word. It's just an issue that can't be fixed easily, requires some good work.
All problems with textboxes, groups and z-order are now fixed since we have implemented a new graphics engine in Aspose.Words 4.0. Please try running your application with the new version.