Frame 16.0.2.916 Print Book issue

[VCurran]

We just moved from Frame 2017 to 16.0.2.916 (whatever that means). I opened one manual's book file, opened all the files in the book, and printed the book to PDF using Adobe Acrobat. About half way through the list, frameMaker closed abnormally but it did produce a PDF file to that point.

Has this happened for anyone else?

[Bob_Niland · Accepted solution]

VCurran: We just moved from Frame 2017 to 16.0.2.916 (whatever that means).

16.x is FM2020.
16.0.2 might be seen as the 2021 release.
.917 might be the latest update for it.
Anyway, useful info for the contributors here.

When opening an older version .book and/or .fm files, the newer product usually pops some notifications that the files will be updated to the current release [binary] format. It might be worth:
a. preserving copies of the FM2017 documents under other names
b. opening them in FM2020
c. saving & closing them
d. re-open, checking for any issues

We then might move to just how you are rendering to PDF, as there are 3-4 different pathways for doing that, and possible issues with JobOptions or Publish (.sts) files.

[VCurran]

Thanks for translating the version number! And providing some steps to take to get the files used to the new version of Frame.

We print to PDF using Adobe Acrobat with the Generate Acrobat Data checked and the tags that generate bookmarks set up. We generally do not bother with generating a postscript file and I didn't check this. 

Since posting, I have generated four other manuals using our standard process and all four generated correctly. So it looks like it's one book that has the problem. Since we are working remote, the VPN or internet provider might have gltched while we had the files open and in use. My plan is to copy the FM2017 files into a new folder, open them with FM2020, save them, and start the update from a fresh set of files.

[Bob_Niland]

re: We print to PDF using Adobe Acrobat with the Generate Acrobat Data checked…
That's still a bit vague, as there are several ways to do something matching that description:
. Publish to PDF
. Save as PDF
. Print to PDF
. Print to .ps & Distill
Since some of your ported documents work, chances are we can rule out the mini-chaos surrounding Microsoft's efforts to respond to the spooler vulnerabilities.

re: Since we are working remote, the VPN or internet provider might have gltched while we had the files open and in use.
Accessing via CMS, network server or remotely can have issues of its own, which can be ruled out by test with local copies. Of course, if there's any imported-by-reference content, make sure the local "copy" is made by re-save, and if the imported asset count is low enough, make local copies of them (and their file system hierarchy) as well.