@michaels90993732 - that sounds like a bug, but I don't think you'd be firing up another instance of FM on the same machine normally. Report to the FM folks anyways.

Can you create one or two files with the default FrameMaker templates and add them to a new book? What happens, if you apply conditions and show/hide them?

But, to do it professionally, I can only recommend a Hilti dry core, with the fantastically awesome dust collector. With the setup I used, there was. no. dust. Really. Maybe a teaspoon laying around the edges of the core, enough that you could just blow it away. None in the air. Honest. I had no trouble drilling through the floors in occupied office spaces. That clean.

When I open a Framemaker book, select all and show/hide conditional text apply I get an error which nobody knows what it it and how to solve it.

The only thing that seems to work is to  open all files in my book and then apply the conditional text. Very time consuming... But I'm sick of this error.

=== Header Begin ===Internal Error: 17014FrameMaker 17.0.1 for IntelBuild: 17.0.1.305Window System: MSWindowsOperating System: Windows NT 10.0 (major.minor.build: 10.0.22621 )Generated on: donderdag 25 mei 2023 13:21:42To file: C:\Users\yvet\AppData\Roaming\Adobe\FrameMaker\17\FrameLog_23.05.25_13.21.42_meta.txtLocale: EnglishCurrent Mode: MakerCurrent View: (null)=== Header End ===

I open FM. This works. Then I'll open FM a 2nd time and the 2nd FM instance crashes with this 17014 error number, because I've only one licence. For me it feels like: FM can't handle the "no license" execption.

It happens with all FM books. I have about 20 different conditions that I choose to apply. Sometimes it helps to apply them one by one, somethimes it helps to update the book, and sometimes nothing helps...

Since you have hundreds of books, it might be worth taking the time to install FrameMaker on a fresh computer or fresh VM to see if a new, raw install (updated to 17.0.2) runs smoothly. If not, perhaps working with 16.0.x would be more efficient for now.

You might also try a MIF-wash of your docs to clean out any stuff that may be causing them to crash (no sense in posting error logs here - only the FM devs can understand them).

I thought it went well. The first went well, the second book I had the error again. This is ever since we have the new version of Framemaker. It creates a new "17" folder (instead of your "14" folder)

IIRC there's a book-wash script out there for MIF washing entire books. I just don't recall if it's baked into FM or you have to obtain it from a third party - have a search in the FM forum.

Well, you could contact the FM folks - see https://helpx.adobe.com/contact/enterprise-support.other.html#framemaker for your Adobe Support options. I'd highly recommend using the tcssup@adobe.com e-mail address as it reaches a team dedicated to Technical Communication Suite products including FrameMaker.

I'm gonna try to do the MIF wash. That means I have to disemble the book, run script to MIF and then back to FM, and then set up a new book?? This will take a while and I have hundreds of books [sigh]

Does this happen with every file or book? Or only with special books with your conditions? Do you have files and books which do not show this issue?