Click to See Complete Forum and Search --> : InDesign CS2 Error (Frustrating!!)
D-Frag
09-14-2006, 12:01 AM
I have been trying to export a pdf file from a 88 page Indesign file. Every single time it exports it gets a serious error and shuts down.
The error reads...
The instruction at "0x4f79cfcb" referrenced memory at "0xefeeecf9". The memory could not be "read"
anyone have any idea in the slightest about what this means, or more importantly how to fix it? its frustrating the hell outta me and ill be damned if I have to pay Adobe $$$$$$ for there lousy tech support.
Edited to add:
PC
Intel 3.8gig
3 Gigs of DDR ram
Windows XP
D-Frag
09-14-2006, 12:10 AM
oooooookay, and now my latest error....
Microsoft Visual C++ Runtime Library
Program: C:\Program Files\Adobe\Adobe Indesign CS2\Indesign.exe
This application has requested the Runtime to terminate it in an unusual way. Please contact the applications support team for more information.
anyone.....anyone??? Bueller....Bueller.....
doubting_thomas
09-14-2006, 12:18 AM
What happens if you try to Export pages 1-10?
Ack I don't have a clue but I'll bet you a brewskie there is a post script object thats causing it. You may just have to trial & error it down. I would try cutting the file in half and see if one or the other half works. If half work but the other doesn't then cut the half that doesn't work in half and so on and so on till you narrow it down to whatever page is causing the error.
rickself
09-14-2006, 01:18 AM
Ack I don't have a clue but I'll bet you a brewskie there is a post script object thats causing it. You may just have to trial & error it down. I would try cutting the file in half and see if one or the other half works. If half work but the other doesn't then cut the half that doesn't work in half and so on and so on till you narrow it down to whatever page is causing the error.Yeppers. Had to do that just yesterday with a 68 page football program. That's the nature of prepress. Divide and conquer. Take the losing half and half it. Eventually got to 10 pages, then 5, then 2 then 3 then found it. A golldern bmp file that the client had applied a 20% tint to. It's the same problem that I referred to in Morea's post about pdf grayscale coming out black.
The_Black_Knight
09-14-2006, 01:41 AM
Ack I don't have a clue but I'll bet you a brewskie there is a post script object thats causing it. You may just have to trial & error it down. I would try cutting the file in half and see if one or the other half works. If half work but the other doesn't then cut the half that doesn't work in half and so on and so on till you narrow it down to whatever page is causing the error.Been there. Done that. It's a pain, but sometimes it has to be done.
budafist
09-14-2006, 03:24 AM
Yeah, I break it into sections too. Sometimes I get errors trying to print this weekly programme we do it's only 8 pages, so I just print the pages 1 page at a time.
You can always join sections of the pdf up again in professional.
urstwile
09-14-2006, 04:40 AM
I've heard that exporting to Interchange format and then reopening that newly exported document in InDesign sometimes fixes odd corruptions in InDesign files, don't know if that's worth a try for you.
Also, any chance that you're exporting the PDF to a network drive, and if so, have you tried exporting it to a local drive and seeing what happens with that? Just a thought. Your error codes look oddly un-Postscript-like.
The_Black_Knight
09-14-2006, 12:17 PM
I've heard that exporting to Interchange format and then reopening that newly exported document in InDesign sometimes fixes odd corruptions in InDesign files, don't know if that's worth a try for you.
Also, any chance that you're exporting the PDF to a network drive, and if so, have you tried exporting it to a local drive and seeing what happens with that? Just a thought. Your error codes look oddly un-Postscript-like.Looking more closely at the errors, I would have to agree with urst that these don't look like PostScript errors, especially the bit about the Runtime library.
It's a dumb question, but did you try restarting the machine? Just kind of thinking out loud, here.
Does it just happen when you ecport to PDF?
Can you print to PDF or create a post script and use distiller?
The reason I ask is that you should be able to get the pdf writer to create a txt document that tells you when the error occurs - save cutting down the document.
PersonasBinar
09-14-2006, 12:58 PM
That looks like a runtime memory (RAM) error.
Eventually got to 10 pages, then 5, then 2 then 3 then found it.
Just out of curiosity, Rick... Why did you go down from 5 pages to 2, then back up to 3? ;)
Sorry, just had to ask.
It sounds to me like this is the best way to solve your problem. Half and half and half and half, until you find the offending page.
Of course, maybe exporting it in pieces you may be able to export it all, but not all at once, if it's a RAM error. You'll find that out along the way, though...
rickself
09-14-2006, 06:24 PM
Just out of curiosity, Rick... Why did you go down from 5 pages to 2, then back up to 3? ;)
Sorry, just had to ask.
It was a crap-shoot. I thought I had it narrowed down to the 2, but they cleared. And that left the 3.
Sometimes ya win, sometimes ya lose.
Sometimes you're the windshield, sometimes you're the bug.
D-Frag
09-15-2006, 05:43 AM
thanks for the replies everyone, this one is still a mystery to me until i can figure out what is causing it.
Here is the deal, this may be long winded. The guy who worked here before me, did some lets say "undesirable" things to the computer, for one, he had alot of "hacking" software and used the gnutella network for who knows what. Upon closer examination, he also has the entire computer hooked up to be "silent" that means no IP, it reads like a wierd text document and he has spoofed alot of the identifying marks on the puter itself, except for he missed a couple spots, almost seems like he is a newbie and was trying out this whole "hacker" feel.
Long story short, I would be very inclined to assume he has screwed this puter up, either by downloading some .exe's off of gnutella and running them, or a million other reasons. Point is, im sure this is what is causing the error because it is very sporatic.
On one occasion, I can get that pdf to save in 3 tries, other times it will take 8 or 10, other times, it won't work past 15 tries. Ive restarted, ive deleted the little .idk file that indesign leaves behind, ive tried saving to different drives, ive even tried moving the entire magazine off of our server on to my hardrive and tried from there with no luck. Im exhausting my ideas here, and today before I left I tried to save it with the same errors.
I will definetely try the breaking it down method. Im also interested in the "Interchange" that you talk about Urst, can you explain in detail?
Also, with our mag, we use a ton of transparencies and different blend modes etc. So now im wondering if this is an issue in ID or in my actual puter. Thanks for all the help, sorry it took me so long to get back to this.
The_Black_Knight
09-15-2006, 12:35 PM
It almost sounds like a nuke & pave is in order for that computer, D-Frag.
urstwile
09-16-2006, 03:34 AM
I'd agree with BK, sounds like it's time to start over with everything on the computer, purge all the yuck.
In terms of the Interchange format, you simply choose to export the file, and that's one of the options that's available, at least in CS2. Then you open that .inx file in InDesign and resave it.
I've used it a few times, mostly with files converted from Quark to InDesign. Don't know if it will help you with your problem or not, it sounds like you might have something more computer related going on, rather than a corrupt file.