Upgraded from Framemaker 2020 to Framemaker 2022. Publishing to PDF causes Frame2022 to crash

[gimpfam]

I just got a new computer and upgraded from Framemaker 2020 to Framemaker 2022. I have several books that I created in Framemaker (unstructured) and I use the Publish command to generate  PDF and HTML5 output. It was all set up so it worked perfectly in Frame 2020. 

I made a test copy of a couple of my books and opened them in Frame 2022. It told me I had to convert the files for the new release and also asked if I wanted to convert the Settings files from 16.1 to the newest version. I converted the files and tried to generate the PDFs with converted settings or non-converted settings.  

When I first generated the PDF, it mostly generated, but the ChapterTitle, Head1, and Head2 paragraphs tags did not display. Also the headers and footers didn't display. I thought maybe I needed to adjust how they were mapped. I tried a few things (but still didn't get those components to display in the PDF). 

I made a few more copies of the original book (before it was upgraded) and tried making some small tweaks. i don't know what I did, but now, whenever I try to publish any book to PDF using my standard settings files I've been using for a long time, Framemaker crashes. No error message or anything -it just shuts down pretty close to the beginning of the Publish to PDF process. 

I can generate the HTML5, which uses the same settings file. There are a few spacing issues I need to correct in the HTML5, but in general the files are generated Ok. 

I read there were some bugs in Frame 2022. Has anyone else had this problem and do you have any suggestions as to how I can get my PDF to generate. It appears the results are the same if I choose Save As PDF from the File menu instead of using the Publish dialog. Thank you in advance. 

Best regards, 

Marcia

[gimpfam]

Forgot to mention, it's a Windows 11 system. 

[FrameMaker-dk]

Have you tried creating a new sts file from scratch using FM2022? It has been my experience that sts files may have difficulties surviving an update to FM. Also -  are you using Distiller?

[Winfried Reng]

Hi Marcia,

What's your update version? The latest one 17.0.7.

Save as and Publish are identical. You can use whatever is more comfortable for you. However, in the Publish pod you can switch from the (default) FrameMaker PDF engine to Distiller. Change the option Use Acrobat Distiller for PDF generation. Distiller might give you some info, if FrameMaker should crash here as well (which I doubt).

And yes. Let FrameMaker create a new STS file.

Best regards, Winfried

[Jeff_Coatsworth]

I would suggest updating to the latest patch version & trying to upgrade your content again.

[Matt-Tech Comm Tools]

Along with the other great suggestions, make sure your preferences are set to display all missing resource messages, and then open all files in the book. Often you'll find image, font, and version messages that until cleared up can make export to PDF and HTML problematic.