"FrameMaker has detected a problem and must quit" Really?! - support for networked drives

rebecca officer rebecca.officer at alliedtelesis.co.nz
Wed Feb 13 12:54:08 PST 2013


Hi Kapil

As in the Framer's post below, Ken's been told by Adobe support that FM11 isn't happy with working across networked drives. This has - not surprisingly - created consternation on the list. It seems very unlikely to be true, but can you please reply and confirm or deny it?

Many thanks
Rebecca


>>> Ken Poshedly <poshedly at bellsouth.net> 02/14/13 9:32 AM >>>
FWIW,

I just learned from Adobe tech support (via phone call) that the permissions in 
FrameMaker 11.0 have been modified so that the data files should also be on the 
same hard drive where FM 11.0 is installed. Working across drives (FM here, data 
files there) is no longer an accepted practice -- at least not with FM11.

I guess this explains the flaky, intermittent nature of my coworker's FM crashes 
because that (the "wrong" way is just how we've been doing things here.

Incidentally, I'm still using FM 8.0 the "wrong" way and with no crashes.

-- Ken in Atlanta



________________________________
From: Ken Poshedly <poshedly at bellsouth.net>
To: techwr-l at techwr-l.com
Sent: Wed, February 13, 2013 10:47:05 AM
Subject: "FrameMaker has detected a problem and must quit" Really?!

To all,

Please excuse this x-posting (Framemaker list), but no replies at all from there 

so far.

My coworker is running FrameMaker 11.0 and is frustrated  because twice this 
morning, FrameMaker crashed on his terminal (luckily  creating recovery files, 
though).

The warning pop-up window that  displayed announcing this glorious impending 
shutdown stated "Internal  Error 11014, 8122692, 8122986, 10866845. . . "

We have looked at the extremely cryptic error log file that was generated and of 

course, it's as clear as mud to me.

Note  that my coworker prefers to keep his book and all member chapter files  
open. He also prefers to embed all his graphics so the various chapter  file 
sizes are MUCH larger than if the graphics were referenced. Thus,  the 
following:

Title page with copyright page -- 835 Kb (no graphics)
TOC -- 870 Kb (again, no graphics)
Section  1 -- 4,740 Kb
Section 2 -- 8,720 Kb
Section 3 -- 14,983 Kb
Section 4 -- 45,815 Kb
Section 5 -- 22,066 Kb
Section 6 -- 53,033 Kb

For instance, Section 6 is 89  pages in length with all graphics (strictly line 
art) embedded and the  file size is 53,033 Kb (that's a little over 53 
megabytes). In a  previous version of this manual (when the graphics were 
referenced), the  file size was just a mere fraction of this (perhaps 20 Kb or 
30 Kb).

His  computer is a "TRISTAR" pc, with an Intel Core2 Duo CPU, E8500 @ 3.16  Ghz, 

3.17 Ghz, 3.24 Gigabytes of RAM; running Windows XP Professional,  Version 2002, 

Service Pack 3.

So the questions:

    * What do those internal error numbers specifically mean?
    * Is/are the error/errors caused by a hardware problem or a software 
problem?
-- Ken in Atlanta
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
STC Vice President Nicky Bleiel is giving a free webinar on best practices
for creating mobile help.

Learn more: http://bit.ly/WNaCzd

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as poshedly at bellsouth.net.

To unsubscribe send a blank email to
techwr-l-leave at lists.techwr-l.com


Send administrative questions to admin at techwr-l.com. Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online 
magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email 
archives @ http://techwr-l.com/archives

NOTICE: This message contains privileged and confidential
information intended only for the use of the addressee
named above. If you are not the intended recipient of
this message you are hereby notified that you must not
disseminate, copy or take any action in reliance on it.
If you have received this message in error please
notify Allied Telesis Labs Ltd immediately.
Any views expressed in this message are those of the
individual sender, except where the sender has the
authority to issue and specifically states them to
be the views of Allied Telesis Labs.



More information about the framers mailing list