Skip to main content
_
_Tommy_Strandberg_
Participant
September 10, 2007
Question

Internal Error 7204, 6107874, 7775428, 0

  • September 10, 2007
  • 21 replies
  • 3495 views
I've seen that I'm not the only one faced with the same problem of Internal Error 7202 but I'm getting rather annoyed because it is now nearly impossible to update a book without a crash. Typical error message as shown below.

---------------------------
Error
---------------------------
Internal Error 7204, 6107874, 7775428, 0. FrameMaker has detected a serious problem and must quit.

A file named "c:\program files\adobe\framemaker7.2\FrameLog_07.09.10_08.44.05.txt" has been generated which contains information that may help Frame development improve the product for future releases.

Please describe your recent actions and send this, along with the generated file, to fmerror@adobe.com. Due to the volume of feedback, we are unable to respond to technical questions. For support, please refer to http://www.adobe.com/support.
---------------------------
OK
---------------------------

And after OK has been pressed

---------------------------
Adobe FrameMaker (Structured): FrameMaker.exe - Application Error
---------------------------
The instruction at "0x0034199f" referenced memory at "0x00000000". The memory could not be "read".

Click on OK to terminate the program
---------------------------
OK
---------------------------

I'm using FrameMaker 7.2b158 in an XP Windows computer including all the latest patches. I've implemented some of the suggestions made in the forum like saving all documents in MIF format and then in fm-format again but nothing helps. So far I've been a quite happy user of FrameMaker because of its stability and capability of handling large documents / books but the status now is worse I ever had with any other Microsoft product. The problem is not new for me, I had it also when I used FrameMaker 7.1 and in the beginning of using FrameMaker 7.2 but it happened very infrequent.

Sometimes, if I close FrameMaker and then re-start FrameMaker again before the update process, it works but it doesn't seem to be reproducible. Please not that I'm still working on the same document, a satellite user manual, although it's now much larger (about 20 files in book with a total page count of about 2500 pages).

Of course there is also a crash log, but I cannot interpret this.

Any ideas what is going wrong?
Cheers

Tommy Strandberg

EADS Astrium GmbH / Germany
    This topic has been closed for replies.

    21 replies

    _
    _J_A__Rehn_
    Participant
    July 11, 2008
    Hi Wendi Missagia. The answer is "yes, but...".<br />I traded several emails with Adobe with much optimism (since they<br />actually responded after I send the crash log)... but, ultimately <br />they didn't (couldn't?) help. I wrote a Perl script to process a set <br />of mif files, looking for duplicate XRef tags. In 60+ files I found <br />50+ duplicates (out of >4000 unique XRef tags). I had to locate/fix <br />them manually, giving each a unique ID. The crashing stopped (but I <br />still hear a ticking sound...). I use a ton of conditional text and <br />it seems that hidden duplicates don't cause the crash, which is good <br />because I have way too many of these to fix. I have seen the problem <br />and fixed it the same way in 2 books. When I asked Adobe why they <br />didn't detect/warn/prevent duplicates they did not respond. Same <br />response when I ask when they will update the UI... sigh.<br />Anticipating questions from others, I am reluctant to expose the <br />Perl script... it is a hack and I can't support it, etc. In the mif,<br />the search target is:<br /> <MType 9><br /> <MTypeName `Cross-Ref'><br /> <MText `everything here is part of the tag ID'><br />Finding the last part in > 2 mif files is the chore.<br />Good luck.
    _
    _m_dulin_
    Participating Frequently
    July 10, 2008
    I had a multitude of problems with Framemaker 7.2 crashing after installing InDesign CS3. I'm posting my current solutions here in case any of these tips or tricks help anyone.

    The Save As ...PDF no longer works. I have to take the long way around to generate a PDF.
    1. File/Print Setup.
    In Print Setup, choose Adobe PDF as the printer name.
    Select Properties.
    Uncheck the box "Rely on system fonts only..."
    OK
    2. File/Print.
    Make sure Print to File and Generate Acrobat Data are checked.
    Print.
    (generates a .ps file.)
    3. Double-click on the .ps file to kick off Distiller to generate the PDF.
    4. Then, I check my pdf to see if it is missing any text, especially in my graphics. If it is, I know it is time to clear out my fntcache.dat file and try again. (I need to do this about once a week.)
    5. To clear fntcache.dat:
    Go to c:\winnt\system32\ and search for hidden file fntcache.dat and delete it.
    6. Restart your PC - this is important!!
    7. Do Steps 1-4 again - and I have a final PDF!!

    Hope this helps somebody!
    _
    _Wendi_Missagia_
    Participant
    July 10, 2008
    To J.A. Rehn,

    We're having the same problem stemming from conditional text and x-ref tags. Have you found a work-around?

    Thanks!
    Wendi
    _
    _J_A__Rehn_
    Participant
    February 12, 2008
    Thanks Arnis, I did this update this AM after seeing it on the download site. Unfortunately, the problem still occurs.

    I would consider upgrading (i.e. paying Adobe for a less-defective
    version) but there is no guarantee that it will fix my problem.

    I have been a Frame user since before Adobe bought it, and I am very
    frustrated that the user interface remains so lame... I really wanted
    to boycot upgrading, at least until they allow me to do things like
    resize dialogs so I can see what I am selecting, etc.
    Now, I might have to pay for a bug fix...but will fix my problem?

    I feel like I'm being held hostage... years of cumulative work has
    suddenly become mostly unusable... sigh.
    _
    _J_A__Rehn_
    Participant
    February 12, 2008
    My crash is related to conditional text and XRef tags, possibly in
    tables. I am using XP-pro SP2, plenty of RAM (almost 500MB available
    after opening all files), plenty of swap, etc. I have all files open,
    etc. This has nothing to do with generating PDF (which always seems
    to work for me). I have tried doing .fm->.mif->.fm and the symptoms
    did not change. Using Frame 7.1p114, non-structured.

    The key is that everything works with all conditional test shown (not
    hidden). Hide some conditions, click certain links and BOOM!.

    When I Show all conditional text I can update the book, and all
    XRefs are resolved (no errors). When I Hide some conditions and update
    the book all XRefs are again resolved (no errors). But, I can reliably
    crash Frame 7.1 just by double-clicking on certain links, in certain
    source files, to an XREF tag located in a table (my book has 50+
    files, 10+ conditional text options, thousands of XRef tags, etc.).

    I can choose a specific link and confirm that the XRef tag exists and
    is not hidden, both before and after hiding any text. Somehow, I think
    that Frame gets confused when hiding some other tag... but even so, it
    shouldn't crash.

    The crash symptom indicates attempting to access address 0x0..00
    (sometimes 0x0..04), which is correctly illegal (I have some sofware
    experience). This is a classic software problem, caused by coding
    flaws. Could be a NULL pointer (a software thing which remembers were
    something is stored) or by not checking a designed-in static
    limit... when the limit is exceeded the code executes into data space
    (i.e. address 0x0..00). In either case (and there are other potential
    causes), the root cause is a Frame implementation error; i.e. bug,
    flaw, etc.

    So, having said all this, I could use some advice on how to approach
    Adobe about fixing this. I have a 100% reproducable problem but,
    except for sending in the crash log, have not yet tried to contact
    Adobe.

    Advice welcome.
    Thanks
    Arnis Gubins
    Arnis Gubins
    Inspiring
    February 12, 2008
    FYI, the latest version of 7.1 is p116 available here:
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=2715

    I doubt that Adobe will fix anything that is two releases back. You
    might be better off upgrading.
    _
    _m_dulin_
    Participating Frequently
    February 11, 2008
    Most files in the book get this error - sometimes. Once it starts occuring the only solution is to reinstall Frame. It seems like the files that have the problem include graphics - .gif files that have a text frame over the graphic. Graphics are inserted by reference.
    _
    _sherman_watstein_
    Participating Frequently
    February 4, 2008
    If the error mesasage still exists, start generating a PDFD for one file in a book at a time. By following this suggestion, you will be able to determinbe which file is generating the erro message/ Once the file is found, you can either try recopying the information onto a new file or start stripping the file down to find the problem.
    _
    _Rebecca_Officer_
    Participating Frequently
    February 4, 2008
    Do you have all the files in the book open when you generate the PDF? How are you generating the PDF (Save As or Print?) What FM 7.2 patch are you using? Can you make PDFs of the offending individual files okay?

    End of third degree. :-)
    Rebecca
    _
    _m_dulin_
    Participating Frequently
    February 4, 2008
    I've been battling the 7204 error message for several weeks now. I'm using Frame 7.2 on Windows XP Pro. I just need to put the finishing touches on this manual and send it to the translator, but this error has set me back several days. Certain files in the book get the 7204 error when I try to generate a PDF. So far I have uninstalled and reinstalled Frame twice and that has corrected the problem for awhile, but there must be a better solution!
    _
    _Marshall_Kult_
    Participant
    January 31, 2008
    I'm running FM8 on Windows XP. When trying to download an update from Adobe and install it, I get the message "Framemaker.exe was detected and needed to be closed". The update doesn't get installed. The message repeats at each attempt.
    Arnis Gubins
    Arnis Gubins
    Inspiring
    January 31, 2008
    Marshall,

    This really should have been posted as a new topic.

    Have you tried manually downloading the update from
    http://www.adobe.com/support/downloads/detail.jsp?ftpID=3837 and
    running the manual install?
    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices