teresas Posted August 2, 2010 Posted August 2, 2010 I recently got a new computer at my work. I installed FusionPro Desktop like I had on the other computer and started working. I made a new template in InDesign, exported it for FusionPro and opened it in Acrobat. Whenever I go to Preview or Compose I get an error message (image below). My old templates that I had made on my old computer still work fine and don't give me the error--just the new template I made. What I'm running: Windows 7 FusionPro Desktop 7.0P1d Acrobat 9.3.3 InDesign CS4 Illustrator CS5 (used to make EPS image resource) What I've done to try to fix: Uninstall/Install: Uninstalled FusionProUninstalled AcrobatReinstalled AcrobatRan Acrobat updatesRestartedReinstalled FusionPro Desktop Started from Scratch: Trashed all files except InDesign fileMoved file to Desktop*Re-created artworkRe-imported artwork to InDesign fileDouble-checked exported frame settings on all framesRe-exported file**Applied resource to template (NOTE: this resource is used on another template that previews and composes without error)***Changed image file to an Illustrator pdf**** * to see if it was a problem with where I had my resources, pdf file, etc., I worked entirely off the desktop (quite a mess) ** at this point (with no resources or rules applied), the document will preview and compose *** at this point (with a resource and no rules applied) I receive the error when trying to compose or preview **** recommended by tech support; this did stop the error, but I would prefer to use eps files in the templates, because that is the format of most of our images (reformatting them all would take months). My thinking is this may be the only option??? I've contacted technical support and they're in the process of trying to figure out what's going on, but I wasn't sure if anyone else had run across this problem and figured out what was causing it. Any help would be appreciated; I'm exhausted from banging my head on a wall. Thanks in advance! http://i808.photobucket.com/albums/zz6/teresasfisher/error1.jpg
rpaterick Posted August 2, 2010 Posted August 2, 2010 Do you have .eps images that were created from CS4 to test only that would convert during the run?
teresas Posted August 3, 2010 Author Posted August 3, 2010 Do you have .eps images that were created from CS4 to test only that would convert during the run? I saved one of my eps files down to CS4 and another to CS3, tried both separately and received the same message. Instead of using CS5, I tried images that were made in CS4 or earlier (not touched by my CS5 version at all), but I still received the same error. I also tried an image that was made in CS4 that works fine with an older template I have but received the error again.
rpaterick Posted August 3, 2010 Posted August 3, 2010 The only thing I could see doing is getting the whole CS5 package, completely un-install all Adobe products(http://forums.printable.com/showthread.php?t=1573) and FusionPro, re-install the CS5(install updates), and install FusionPro.< financially might not be possible though for you or your shop. I can't imagine FusionPro didn't test the CS5 products with Windows 7 for conversion with what you are experiencing. I know, still doesn't explain why you are having problems with CS4 products..... Other than that. You may want to look into either Scripts that could convert your .eps to .pdf in Illustrator or buying a program that converts .eps to .pdf and let it crank out some of your images overnight to avoid production issues. Hopefully Printable comes back with a simple solution otherwise.
teresas Posted August 3, 2010 Author Posted August 3, 2010 I was told that the Illustrator CS5 workflow and features are not yet supported by FusionPro and support for EPS files created in CS5 is slated for release in a later version of FusionPro7. I'm not sure why CS4 EPSs don't work, though. I hate the idea of changing the format of the images to pdf, but it may be my only option. The issue was submitted to engineering, so maybe I'll get lucky. I'm just surprised no one else seems to have had this problem. I'll be sure to post an update when a solution is figured out.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.