Skip to main content
D
don_sizemore_unc
Participating Frequently
December 20, 2012
Question

Photoshop CS6 (and only Photoshop) dies on first run

  • December 20, 2012
  • 1 reply
  • 5640 views

Hello,

I'm hoping someone can help me.  I used AAMEE 3.1 to generate a serialized package of CS6 on OS X Mountain Lion (10.8.2).  It's fine, or so I thought.  I created a Mac OS image through DeployStudio and deploy it across our school's iMacs.  Great.  However, during the first run, Photoshop (and only Photoshop) launches the Adobe Application Manager alongside it, and they both exit.  Subsequent launches of Photoshop proceed as they should, and other programs in the suite load properly on first run.

This would be a minor annoyance, except all of our Macs are frozen using Deep Freeze, so everyone will experience this behavior, every day.  I haven't found anything helpful in the system or Adobe logs, haven't been able to web-stalk anything, and monitoring the filesystem for changes during this sputtered launch only yields three binary files, two in /System/Library/Preferences/Adobe and one beneath ~/Library/Preferences/Adobe/SLStore.  Pushing out these files to another machine as a test doesn't change Photoshop's behavior - is this tied to the Adobe ID (mine), the user account, some hardware identifier, or a combination of the three?

Thanks for any pointers,

Donald

This topic has been closed for replies.

1 reply

SeanAlexander
SeanAlexander
Known Participant
December 20, 2012

My thoughts:

  1. Confirm the permissions of ~/Library/Preferences/Adobe/SLStore. Adobe likes "drwxrwxrwx root admin" for that folder.
  2. Does problem occur on both administrative account and standard account? If administrative account, that would further indicate a permissions problem.
  3. Since further launches work, I am also inclined to suspect corrupt cache files that are updated after launch. Check/Move to Desktop/Delete Photoshop-related (or Adobe-related) cache files in ~/Library/Caches, then test
D
don_sizemore_uncAuthor
Participating Frequently
December 20, 2012

I really appreciate the pointers:

1. Permissions were correct (albeit I should have referenced SLStore beneath Application Support, but... everything was world-writable.

2. Administrative and standard accounts alike.

3. I've trashed all Caches in any directory containing  "Adobe" case-insensitive, and wiped out /Library/Caches for good measure.  Then signed in with my personal account on a new machine and... same thing

Thank you again for any ideas or further thoughts!

Donald

D
don_sizemore_uncAuthor
Participating Frequently
December 28, 2012

Don and/or Carlo,

If you use JAMF Casper Suite and if you have not already done so, check out the knowledge base on the JAMF Software website. Use "CS6" as a query. Even post a discussion. I have found my JAMF peers to be quite helpful.

If an Adobe technical rep responds, I would highly recommend you take the opportunity to send the PDApp.log file to them.

Don,

I have not played with serialization files so I cannot help you with that, though, if you turn the serialization into an installable package (either .pkg or .dmg) and it is only affecting one account, make sure you "Fill User Templates" and/or "Fill Existing User Home Directories" on the package so that it applies to all home directories (accounts).

At this point, I am sad to say I am not sure what else to tell you.


Hello,

We do use Casper here, but not for initial deployment as a binary restore performs much faster and we need to image over 100 machines during School breaks.  I've been using Casper's Composer in "New and Modified" package mode to experiment with Serialization packages, but nothing seems to go into the present (and only/admin) user's home directory.  I tend to copy those into /Library/User Templates/English.lproj, as non-admin users aren't present on our "frozen" lab machines.

Re-running the serialization commands using Adobe's CLI tool seems to have quieted everything, for all users on the machine, but those filesystem modifications don't carry to the machine next door - still tied to hardware somehow.

I'm procrastinating with coffee, then building a package to push out the Adobe serialization stuff for CS6 MC and inCopy somewhere beneath /opt, with a short shell script to run them individually on each machine.  Seems like it should do the trick - thank you for all your ideas and help.

Donald

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices