FrameMaker 2022 Update 4 disables some API clients

[frameexpert]

Be aware that FrameMaker 2022 Update 4 is not compatible with 64-bit FrameSLT and FrameScript 7. These were working for me in Update 3.

Cannot initialize API client C:\Users\Rick\AppData\Roaming\Adobe\FrameMaker\WestStreet\FrameSLT_FM2020.dll.

Check for errors in the APIClients section of the maker.ini file in FrameMaker install location or your %appdata% folder, verify that the client program exists, and make sure you have enough swap space to run the client.
Cannot initialize API client C:\Program Files (x86)\ElmSoft\FrameScript7\fsl7_160_64.dll.

Check for errors in the APIClients section of the maker.ini file in FrameMaker install location or your %appdata% folder, verify that the client program exists, and make sure you have enough swap space to run the client.
Cannot initialize API client C:\Program Files (x86)\ElmSoft\FrameScript7\fsl7_160_64.dll.

Check for errors in the APIClients section of the maker.ini file in FrameMaker install location or your %appdata% folder, verify that the client program exists, and make sure you have enough swap space to run the client.

[frameexpert]

Be aware that FrameMaker 2022 Update 4 is not compatible with 64-bit FrameSLT and FrameScript 7. These were working for me in Update 3.

Cannot initialize API client C:\Users\Rick\AppData\Roaming\Adobe\FrameMaker\WestStreet\FrameSLT_FM2020.dll.

Check for errors in the APIClients section of the maker.ini file in FrameMaker install location or your %appdata% folder, verify that the client program exists, and make sure you have enough swap space to run the client.
Cannot initialize API client C:\Program Files (x86)\ElmSoft\FrameScript7\fsl7_160_64.dll.

Check for errors in the APIClients section of the maker.ini file in FrameMaker install location or your %appdata% folder, verify that the client program exists, and make sure you have enough swap space to run the client.
Cannot initialize API client C:\Program Files (x86)\ElmSoft\FrameScript7\fsl7_160_64.dll.

Check for errors in the APIClients section of the maker.ini file in FrameMaker install location or your %appdata% folder, verify that the client program exists, and make sure you have enough swap space to run the client.

[Winfried Reng]

I have a number of FrameScript scripts which I need. I cannot do some tasks without them.

And this means that I cannot update to Update 4. Pity!

[frameexpert]

https://tracker.adobe.com/#/view/FRMAKER-14912

[Winfried Reng]

Thank you very much! Voted!

[Winfried Reng]

Frank Elmore, Project leader for FrameScript, sent an e-mail that they will be preparing a new FrameScript client as soon as they can.

Sounds good!

[Jeff_Coatsworth]

@frameexpert I'd suggest getting this on the FM team's radar by logging it in the Tracker (https://tracker.adobe.com/); unless you've already pinged the tcssup@adobe.com e-mail address.

[Nandini Krishna]

Hi ,

We will be releasing the updated FDK soon for recompiling the plugins. This is required as there were library updates  for security fixes. Will keep this thread updated.

Thanks and Regards

Nandini

[Nandini Krishna]

The new FDK is available now and can be downloaded from here.  Custom plugins will need to be recompiled using this FDK. Please let us know if this works for you.

Thanks and Regards

Nandini

[Russ Ward]

There is no link on that page that says "17.0.4". There is just one link, "September 2022 release - FDK ZIP". Is that it?

[Stefan Gentz]

@Nandini Krishna, I guess https://helpx.adobe.com/in/framemaker/kb/framemaker-downloads.html is not updated yet, and the download link is pointing to 17.0.2 FDK, not the 17.0.4 FDK.

Can you please confirm that the correct link to the latest 17.0.4 FDK for Update 4 is this one:

https://download.adobe.com/pub/adobe/framemaker/win/17.0.4/FDK2022.zip

[Russ Ward]

This is exceptionally disappointing, making a decision like this that instantly breaks the critical workflow of many FrameMaker users. Without any notification to the suppliers of the addon software that many depend on. As much as I love FrameMaker, I can't imagine that its lifespan will be that much longer if business decisions like this persist. Can users at least roll back to 17.0.3 so they can continue to use FM as normal?

[frameexpert]

I totally agree Russ. Fortunately, I was able to download and reinstall 17.0.3 so I can continue to use FrameSLT and FrameScript.

Adobe's silence on issues like these is frustrating. I have been trying to get an answer on their future plans for FrameMaker scripting, but haven't gotten a response. It appears that Adobe is in maintenance mode with FrameMaker, just releasing patches. So sad to see a legendary program like FrameMaker die out.

[Stefan Gentz]

Feedback taken, @Russ Ward and @frameexpert.

Generally said, with Updates that include library updates (like the security updates in this release), it is often (if not always) necessary to update the FDK clients. The library updates are mentioned in the release notes.

Unfortunately Update 4 was released a couple of days before the FDK Update was released. This is obviously not ideal, completely agree. Ideally there should have been a Prerelease for Update 4 including the FDK. We will make sure to have this ready in time for the next Update.

Regarding the future of FrameMaker: Our main focus this year is on the ARM release which is a massive undertaking as it goes deep into the core of FM and needs extensive testing as well. Once this is done, I’m confident, the doors are wide open for a bright future for FM in the coming years 🙂

[Winfried Reng]

Stefan, thank you very much for this clarification!

I look forward to the bright future!

Have a good day!

[Russ Ward]

Hi Stefan, I hope you are right. It would certainly be my preference. I would say respectfully, though, that a bright future would depend heavily on a significant paradigm shift in how Adobe markets the product and adds value for its users. Increasingly, the product is seen as a clunky dinosaur that is just good for making books, when in fact it has several key features that make it still a stellar tool for technical writing. But the great majority of users (or former users) never use them or even know how they work. And Adobe never promotes them. So the customer base gets gee-whizzed by other products that are actually inferior but seem more flashy. Anyway, I say again that I hope you are right. But I am concerned that the current sentiment in the field does not seem positive in that direction. Thanks for listening.

[frameexpert]

@Stefan Gentz Regarding the ARM release: As far as I know, there is no ExtendScript support in that release, which is a major concern. What are the future scripting plans for FrameMaker?

[Stefan Gentz]

Unfortunately, as of now, I cannot comment on future scripting plans. But what I see is that there is a general move towards UXP within Adobe …

[frameexpert]

Thanks for the "hint". Hopefully, we will have enough advance notice to prepare for any changes.