Framemaker crashes with internal error: 7104, 6062898, 7693379, 0 when saving as XML

Report · Feb 21, 2008

Hello all,

we have written a structure application for exporting XML from structure FrameMaker (7.1 p116). An internal error ""7104, 6062898, 7693379, 0" with the message: Allocation at "0x00341469" points to memory address "0x00000000" kept reoccurring during XML export of certain files. The "read" procedure could not be carried out on the memory.

After a number of test we have discovered that the reason lies in resolving external links.
Therefore we tested which links that cause the crash, renamed the corresponding source files, resolved the references again and low and behold - the XML Export worked for all our documents at some point.
Because we need a stable XML export and cannot accept the current state of continually renaming files, we have tried to limit the error and found out the following in the process.

Our structure application contains the instruction that external links should not refer to the original FM but to the corresponding XML.

External X-Ref:
Change Reference To .XML: Enable

During export therefore, FrameMaker has to perform a conversion of the source file names for external links.

If the source file name (.XML) for an external link is 16 characters long (including full path) or a multiple of 16 (i.e. "C:\Test\Doc1.xml"), FrameMaker crashes with the error mentioned above ("7104, 6062898, 7693379, 0").

If the length of the source file name (.XML) (including full path) is not 16 characters (or a multiple of 16 characters) the XML export is successful.

Best regards

Annett

Report · Feb 21, 2008

Hi Annett,

do you have a chance to test this behavior with FrameMaker 8? There is no chance for fixes to any previous versions, as bad as this is to existing processes.

Possible workarounds that come to my mind:

Using FrameMaker 7.2 one could use post-processing XSL to fix the file names in links.

Using FrameScript 5 one could create (most probably) a structure client that handles the link naming instead of FrameMaker doing it.

You could post-process the created XML files using XSL or other software, or include the renaming in the next phase of your processing chain.

You obviously invested quite a lot of time into this case!

- Michael Müller-Hillebrand

Report · Feb 21, 2008

Hi Michael,

Thanks for the workaround suggestion. Unfortunately we cannot do a test with FrameMaker ver. 8. At the moment it is not feasible for us to upgrade to this version.
Since we have to rework the XML output anyway, I think the best idea is to rename the source file data using a post-processing function.

Annett