Skip to main content
_
_Charles_Kindall_
Known Participant
July 23, 2008
Question

Internal Error: 8004, 6345644, 8487696, 0 when attempting to Save as PDF

  • July 23, 2008
  • 13 replies
  • 5072 views
I keep getting this error every time I create a PDF after crashing with a particular book. Now it looks like the PDF creation is corrupted. I have tried creating PDF's from books I had no problems with but I have had no luck without crashing FrameMaker with this exact error. I am using v8.0p277 on Vista Ultimate SP1 with and AMD.

This all started when I opened an older book created in 6.0 and updated in 7.0 and now when I opened it in 8.0 and created a PDF some images were randomly missing from one chapter. They appeared grayed out in the PDF. I opened the chapter and attempted to recreate the PDF and different images were grayed out in the PDF. Next attempt crashed with this error and now it does this every time regardless of the file or book. It appears to do this when it attempts to write the TPS file and access Distiller. I can open Distiller separately with no problems.

I can continue to use FrameMaker but I can't create a PDF using the Save Book As PDF. Is there a way to "Recover" the application without re-installing it?
    This topic has been closed for replies.

    13 replies

    A
    Anonymous
    June 28, 2010

    This error  hit me yesterday, but none of the fixes in this thread worked. In my case, Frame wouldn't even fully load before it crashed.

    After a bit of investigative work, I found Adobe  FrameMaker 8 with Windows XP SP3 fix on the Adobe download site (http://www.adobe.com/support/downloads/product.jsp?product=22&platform=Windows).

    After a complete uninstall/reinstall, problem gone!

    jjj

    Z
    Zac Lam
    Inspiring
    November 27, 2008
    Thanks for sharing Adam, that fixed my problem with Export to PDF also. :)

    Previously I was seeing crashes with Export to PDF. I'm running FrameMaker 8.0.4 with Acrobat 8.1.3 on Vista. After installing the hotfix, I'm up and running again.

    Cheers,

    Zac
    _
    _Adam_Hartfield_
    Participant
    October 27, 2008
    Charles, Art -

    Thanks for the replies. I do appreciate them!

    As it turns out, after I submitted the log of the crash to fmerrors@adobe.com (as the dialog box in FM instructed me to do), I got email from an Adobe employee pointing me to a blog entry about this problem. I replied and asked if it would be alright for me to post that link here. As of yet I have not received a reply, but I figure since it's a blog entry accessible via the Internet it's meant for public consumption. To wit:
    http://blogs.adobe.com/techcomm/2008/07/hotfix_for_framemaker_1.html

    I applied the hotfix and it fixed my problem. :) I hope this will help others who have the same problem.

    --Adam
    A
    Art Campbell
    Inspiring
    October 25, 2008
    Adam,

    The first thing to check is whether the Adobe PDF printer instance is linked to a File port or not, in the operating system. The port is required, but occasionally disappears. If the printer isn't linked to a port, you can create one or do an uninstall/reinstall of Acrobat.

    But I'd disagree slightly about the need for a whole reinstall because the problem is most likely in Acrobat, not Frame, because the printer instance is unrecognized...

    So I'd try first just uninstalling the Acrobat instance and re-running the Acrobat installer. But leave Frame alone for the time being.

    Art
    _
    _Charles_Kindall_Author
    Known Participant
    October 25, 2008
    Try doing a full re-install. If that doesn't work, I have also felt it could be a problem with a FM update. You could reinstall both apps and don't allow them to update.
    _
    _Adam_Hartfield_
    Participant
    October 23, 2008
    I'm getting that error now, too, and my repair of Acrobat 8 didn't help. I can't print to the Adobe PDF printer instance, either.

    System: Dell box, Windows Vista Business with SP1, 4 GB RAM (but only 3 GB used), FM8p277, DITA-FMx 1.00.26, Acrobat Professional 8.1.2.
    _
    _Charles_Kindall_Author
    Known Participant
    July 24, 2008
    Well, I believe I have finally figured out the problem. I was correct in assuming the Postscript engine had a problem. I did a repair install of Acrobat 8 and it seems the AdobePDF.dll file some how became corrupt from something in one of the chapters. I believe it could have been an old TIF file that was moved from Mac to PC. A similar corruption better known to Photoshop EPS files with clipping masks. I'm guessing it was the DLL because when I did a repair it specifically asked for it and I had to extract it from the .CAB file (I had the downloaded version) and it asked for the CD. After running the Repair install on Acrobat all my problems went away.

    BTW the printer is still set to the MS XPS Writer and I have no problems.
    _
    _Charles_Kindall_Author
    Known Participant
    July 24, 2008
    Again no. This also creates the same Error. Maybe the entire Postscript engine is corrupt? I get to Printing Page 1 of 4 in the TOC (8% complete) It printed the chapter before. I have Reinstalled FrameMaker and I still get the error on anything I print or Save As PDF.
    _
    _Van_Kurtz_
    Known Participant
    July 24, 2008
    Charles,

    At many times and in many places in these forums, users have been advised NOT to create PDFs by selecting Save as PDF. I have never done it, so am not sure why it has problems.

    Instead, PRINT the book or document or selected documents to the Adobe PDF printer. Doing that creates a PDF. In the print dialog box, you can also specify the job options for Distiller by clicking the Properties button. If you want to distill from Distiller directly, then you can save the print file to disk, which is the Postscript output.

    But I have heard that saving to PDF is not the best way to create PDFs.

    Good luck,
    Van
    _
    _Charles_Kindall_Author
    Known Participant
    July 24, 2008
    No that's not it. It has always been set to that. I have never had a problem before. I have changed it to Adobe PDF and it doesn't make a difference. It doesn't use that driver when you choose Save As PDF.
    Show more replies
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices