RE: Persistent Application Failure when Updating Book

[Jim Stauffer <JStauffer@xxxxxxxxxxxxxxxxxxxxx>]

Bart -

I experience something similar on Windows NT / FM 6. In my case it was the
addition of a generated List of Markers. The file would generate OK, but I
would get the Internal Error message if I tried to save it, or the book. The
only solution I found was to save the L of M as a MIF file the resave as FM.


I couldn't find anything on this in Adobe's Knowledge Base. I think there's
a book-level bug that Adobe hasn't yet acknowledged.

Jim Stauffer
Sr. Technical Writer
BeamReach Networks
Sunnyvale, CA
www.beamreachnetworks.com


-----Original Message-----
From: Bart Windrum [mailto:bart.windrum@DiogenesInc.com]
Sent: Wednesday, September 04, 2002 1:59 PM
To: Framers/Adobe; FrameUsers Short
Cc: fmerror@Adobe.COM
Subject: Persistent Application Failure when Updating Book


Framers,

Mac OS9.1/Frame7:

I am plagued with a persistent book update failure on a modest book and its
files. It contains, as separate files, (#ing scheme follows / ):
- front cover/A
- inside front cover/B
- generated TOC/i
- [13 files]/1, consecutive #ing from pervious file
- rear cover/Z

(btw I use this #ing scheme to make the PDF's goToPage process easier)

There are no cross references or text insets. I notice that the generated
TOC icon in the book is green/white rather than orang-ish (as it is in the
Finder). Total page count is about 70.

When attempting to update the book Frame almost always quits with the dialog
containing this lovely message:

Internal Error 7002, 1668596, 1673748, 1745216. FrameMaker has detected a
serious problem and must quit. A file named "FrameLog_[datestamp] has been
generated [snip]

And the file contents are:

 === Header Begin === Internal Error: 7002, 1668596, 1673748, 1745216
FrameMaker 7.0.0 for Power Macintosh Build: 7.0p492 Window System: Mac OS
Operating System: Mac OS (OS version not captured) Generated on: Wednesday,
September 4, 2002  2:41 PM To file: FrameLog_02.09.04_14.41.49 === Header
End ===
 === Stack Trace Begin ===  $1975f4  $198a14  $1aa140  $3084f4  $306608
$309a38  $16b4cc  $16e4fc  $16d9c0  $16c0dc  $1762c4  $3a5264  $398b38
$399c40  $453408  $453360  $39d2d8  $454c00  $454b64  $454cfc  $42eeec
$42ea94  $42e9c0  $11a690  $120470  $122870  $19cd8  $7e2c  $8c4c  $71cc
$40  $4bbc54  $c36e2f1c === Stack Trace End ===
 === Open Window List Begin === # not implemented === Open Window List End
===
 === Recent Commands Begin ===  $03e1 = Update  $02b0 = TableOfContents ===
Recent Commands End ===
 === Recent API Calls Begin === # not implemented === Recent API Calls End
===


I have not yet engaged in a conflict test via Conflict Catcher; before going
that route I wanted to query the list to see if anyone might shed light on
this crippling affair -- the only solution to which to date has been to
generate and manipulate a brand new TOC.

Of minor interest is that this is the only manual I've made so far that
contains numerous files to number/renumber; all the others, including our
150 page User Guide, contain only front/inside front/rear covers plus a
single file for the guts. Frame's inability to update uneventfully gives me
considerable pause when I consider a) how to manage our doc's growth and b)
that I know this app is used routinely in a far heavier-duty manner than my
small scenario.

__________
Bart Windrum
GUI Fit&Finish and Documentation
Diogenes Inc.
410 17th St. #1260
Denver CO 80202

720 904 2321 x125
fax 720 904 9032
Bart.Windrum@DiogenesInc.com



** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **

** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **