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

Hello everyone, I have a  similar issue.

It affects both "Master Collection" and "Design&Web" CS6 suites - packaged with AAMEE 3.1 (same setting as Penguin2071) and deployed with ARD or Casper (it seems not to make a difference),  after imaging clients.

After a few hours or days of regular and smooth usage on the user side - as soon as they open any CS6 app, ­ it keeps bouncing in the dock together with Adobe Application Manager.

So it looks like the "first run" went fine but somethin happened later.

Whatever the CS app is being opened, it somehow needs to "talk" to AAM to check for something (I assume correct licensing) but they go into a never ending loop and keep bouncing - one after the other - within the dock.

The only "solution" I found so far is un-installing and re-installing the suite and hoping it does not happen again (at times it does though).

The weird thing is only some clients are affected and they all share the same image (OS 10.6.8/configuration) and CS6 installation (only recently added).

Network clients (Active Directory) are managed with MCX but this issue also affects the local admin (with administrative privileges).

Permissions on relevant Adobe folders are fine.

The relevant message within Console is

23/12/12 01.09.42    [0x0-0xab0ab].com.adobe.PDApp[3491]    objc[3491]: Class

HTTPHeader is implemented in both /Applications/Utilities/Adobe

Application Manager/CCM/CCMNative.dylib and /Applications/Utilities/Adobe

Application Manager/CCM/../UWA/UpdaterCore.framework/UpdaterCore. One of

the two will be used. Which one is undefined.

23/12/12 01.09.42    [0x0-0xab0ab].com.adobe.PDApp[3491]    objc[3491]: Class

ProxyManager is implemented in both /Applications/Utilities/Adobe

Application Manager/CCM/CCMNative.dylib and /Applications/Utilities/Adobe

Application Manager/CCM/../UWA/UpdaterCore.framework/UpdaterCore. One of

the two will be used. Which one is undefined.

I have only a few 10.8 clients where CS6 was "manually" installed from the Adobe dmg and I have not seen this behavior yet.

Any help woudl be greatly appreciated!

Many thanks

Carlo


I've experimented with producing Serialization files to re-install on top of the existing "trial" installations, which seem to help briefly.  For instance, I started with CS6 Master Collection working, if you launch any of the executables twice.

But then inCopy for CS6 decided it wasn't registered any more, and drops back to trial mode.  I can install the serialization file for inCopy, and that may or may not break the registration for Master Collection.  Further, if I use Composer to turn the serialization for inCopy into an installable package, it works for one user but not another (still tied to account?).

I'm going to try scripting an install package to serialize both CS6 Master Collection and inCopy CS6 to run on system boot, and see if that will silence Unregistered/Trial warnings for all CS6 packages.

This makes me really sad - my organization spent I believe $40k on Adobe software, and it may or may not launch depending on the day, user, HTTP response, whatever.

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