FrameMaker 9 "Internal error 9004" issue

Robert Lauriston robert at lauriston.com
Tue Jun 16 08:36:54 PDT 2015


Since getting the current release would cost $1000, you might consider
migrating to Flare instead. Not that I'm a huge fan of Flare, but it
won't cost you anything to evaluate.

On Mon, Jun 15, 2015 at 9:47 AM, Frank Ripp
<fripp at pacificbiosciences.com> wrote:
> I noticed that my problem started several days after a series of IT-pushed
> system updates. (Frame 9 was running fine on Windows 7 for quite a while
> before that.)
>
> Fred Ridder said “FWIW, Frame 9.0 is six and a half years old and as of this
> week is now four versions behind the current release. Adobe's usual policy
> is to provide support for no more than two previous versions plus the
> current release. I suspect you may need to bite the bullet and upgrade.”
>
> Maybe it is time – if I upgrade, should it be to Frame 12 or “Frame 2015”?
>
>
>
> Thanks, Frank
>
>
>
> From: Frank Ripp
> Sent: Friday, June 12, 2015 2:34 PM
> To: framers at lists.frameusers.com
> Cc: Frank Ripp
> Subject: FrameMaker 9 "Internal error 9004" issue
>
>
>
> Hi Framers,
>
>
>
> I’m running Frame 9 (v9.0p255) under Windows 7 on a Dell Latitude with 16 GB
> of RAM.
>
> The software was recently installed, and for a few weeks everything worked
> as expected.
>
>
>
> Today, when I open *any* existing Frame document:
>
> 1)      The document is blank.
>
> 2)      When I close the document, the content now displays underneath the
> “Do you want to save changes” dialog. (So my content is still there!)
>
> 3)      No matter which button I click, an error message displays:
> “Internal error 9004 <lots of numbers> FrameMaker has detected a serious
> problem and must quit.”
>
> 4)      I click OK in the error dialog and FrameMaker quits.
>
>
>
> Our IT folks uninstalled Frame, then reinstalled it from disk. I then
> updated it with 4 separate patches, updating it from 9.0p196 to 9.0p255.
>
> I’m still seeing the same behavior. (And of course, I’m in the middle of
> working on many documents!)
>
>
>
> As per the error message, I sent the log files to Adobe at
> fmerror at adobe.com. Not sure when I’ll hear back from them.
>
>
>
> Anybody out there run into this problem? How did you resolve it?
>
> Any help on this is greatly appreciated!
>
>
>
> Frank Ripp
>
> Pacific Biosciences
>
> Menlo Park, CA
>
>
> _______________________________________________
>
>
> You are currently subscribed to framers as robert at lauriston.com.
>
> Send list messages to framers at lists.frameusers.com.
>
> To unsubscribe send a blank email to
> framers-unsubscribe at lists.frameusers.com
> or visit
> http://lists.frameusers.com/mailman/options/framers/robert%40lauriston.com
>
> Send administrative questions to listadmin at frameusers.com. Visit
> http://www.frameusers.com/ for more resources and info.
>



More information about the framers mailing list