Skip to main content
SER617
Known Participant
Jun 30, 2021 1:38 PM UTC
Question

FM 2020 - Crashing When Publishing to Responsive HTML5

I have tried publishing a book to Responsive HTML5, and each time I get the "serious internal error" message. I am using an .sts file that we used in FM2015, but I clicked yes when FM 2020 asked about updating it. Has anyone else experienced this?

    16 replies

    Dino-Software Writer
    Participant
    Feb 9, 2022 2:42 PM UTC

    I had the same issue when publishing to HTML5. One of my books published correctly without issues. Another book that uses the same template and the same .sts file crashed each timed I published. Adobe support thinks it's something to do with the .sts file. However, if it worked with one book but not another, I doubted that the .sts file was to blame.

    In the end I copied one .fm file from the "good" book, deleted its content, then saved it as a "blank". I copied the content from files in the "bad" book one at a time into a blank file. 

    That did the trick. A bit tedious, but at least I was able to move foreward with the project. BTW, I had tried the BookWash utility but that didn't work.

    Translate
    Community Expert
    Winfried RengCommunity Expert
    Community Expert
    Feb 10, 2022 4:59 PM UTC

    Good that you found a solution.

    Sometimes, rarely, files can get corrupted, and then you should always try to move everything into fresh fils.

    MIF wash should consolidate files. I do not know, why this did not work here.

    Translate
    bernd_steffens
    Participant
    Feb 11, 2022 9:09 AM UTC

    By using MIF wash, it is important that you set the MIF files to read only in the file system after first running MIF wash. If you then run MIF wash a second tine, the MIF files are not changed, but the .fm files are regenerated from the MIF files.

    Translate
    Matt-Tech Comm Tools
    Community Expert
    Matt-Tech Comm ToolsCommunity Expert
    Community Expert
    Feb 8, 2022 11:17 PM UTC

    I've had issues with STS files that get updated to new versions. 

    If you can confirm that a new STS file resolves the crash, you're likely going to save time by going with the new STS file.

    The STS is a glorified ZIP, so you should be able to dig into the old file to copy/paste parts of it from the old file as needed.

    Personally, though, I'd go with your thought of opening the prev Fm and the new Fm side-by-side and grinding through it.

    Translate
    -Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
    Matt-Tech Comm Tools
    Community Expert
    Matt-Tech Comm ToolsCommunity Expert
    Community Expert
    Feb 8, 2022 11:20 PM UTC

    One thing to try first though...

    Whenever Fm crashes consistently, the first thing I do is create a new preferences file by renaming the 16 directory to 16-Feb8, or something similar.

    See https://techcommtools.com/find-framemaker-preference-folder/ for details

    Translate
    -Matt Sullivan, FrameMaker Course Creator, Author, Trainer, Consultant
    bernd_steffens
    Participant
    Feb 2, 2022 2:59 PM UTC

    I had also crashes with a lage FM project (more than 2000 pages) when publishing to Responsive HTML5 Help from FrameMaker (Version 16.02). I could solve the problem by generating .mif files using the BookMifWash menu command. After executing the BoofMifWash command, I set all .mif files to "read only" in the Windows explorer. Then I executed the BookMifWash command again. With this procedure, the original .fm files are converted to .mif (ansi format) and back agaain to .fm (binary format). I suggest that his "cleans" the fm files. As a result, the Responsive HTML5 Help was generated without crashing.

    Translate
    pulkitn
    Adobe Employee
    pulkitn
    Adobe Employee
    Jul 1, 2021 1:35 PM UTC

    Hi,

    If you facing any " serious internal error", I suggest you mail the ".dmp" file present at "%appdata%\Adobe\FrameMaker\16"  to fmerror-reports@adobe.com, Someone will surely assist you there.

    If the matter is not resolved or you still face issues, feel free to Email me ( sent email address over DM to you).

    Thanks 
    Pulkit Nagpal

    Translate
    SER617Author
    Known Participant
    Jul 1, 2021 3:16 PM UTC

    Thank you very much!

    Translate
    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity Expert
    Community Expert
    Jun 30, 2021 2:56 PM UTC

    Personally, I'd go the e-mail route - you have to think of the time differences involved.

    Translate
    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity Expert
    Community Expert
    Jun 30, 2021 2:29 PM UTC

    If you're getting an error message with a new doc and .sts file, then it's time to contact support - see https://helpx.adobe.com/contact/enterprise-support.other.html#framemaker for your support contact options.

    Translate
    SER617Author
    Known Participant
    Jun 30, 2021 2:54 PM UTC

    Thank you again for the help. The online support was unable to help me, so they are supposed to be giving me a call in the next 24 hours... Not sure if that will actually happen, haha. Thanks again!

    Translate
    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity Expert
    Community Expert
    Jun 30, 2021 2:11 PM UTC

    What's your point version of FM2020? Try as an experiment creating a new .sts to play with - if it works, then you know that your FM2015 one didn't upgrade properly. If that's the case, then you will have to either contact the FM folks for help or recreate your .sts settings (you DO have them all documented someplace, right?) 

    Translate
    SER617Author
    Known Participant
    Jun 30, 2021 2:23 PM UTC

    I am on version 16.0.2. I did not document the settings anywhere...sigh. Lesson learned. Thankfully though I do still have FM 2015 and can open the .sts files there to compare when recreating .sts files for FM 2020. I did create a new .sts file for this book and got the same result - serious internal error.

    Translate
    Jeff_Coatsworth
    Community Expert
    Jeff_CoatsworthCommunity Expert
    Community Expert
    Jun 30, 2021 1:42 PM UTC

    Assuming you're all patched up, have you tried creating a new .sts file to try out?

    Translate
    SER617Author
    Known Participant
    Jun 30, 2021 1:47 PM UTC

    No I haven't - I was hoping not to have to go that route b/c we have unique .sts files for all of our books. Do you know if there is a way to see all of the output styles (maybe a txt file??) that I currently have set for this .sts? My FM should be all up to date - we just upgrade this morning from FM 2015. Thanks for the reply!

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