Skip to main content
Participant
May 12, 2015
Question

Internal error "Framemaker has dectected a serious problem and must quit"

  • May 12, 2015
  • 2 replies
  • 4554 views

I keep getting an Internal error "Framemaker has dectected a serious problem and must quit." Can someone tell me what I need to do to correct this?

This topic has been closed for replies.

2 replies

October 23, 2015

This has happened to me with several different files. The file crashes and when I open the files the pictures are grayed out. I have repeatedly worked with Adobe support and they have not been able to help. I now save the files as a new name and then back again as I work to eliminate the rework when Frame crashes.I am at the point where I am going to use something else due to the lack of reliability. Support has tweaked, re-installed twice. I have created new files and cut and paste the text into it and so on. I am not doing anything fancy - just typing, inserting (not linking) pictures, working locally.

Jeff_Coatsworth
Community Expert
Community Expert
October 23, 2015

Are you getting any Missing Fonts messages? Any locked files? What version of FM? Is it up to date? Have you MIF-washed your files? Where are you maintaining your files – local or on a network?

October 23, 2015

Framemaker 10 and it is new. I just started using it and now have re-installed 4 times, twice by Adobe support. I work locally and do nothing out of the ordinary. I maintain everything locally. I do not link to a network.  I use few of the bells and whistles. It used to happen infrequently and now occurs daily with multiple files. I get a locked file which you cannot open because Frame doesn't interpret it as a Frame file. I also get one with an A5E error. I can remove the A5E error extension to open the file and recover the text but the images are grayed out and not recoverable. I have no missing fonts. What is MIF-washing? These are new files since I just started using Frame recently. I used it  years ago when it was Macromedia. Was happy to use it again but now rethinking this because of the rework and unreliability.

Jeff_Coatsworth
Community Expert
Community Expert
May 12, 2015

What version of FM & what are you doing at the time that’s throwing the error? Also, have you sent your error log into Adobe Tech Support?

Participant
May 12, 2015

No, I haven't sent this into Adobe Tech Support. I was trying to figure out how to do that when I got to this forum. Do you have any advice for me?

I have Framemaker 12 & when this happens I'm trying to "Update Book".

Jeff_Coatsworth
Community Expert
Community Expert
May 12, 2015

The error logs are created in a normally-hidden folder C:\Users\user_name\AppData\Roaming\Adobe\FrameMaker\12\ - send them to fmerror@adobe.com<mailto:fmerror@adobe.com>.

Make sure you’re all patched up in FM12 – you should be at 12.0.4.445. Does the error happen with all books or just one? Does the FM Console show any warnings or messages?