FrameMaker 9 renames files in book to odd suffix

[Guest]

I am experiencing FrameMaker 9 (from TCS II) renaming files in my books and then sometimes crashing. Sometimes it merely renames one or more files within the book with suffixes like filename.fm.842 or filename.fm.29E. The book then complains that the file no longer exists. Renaming the file to remove the odd suffix often fixes the problem however the frequency with which this occuring is increasing.

Has anyone else experienced this? I am running 64-bit Windows 7.

[AxialInfo]

Rick, please post the exact version you're using, from Help > About, the "pxxx" numbers.

Also, are you accessing or saving the files locally or across a network?

Sheila

[Guest]

It is Framemaker 9.0p250 and the files are local to the Framemaker installation.

[Arnis Gubins]

Rick,

This sometimes happens when FM can't write the file to the specified location for whatever reason - been there. Check the permissions for the specific folder, or the file itself (i.e. is it a read-only from a CD archive?). You may even have Policies that have overly aggressive virus-checking/firewall software grabbing the original file and messing with FM making it think it is a botched write/save.

[Guest]

FrameMaker is installed in C:/Programs (x86)/Adobe/Adobe Technical Communication Suite2/Adobe FrameMake 9

My working files are installed in C:/Local WIP

This doesn't happen every time for every file. It is intermittent and happens to random files in a book.

I created all the files and the permissions for the files are all correct.

We are using eTrust Threat Management Agent.

Given what you guys have said and the state of my set up it looks like eTrust may be the culprit but I'm at a loss of what to do about it other than turn it off which I really don't think is an option.

[Guest]

eTrust isn't my problem. I'm still seeing this. Is this a Windows 7 64-Bit thing?

[AxialInfo]

This error has been around for a kazillion years, going way, way back, so it's definitely not specific to Win7 or 64-bit.

edit: here's a recent thread:

http://forums.adobe.com/message/1238358#1238358

If you haven't yet done so, you might search the Framers archives to see if any other causes or solutions ring a bell; here's some info for searching:

http://lists.frameusers.com/pipermail/framers/

you can  also search the Framers archive by using Google, doing this:

SearchTerm  site:frameusers.com

If your search term has spaces, put quotation marks around  it, e.g.

"master  page" site:frameusers.com

[AxialInfo]

Rick, I don't know what the feature might be called in Win7, but in XP there is the system event viewer log, I wonder if that might have entries at the same time as the odd suffix error occurs and so might give a clue whether any other app is conflicting.

Another possibility would be the Sysinternals tools (now Microsoft), at http://technet.microsoft.com/en-us/sysinternals/default.aspx

[Art Campbell]

There are a few flavors of this, but this usually happens if you have automatic backup turned on and there's a network interruption or other problem that prevents FM from saving the temp file(s)  to the correct path. The odd suffix files are the temporary save files, but they're orphaned because the actual directory or parent path wasn't reachable.

It can also happen with different version control setups...

And it also happens if FM crashes for some reason and leaves the temp files behind.