RE: Frame error message when saving

["Ede, Craig" <craig.ede@xxxxxxxxxxxxx>]

I've seen this in the Unix environment when multiple users on PCs are using shared licenses operating as terminals from a single Unix server. The problem there is related to the /tmp drive where on startup, each use's session tries to create (at least) three .fm* directories for some behind the scenes work by each user's session. If another user has already created the directory, the new user's session will attempt to use that one. 

It appears that if one or more of these .fm* directories are created with permissions that prevent one of the other users from writing to it, the error message cited in the original post pops up and that session creates files with the random character extensions.

On Windows the /tmp drive would probably equate to the swap space.

Our solution is to use the TMPDIR variable to redefine the place where the .fm* directories are written so they are unique for each user. The idea that "the only known work around is the one you're using (see below)" is completely unacceptable. The save, exit, rename routine gets old very rapidly and reduces efficiency to a point where people would stop using FrameMaker if that was the only option.

Maybe someone from Adobe can clarify what is happening and address how to deal with this on each platform (and keep some customers).

Best,

Craig
Los Jugadores Bazutadores

-----Original Message-----
From: larry.kollar@arrisi.com [mailto:larry.kollar@arrisi.com]
Sent: Thursday, February 13, 2003 1:45 PM
To: Framers List
Cc: framers@omsys.com
Subject: Re: Frame error message when saving


It may have something to do with your Compatibility Preferences settings 
(File -> Preferences -> General). If you set it to "Macintosh," then 
you'll get that error if your Frame file name is longer than 31 
characters. The problem stems, I think, from Frame tacking on a ".backup" 
to the old file name when you have automatic backup turned on -- the OS 
ends up truncating the name & then Frame can't find the file.

In short, your best bet to avoid that problem is to turn off "Automatic 
Backup on Save" (also in Preferences). You could also keep file names 
relatively short (less than 24 characters or so).
--
Larry Kollar, Senior Technical Writer, ARRIS
"Content creators are the engine that drives
value in the information life cycle."
    -- Barry Schaeffer, on XML-Doc

"Rick Henkel" <frameuser@hotmail.com>
Sent by: bounce-framers-84669@lists.FrameUsers.com
02/13/03 08:33 AM
Please respond to "Rick Henkel"
 
        To:     framers@FrameUsers.com (Framers List)
        cc: 
        Subject:        Re: Frame error message when saving
=

> I am having a very strange intermittant problem in Frame 7, Win2K.
> Occasionally, but becoming more annoyingly common, when I'm working in a
> file and do a routine Ctrl+S to save it, I receive the following error
> message: "The document was saved to a temporary file, but Framemaker 
can't
> rename it to have the correct name. The newer version has an odd 
suffix."
>
> There is no replicable trigger for this message that I can determine.
> Sometimes I may have saved the file several times just prior to a save
that
> generates the error. My workaround is to rename the file, close out of
> Frame, delete the older version, change the name back to the original
file,
> and reopen Frame. What a pain!!
>
> Has anyone else seen this error? Any ideas?


I used to see this at a previous job. Unless something has changed in the
last year or so, the only known workaround is the one that you're using.

Rick
==========================


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **