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

Internal Error 7204, 6107874, 7775428, 0

  • September 10, 2007
  • 21 replies
  • 3503 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

    Show previous replies
    _
    _Philo_Calhoun_
    Known Participant
    September 11, 2007
    I'm glad it is working for you. I've made very large manuals with FM (pdf) without problems in the past myself. It was one of the most stable programs I owned. Even in the past though, I always used the shift key to open all files in the book before updating.
    _
    _Tommy_Strandberg_Author
    Participant
    September 11, 2007
    Thanks for the inputs; it seems to be working again. I'm really not a "hacker" but just a user and so far I've been very happy with FrameMaker which we use to generate manuals (which can be up to 5000 pages in size) for various satellites. It was really new to me that it is better to open all files before updating the book so this was a good input. By the way, the manual is structured.

    Concerning XP and NT, there the company policy dictates what we get and that's simply XP today ==> no choice.

    Thanks again for your inputs

    Tommy
    _
    _Philo_Calhoun_
    Known Participant
    September 11, 2007
    See post about error generating pdfs. I get the same error message about error reading 0X0000000. I have a new laptop and lots of RAM (4GB) and HD space (75 GB). I think this must be some bug in FM.
    R
    Russ Ward
    Legend
    September 11, 2007
    Sherman, sometimes I just have no idea what in the world are you talking about. Consider taking a little more time to compose decipherable English... your points might be better taken.

    Russ
    _
    _sherman_watstein_
    Participating Frequently
    September 11, 2007
    Russ- If you do an update Book to close files that have cross references, you will get error messages, you must always open ALL files. Since I avoid using Windows XP with FrameMaker, always Windows NT or 2000, a lot opf problems I read don't exist at any of the companies I've worked for.

    IS this manual structured or not? The error message seems to say yes?
    Suggest you go to your Search and do a search for Files and Folders and enter *.tmp. Delete ALL temp files found except those for the current date (these can not be deleted). Reboot and try iopening all files in your boo and let us know what happens. I find down loading files from SourceSafe and uploading a pain, and would rather work over the network any day. I never lost a file in 13 years when files on on main server.

    Tommy- The memory size you gave us is the Process memory, the amount MS uses when FM is loaded, it isn't the memory your system is using. What you need to look at is the Physical memory Available found under the Performance tab.
    R
    Russ Ward
    Legend
    September 10, 2007
    As a post-script, there really isn't any good reason not to open them anyway. FrameMaker will open them if you don't, because it can't operate on closed files.
    R
    Russ Ward
    Legend
    September 10, 2007
    Tommy,

    It seems that book-wide functions with closed files is simply an invite for a crash. This includes Find/Change and the spell checker too. It shouldn't be this way, but it is. As a rule, I always open all files before updating and have never seen a crash since.

    Russ
    _
    _Tommy_Strandberg_Author
    Participant
    September 10, 2007
    The FM files are kept under version control using Visual SourceSafe where the SourceSafe "library" is kept on a company server. When I work on the book however, I check-out all files to my local harddisk. When I open all files, which is possible, the FrameMaker Memory usage(task manager)is only 14.6 MB.

    After I opened all files, I tried to update the book and it worked, very fast fact. Maybe this is the solution.
    A
    Art Campbell
    Inspiring
    September 10, 2007
    For that size book, the amount of RAM may be marginal. Also, having a lot of space in your \temp directory would be important.

    Can you open all the files at once? Sometimes a delay in opening files across a network can generate that type of crash too, when FM times out waiting for the file to open or update. Graphics, both embedded or referenced can also be a problem if they're updated across a network.

    Art
    _
    _Tommy_Strandberg_Author
    Participant
    September 10, 2007
    2 GB

    Tommy
    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