Skip to main content
_
_Derek_Fosberry_
Participant
February 25, 2009
Question

FrameMaker 7.1 crashes at startup

  • February 25, 2009
  • 7 replies
  • 761 views
When I start FrameMaker, either from the Start menu or from a .fm file, I get:

Internal Error 7104, 6063074, 7693891, 0. and the application closes.

I run version 7.1p116 under Windows XP SP3.

Yesterday Frame worked OK, today I can do nothing.

I googled and it may be related to using Search and Replace at book level (see http://en.allexperts.com/q/Adobe-Framemaker-1523/FrameMaker-crashes-performing-find.htm).
I did indeed use Search and Replace at book level yesterday (they changed the product name). But I cannot even start Frame any more.

I de- and reinstalled Frame (twice) but that did not help. Could there be something left in the registry? Does anyone have any suggestions?

Hope someone can help, product release is scheduled for 1 March.

--- Derek
    This topic has been closed for replies.

    7 replies

    A
    Anonymous
    February 26, 2009
    Opps, Derek, I mis-read your last comment as a nonchalant "I shall discover it all by trial and error" and was just about to beg you to move up to FM9, where I believe there's much more room for "discovery" of one sort or another ... <g>
    _
    _Derek_Fosberry_Author
    Participant
    February 26, 2009
    That's something you can philosophise over. The directory <br /><br />C:\Documents and Settings\<username>\Application Data\Adobe\FrameMaker\7.1<br /><br />also contains a couple of INI files, with things like display size and screen layout. I think the installer should ask you whether or not to retain these data, or at the very least should tell you that these files exist and where they are. <br /><br />I had to discover it all by trial and error.<br /><br />--- Derek
    R
    Russ Ward
    Legend
    February 26, 2009
    It interests me to know that a personal dictionary persists through an uninstallation/reinstallation. Maybe the deletion of the entire installation folder afterwards is good additional advice when we recommend a reinstallation. I suppose any files that were changed or added simply hang around after an uninstall.
    _
    _Derek_Fosberry_Author
    Participant
    February 26, 2009
    Sheila and Art, thanks for thinking along. <br /><br />However it was something else. After about a day of trying this-and-that found that my personal dictionary contained the entry:<br /><br />-airbags)<br /><br />and that was crashing Frame. I removed the right paren and all seems to be sweetness and light.<br /><br />For reference the dictionary is located in:<br /><br />C:\Documents and Settings\<username>\Application Data\Adobe\FrameMaker\7.1\user.dct<br /><br />I remember clicking "Learn" for the word "airbags" during a spellcheck, and presumably Frame had included the paren in the selection.<br /><br />I shall report it to Adobe.<br /><br />--- Derek
    A
    Art Campbell
    Inspiring
    February 25, 2009
    And if you are indeed running the unpatched CD version, install the patch to get to the level you cited in your initial message...

    Two other things to check are how much free temp space you have on your local hard drive and to a lesser extent how much RAM is on your box.

    Also, make sure you open all files in the book before doing book-spanning activities so you can eliminate network delays and timeouts as a possible cause.

    Art
    A
    Anonymous
    February 25, 2009
    FrameMaker uses the system printer, and the best results are obtained by having the Acrobat PDF printer as default printer, as you have read.

    There is a free third party utility called "SetPrint" at
    http://www.sundorne.com -- look for the FrameMaker section -- that will let you set the printer just for and when FM is opened, which takes a lot of the nuisance away from remembering to change it specifically for FM.

    As far as the crashes go, did you reboot between uninstall / reinstall?

    Are you colleagues all using SP3?
    _
    _Derek_Fosberry_Author
    Participant
    February 25, 2009
    Update: at some stage (probably when I re-installed Frame) the error message changed; it is now

    Internal Error: 7104, 6062898, 7693379, 0

    and I am running build 7.1p114 (the version that came from the CD).

    Two colleagues have Frame and it runs without problems; one says that he regularly uses Search and Replace at book level so that sounds like a red herring.

    In the release notes for 7.2 I find a description of my problem (issue 1054343) but the suggested workaround (use AdobePDF as default printer) does not help.

    --- Derek
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices