Thanks for the suggestion, but unfortunately I can't do anything of the troubleshooting suggested at that link because, I have said, InDesign almost immediately freezes whenever I open the file.
Did you try this method:
Close and relaunch InDesign, and IMMEDIATELY hold down Ctrl + Alt + Shift (Windows) or Cmd + Ctrl + Opt + Shift (Mac), and respond in the affirmative to the dialog asking if you really want to replace the preferences. You must be extremely fast on the keyboard (if you don’t see the confirmation prompt, you were too slow).
You may need to do this a couple of times before getting the hang of it!
Thanks Derek. Unfortunately this is not making any difference. The file still opens and then immediately freezes InDesign.
And you haven't made any incremental Save As backups?
No. It's my first time working with InDesign and I just didn't really think twice about it. Obviously I'll do things differently next time.
You may need the information at How to install scripts in InDesign | InDesignSecrets
Thanks Peter. I tried this earlier today. It starts to work and then InDesign crashes as it's making the .idml file. The file DOES exist in finder after the crash, but it's only a few bytes. I try opening it and it says the file cannot be opened. I have tried creating other .idml files using the script and it works fine.
I see you have also looked at my crash logs in the thread you just linked me to (thanks--my apologies for failing to use pastebin). I appreciate the help.
AH, I see you've tried that already.
Can you clarify for me if the program is crashing on launch or only after your file opens? In other words, are you able to start InDesign without it going into autorecovery?
If it is constantly crashing during the startup recovery process, find the InDesign Recovery folder in Hard Drive/Users/<USER>/Library/Caches/Adobe InDesign/<Version #>/<Language>/ and empty it. This is a hidden folder by default, so see Access hidden user library files | Mac OS 10.7 and later
You should also try File > Open.. and choose As a Copy in the dialog.
Since your crash report on the other thread indicates some sort of text problem it might help to try opening on a Windows machine. I'm gong to send you a link where you can upload the file and I'll see if I have any better luck here, if you like.
I will respond to your post from the other thread here as well to keep it all in one place.
When I try opening the file in InDesign, it seems to work for about three seconds and then InDesign freezes. I am left with no choice but to force quit. When I reopen InDesign, sometimes it does try to autorecover the file and it freezes again...so what I do is change the name of the folder the file is in. That way InDesign cannot find the file to recover (maybe it's a "n00b" solution). This allow me to postpone autorecovery and avoid being locked out of InDesign completely. I have also occasionally moved the autorecovery files.
The "good" thing about InDesign freezing on this file is that it does allow me to see a bit of the document in the three seconds I get before the crash. From my crash report, you indicated that there was a text problem. I do see some wonky text in the damaged file. There is at least one spread where my different paragraph styles are in the place on the page where they should be, but the wrong text is "in" these styles. So, for example, where there should be a header, half a sentence from my paragraph text appears and "takes on" the header style. It's quite strange. Could this count as the text-related problem?
The only other cause I could think of would be one of the fonts I am using. Most of the document is just Arial and Times New Roman, but I am also using Euphemia UCAS to include Inuktitut syllabics (as seen here https://www.google.ca/search?q=inuktitut+syllabics&espv=2&source=lnms&tbm=isch&sa=X&ved=0a hUKEwjVnciyj-TPAhXKjFQKHce2Bt4Q_AUICCgB&biw=1920&bih=950#imgrc=iqiJ7J-2qv43DM%3A). That being said, I have other InDesign documents using the same font from the same location, and there's no problem. Also, I was using the Eupehmia UCAS font for months on the crashed document with no problem before things recently went south... So I'm not convinced it's that.
I have tried opening as a copy and it still doesn't work.
I just received your PM and will send you the file. I appreciate it!
Could be a corrupt style, just a bit of corrupt text, or that font. Or not, that's the trouble with crashes.
One thing that would be easy to check is to uninstall the font and see if the file opens with missing fonts.
Unfortunately I'm at home on a work laptop without administrator privileges so can't uninstall the font. The file is uploading though... when I send it over, I assume you won't have this font... so I guess we can see then!
That is plan A.
1 person found this helpful
I got your file, and the bad news is it behaves the same for me, more or less, opening, then freezing the application. The text on the visible spread is clearly corrupt with lines breaking short and mid-word without hyphens. I also tried the online IDML conversion feature, but that failed at 33 %, and the Windows INDDRecovery program made no changes that would allow use of the file, but it was able to recover the text for the introduction, if that's of any use. Open as a copy also freezes, so there's nothing more I can think of to try here.
At this point I think your best bet might be to send this to Adobe (instructions are at Adobe Corrupt Docs email and I would send Sanyam a message first to alert him) and hope someone looks at it, or if you are in a real hurry and it's worth a few hundred dollars, you can try Markzware: Bad InDesign or Quark File Recovery Submission Form. I have used the latter once, and the recovered file was usable, but took a lot of time to rebuild the styling, as I recall.
Since the file freezes before I get a look at it in depth, I can't say much about what went wrong, but here's some general workflow advice:
First, ALWAYS save your file before attempting to print or to export to PDF. You have a better chance of being able to open the saved file in the event of a crash. We see far too many reports of crashing on output.
Second, especially with long documents and projects that are large, do a periodic Save As. This removes all the change data from the file and rewrites it, making it more compact and less likely to become corrupt. I do a Save As at any major change in direction, and at the end and beginning of each editing session. The Save As at the end before closing the file uses the same name and is just to clean out the junk, those at opening and at change points I use a new name -- my preference is to add a version suffix -- which builds both a backup chain for situations like you are experiencing and also lets me go back in time easily to a previous state if a client shifts gears.
Sorry I can't do more. Good Luck.
Thanks for your help. This is my first time really desktop publishing anything, so I've definitely learned a valuable lesson.
Peter's recommendations re: Save As... are really spot-on, but enough can't be said for a live backup solution. Using a cloud-based backup system such as Carbonite or CrashPlan (my favorite) could at least get that file back to a spot a day (or even hours) before the incident occurred. You know the file's going to get damaged, but at least the restored file will let you open ID and do that Save As to hopefully let you do an end-route on the problem. Backup is insurance, but it's unbelievably useful when you do need it.
Good advice. I don't use a cloud-based backup, but I do image my data drive every night and keep at least three weeks worth of backup images at all times.
There are multiple factors both internal and external to InDesign application that can lead to document corruption. However, I can take a look and see if the file can be repaired. Please email your InDesign file to firstname.lastname@example.org and I will take a look at the document.
If the file is larger than 10 Mb, you can zip (and password protect) the file and upload to Creative Cloud account (or Dropbox) and send us the document link.