Article View: adobe.framemaker
Article #120Re: Any 9004 errors?????
From: Arnis_Gubins
Date: Tue, 31 Mar 2009 01:50
Date: Tue, 31 Mar 2009 01:50
37 lines
2773 bytes
2773 bytes
Hopefully, you've (or someone in your organization has) sent copies of the crash log files to Adobe at fmerror@adobe.com The Adobe engineers do pay close attention to these errors. FM9 is still quite new out of the starting gate and there are always teething problems, especially with the major changes to the UI. That's also why you're probably not finding many systematic reports yet on crashes, as many people are still kicking the tires (so to speak) and trying to make decisions about updating their workflows, rather than going full bore production with it. I know I'm still at that stage. FWIW, 9004, 6920460, 9676766, 0 is for deleting too many variables in a row using the new pods. As far as the start of this thread goes, there were no "issues" stated. You only asked if anybody else had errors starting with 9004 and I simply tried to point out that *all* FM9 errors start with 9004. I still don't understand what your stated problem with not patching is? "FM 9 no patch because the fix for it to work is a pain to do every time the it crashes (since the fix has to be done every time you open it)" You only need to install the patch once. If getting FM to crash somehow removes the patch in your installation, then I think Adobe would be extremely interested in that. Patch issues are part of the installation and are free technical support from Adobe. It's important to let people know that the TCS version is being used, since you state that you're also encountering a crash updating books from RoboHelp 8. And it's also important to know if crashes are happening with the structured or unstructured versions of FM. You also could try take the reverse approach (in keeping with the mutually beneficial spirit of these forums) by posting crash cases here, indicating the relevant info, error code, and steps taken, in case some else has encountered the same error or perhaps could suggest a possible workaround. This might alert other users to serious bugs that can be verified and hopefully passed on to Adobe engineers.
Technical Details
Message-ID:
<avq2t41mo8jt2e4kj59g7hnf95tcumoujh@4ax.com>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news.glorb.com!news2.glorb.com!news.glorb.com!newshub.sdsu.edu!webcrossingReferences:
<59b873fc.-1@webcrossing.la2eafNXanI> <59b873fc.4@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: fd315,68f560e07e7615af X-Google-Attributes: gidfd315,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: Arnis_Gubins@adobeforums.com Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news.glorb.com!news2.glorb.com!news.glorb.com!newshub.sdsu.edu!webcrossing Newsgroups: adobe.framemaker Subject: Re: Any 9004 errors????? Message-ID: <avq2t41mo8jt2e4kj59g7hnf95tcumoujh@4ax.com> Date: Mon, 30 Mar 2009 18:50:55 -0700 References: <59b873fc.-1@webcrossing.la2eafNXanI> <59b873fc.4@webcrossing.la2eafNXanI> Lines: 37 X-Newsreader: Forte Agent 5.00/32.1171 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit