Any 9004 errors?????

Report · Mar 30, 2009

Is anyone getting a 9004 error doing anything in FM9? If so please tell me what you are doing to get the error and what patch you are at and what version of Acrobat you have. Also be very clear on what you are doing to get that error step by step will be great. Trying to find fixes for people and nothing is working and no one is saying anything about it!!!

Thank you from a very tried tech support person.

Report · Mar 30, 2010

Hi Gay,

Why do you have to restore the directory structure? My writers haven't had to restore the old,

corrupted directory structure. The new, generated one seems to be fine. None of the writers who had that

Localization error have seen the error since. Are you getting more errors which seem to result from

renaming the directory?

Has anybody heard anything from Adobe on these issues?

Kind regards,

Edward

Report · Mar 30, 2010

Hello, Edward,

No, I haven't had any more crashes since I renamed the Linguistics folder. But Arnis' point makes sense to me, that I should do something to restore the 35 language subfolders under each of the four Dictionary folders within the Linguistics folder. The renamed (i.e., original -- but I have no idea whether or not it was corrupted) folder has the original folder structure, with all 35 of the language subfolders under each Dictionary folder, whereas the new (FM-generated) Linguistics folder has all four of the Dictionary folders but each contains only two subfolders ("all" and "eng").

I'm on a deadline and haven't had time yet to go back and try to restore the original directory structure but I figured it was something I should try when I get some time...

As for hearing back from Adobe, no, all I've received is the usual auto-response acknowledging receipt of the fmerror files.

Thank you for your input -- maybe with enough help I'll actually understand this whole thing one of these days...

Cheers,

~~Gay

Report · Oct 04, 2010

This is an oldish thread but I wanted to add my experience for the record ...

This (Monday) morning, very mysteriously, I was unable to launch FrameMaker. The

error I was getting was 9004, 6921852, 9677150, 0. As it turns out, I hadn't used

FrameMaker since the preceding Thursday, but had used it heavily all day (including

creating many PDF files) without any issues.

When I saw the post about the Linguistics folder, I tried renaming it, and

voila! the problem disappeared. Then I hunted for any files in that folder that

had been updated the last day I had used FrameMaker. I found three: added.txt

and excluded.txt in FMDocDictionary\all, and added.txt in FMUserDictionary\all.

As an experiment, I removed the newly-created Linguistics folder, restored the

original Linguistics folder, and renamed these three files. Frame launched fine.

Then I tried viewing all three files (since they are .txt files) to see if I could see

any corruption or anything odd. The FMDocDictionary\all\excluded.txt file included

very little text I could read, and a lot of ascii symbols, so I guessed that was the

culprit; sure enough, when I restored the other two files, Frame still launched

just fine.

Looking back four days it's hard to be precisely sure, but it seems likely that,

in spell-checking some documents I was finalizing for release, I did add some

terms to the dictionary. Somehow I guess this got corrupted.

Just FYI for the next person who encounters this error ... and now I am off to

forward the error files to Adobe.

Report · Oct 13, 2010

Thank you for reporting your results to this thread, Kyle, it will certainly be useful for other folks having this error.

Report · Dec 11, 2009

jcpal, a couple of questions. You say you get the error when going from tab to tab; could you list your exact actions, whether you're using the mouse or keyboard commands and so on? How many files do you typically have open, how do you open them (e.g. from a book file, by double-clicking in Windows, or by using FM's File > Open? Are the files that you typically have open all within the same book, or are they from multiple books?

Also, how much RAM does your system have? As Jeff is indicating, FM needs a fair amount of elbow space in RAM, particularly if you have lots of cross-refs, it would need to open lots of files when updating links.

Fwiw, using 9.0.3 and WinXP w/ 4GB RAM, FM crashes on me fairly often if I open files by double-clicking them in Windows, but not if I do File > Open in FM or if I use the splash-screen links to the most recent files. Although I work with lots of FM files I don't often need to open more than 2 files at a time in FM, and don't use cross-refs very often so I can't offer any comparison on those aspects.

Have you checked for updated video and mouse drivers? FM has always been "sensitive" to video drivers, and slightly less so to mouse drivers, for that matter.

Do your files get moved or backed up and later restored in any way, either on your system or to/from a network? What I'm wondering is whether there might be something getting clobbered if the files are moved or the path names changed or "reconstituted" from time to time.

How about graphics or any referenced files, is everything always kept local or does anything migrate from location to location?

edit: oops, I see you mentioned having 9 files open. Well, that really does point a finger at RAM being an important question. Also, do you have other apps open when you're using FM?

Sheila

Report · Oct 13, 2010

While I must get some time to try all the suggested solutions, I'm getting the following error several times a day:

9004, 6921628, 9677518, 0

I cannot find a pattern triggering it. I remember having had this kind of problem earlier, on a work I did starting from scratch. Now, I'm reusing material created on FM 6.0 Mac, and the crash is my best friend hour after hour.

I'll get back as soon as I have some more info. Unfortunately, I don't know how to send the crash log to Adobe (the bug report form only allows for 2000 characters, and no attachment is allowed).

Paolo

Report · Oct 13, 2010

The error message asks you to e-mail it to them at the address they specify. Don't send it through the bug reporting system.

Report · Feb 22, 2011

This may not help anyone, but in my case, the crash was being caused by a "hidden" graphic on a master page. Frame would give me the standard "some images cannot be displayed" message, but since there were no gray boxes, I assumed it was a false error. Turns out that the master page had originally been linked to a missing logo that was pasted over with a valid image file. Even if it looks like there are no missing images, it's worth it to double-check.

Another workaround that succeeds, most of the time, is to only print the book after opening all of the constituent fm files. Don't know why, and maybe it's coincidental rather than causal, but when the Lingusitics dictionary and image file fixes don't fix anything, the Open all files ib book command before printing is worth a shot.