Return of the dreaded FrameMaker error
December 17th, 2004
FrameMaker 5.5 used to intermittantly crash, with a large but unhelpful error message that would make your heart sink every time it appeared.
I never encountered this error in FrameMaker 7.0, but now, in 7.1, it has returned. For the third time this week, the dreaded error has appeared:
It occurs with no warning and with no apparent reason (i.e. it doesn't happen when you do something in particular). The FrameLog text file just contains a lot of stack information that sheds no light on the problem for a non-Frame-programmer. The error message suggests emailing the log file to Adobe. But do the handful of underpaid coders out in India really want to get emailed this information. From my own experience of software development, I doubt it.
Potentially similar posts
- Use the existence of a file on the server to determine Javascript behaviour in the browser – November 2010
- Video plays locally but not on the web – August 2010
- The four levels of software support – June 2010
- Does online help need an overall structure? – June 2010
- Madcap Flare 6 breaks PushOK SVN plugin – March 2010
