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

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

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

[Host edit: the Microsoft "fix" is for the PDF drop-out issue, NOT the OLE issue. AFAIK, this (OLE)is still unresolved and one has to rollback SP3 if OLE linked graphics are wanted in FM. OLE and FM continue to have a strained relationship and IMHO should be avoided.]

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.

Kessey,

I'm curious about why would you expect Adobe to fix a new bug in a non-current, not-supported program that is caused by a change to the Microsoft operating system?

Why aren't you asking Microsoft to fix it?

Or just back out of SP3 and go on with life?

Art

Does FM plans to resolve this? I need to have both working, XP SP3 with my latest FM 7.2 patch. Can we expect this to be resolved soon?

Uninstall SP3.

Art

We use 7.0 and we have hundreds of OLE objects in our FM files - e.g. MS Visio files or tiny symbols we inserted via copy+paste ...
Please tell me that there is a fix, because we have to deliver approx. 50 PDFs from FM files in two weeks time - quite a few of them books with about 10 files in average ... there is absolutely no way to find and repair all those OLE occurencies and include all the changes that have to be in there in TWO WEEKS!

The documents I an editing are a collaboartive project, point being that many graphics have been imported into the documents and not by me. We are supposed to be importing everything by reference but I'm not sure what others have done. Is there an easy way I can search a document or book for OLE objects?

Brandon, are you importing anything as an OLE object?
That's been the reported cause of the problem; replacing whatever with an imported graphic also fixes it.

Art

Thanks for reporting back, Brandon -- one more nail in the coffin for SP3 ....