Have you run the 8.0.1 update for InDesign? if not, please update your application.
The error message shows that the exe file has been updated but that the faulting module was not properly updated. Sounds like it's time to uninstall, run the cleaner tool and reinstall.
Thanks Larry -
is there a specific cleaner tool from Adobe that you are speaking of?
I just checked, and that particular plugin is not updated with the 8.0.1 patch, so that's not the problem (though reinstalling may still be in order).
Thanks for the work, Peter.
No biggie. Just wish I had a clue what the root cause is.
Thanks guys - I'm not even sure what that plugin is....
But, I'm taking Larry's route towards total uninstallation and cleaning. To the point now that I'm reinstalling InDesign from scratch. SLOWWWWWWWWWWW.
Will post update.
Ok, thanks for everyone's help, but after a full uninstall and clean, still getting this:
Faulting application name: InDesign.exe, version: 188.8.131.526, time stamp: 0x50335e39
Exception code: 0xc0000005
Fault offset: 0x00020334
Faulting process id: 0x12fc
Faulting application start time: 0x01ce309f4c9c15c9
Faulting application path: C:\Program Files (x86)\Adobe\Adobe InDesign CS6\InDesign.exe
Report Id: b30f5309-9c92-11e2-8f20-bff27640c70f
Any suggestions out there?
Unfortunately it's required for ID to run. I have a feeling Java may not be properly installed on the computer. Let's try re-registering the jscript.dll file with the OS.
Go to the Start button, then choose Run...
In the command line field type regsvr32 jscript.dll (there's a space between the two parts), then click OK. You should get a success confirmation, and you can't hurt anything if it's already registered and you do it again.
That didn't seem to help (and same event viewer error).
Can I completely reinstally Java somehow?
I have CS6 installed on 2 computers, both windows7 64 and both have same version of Java. For whatever reason, my laptop is not working, but desktop is.
Yes, but we're getting outside the kind of advice I'm comfortable giving here. It's possible to screw things up even more.
I think this probably qualifies as an installation issue, which means you should be able to call Adobe tech support and get some help from them for free (and they have access to more information than we do about what might be doing this).