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

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

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?

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...

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?

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???

Awesome! My name is actually Robin :)

Thank you Bindy Card. It worked like a charm.

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 its fine from that point on. You can edit it and resave, etc.

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?

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.