Skip to main content
Participant
May 16, 2008
Question

An internal error occurred while writing imported graphics in this document. The file has been saved

  • May 16, 2008
  • 49 replies
  • 12982 views
An internal error occurred while writing imported graphics in this document. The file has been saved, but has lost some image data. Please report this error to Adobe Technical Support.

How do i fix this, there are no images in the document

thanks

emma
    This topic has been closed for replies.

    49 replies

    Inspiring
    January 29, 2009
    Several people have reported that temporary files created during the crash (ending in a numeric suffix) can be opened and saved and they work. So you may want to see if you have any of those files...

    Other than that, because the problem is with OLE and imported objects... generate PDFs or other graphic files from the slides and reimport them as referenced graphics.

    FM 9 seems to handle OLE objects better, so you may also want to download the eval and test that.

    Art
    Known Participant
    January 9, 2013

    The original post on the forum is old, but we are seeing the same error today.


    We use FrameMaker 10 on a Windows 7 platform.

    We see this error: "An internal error occurred while writing imported graphics in this document. This file has been saved, but has lost some image data. Please report this error to Adobe Technical Support."

    We create an anchored frame, select it, then use File > Import > File for all graphics. On the Import window, we then select "Copy into Document" for all graphics.  We cannot import by reference, so please do not suggest that.

    When we attempt to publish that file to WebHelp (from within FrameMaker, but via RoboHelp), the content is empty except for the message, "This Help System has no topics."

    Can anyone help?  I did not see a resolution for FrameMaker 10 and Windows 7 in the thread.

    Thank you!

    Arnis Gubins
    Inspiring
    January 9, 2013

    What format were the graphics that were lost?

    Do you have sufficent space in your system TEMP area? FM uses that for intermediate steps. Some graphics are written out in simple raster format so they might be huge compared to the input graphics file. Also, if you are writing across a network, there may be issues there (aggressive anti-viral scanners have been known to give FM flakey behaviour).

    It is known that graphics imported by copy sometimes spontaneously disappear (i.e. the ubiquitous grey box) from FM files, which is only one of a number of reasons why the importing by reference is preferable.

    Why can't you import by reference? Re-evaluating your workflow might yield some benefits.

    Participant
    January 29, 2009
    I have a related issue. The only way I was able to stop the external error message from appearing was to remove all my links to associated PowerPoint slides. Unfortunately I now cannot re-associate the slides using the Edit>paste special>paste link feature for the frames. Can anyone suggest a workaround?

    I am unable to rollback from sp3 and the hotfix mentioned in previous posts did not help.
    December 16, 2008
    For the record, the blog post with the hotfix is:

    http://blogs.adobe.com/techcomm/2008/07/hotfix_for_framemaker_1.html

    and the hotfix is at:

    http://support.microsoft.com/?id=952909

    But as has been edited into the posts, this does not solve the imported graphics problem, only exported PDF problems.
    Participating Frequently
    October 29, 2008
    I think it's the consensus that the problem was introduced with Windows Service Pack 3 and you will have this problem even when saving to a fixed disk. Even though you get the error, the document is still saved with a number extension, such as document.fm.135. If you open that document with FrameMaker, your changes are still there, and any graphics that were 'pasted' into the document will appear as gray boxes.

    The workaround is to 'import' the graphics into your document, rather than 'pasting' them. Just delete the gray boxes and replace them by importing the appropriate graphic file, such as a bmp file, into your anchored frame. Then save as the document with the usual FM extension, e.g., document.fm.

    Hope this helps,
    Bindy
    Participant
    October 29, 2008
    We have been saving files to a shared drive for 5 years with no trouble until our IT department loaded windows Service Pack 3. This problem appeared suddenly on two other work stations in our publishing group soon after the installation of Service Pack 3. The one work station that is not experiencing this problem did not have service pack 3 loaded.
    Try saving your files to a fixed disk, not a network drive and try saving your work.
    Legend
    October 24, 2008
    Brian, I'll let your post remain for the sake of general amusement. Further unreasonable insults towards long-time, dedicated contributors will grow old quickly, though.

    Art, no need to respond. It would be tough to debate sensibly with an IT specialist who can't find a Microsoft hotfix.

    Russ
    (Forum host)
    Participant
    October 24, 2008
    WHY IN THE WORLD WOULD YOU MAKE IT SO HARD TO FIND THIS HOTFIX?

    THIS IS SUPPOSED TO BE A SUPPORT FORUM, GOD FORBID YOUD ACTUALLY HELP PEOPLE.

    NEXT TIME INCLUDE THE LINK TO THIS HOTFIX ART, INSTEAD OF ACTING LIKE A LITTLE SNOB AND TELLING PEOPLE TO JUST SEARCH THE SITE FOR IT.

    -regards,

    An actual IT support specialist.
    Participating Frequently
    October 24, 2008
    Brian

    This is a user-to-user forum, and Art is a user just like you. Art posts
    here frequently, often several times a day. The support he offers is
    free, he gets paid nothing for it, and he owes you nothing.

    --
    Kenneth Benson
    Pegasus Type, Inc.
    www.pegtype.com
    Participant
    October 8, 2008
    Robin, I simply cannot thank you enough. Your trick has made my life so much happier. I was updating 15 Frame documents, each with tons of OLEs of various forms (Visio drawings, gif, and pdf) and our corporate process does not allow for importing by reference. Your trick allowed me to save and build the documents without errors. There are "grey boxes" where something used to be, but at least now I have something to work with instead of ALL of the imported figures.

    Thanks again, ya'll!

    Caroline
    Known Participant
    September 25, 2008
    yuk, don't create a JPG, the lossy compression on all the Visio chart's straight lines will look like hell.
    I'd export from Visio as PDF, personally, and then import that by reference into FrameMaker.
    Participating Frequently
    September 24, 2008
    My simple answer is to create a graphic file, such as a BMP, JPG, or GIF, from the Visio chart. Then import the graphic into your documents. At least, this works for me.

    Hope this helps,

    Robin