Known Participant

Question

FM2019 crashes opening a formerly good .fm file

14 replies
1449 views
Translate

I have FM2019 15.0.8.979 installed - the latest version for that edition. I can open some of my (smaller) .fm files but my largest one crashes with Internal error 15084. I have sent the dump file to Adobe as requested but of course have not heard from them. Internal errors are always the fault of the app.

I have lots of backups of the .fm document of various vintages but most fail. I did get one to open but it looked very corrupted. I immediately created a mif file of this but when I tried to open the mif file, my PC spun for a couple of hours before I killed it.

I have tried the shortcut to avoid the checking on opening but that didn't help either.

Any advice please?

This topic is closed to new replies. Start a new post to keep the conversation going.

Bob_Niland

Community Expert

Although not likely the problem in this instance, another thing to try is reboot, particularly if you rarely shut the machine down and/or have have been using the Windows Hibernate feature in lieu of Sleep or Shut Down.

I have seen some peculiar behavior* in various apps, but mostly FM2019 & FM2020, the longer I go between reboots. And the problem invariably cannot be duplicated after a clean reboot.

* (like silently omitting an entire component file when rendering a book)

Translate

K.Daube

Community Expert

another thing to try is reboot,

I always shut down the system in the evening... Hibernation creates strange effects not only in FM. Therefore reboot is IMHO a first measure in strange situations.

Translate

K.Daube

Community Expert

Hi Kinabalu2,

I have FM2019 15.0.8.979 installed - the latest version for that edition.

How did you get this update ...979? I'm on ...973 and when I ask to update it says "Your app is already up to date.". As far as I know ...979 is a release candidate, but not yet listed in http://www.adobe.com/support/downloads/product.jsp?product=22&platform=Windows

Translate

kinabalu2Author

Known Participant

Interesting. I can't really remember but I'm pretty sure it would have been through the official update mechanism. I didn't go through any devious means to get it for sure. Maybe it was a mistake on Adobe's part or they have pulled it. I certainly would like to go back to a stable version. Is that possible?

Translate

W

Winfried Reng

Community Expert

Download one of the latest version (in my rememberance update 7 had some bugs, but I am not sure) from here:

https://supportdownloads.adobe.com/product.jsp?product=22&platform=Windows

Test, whether this is really a full setup or only an update. (At least until FM 2017 the updates were just an update of the latest version.) If this is a full setup, then uninstall FrameMaker 2019 and install this download.

Then go to Help | Update and update to the current version.

Translate

LinSims

Community Expert

Did you save from FM2020 to FM2019, or FM2020 to MIF? I suggest saving to MIF and then opening in 2019. Make sure you backup the MIF file somewhere.

Translate

kinabalu2Author

Known Participant

Thanks for your reply.

I saved from FM2020 to .fm(2019) and to .mif and to .mif(7.0).

None of these worked - they all gave the same internal error 15084. So yes, I did save to mif and opened in 2019.

I get the following message in the console when opening both 2020 and 7.0 mif files:

<filename>.mif (13519) Invalid opcode: DFNoteKeepWithAnchor - Skipping these characters: 0>---Done skipping.

With the 2020 mif file, the above error number changes from 13519 to 14004 but the message is otherwise the same.

Translate

kinabalu2Author

Known Participant

Update on the above. I installed a trial version of FM2020 and read in the offending document OK with that. I saved as FM2019 format but got the same error as above when I tried to open it in FM2019.

Translate

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.