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

[Ralph_...@adobeforums.com]

We are running FM version 7.2b144 on MS Win xp Pro (32 bit), and I did not notice this until service pack 3 was installed. I believe I have found a work around to the situation and another contributing cause. If graphic files are placed directly in an anchored frame instead of importing by reference, the file somehow becomes misplaced. If you right click the graphic and open the Object Properties dialog box, and see the phrase "no referenced file" below Main Editor: Referenced File: in the lower left hand corner, this has happened. I found if I removed all graphics files without references and imported them by reference, the source file may then be properly saved. I am also using a program called CCleaner, which removes cookies, temp files, browsing history and the like from a system. If the program settings are chosen too aggressively, and the application runs when FM has a file open, this same error will occur, even if all files are referenced properly. I don't know if SP3 has some similar application which is now running in the background and causing this.

To summarize, if you want to retain SP3, I have eliminated this error by confirming the links to referenced graphics files and avoiding using 3rd party "cleaners" while FM is open.

[Sheila_...@adobeforums.com]

Thanks for posting your solution, Ralph -- I don't recall anybody ever mentioning using apps such as CCleaner and moreover realizing that they were having an effect on FM files, so that's very useful to know.

fwiw, is there any reason you haven't updated to the latest version of 7.2 (p158)? There were several significant problems in b144 that were fixed in p158 -- here's a small list: <http://www.adobe.com/support/downloads/detail.jsp?ftpID=3332>

[Art Campbell]

Ralph,

No disagreement on your third party cleaner assessment, but Microsoft has released a hotfix for this bug; it's discussed in several other topics and the Adobe FM product manager's blog.

Applying the hotfix seems to be the way to go...

Art

[Ralph_...@adobeforums.com]

Actually, there was a reason (no longer valid). I had been running b144 on Win xp Pro 64 bit system, which occasionally presented unique challenges of its own with other applications. I was loathe to routinely update and perhaps go from workable to unworkable. Now that I am on a 32 bit system, I will update FM 7.2 to p158.

I am also interested in the hotfix to SP3 referenced above. If there is a link to a posting that contains it, or if a direct MS link can be posted, that would be helpful.

[Art Campbell]

If you're in a hurry, do a search in the forum messages for the hotfix, or visit the product manager's blog -- should pop in google too, although I will poke around for old messages, the info is already available here in the forum and on the Adobe site.

Art

[Sheila_...@adobeforums.com]

<http://blogs.adobe.com/techcomm/>

Categories:
FrameMaker
RoboHelp
TechnicalCommunication

The hotfix that Art is referring to is listed on the "FrameMaker" category.

[Maria...@adobeforums.com]

Hi All,
I am running Windows XP with SP3. Using FrameMaker 7.2p158. I get the error as described in the post: An internal error occurred while writing imported graphics in this document. The file has been saved....

I am unable to back out of Windows XP SP3 (IT does not recommend it because it breaks other things). So I have to stay with it... I went to the hotfix that Art referenced from the Adobe Blogs. The Hot fix it references doesn't seem to match with the above described error message. The hotfix seems to fix: Save as PDF leading to a crash and
Text dropping out of PDF created from FrameMaker.

Does anyone have any other bright ideas? I am stuck!!! I can't save my changes, I can't do anything. Help please.

[Art Campbell]

Mariana,
Read the previous posts in the thread that you added to -- they contain the details of what's wrong and how to fix it.

Art

[Ar...@adobeforums.com]

Art,

I've edited the messages to clarify. Deleting them would have made things disjoint in this thread.

Let me know if there is another link that you posted on this that also needs to be edited.

Arnis

[Rania_...@adobeforums.com]

Hello,

I am running Framemaker 7.0 from a windows 2003 server. When i try to insert an object into the fm file and save, i get the error below:

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.

The second thing i also noticed is that I have some files created in FM that contain objects (Excel Worksheets). These files where not created on that server. When i open these FM files i can actually see the objects, but if i try to import these files into another FM file then the text is imported but the objects do not show. I am not sure if both issues are related.

Does anyone have any idea of what is wrong here??

Any help is really appreciated.

Rania

[Gaz_...@adobeforums.com]

Thanks for that Art. I shan't go badgering Purchasing for the £300 required to "fix" the problem then.

Time to persuade I.T. that I HAVE to live without SP3.

[Art Campbell]

I believe the problem is that Microsoft changed the way OLEs are handled. I don't think it has anything to do with Adobe FM... the OLEs that I had don't work in either version.

Art

[Gaz_...@adobeforums.com]

I'm also having great problems with this error. I have a lot of Word and Excel OLEs that will take a very long time to replace. Time I don't have. SP3 removal is not allowed in the company unfortunately, but buying software to fix the problem is very definitely allowed.

So will an update to FM8 fix this problem? Need to know pretty quickly as I have a deadline looming.

[Jean_...@adobeforums.com]

I've also gotten this message. We're still on FM 6.0p405 (ancient, I know). In the first file, I was able to find the OLE graphic and get rid of it. In the second one (today), I checked all graphics, and all are imported by reference or were originally drawn in FM. Is there anything else besides OLEs that cause this error?

[Bindy...@adobeforums.com]

I think I found a way around this problem – when you get the error in FrameMaker, it does actually save the document with a number after the file extension, such as chapter3.fm.387. If you open that file it has all your latest changes. Then you can save it as chapter3.fm and it’s fine from that point on. You can edit it and resave, etc.

[Diane_...@adobeforums.com]

Thank you Bindy Card. It worked like a charm.

[Bindy...@adobeforums.com]

Awesome! My name is actually Robin :)

[Wenke_C...@adobeforums.com]

Hey Robin,

the same problem occurred when I tried to import excel-charts into a framemaker file some days ago. I never had problems with this import till now.
So I tried your trick (opening that file created when the error occurs), but it didn't work: I could only see a grey area where the chart should have been. Any ideas???

[Bindy...@adobeforums.com]

I found that same thing with graphics that were pasted rather than imported into the document. Could you try saving the charts in a format that can be imported, such as PDF, and then importing the file rather than pasting it?

[Wenke_C...@adobeforums.com]

I'll try that now - although I'm afraid that the charts won't look the same once they are imported as a graphic and not a chart. The strange thing is that the error happens whenever any "connection" to excel is made. It occurs when I import a chart already created in excel, when I create an excel-chart in framemaker (using file>import>object>create new object), or even when I change already existing excel-charts in older framemaker-files...

[Lyle_...@adobeforums.com]

I am getting the same internal error message trying to save a document with a reference to an imported visio object.

This is happening using my trusty FM 5.5.6p145 on Vista Home Premium which I was forced to move to. Prior to this I was running on Win2k Server without any problems. I never migrated to XP so this is a new problem for me after moving to Vista. (I didn't bother upgrading to newer FMs over the years as there always seemed to be significant problems in each new version - FM 5.5.6 just chugs along without a problem UNTIL now.)

The fact that this problem has been reported with various versions of FM starting with Windows XP points to something Microsoft changed starting in XP and it has continued with Vista.

The workaround of opening the error recovery file (*.fm.xxx) didn't work in my case. The imported visio drawing is just a gray box as someone else noted earlier.

Any other suggestions?

[Art Campbell]

OK, so far as we know....

The problem is a manifestation or a result of Microsoft plugging security holes in the way that Object Linking and Embedding, OLE, functioned for most of its lifetime. Most people experienced this when they installed XP SP3 because that's how the fix was delivered to their systems. But there's no reason to suppose that MS would leave the same security hole open in Vista.

* ** As far as a PDF of an Excel chart not looking like the Excel chart...
If you specify high quality job options and embed fonts, it's unlikely that anyone would be able to tell a difference. And they'd have to compare the original with the graphic pretty much side-by-side to do it.

Cheers,
Art

[Bindy...@adobeforums.com]

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

[david@codefarm@adobeforums.com]

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.

[Caroli...@adobeforums.com]

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

[brian_...@adobeforums.com]

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.

[Russ Ward]

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)

[Kenneth...@adobeforums.com]

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

[Joe_D...@adobeforums.com]

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.

[Bindy...@adobeforums.com]

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

[Captai...@adobeforums.com]

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.

[Penny...@adobeforums.com]

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.

[Art Campbell]

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