Skip to main content
Legend
May 13, 2014
Question

reluctant Acrobat

  • May 13, 2014
  • 2 replies
  • 309 views

Sudden flurry of management activity after reseller notices there's no documentation in the package the developers send … so, of course, FM/Acrobat choose now to start playing up. A .book that has saved as .pdf without any problems beyond the treacle-through-muslin speeed I associate with FM10 on Windows 7 now hangs; and I also notice that when I break it into a suite of smaller book-jobs, .tps files are being left behind after distilling has finished.

Sympathy would already be good <g> Tips on diagnostics would also be appreciated.

    This topic has been closed for replies.

    2 replies

    Arnis Gubins
    Inspiring
    May 14, 2014

    Niels,

    Try using the manual Print to postscript route and distill. If there are FM issues, this may show more clearly where they are occuring.

    The .tps files left behind may be suggesting that the Acrobat installation may have an issue. You can always try to use the Acrobat Help > Repair option to ensure that side of the coin is ok.

    Bob_Niland
    Community Expert
    Community Expert
    May 13, 2014

    > A .book that has saved as .pdf without any problems ... now hangs;

    How do you know it's hanging, rather than just taking a long (and possibly growing) amount of time? How long are you waiting, and how are you terminating it?

    > ... FM10 on Windows 7 ...

    Win7 32-bit or 64-bit?

    How large are the .tps files getting?

    I don't know what the FM10 limit is, but there were historical issues at 2GB (now fixed) and I've tested FM9 to above 4GB, but rendering time is glacial.

    > .. .tps files are being left behind after distilling has finished.

    Any clues in the log file?

    One extremely unlikely degenerate case that can cause this is if the document is importing itself as a text inset, possibly in anchored frame where it might be hard to find. Fm does not detect this sort of recursion. Both the .fm file size and the rendering time will grow every time you open it. I have seen this happen as a result of file corruption, although it could be done by accident.

    Legend
    May 14, 2014

    Having solved/sidestepped the immediate problem by making several smaller books – which all distilled correctly – and stitching the .pdfs together, I shall launch a Save as … on the original .book when I go to lunch. After that, without implying any priority, I'll try Print to .ps

    As for Acrobat Help > Repair, I'll save that till I don't have/foresee any documents to deliver for a couple of days :-}

    Legend
    May 16, 2014

    Happy to report that once things had got worse, they swiftly got better :-} Acrobat hit crash and burn levels of failure, but this did at least throw a clear error message; it seems the underlying problem was disc space. IT support have increased my quota, and things now appear to be running smoothly again. For now …