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

[Jeff Coatsworth]

When creating a PDF, I’d be looking to eliminate the network part of things by generating to a local location (leaving all the source files/resources where they are on the network). I seem to remember reading some “best practice” that recommended generating PDFs to a local location first, then copying them to their network home after.

From: framers-bounces at lists.frameusers.com [mailto:framers-bounces at lists.frameusers.com] On Behalf Of rebecca officer
Sent: February-18-13 4:40 PM
To: framers at lists.frameusers.com; Gary Zimmerman
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!

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.

Cheers
Rebecca

>>> "Zimmerman, Gary" <Gary.Zimmerman at Teradata.com<mailto:Gary.Zimmerman at Teradata.com>> 19/02/13 07:20 >>>
Hi Rebecca,

Just for the record, we have had instances where very large (2000 page) documents with extensive conditionalization have been unable to Save as PDF over the network.  I don't believe FM crashed, it just hung indefinitely and never finished PDF production.  This was probably due to network timeout issues, as relocating all the component book files (chapters, appendices, FM-generated TOC/index) to a local computer and saving as PDF there alleviated the problem.

Mind you, that was with FM7 and 9, and I believe that has not been an issue for us with FM10, however we also removed a LOT of the now-unnecessary conditions and conditional text from those books.

Cheers.

-- garyZ


> -----Original Message-----
> From: framers-bounces at lists.frameusers.com<mailto:framers-bounces at lists.frameusers.com> [mailto:framers-
> bounces at lists.frameusers.com<mailto:bounces at lists.frameusers.com>] On Behalf Of rebecca officer
> Sent: Saturday, February 16, 2013 2:02 PM
> To: isaacs at adobe.com<mailto:isaacs at adobe.com>; kverma at adobe.com<mailto:kverma at adobe.com>; Syed.Hosain at aeris.net<mailto:Syed.Hosain at aeris.net>;
> alan at alphabyte.co.nz<mailto:alan at alphabyte.co.nz>; poshedly at bellsouth.net<mailto:poshedly at bellsouth.net>; framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>
> Subject: Re: "FrameMaker has detected a problem and must quit" Really?!
>
> Hi Ken
>
> I'm the person who asked Kapil to clarify, so I suspect I've contributed
> to what you're feeling is the argumentative tone.
>
> Given that, I wanted to explain *why* I reacted like that. Very likely
> other people are in the same position as me.
>
> I wasn't feeling negative towards you, or disagreeing that following
> tech support's advice had fixed your problem. I lead a team of writers
> who all work on a single multi-chapter docs set. We can't just change
> our workflow so everyone's working on their local drives. And we're
> still on FM10 but planning to upgrade soon. So I looked at tech
> support's advice that FM11 didn't support networked drive locations, and
> thought "If that's true, we can't upgrade to FM11. If it's a long-term
> decision from Adobe, we'll have to stop using FM. That seems awfully
> unlikely."
>
> So it mattered to me to get things clarified by someone higher in Adobe
> than a tech support engineer. I'm relieved to find that FM11 does still
> support networked drive locations, as I expected.
>
> We don't always find that FM10 talks nicely with our networked servers,
> so sometimes we end up doing part of our workflow on our local drives
> too. I'm not surprised that moving a doc to your local drive would make
> a crashing doc behave. I just wanted people like Dov and Kapil to
> confirm that it's still the exception rather than the rule!
>
> Cheers and have a good day
> Rebecca
>
>
>
> >>> Ken Poshedly <poshedly at bellsouth.net<mailto:poshedly at bellsouth.net>> 02/17/13 1:55 AM >>>
> To all,
>
> Maybe I'm wrong but the argumentative tone of all of this with regards
> to my
> question is the pits.
>
> As far as I'm concerned:
> 1. Contact Shekhar at tcssup at adobe.com<mailto:tcssup at adobe.com> and discuss it with him.
> 2. We did what he told us to do.
> 3. No more problems (so far).
>
> OK?
>
> -- Ken
>
>
>
>
> ________________________________
> From: Kapil Verma <kverma at adobe.com<mailto:kverma at adobe.com>>
> To: "Syed Zaeem Hosain (Syed.Hosain at aeris.net<mailto:Syed.Hosain at aeris.net>)" <Syed.Hosain at aeris.net<mailto:Syed.Hosain at aeris.net>>;
> Dov
> Isaacs <isaacs at adobe.com<mailto:isaacs at adobe.com>>; Alan T Litchfield <alan at alphabyte.co.nz<mailto:alan at alphabyte.co.nz>>;
> "framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>" <framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>>
> Sent: Fri, February 15, 2013 7:33:39 AM
> Subject: RE: "FrameMaker has detected a problem and must quit" Really?!
>
>
> Hello Everyone,
>
> Hope you are well. Well, there has been a flurry of emails on this topic
> and I
> (as the product manager for FrameMaker) wanted to mention a couple of
> things
> here to set the record straight J
>
> ·         Network file paths: FrameMaker 11 has been tested to work with
> network
> file paths. There is absolutely no change in behavior between FM11 and
> the older
> versions. So, you should not have any problems when your files are
> stored on the
> network location. However, in case you are experiencing any crashes when
> working
> with network files, we will be happy to take a look at your crash logs
> and help
> your troubleshoot your specific issue.
>
> ·         FrameMaker Lock file:There is lot of discussion and some
> confusion
> around the purpose of the lock file. Lock file is created by FM to tell
> the user
> that the file is open in another instance of FM. So, if we take the
> scenario of
> multiple users working on the same file set (which is stored on the
> network
> drive) and when a file is opened in FM, it creates a lock file. If
> another user
> tries to open the same file, FM will give the other user a warning that
> the file
> is open in another instance of FM. So, this is a feature, that prevents
> users
> from overwriting each other’s content. Furthermore, If you don’t want
> lock
> files, you can turn them off as well. Lastly, for more information,
> about the
> lock file and its behavior, please read the help page here
>
> Hope this information is useful and clarifies things. Have a great
> weekend!
>
> Thanks,
> Kapil Verma
> Sr. Product Manager – Adobe Technical Communication Products
>
>
> From:framers-bounces at lists.frameusers.com
> [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Syed Zaeem
> Hosain
> (Syed.Hosain at aeris.net<mailto:Syed.Hosain at aeris.net>)
> Sent: Friday, February 15, 2013 5:43 A
> M
> To: Dov Isaacs; Alan T Litchfield; framers at lists.frameusersWhat<mailto:framers at lists.frameusersWhat> you say
> below is indeed what I would expect, and what is also my
> experience, with the Adobe applications I use (FrameMaker, PhotoShop and
> Acrobat
> Pro)– pretty much any Windows application today!
>
> Thanks for the clarification,
>
> Z
>
> From:Dov Isaacs [mailto:isaacs at adobe.com]
> Sent: Thursday, February 14, 2013 1:24 PM
> To: Syed Zaeem Hosain (Syed.Hosain at aeris.net<mailto:Syed.Hosain at aeris.net>); Alan T Litchfield;
> framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>
> Subject: RE: "FrameMaker has detected a problem and must quit" Really?!
> Importance: High
>
> With regards to network folders and drives, Adobe software in general is
>
> essentially unaware of the media and location of the file. The provided
> file
> path, whether provided explicitly by the user with a file open dialog or
>
> implicitly as a link in a document is used “as is” for operating system
> file
> access calls. That having been said, when one accesses files on remote
> and/or
> slow links or even with semi-reliable media (such as old and scratched
> CD-Rs and
> DVD-Rs), read errors and/or timeouts can and do occur that are much less
> likely
> than when accessing a file on a “local” drive. The Adobe applications
> typically
> don’t attempt any special recovery operations when such read errors
> and/or
> timeouts occur. That is likely the source of problems reported.
>
>             - Dov
>
>  Dov Isaacs
> Principal Scientist
> Adobe Systems Incorporated +1 408.536.2896 (tel)
> +1 408.242.5161 (cell)
> isaacs at adobe.com<mailto:isaacs at adobe.com> 345 Park Avenue
> San Jose, CA  95110-2704 USA
> http://www.adobe.com
>
> Feel free to print this e-mail if your needs dictate hard copy.
> There is no need to feel guilty about printing!
> Paper is renewable and recyclable.
>
> ISAACS-OFFICE.corp.adobe.com
>
>
>
> From:framers-bounces at lists.frameusers.com
> [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Syed Zaeem
> Hosain
> (Syed.Hosain at aeris.net<mailto:Syed.Hosain at aeris.net>)
> Sent: Wednesday, February 13, 2013 12:32 PM
> To: Alan T Litchfield; framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>
> Subject: RE: "FrameMaker has detected a problem and must quit" Really?!
>
> I think that there may be some confusion about local vs. network
> folders/drives.
> Perhaps I read too much into Ken's responses from the Adobe tech!
>
> In my case, all application executables are on my drive C and the data
> files are
> on drive E on the _same_ system. I.e., drive E is _not_ a
> network-mounted drive
> ... it is physically installed on my laptop.
>
> For this "all local drives" arrangement, there should _never_ be any
> issue for
> any modern Windows application.
>
> However, if the data files are on a network server, even if that
> folder/drive is
> "mounted" as a "local" drive letter in Windows, then I can see where
> incorrect
> permissions on that remote location can cause confusion and access
> issues. You
> _have_ to have write permission on that remote drive/folder for example.
>
> FWIW, I have used FrameMaker on a network without problems. I regularly
> back up
> my files onto a network server (into a folder where I have read/write
> access).
> Indeed, I just checked ... I don't have any difficulty opening those
> remote
> files, editing/saving, etc.
>
> The point being that things on networks just have to be set up
> correctly, so an
> Adobe tech may want to _not_ recommend this for everybody. Regardless, I
> would
> not consider that as official Adobe policy.
>
> Z
> NOTICE: This message contains privileged and confidential
> information intended only for the use of the addressee
> named above. If you are not the intended recipient of
> this message you are hereby notified that you must not
> disseminate, copy or take any action in reliance on it.
> If you have received this message in error please
> notify Allied Telesis Labs Ltd immediately.
> Any views expressed in this message are those of the
> individual sender, except where the sender has the
> authority to issue and specifically states them to
> be the views of Allied Telesis Labs.
> _______________________________________________
>
>
> You are currently subscribed to framers as Gary.Zimmerman at teradata.com<mailto:Gary.Zimmerman at teradata.com>.
>
> Send list messages to framers at lists.frameusers.com<mailto:framers at lists.frameusers.com>.
>
> To unsubscribe send a blank email to
> framers-unsubscribe at lists.frameusers.com<mailto:framers-unsubscribe at lists.frameusers.com>
> or visit
> http://lists.frameusers.com/mailman/options/framers/gary.zimmerman%40terad
> ata.com
>
> Send administrative questions to listadmin at frameusers.com<mailto:listadmin at frameusers.com>. Visit
> http://www.frameusers.com/ for more resources and info.

NOTICE: This message contains privileged and confidential
information intended only for the use of the addressee
named above. If you are not the intended recipient of
this message you are hereby notified that you must not
disseminate, copy or take any action in reliance on it.
If you have received this message in error please
notify Allied Telesis Labs Ltd immediately.
Any views expressed in this message are those of the
individual sender, except where the sender has the
authority to issue and specifically states them to
be the views of Allied Telesis Labs.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20130219/7950587a/attachment.htm>