We have the following scenario:
1) Several docx files are processed by the MailMerger to fill some MergeFields.
2 a) On a first approach, we then put the main document part content Objects together to perform a manual concatenation merge.
2 b) On a second approach, we tried the enterprise edition to perform the merge.
Both a) and b) generate invalid hexBinary for paraId and textId of a paragraph.
The approach a) additionally duplicated bookmarkStart and bookmarkEnd ID's, that should be unique.
The validation against Word 2010 with OpenXML Productivity Tool stated the problems above.
As a result, we are currently not sure how to guarantee a valid, non corrupt docx file. We encountered in both situations "corrupt" docx files.
The introduction of the enterprise trial edition improved the situation, but the watermarks itself and a numbering generate the hexBinary problem.
Can the invalid hexBinary id's cause a corrupt docx and make the document not open in Word ?
Is there a different behaviour possible when opening the docx from the browser or from file system ?
EDIT. removed attachment.