Article View: adobe.framemaker
Article #1839Re: An internal error occurred while writing imported graphics in this document. The file has been saved
From: Bindy_Card
Date: Wed, 29 Oct 2008 19:30
Date: Wed, 29 Oct 2008 19:30
6 lines
1413 bytes
1413 bytes
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
Technical Details
Message-ID:
<59b54413.47@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news4.google.com!news.germany.com!fu-berlin.de!news4us.nl!webcrossingReferences:
<59b54413.-1@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: fd315,6ccbb19a04164000 X-Google-Attributes: gidfd315,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: Bindy_Card@adobeforums.com Newsgroups: adobe.framemaker Subject: Re: An internal error occurred while writing imported graphics in this document. The file has been saved Message-ID: <59b54413.47@webcrossing.la2eafNXanI> Date: Wed, 29 Oct 2008 12:30:35 -0700 References: <59b54413.-1@webcrossing.la2eafNXanI> Lines: 15 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Path: arc1-ca.pugleaf.net!g2news2.google.com!news4.google.com!news.germany.com!fu-berlin.de!news4us.nl!webcrossing