Skip to main content
JonBe
JonBe
Inspiring
February 10, 2022
Question

Odd corruption with a FrameMaker 2019 document

  • February 10, 2022
  • 2 replies
  • 310 views

I have had to resolve a problem with a document that would cause FramerMaker to crash when either the book was updated or validated.

The document was originally in 2019 MIF format with a .fm extension. The evidence of the corruption was visible after the following steps:

  • Opening document in 2019 MIF format and save as a 2019 document.
  • Close the document and re-open, and then save in 2019 MIF format. 2019 with update 8 crashed with a 15084 error, while 2020 (2020 MIF format) with update 1 crashed with a 16014 error.

Deleting the content of the document, but not any master pages, made no difference.

The only wrinkle was that, when the document was not closed after it was saved in 2019 document format, FrameMaker would not crash, when the document was subsequently saved in MIF format.

 

The resolution in this case was to start with an empty template, copy the content across from the mif, set any variables, and replace the document. This new document could then be saved in 2019 MIF format without FrameMaker crashing. As well the crashes when the book the document was part of, was validated or updated, no longer occurred.

 

A bit odd hey!

 

Jon

 

This topic has been closed for replies.

2 replies

Matt-Tech Comm Tools
Community Expert
Matt-Tech Comm ToolsCommunity Expert
Community Expert
February 11, 2022

Yup, when dealing with a corrupt doc, sometimes copying content to a new doc will resolve the issue.

I've used that trick in lots of apps, including Photoshop.

 

Glad to hear you got past the corruption. Luckily, the bad code was somewhere in the definition of master pages, reference pages, or other noncontent things!

-Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
QuintinSeegers
QuintinSeegers
Legend
February 20, 2022

We run into simlar problems with some of our FM files. Some of our files go back to FM7, resaved in newer versions over the years. Occationally, one of them will decide not to play nicely anymroe. Then, the only option is to save it as MIF, open the MIF file, copy the content into a new FM document.

 

Though, we sometimes do get crashes with brand new documents when importing either Variables or ConditionalText settings from another document.

frameexpert
Community Expert
frameexpertCommunity Expert
Community Expert
February 10, 2022

Hi Jon, Very odd! Note that what appear to be error codes are just the FrameMaker version numbers: 16014 is FrameMaker 2020, update 1 (16.01.something) and 15084 is FrameMaker 2019, update 8 (15.08.something). -Rick

JonBe
JonBeAuthor
Inspiring
February 10, 2022

Hi Rick,

 

Thanks for pointing that out. How very FrameMaker like to use the version as a error number! IMHO the crash dialog should be replaced with an 'Oops something went wrong' with clickable links rather than the current verbose version where the text is not selectable. I find the FrameLog version in %appdata%Adobe\FrameMaker\[n]\ to be no more useful and any eventlog entries the same.

 

Jon

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices