Skip to main content
Known Participant
June 25, 2021
Answered

FM2019 Hard Crash when opening Book file

  • June 25, 2021
  • 3 replies
  • 462 views

Need some guidance here:

Any time I try to open a Book file with FM2019, the program hard crashes. Even trying to create a New Book will crash FM. Opening a Book file from a different folder has the same effect: Frame 'thinks' about it for a minute or so, then 'trips over its feet and falls on its face'.

 

This behavior just started a week ago; a removal and reinstall didn't help. I do have one hard-and-fast restriction: I cannot share Book files as they are proprietary. 

 

I'm running out of hair to pull out; any help is much appreciated. Thanks to any and all who can help.

    This topic is closed to new replies. Start a new post to keep the conversation going.
    Correct answer Winfried Reng

    When this started now, something had to happen.

    Is your FrameMaker version up-to-date? What's the exact version number?

    Can you open book files, when you deactivate your anti-virus software?

    Does FrameMaker create any dump files or crash logs? These are here:

    c:\Users\xxx\AppData\Roaming\Adobe\FrameMaker\15\

     

    You could also close FrameMaker and rename this folder from 15 to e.g. 15_backup and then start FrameMaker again. FrameMaker will recreate this folder.

    Or do the same with the Linguistics folder:

    AppData\LocalLow\Adobe\Linguistics

    Sometimes this helps.

     

    Best regards

     

    Winfried

    3 replies

    Winfried RengCommunity ExpertCorrect answer
    Community Expert
    June 28, 2021

    When this started now, something had to happen.

    Is your FrameMaker version up-to-date? What's the exact version number?

    Can you open book files, when you deactivate your anti-virus software?

    Does FrameMaker create any dump files or crash logs? These are here:

    c:\Users\xxx\AppData\Roaming\Adobe\FrameMaker\15\

     

    You could also close FrameMaker and rename this folder from 15 to e.g. 15_backup and then start FrameMaker again. FrameMaker will recreate this folder.

    Or do the same with the Linguistics folder:

    AppData\LocalLow\Adobe\Linguistics

    Sometimes this helps.

     

    Best regards

     

    Winfried

    K.Daube
    Community Expert
    Community Expert
    June 27, 2021

    Eric (if I take it right), try this:

    - In FM-15 (aka 2019) open a good document or create a new one

    - Use ESC, o, H (heroic open) to get a prompt for the file selection

    - Select the book file in question

     

    This function can open many sorts of damaged FM files - but miracles are not always possible.

    See also https://www.daube.ch/docu/files/compendium.pdf#page=507 Open damaged file anyway.

     

    Known Participant
    June 28, 2021

    Yes, it's Eric... Sorry for not signing that; I was at my wit's end. 

     

    More details:

    FM version is 15.0.8.979.

    Full de-install by our Desktop Services guys, fresh reinstall. 

     

    Opening an ordinary file and then trying the Herioic Open brings no joy. It's as if FM is ignoring book files completely; even trying to create a New Book brings no action. 

     

    I am limited as to what file information I can share as I work on secure materials.

     

    To answer Winfried, below:

     

    Problems started a week ago, with no warning. Our machines are remote-controlled by the Corporate Desktop Services people; I have absolutely NO say as to what antivirus stuff is active or inactive. I have literally unlocked the machine on some days to find it changed. 

     

    FIXED IT!!!

     

    The problem was a corrupted 15 folder! 

     

    I had not thought to have FM recreate the folder; I had done it so often with the so-called "2020 Version" that I completely forgot about it. Twenty years of 'swearing at Frame', and you'd think I would have remembered this!

     

    Marking Winfred's response as CORRECT, so that others with this problem will have a solution available.

     

    Thanks again and back to work,

    Eric