"Acrobat PDF File Format is having difficulties. Object level badly formatted."
The file save seems to get almost to the end when the message appears and consequently nothing is saved.
At first I thought that the problem was limited to when I was trying to save files that were being worked on off of a server (XServe, in case anyone was wondering). This was soon proven incorrect as after a few saves the exact same problem appears when saving a file locally.
It seems to take three saves for the problem to appear with ANY file save on three different Macintoshes.
I am have trashed Illustrator preferences, re-intalled the application, trashed "dfont.xx" files and the whole shooten-match. I am also running Font Reserve Client 1.6 (running of the server application) on all machines. In that software's respect I have cleaned cache and preferences on multiple machines, as well.
This seems as this may be a problem from the recent 10.2.5 system update since it was only a few days after that that the problems began--on multiple computers. Why it would take days to manifest itself I cannot say.
Adobe, please help!
I worked on the file in AI 10.0.3 (All OS X 10.2.5) atempted to rasterize in Photoshop 7.0.1. Got the "Save as PDF compatible" result when I rasterized, then reopened in AI, resaved as AI with PDF compatibilty, tried to rasterize in PS. Photoshop errored- "problem with the file" Try to open in AI - file errors with Object label badly formatted.
Changing the file suffix to .pdf and attempting File-->Place... failed with the same message.
It gets all the way to the end of saving the file then errors out and nothing is saved. I have to save the file locally to my desktop to save it, then manually move the file to the server.
I updated Suitcase and upgraded to 10.2.5 as well and I can't pin it down but it was around the same time I started getting the file saving problem.
I've tried the whole "shootin match" as well with no success.
Thanks!
I've just started saving all of my documents as Illustrator v.8 documents. This seems to be a viable work-around...until a fix is realised and released, of course.
-Jan
=:-)>