FrameMaker crashes when saving a file as XML

An update -

So FM now appears to crash "sometimes" when saving as an xml file AND when saving the file in general. I have 3 machine with FramMaker installed, first with version 11 now with version 12. These 3 machines are all identical as far as SW running on them, etc... I have been unable to detect a pattern as to when FM will crash thus far. Sometimes it will crash when I try to save the file as an .xml file and sometimes it will save just fine. I have resorted to marking up the document a little at a time, saving the file, then trying to save as an XML file. It will work sometimes and other times it will crash. Sometimes it crashes when trying to save the .fm file other times it works; sometimes it will crash when I try to save the .fm file as a .xml file, other times it will work. About the only thing in common that I have found thus far is the fact that it happens with the same file over and over again; meaning that if I have a pool of 12 files that I need to load into FM and markup, 11 of the 12 files may work just fine and the 12 file will not - it will crash FM at some point in the markup/saving process every time. One might guess that the original file is somehow corrupt and that may be, but at this point I am not sure how I prove that is the case as FM seems to load it in just fine and I can save it right off the bat just fine. Does anyone know how I can prove that the structured file i receive initially is corrupt when it loads into FM fine? If we were causing some issue with the import of our modified EDD then why dont we have the same issue with the other 11 files in the batch as they all are using the same EDD?

I have sent my most recent log files to adobe tech support this morning. I have tried saving files on shared drives as well as on local drives. I have tried the same process on the other workstations with the same results.

Does anyone have ideas on how I can isolate a problem with the source file (structured doc) or on why FM is crashing when I perform these actions?

Thanks,

Gavin (Ryan)

Gavin,

Please forward any such log files (along with a brief description of what happened - especially include the fact that it worked on another machine with the same FM file) to fmerror@adobe.com for the engineers to analyse. If they find anything really weird in there, they will follow up with you.

It sounds like something on your machine isn't cooperating with FM, if the same file saves properly on another machine. Are there any differences in hardware, operating systems (32-bit vs 64-bit), background services, concurrent apps with the FM sessions, etc. ?