Quantcast
Channel: Adobe Community : All Content - InDesign
Viewing all articles
Browse latest Browse all 62281

Why does InDesign 8.0.1 crash under 10.8.2

$
0
0

InDesign is driving me nuts!  We have 200 Macs running 10.8.2 and Design Web Premium CS6.5.   I made a golden image and pushed it out to the 200 others.  When a user logs in they get a new Home Directory from the local User Template so that the prefs are fresh for each user on every login.

 

To troubleshoot I have removed the Adobe prefs from the User Template and re-applied the 8.0.1 update and no luck.  InDesign files are randomly getting corrupt and students loosing their work.  After the file has been made corrupt the student goes to use it the next day and the mesage is the following:

Cannot open "filenamehere.indd".  The file "filenamehere.indd" is damaged and cannot be recovered (Error Code: 5).

 

Today I logged in trying to duplicate the issue and launched InDesign and made some lines on the page and went to save the file to the Desktop and got this error that I haven't seen yet:

Cannot save "Untitled-1" under a new name.  The file "DBTmp7561446801480" is damaged (Error code: 2).

 

The file did save correctly and Indesign crashed.  Opened InDesign up opened the file fine, made a new file and no problems.

 

No other apps have problems, the user owns the Desktop and profile and permisssions look fine on the Home Directory.  Disk Utillity finds no problems.

 

I'm about out of ideas?   Anyone have any?   This is a package of the Suite made with AAMEE 3.1.

 

InDesign should be like a new version on every login, but seems to be having issues.  No Adobe prefs are in the Home Directory.

 

I did find a problem early on when I made the image causing Indesign to crash on startup and that is because InDesign calls home to Adobe on launch and does not use the proxy settings set in System Preferences and I had to punch the address out in the firewall.  The IP is 192.150.16.64 port: 443 and the plugin doing it I believe is PMWelcomeScreen.InDesignPlugin in Plug-Ins/PMPack.  That fixed the crashing early on, not sure what is going on now.

 

Any ideas anyone?

 

Thank you!


Viewing all articles
Browse latest Browse all 62281

Trending Articles