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

Robert Lauriston robert at lauriston.com
Tue Feb 19 08:38:54 PST 2013


Best practice is to use a version control system such as Subversion.
Gives you the performance of local files, all the advantages of
network sharing, plus additional advantages.

On Mon, Feb 18, 2013 at 1:40 PM, rebecca officer
<rebecca.officer at alliedtelesis.co.nz> wrote:
> Hi Gary
>
> That's interesting. It sounds very like the problems we've seen: 3000+ page
> docs, lots of conditional text, sometimes can't create a PDF over the
> network.
>
> We're using a Novell server. Our IS team have checked for choke points,
> overloading etc, and can't find any problems. They reckon it's just Novell.
> We're going to be changing to a Microsoft server anyway, and they reckon
> that'll be happier with Frame. I hope they're right!
>
> Like you, we've "resolved" the issue by copying all the components to a
> local drive before creating the PDF. We're ok with having to do that part of
> the workflow locally, as long as we can keep editing the source files over
> the network.



More information about the framers mailing list