Skip to main content
R
robert_humphreys
Inspiring
January 17, 2013
Answered

AAM causing a loop not allowing any Adobe Apps to launch.

  • January 17, 2013
  • 4 replies
  • 1346 views

I have CS6 Design Premium build created with the AAMEE tool. It's on my Builds, and has been pushed out to existing machines.

It's worked great, and i'm only having problems with one machine.

Adobe CS6 worked fine for a couple months, then one day, out of the blue, No CS6 apps would launch, the icon counces once, the AAM comes to the dock and bounces, then they both quit and relaunch about 10X in sequence and immediately quit, and then jsut stop trying.

It's bad for any user of the machine, including root and Admin.

The CS 5.5 apps all work fine.

I gave up and deinstalled/reinstalled CS6.

That worked for 2 days, and now it's happening again.

I figure I should ask about this. It's not a big deal to just wipe/rebuild the machine, but it's not Prefs, Cache's; I tried removing those.

It's happening to any user on the machine, so it's not a user/permissions problem.

I just thought I should get on top of it before it starts happening to my 70 other users that have the same build/install.

Anyone seen this before?

    This topic has been closed for replies.
    Correct answer robert_humphreys

    So, after the call with the Adobe Tech today the machine is working again.

    Basically, what he did was, put the filder with the Serialization File and the prov.xml file ontot he desktop.

    Opened Terminal

    Dragged in the Serialization file

    added this: --tool=VolumeSerialize --provfile=

    dragged in the prov.xml file

    and hit enter

    It ran and got a Return Code =0

    Now the apps run.

    The tech is sending it over to Engineering to get me either a batch file, or a Patch file.

    If he gets me something I can run for the next time that automates this or a Patch, I'll report back.

    But that seems to fix the issue.

    I'm not a scripter, but it should be pretty easy to use ARD to put the Serialization folder onto the Shared directory of every machine.

    Then just run a script or command from ARD or SSH that re-serializes CS6.

    4 replies

    alfiedagit
    alfiedagit
    New Participant
    August 7, 2015

    My AAM just bounces onthe dock too.. even tried the Adobe cleaner tool
    What is a serialization file????

    J
    jcincbus
    New Participant
    January 24, 2013

    I too am having this problem. I have gobs of machines in use that could potentially have this problem. Though at the moment it is only a few but this could mushroom to about 180 machines. Thank you for any updates as to what fixes it for you. So far uninstall and re-install minus patches has made my test machines functional again. So has unserializing and reserializing the installation with a pkg that I created with https://github.com/gregneagle/makereserializationpkg

    Though I am only about 3 hours into dealing with the problem. I will check on the machines in a few days time. If I don't post report of a failure here please assume that both these methods worked for me. Cheers,

    R
    robert_humphreysAuthor
    Inspiring
    January 24, 2013

    I had a second machine start with the issue.

    I tried the fix of re-serialization myself using this command from the Adobe Tech.:

    adobe_prtk --tool=ReplaceSN --serialize=LEID --serial=SN

    I got a return code of 6 and it did not work.

    So, I have another call with Adobe (same tech) today, and will report back when it's done.

    R
    robert_humphreysAuthor
    Inspiring
    January 22, 2013

    On Friday, i let an Adobe Tech remote onto the problem machine. After trying a few things. I suggested a re-application of the Serialization file.

    The tech agreed, and went ahead and re-applied the Serialization file, but he did a couple of things in the /Library/Application Support folder also. Then ran the Serialization file a second time.

    We did this while in the Administrator's account, not the users.

    I did not get to see exactly what he did, asi was busy on a couple other things while he was on the machine.

    But, as of this morning, the fix is still working. Everything is fine now. Whatever the solution is; it HAS to do with the Serialization file.

    A
    Anonymous
    January 17, 2013

    Yes - I have.

    I posted about this yesterday.  I'm five messages below yours.

    http://forums.adobe.com/message/4999200#4999200

    R
    robert_humphreysAuthor
    Inspiring
    January 18, 2013

    Yeah, i tried the Serialization file before when my deploys of CS6 suddenly went unuseable. That did fix them.

    This one is something that the serialization file won't fix for me this time. It's a clean CS6 deployment that works on 50 other machines, just this one is having a problem.

    We have a support Contract, and Adobe is on the machine, and my phone, trying to see what's going on. Hopefully he will figure out what it is. I'll try and post back if he is able to resolve the issue..

    A
    Anonymous
    January 18, 2013

    It looks like re-applying the serialization will only temporarily prevent this issue for a couple of days before it starts over again.  Rumor has it that Adobe is close to having a fix for this and some of the serialization issues they are having with AAMEE packages.

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