Adobe CS6 crashing loop.

Same here, unfortunately...
At 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).
To me, it looks like something related to AAM checking for licensing.
I have already posted here on the Adobe forum but have not found a solution yet http://forums.adobe.com/message/4964592#4964592

The relevant console message I got was this

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 already checked all the relevant folders within Library/Application Support/Adobe and they have the right permissions.

I am VERY worried (and disappointed) because I thought I could live with this until the transition from CS5/10.6 to CS6/10.8 but today a couple of the clients already with CS6/10.8 - first fully updated and manually installed to what is now my "base" image for 10.8 - called to report the same problem, after some week of smooth usage.
Hope that someone from Adobe will soon tell us what to do, as I find it weird that something that seems to be properly installed suddenly stops working without any reason (also most of 10.6 clients showed that issue after some day) and - since all clients comes from the same image and receive the same periodic updates/apps - I wonder how come some is fine and some is not.

Thank you for bringing this up!
Ciao
Carlo

Same here. Was just going to sort out a user UAT group before rollout and this happens!

Adobe loathing is coming back!

So far, the only thing that has fixed this on the affected computers is a full uninstall and reinstall of the Adobe CS6 suite. Just to be sure there wasn't an issue with the packages, I rebuilt my CS6 package using AAMEE 3.1.

~Ted

Take a gander at this thread: https://jamfnation.jamfsoftware.com/discussion.html?id=6289#respond

Don posted a link to a write up Greg Neagle did about the issue and a fix.

Guys don't let Adobe get away with this absolute Munson!

I have seen Adobe delete posts they don't like on their enterprise blogs and forums.

Post here on JAMF and keep pasting the links.

They can't sweeping the screw ups under the carpet!

Thanks guys and to Greg. I find Gregs site the easiest and clearest to use instead of getting lost in the Adobe maze

have this problem and pkgs ARE built with AAMEE 3.1

@Tim, RUM??

what about RUM?

Possibly...... if i find out it was a dodgy update i am scrapping RUM and never using it again and never updating.

We haven't seen this with our Mac CS6 installs yet... around 1000 of them. Used AAMEE to package them up last Sept.

Our Windows versions did use 3.0 and started having this problem. 3.1 seemed to help.

@tkimpton: What/who an "absolute Munson?"

@bentoms: Remote Update Manager. Can tell the CS6 suite to grab its updates from an internal server and install them instead of going all the way to Adobe's server to download the updates. We tried it out here and seemed fine for what it offered. Back in late summer/early fall when we tried this, the biggest problem was that when we updated our local update repository, it grabbed whatever was available from Adobe. Then the clients would then grab the latest from our repo. While great if you just want to go along with the latest, but if you need some version control, then need to be very careful when you update the local repo. Asked Adobe to add a feature to allow us to choose which version each app should install, but haven't heard anything since and haven't bothered looking.

We have it in place but won't be using it for our Macs. We'll be upgrading every year due to Apple's OS releases and we'll toss on new CS updates at that time. If we really, really need to push out an update, then AAMEE will take care of that. Might use it for our PCs, but that's someone else's headache.

@Tim.. i was asking if you guys use RUM, maybe it's not a AAMEE 3.1 thing & instead a RUM new update thing?

No RUM here
CS6 (Master and Design+Web) fully updated before closing the serialized AAMEE pkg (10.6 only) and/or when manually installed from Adobe dmg directly on the clients (10.8 only)
I am thinking of the last two updates (Photoshop 13.0.3 + Illustrator 16.0.3 ) that came out after deployment and installed creating an addition PKG from AAMEE I then deployed with Casper at login.
But the issue with the loop did start earlier that those.
Cheers
Carlo

That's what I thought Ben.

@Carlo I deployed mine via a policy in the form of a dmg and a script to mount and install it.

Also I include RUM and they update out of hours.

Have 2 tester one has hardly used it and hasn't had the problem and the other used it constantly and had it happening on Monday.

@Greg Roy Munson from the film Kingpin. With these continual goofs at Adobes end they will push every one away by being stupid and will lose everything

http://m.urbandictionary.com/#define?term=munson

Good news...
Created a policy to distribute and run serialization over a "broken" CS6 ("with loop") and everything seems fixed (until next time that happens...)
Policy tested from SelfService as logged user with closed Adobe apps
Until final fix from Adobe, I think I will put the policy ongoing at every login, so that at least users can start working. If the problem arises during the day, then manually from SelfService (or simply loggin out/in again).

I don't believe it's RUM. I just checked in a machine with a fresh install that just started crashing - again (after a re-install) - with the crashing loop between Photoshop and the Adobe Application Manager. RUM hasn't been launched in a few days, but this problem just cropped up today.

One thing I am noticing - when I open the Adobe Application Manager by itself, it forces an update from 6.0.281 to version 7.0.0.189. This update is being forced from Adobe, and it doesn't look like there is an option to disable it anywhere. After the update is completed, it asks for the Adobe ID credentials, ignoring the settings configured when the Adobe CS6 package was built in AAMEE 3.1.

I'm checking to see if re-serializing fixes this. If so, then it looks like my workflow is to reserialize all the Adobe CS6 installs on campus. More to come...

UPDATE - Indeed it looks like re-serializing Adobe CS6 resolves the issue - at least temporarily.

~Ted

Yep, I'll be re-packaging Monday morning. Funny thing is, today was the first day we deployed CS6 to anyone :(

Curses, Adobe!!!

Its happened again after a few days on a machine i already reserialized and was built using AAMEE 3.1

Adobe stop screwing with things, we know you are pushing to Cloud Ready and this is signs of Adobe screw-ups again!

Only thing i can do at the moment is put this in self service.

At this rate the users would be better of learning and using Quark instead!

I posted this morning:

https://jamfnation.jamfsoftware.com/discussion.html?id=6289

Is Adobe aware of this 'crashing loop' problem between the CS6 apps and the AAM? I haven't posted this issue there yet, and @donmontalvo, the posts you reference on the Adobe Forums seem to be for a related, but different problem. I'm not having any issue with getting a sign-in screen on the Macs in question, and the packages I built were built with AAMEE 3.1, not 3.0.

Something is definitely going on over there at Adobe, though, as the enterprise forum has been much busier as of late.

~Ted

@tedaugust04 Our Desktop Support folks report pushing the serial number to the user and rebooting fixed the loop for some users. I think they also applied the AAM patch.

@donmontalvo There is a patch for AAM? If so, is this a deployable package, or a manual install?

@taugust04 Oops...yes, sorry!

http://www.adobe.com/applicationmanagerpatch/index.html

@donmontalvo - thanks for the link.

Happened again today - in case anyone is interested, or having the same issue:

http://forums.adobe.com/thread/1136451?tstart=0

I have my logs and a video of the issue posted there via Dropbox.

~Ted

@taugust04 Lots of threads on this, and I'm betting you already know, Adobe released Photoshop 13.0.4 patch today, have you tried running it to see if it fixes the looping crash?

PS, might want to follow/post here so Adobe can keep their finger on the pulse of the Admin community...lots of updates on this and other issues:

http://twitter.com/Adobe_ITToolkit

Don

Thanks Don. Our whole company is using CS6 and people are starting to notice problems and are really shouting :(

Can't believe Adobes choice of comms is f**in Twitter!

Surely if I have RUM and my AUSS server polls Adobe updates at night then if this Photoshop update was to fix it people wouldn't be shouting ( machines get RUM checking at night) unless this update isn't on Adobe Servers yet which wouldn't surprise me!

Personally I'm not doing this faffing about and I'm not testing Adobes CRAP out when they should be doing it.

I want Adobe to sort it out even if I need a new AAMEE and remake the packages!

All I can say is GO QUARK LOL!