I am now getting multiple systems that will not open Photoshop CS 6. As soon as PS starts to open, Application Manager starts and prevents PS from opening. The two applications alternate for control with neither being able to open. This problem is also occurring with Illustrator CS 6 and now has started in Photoshop.
When the "fight" starts you have to do a forced shut down (power button for 10 seconds) in order to be able to login. Then Uninstalling the application, either by the Uninstaller of PS or by using the ELA uninstaller created when the Install package is created. Systems are Apple 10.8.2 with Adobe Application Manager Enterprise Created installer for Master Suite.
This has now appeared on six or seven systems of the approximatly 200 that got the install. The applications ran normally with no problems for about two weeks bu now the problems are popping up for no appearent reason.
The image now installed is 13.0.1 That is the image that was created when AAMEE created the install package. This is the umage that was installed after the conflict. I do not know what version was installed at the time of the crash since once the conflict started any attempt to open Photoshop (or Illustrator for the systems that had that crash) results in the "fight" starting again with no chance to actually get Photoshop to open enought to even get its version number.
I will run a scan on all the systems I have with CS6 Master installed to try to get the versions installed and see if any correlation can be made as to which version is installed before a crash. I do know that some systems have been updated, using AAM without problems ocurring during the update and one system actually did go into "fight" mode when Photoshop tried to open after AAM had already started an update. That update was started manually. I am not sure why POhotoshop started to try to open at that time. It will take a while to do the scan to get the currently installed versions.
AAM version installed on the system I checked is 126.96.36.199 This was after the Photoshop reinstall on the system that crashed.
Just for info. One of the systems that crashed was on 13.0.4 It did change its crash mode while I was watching it. Previously a crashing system would fight the fight for a minute or more till I forced a shut down. Now the crashing 13.0.4 system fights the fight for about a half minute or maybe a bit less then both PS and AAM give up an do not open but at least the rest of the programs (other than Adobe which I did not try) will function. This fight will continue even after a shut down and cold start.
Again: are you crashing (getting a crash dialog and a crash report that we can use), or is it just the "who's in front" conflict that you described earlier?
You use the term "crash", but then the rest of your description sounds nothing like a crash.
Mine is doing the exact same thing (as above) and now it's happening to 2 different machines.
It's not crashing persay. The icon is just rebooting, . . . over and over and over for about 45 sec and then. . nothing.
Attached is the video showing what it does after you try to start any adobe application.
(use chrome to see video) flash thing
Everything is up to date.
OK, that is not crashing or rebooting (not even remotely - those words have specific meanings).
But something is wrong with licensing or AAM that is causing the apps to keep relaunching.
We'll need to get the licensing and AAM folks involved to figure out what is going on.
Thank you for the video. It is exactly what has been reported by me and some others in the Illustrator forum also. To me a "crash" is when a program fails to open properly and requires a forced power off to recover the computer. I will add that the same problem as shown will appear again as soon as Photoshop (or Illustrator if that is the broken program) is reopened. The problem will remain until PS (or AI) is uninstalled and reinstalled. The version I have for the installer is the older 13.1 but that had worked for several weeks and this problem just started recently and I had not installed (at least knowingly) any changed software be it PS, AI or AAM. prior to that time. I did have some systems at the latest update and at least one of those failed also.
I have tried creating an Update package from AAMEE but the package that is created does not install using Apple Remote Desktop nor does it install if the created package is copied to the desktop of the system I am trying to update.
It is looking to me like the problem is located in the Adobe Application Manager since that app is common to both Photoshop and Illustrator. I have tried using the AAM that installs as part of the Master Suite and the first thing it does is update itself. My guess is that this "update" that AAM self-installs is broken and is causing the problem. That is only my guess based on my observations. Perhaps someone can come up with a way to prove or disprove my guess.
My next project for tomorrow will be to try to create a brand new installer with all updates since trying to individually use the Update button in the actual Photoshop does work but I'll be damned if I am going to visit two hundred seperate machines to have to install the update on each and every system as a stand alone update, especially since I have already had at least one system that I know was on the latest update but still failed in exactly the way your video shows.
A follow up will be to try to remove the AAM and reinstall a new version from the Adobe web site just to see if that helps, hurts or has no discernable effect.
>> To me a "crash" is when a program fails to open properly and requires a forced power off to recover the computer.
Crashes are a very specific set of circumstances, usually followed by a crash reporting dialog.
And most crashes do not require restarting the computer (unless the OS has crashed).
The AAM team will need to get logs from your system to see what is happening.
Where are we with this? I can provide anything you need as I have a computer dedicated to finding a solution to this.
This is turning into abigger problem than it seemed. I now have 4 machines with this same issue.
HELLOOOOOO ADOBE, WHERE ARE YOU?
Since I am now up to 19 (and coutning) systems that have developed this problem. and the problem is also appearing when InDesign is opening, some acknowledgment from the AAM team at Adobe would be useful.
Chris Cox, if this is out of your realm, can you please put us in touch with the AAM team or at least point to where the forum is for AAM???
We already forwarded this topic to the AAM team. But I haven't heard anything from them.
AAM doesn't have it's own forum, but this is the forum for general install/setup/download issues (whihc should cover AAM): http://forums.adobe.com/community/download_install_setup?view=discussi ons
We encountered the same issue at our workplace. As we are not too sure why it was doing, we were able to fix it regardless.
It required running the AdobeSerialization file through the terminal. When running AAMEE, we checked the option that asked if we wanted a seperate AdobeSerialization file, which gave us a .xml file and the command to run it on a seperate folder that says CS6_Serialization.
If you guys find it, I can help in trying to re-run it.
Hope this helps!
Same issue here in a lab environment with over 100 installations. Thankfully only some have developed this issue and most importantly chila101's recommendation of manually re-serializing did work.
If anyone from Adobe is checking this I'll gladly provide troubleshooting info for you if you let me know what would be useful.
Thanks again to chila101 and to jpryes for posting the video.
To be clear:
-Run AAMEE and select "Serialization File" on your admin machine.
-Transfer that folder to the machine with problems.
-Drag the "AdobeSerialization" file (the file in the folder AAMEE created) in the terminal window and type --tool=VolumeSerialize
and hit enter.
This will re-serialize the Adobe Suite.
More infor found here: