The relevant console message I got was thisĢ3/12/12 01.09.42. I have already posted here on the Adobe forum but have not found a solution yet To me, it looks like something related to AAM checking for licensing. Anyone else experiencing these issues?Īt least 1/3 of my CS6 clients (both Master and Design+Web suites) installed with a Casper policy from 3.1 AAMEE-created pkgs have/had the very same issue (OSX 10.6.8, all installed over the same base image). Not sure if this is related or unrelated. After the update runs, it allows AAM to run as if I had never had the administrative settings configured. I'm also noticing that if I manually open the Adobe Application Manager, it automatically updates itself to version 7.0.0.189, despite having updates turned off. We use RUM - and I'm wondering if Adobe pushed down (and then I pushed down on their behalf) a bad update recently. Open up a CS6 application, and it starts again.Īll the CS6 installs were built with AAMEE 3.1.1 and installed via Casper. It's a really nasty loop, and hard to end without a full restart. All their Adobe CS6 apps are getting stuck in a crashing loop where an application such as Photohop launches, quits, the Adobe Application Manager opens, then crashes, and the cycle is repeated over and over again. Hi all - this is something that has occurred suddenly in the last 48 hours or so have their entire CS6 quit and stop working.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |