"FrameMaker has detected a problem and must quit" Really?!

Wed Feb 13 13:10:08 PST 2013

Interesting ... I tried what your coworker did (steps 1 to 4 below), without any problems accessing/reading/writing network server FM files. It is a GigEthernet network, accessing folders to which I have read/write permission, on a fast server, etc., etc., etc.

Of course, I _normally_ just run with my data files on a separate drive ... since it is a laptop and I am not always on the corporate network here. The network server is simply a backup archive for my files.

I suppose if the "keep all data files local" work-around works for you, then continue using it. :) But many people do not necessarily have write access to their local drives (because of corporate policy for example), so I cannot see Adobe making this an "official" recommendation/requirement.

Z

From: framers-bounces at lists.frameusers.com [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Ken Poshedly
Sent: Wednesday, February 13, 2013 11:28 AM
To: Fred Ridder; robert at lauriston.com; framers at lists.frameusers.com; techwr-l at techwr-l.com
Subject: Re: "FrameMaker has detected a problem and must quit" Really?!

My coworker did the following (with my help as I followed Fred's previous e-mail):

1. Unchecked the Network File Locking option and saved this choice before exiting Properties.
2. Opened Framemaker 11.0 and the book-in-question.
3. Opened one of the book files on the network drive and scrolled through it -- no problem.
4. Opened another of the book files on the network drive and scrolled through it -- again, no problem. Wait, darn it! There's that crappy crash pop-up again!

So next, he did the following:

1. Copied the entire folder with all book and chapter files from the network drive to his own C-drive.
2. Once more did steps 2, 3 and 4 using only the files on his own C-drive, but this time with no FM crashes -- at least so far.

So it APPEARS this has solved the problem. More info if / as it develops.

-- Ken in Atlanta

________________________________
From: Fred Ridder <docudoc at hotmail.com<mailto:docudoc at hotmail.com>>
To: poshedly at bellsouth.net<mailto:poshedly at bellsouth.net>; robert at lauriston.com<mailto:robert at lauriston.com>; "framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>" <framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>>; techwr-l at techwr-l.com<mailto:techwr-l at techwr-l.com>
Sent: Wed, February 13, 2013 2:01:54 PM
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!
Actually, there is *less* to it than that. There is no prevention and no real notion of permission in the .lck file mechanism.

When you open any file from FrameMaker, it looks for a matching .lck file. If it finds one, it displays a message telling you that some user (which may actually be *you*) has the file open already. You still have the ability to force Frame to open the file. FWIW, Word does something very similar except that it replaces the first two characters in the filename with ~$ and flags the file as a hidden file so that most users won't even be aware of it. The presence of one of a ~$ file is what triggers Word to display a "recovery" window with information about the any autosaved or recovered version of the file you are trying to open.

FrameMaker does give you the ability to disable the .lck file creation because there are lots of circumstances where such a simple-minded pseudo-locking mechanism is pointless, like when you are the only FrameMaker user, or when content is stored in a CMS or collaboration repository where permissions really are managed.

-Fred Ridder
________________________________
Date: Wed, 13 Feb 2013 09:37:02 -0800
From: poshedly at bellsouth.net<mailto:poshedly at bellsouth.net>
Subject: Re: "FrameMaker has detected a problem and must quit" Really?!
To: docudoc at hotmail.com<mailto:docudoc at hotmail.com>; robert at lauriston.com<mailto:robert at lauriston.com>; framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>; techwr-l at techwr-l.com<mailto:techwr-l at techwr-l.com>
I was only aware that an .lck file prevents two people from working on the same file simultaneously, each with permission to save the file with his/her latest changes.

But I guess there is/was more to it.

-- Ken

________________________________
From: Fred Ridder <docudoc at hotmail.com<mailto:docudoc at hotmail.com>>
To: poshedly at bellsouth.net<mailto:poshedly at bellsouth.net>; robert at lauriston.com<mailto:robert at lauriston.com>; "framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>" <framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>>; techwr-l at techwr-l.com<mailto:techwr-l at techwr-l.com>
Sent: Wed, February 13, 2013 12:28:30 PM
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!
Note that creation of a .lck file is an option that the user can turn on or off. In the "General" tab of the FrameMaker Preferences dialog, it's the "Network File Locking" option. (At least that's what it's been named and where it's been located in every version from 5.5.6 through 9, which is what I'm currently using).

-Fred Ridder
> Date: Wed, 13 Feb 2013 09:16:06 -0800
> From: poshedly at bellsouth.net<mailto:poshedly at bellsouth.net>
> Subject: Re: "FrameMaker has detected a problem and must quit" Really?!
> To: robert at lauriston.com<mailto:robert at lauriston.com>; framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>; techwr-l at techwr-l.com<mailto:techwr-l at techwr-l.com>
>
> Yes, an .lck file is created but perhaps it no longer does what it used to do
> before. Capisce?
>
> -- Ken in Atlanta
>
>
>
>
>
> ________________________________
> From: Robert Lauriston <robert at lauriston.com<mailto:robert at lauriston.com>>
> To: Ken Poshedly <poshedly at bellsouth.net<mailto:poshedly at bellsouth.net>>; framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>;
> TECHWR-L <techwr-l at techwr-l.com<mailto:techwr-l at techwr-l.com>>
> Sent: Wed, February 13, 2013 12:11:02 PM
> Subject: Re: "FrameMaker has detected a problem and must quit" Really?!
>
> That's a pretty radical change. Does FM11 not create .lck files when
> you open an .fm file?
>
> On Wed, Feb 13, 2013 at 8:55 AM, Ken Poshedly <poshedly at bellsouth.net<mailto:poshedly at bellsouth.net>> wrote:
> > 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.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 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 docudoc at hotmail.com<mailto:docudoc at hotmail.com>.
>
> To unsubscribe send a blank email to
> techwr-l-leave at lists.techwr-l.com<mailto:techwr-l-leave at lists.techwr-l.com>
>
>
> Send administrative questions to admin at techwr-l.com<mailto: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20130213/562fae1d/attachment.htm>