Error 17014

[Yvet28909425mchn]

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.

Sometimes things help like:

1. Apply the conditional text one by one,

2. Update book,

3. Open all files and 'save and open files'.

Usually they don't help. I have hundreds op books and there is no way to solve this problem...

Is anybody familiar with this?

This is in the log:

=== Header Begin ===
Internal Error: 17014
FrameMaker 17.0.1 for Intel
Build: 17.0.1.305
Window System: MSWindows
Operating System: Windows NT 10.0 (major.minor.build: 10.0.22621 )
Generated on: donderdag 25 mei 2023 13:21:42
To file: C:\Users\yvet\AppData\Roaming\Adobe\FrameMaker\17\FrameLog_23.05.25_13.21.42_meta.txt
Locale: English
Current Mode: Maker
Current View: (null)
=== Header End ===

=== Open Window List Begin ===
# not implemented
=== Open Window List End ===

=== Recent Commands Begin ===
=== Recent Commands End ===

=== Recent API Calls Begin ===
# not implemented
=== Recent API Calls End ===

=== Last few fcodes Begin ===
0x367
=== Last few fcodes End ===

[kglad]

reset your preferences.

• Close FM.

• Rename the  folder 17 to 17_old in C:\Users\UserAccount\AppData\Roaming\Adobe\FrameMaker.

• Clean the “temp” folder which is located at ‘C:\Users\user profile\AppData\Local\Temp’.

• Launch FM and check the issue.

<moved from enterprise&teams>

[Yvet28909425mchn]

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)

There were a lot of documents which I couldn't delete in the "temp" folder.

[kglad]

make sure fm is closed.

check your task manager to make sure there are no fm related processes running

then do the rename and clean

restart your computer

reopen fm

[Yvet28909425mchn]

Nothing, still the same

[Jeff_Coatsworth]

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).

[Yvet28909425mchn]

Must try this tomorrow.... Not sure how to do this, I'll figger it out. Thank you.

So strange. Could it be because of the new version Framemaker? I never had this problem.

[Jeff_Coatsworth]

Could be - I forget what 17 converts to - if that's FM2022 check to see if the latest patch has been applied.

[Winfried Reng]

The poster has version 17.0.1. That's the latest version.

kglad's recommendation is definitely helpful.

Generally it's no problem to assign conditions or to hide/show conditions.

I do this every day and do not get any crashes.

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?

Definitely try a MIF wash!

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?

Do you use expressions for your conditions? Or do you just select single conditions to show/hide?

[Winfried Reng]

Another question: Do you use structured or unstructured files?

[Yvet28909425mchn]

Unstructured

[Winfried Reng]

Sorry! Yes. We have already a second update for FM 2022/17.

Therefore the first step should be to update your FrameMaker installation.

https://helpx.adobe.com/framemaker/kb/framemaker-downloads.html

[Yvet28909425mchn]

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...

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]

[Jeff_Coatsworth]

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.

[Matt-Tech Comm Tools]

Start here, with Adobe's utility.

https://helpx.adobe.com/framemaker/kb/how-to-use-mifwash-utility-in-framemaker.html

[Matt-Tech Comm Tools]

Why would a MIF wash be more than saving to MIF, then opening and resaving over the old files?

[Matt-Tech Comm Tools]

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.

-Matt

[Yvet28909425mchn]

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. 

I'm not very happy with this new Framemaker, I prefer the old one.

This one have errors all the time, everywhere. And very VERY slow.

Thanks everybody

[Jeff_Coatsworth]

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.

[Yvet28909425mchn]

I send an email, thank you!

[michaels90993732]

I can reproduce the 17014 error here. For my case I must do:

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.

[Jeff_Coatsworth]

@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.