Having trouble saving a Framemaker file as RTF on network server

Question

I'm working on a project for which the files have to stay on my company's server. When I try to save a FM (2020) file as .rtf, Framemaker quits responding and I have to force quit. It seems to start creating the the rtf file but that file won't open (error says it may be corrupt).

Are there certain approaches I need to be taking when working in FM on a network server, and/or can someone help me with the words I'll need to get help from company tech support, who will know nothing about Framemaker itself.

Thanks!

KateK-475 · Accepted Answer

UPDATE: My Adobe support request did get answered and I worked with a tech over the phone for troubleshooting. He agreed that it was more likely something to be fixed on my network rather than in Framemaker, but suggested some additionl things I could test out before sending it back to my company's IT support team. That's pending.

I appreciate all the guidance I've gotten here!

Bob_Niland · Answer

Any chance of saving locally, then moving the file?
(if that fails too, then the problem isn't the NFS)

And I presume that all are aware that saving to RTF usually results in substantial deletion of formats & styles, down to a very small subset of what FM can do. If RTF is the common enterprise document format, FM might not be the ideal tool for stewardship. I only ever use RTF to export a simulation of an FM document, to someone who needs to hack on the content and doesn't have FM.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.