FM 2022 Keeps crashing with Internal Error 17024 (Windows 10)

[QuintinSeegers]

No matter what document/book I open, FrameMaker keeps crashing with the following error:

 

I have :

• deleted my Appdata\..\17 folder,
• restarted my PC, 
• opened a file located on a server,
• opened a file located on my local drive,

I have a 300 page manual that needs to be updated and ready for publication by the 1st of July, 2023, so it is urgent that I find a solution to this error. I have sent the dump file to fmerror@adobe.com, but as the error states, I my not get a response soon.

Any suggestions on what I can do to fix this?

Thanks,

Quintin

[Winfried Reng]

When FrameMaker crashes, the cause can be completely different. The fix of your issue can be irrelevant for others.

Nevertheless, let's hope the best!

[QuintinSeegers]

100% agree. That's the 'beauty' of software :-). I'm just glad Adobe did find an issue and is working on a fix for it.

[DebralynnMedDev]

I'm having the same issues and I've tried fmerror@adobe.com from two different emails and neither work. 

[Jeff_Coatsworth]

We've had reports that the fmerror email is down right now - the FM folks are aware of it & recommend using tcssup@adobe.com to contact them instead (the fmerror one is really only used for error reporting, not getting any help).

[DebralynnMedDev]

The fix was fairly easy to follow C:/Users/name/AppData/Roaming/Adobe/FrameMaker/17
Once I found the 17 folder, I had to change the name to 17.old and restart the program and it worked. I had FrameMaker 2022 and the error was 17024.