Internal error 17004 has detected a serious problem and must quit

Forum|Forum|3 years ago
November 30, 2022
2 replies
954 views

I worked on various devices with Framemaker and this error shows everytime. I use structured FM and always have open book and files within. It can happen during work on a file or an update of a book... and it happen one time or 5 times per day or none.
Please help.

This topic has been closed for replies.

Bob_Niland

Community Expert

As I recall, the 17004 decodes as:
FM release 17.0
Platform 04 (Windows)
which isn't terribly useful by itself.

There should be a crash log somewhere that might be helpful if sent to Adobe.

What Windows is this, by the way, and on what hardware platform?
17004 might be unsurprising in some some configurations, such as virtualizations.

I used to get nailed by 7003 years ago (03 being Unix). Never did find a root cause.

Jeff_Coatsworth

Community Expert

First make sure you're all patched up with the latest changes. Is it happening on all docs you work on or just one in particular?

N

nalepapelanAuthor

Participant

I have the latest version of FM and I updated files to FM 2022 also. I don't think it's one file because I work on many of them and it happens with different set of docs.
But I just saw that I didn't have latest version of EDD. Do you think that may be the issue?

Jeff_Coatsworth

Community Expert

Could be? I live in the unstructured & antique FM world of FM12 at the moment, so I haven't a clue. But you can always ping the FM folks - see https://helpx.adobe.com/contact/enterprise-support.other.html#framemaker for your Adobe Support options. I'd recommend using the tcssup@adobe.com e-mail address as it reaches a team dedicated to Technical Communication Suite products including FrameMaker.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded