Skip navigation
seaneyefi
Currently Being Moderated

AIR 2.0 application with 2.5 Runtime Installation Error

Nov 4, 2010 5:43 PM

Hi there,

 

I'm getting an error while trying to install an AIR application. Basically, I just see the AIR installer dialog with an empty progress bar and an "Installing ..." message. Here's what the log file looks like:

 

Nov 4 23:07:57 MM /Applications/Utilities/Adobe AIR Uninstaller.app/Contents/MacOS/Adobe AIR Installer[201]: Commandline is: -psn_0_172074
Nov 4 23:07:57 MM /Applications/Utilities/Adobe AIR Uninstaller.app/Contents/MacOS/Adobe AIR Installer[201]: Installed runtime (2.5.0.16600) located at /Library/Frameworks/Adobe AIR.framework
Nov 4 23:08:02 MM /Applications/Utilities/Adobe AIR Uninstaller.app/Contents/MacOS/Adobe AIR Installer[201]: Runtime Installer end with exit code 6
Nov 4 23:08:02 MM com.apple.launchd.peruser.501[97] ([0x0-0x2a02a].com.adobe.air.Installer[201]): Exited with exit code: 6
Nov 4 23:15:15 MM Eye-Fi Center[226]: NSDocumentController Info.plist warning: The values of CFBundleTypeRole entries must be 'Editor', 'Viewer', 'None', or 'Shell'.
Nov 4 23:15:15 MM /Applications/Eye-Fi/Eye-Fi Center.app/Contents/MacOS/Eye-Fi Center[226]: Launching subprocess with commandline /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/Adobe AIR Updater -eula -nai
Nov 4 23:15:15 MM /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/Adobe AIR Updater.app/Contents/MacOS/Adobe AIR Installer[229]: Runtime Installer begin with version 2.5.0.16600 on Mac OS 10.6.4 x86
Nov 4 23:15:15 MM /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/Adobe AIR Updater.app/Contents/MacOS/Adobe AIR Installer[229]: Commandline is: -eula -nai
Nov 4 23:15:15 MM /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/Adobe AIR Updater.app/Contents/MacOS/Adobe AIR Installer[229]: Installed runtime (2.5.0.16600) located at /Library/Frameworks/Adobe AIR.framework
Nov 4 23:15:15 MM /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/Adobe AIR Updater.app/Contents/MacOS/Adobe AIR Installer[229]: Starting eula display
Nov 4 23:15:17 MM /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/Adobe AIR Updater.app/Contents/MacOS/Adobe AIR Installer[229]: Finished eula display
Nov 4 23:15:28 MM configd[13]:
Nov 4 23:15:29: --- last message repeated 2 times ---
Nov 4 23:15:29 MM /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/Adobe AIR Updater.app/Contents/MacOS/Adobe AIR Installer[229]: Finished eula display
Nov 4 23:15:29 MM /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/Adobe AIR Updater.app/Contents/MacOS/Adobe AIR Installer[229]: Runtime Installer end with exit code 0
Nov 4 23:15:29 MM /Applications/Eye-Fi/Eye-Fi Center.app/Contents/MacOS/Eye-Fi Center[226]: Subprocess /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/Adobe AIR Updater failed (1)
Nov 4 23:15:29 MM configd[13]:
Nov 4 23:15:59: --- last message repeated 14 times ---
Nov 4 23:16:31 MM /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheSe rver[156]: No valid tickets, timing out

 

Some background on the application I'm trying to install:

 

1. The application descriptor file points at the 2.0 version of the runtime. The application I'm trying to install has been packaged as a dmg.

2. I already have the 2.5 version of the AIR runtime installed on this machine, so I'm not sure why there are references to the EULA in the log file.

3. I'm not actively double clicking on the dmg file. The .dmg is actually being installed by a third party application via the command line.

 

Any ideas on what could be happening here or can you offer any remedial action on how to get this application installed correctly?

 

Thanks

 

Sean

  • Currently Being Moderated
    Adobe Employee
    Nov 4, 2010 6:24 PM

    Hi Sean,

    Do you know what parameters are being sent to the AIR native installer when it is being sublaunched?

     

    Thanks,

    Chris

    |
    Mark as:
  • Currently Being Moderated
    Community Member
    Nov 4, 2010 6:27 PM

    That looks like the log you get when we display the EULA on first app launch. You should only be able to get into that state if you've installed the runtime silently without accepting the eula.  Are you sure that's what you're getting when actually running the installer? You might want to clear out your logs and try again to be sure

    |
    Mark as:
  • Currently Being Moderated
    Adobe Employee
    Nov 11, 2010 11:58 AM

    Hi Sean,

    After doing those steps, was the runtime able to install? 

     

    We do have an open issue with the following folders possibly having improper permissions set:

     

    ~/Library/Application Support/Adobe

    ~/Library/Application Support/Adobe/AIR

    /Users/Shared/Library/Application Support/Adobe

    /Users/Shared/Library/Application Support/Adobe

     

    It's also possible for a user to have a bogus file named "Adobe" located in their /Applications folder.

     

    This was caused by older Adobe CS installers and it's something we're actively looking into.  However, I haven't seen anything regarding ~/Library/Frameworks or ~/Applications.

     

    Chris

    |
    Mark as:
  • Currently Being Moderated
    Community Member
    Nov 11, 2010 3:07 PM

    Hi, I'm the engineer who's dealing with this

     

    Now that I see all the new logs I'm pretty sure the root of the problem was that ~/Library/Application Support/Adobe/AIR or /Users/Shared/Library/Application Support/Adobe was read-only or otherwise inaccessible. We store some state there, to track whether the eula has been accepted and a few other things. The installer unfortunately doesn't handle being unable to write to either folder well and gives the unhelpful errors you've been seeing. It's a relatively new issue that we've been seeing, and we're still not sure which other Adobe product or whatever else is setting the wrong permissions there. If you catch one in the act let us know. We've got a bug logged to make the installer robust enough to handle such cases or at least give sensible error.

     

    The line

    Nov 11 15:28:10 Gallifrey /Applications/Eye-Fi/Eye-Fi Center.app/Contents/MacOS/Eye-Fi Center[2722]: Subprocess /Library/Frameworks/Adobe AIR.framework/Versions/1.0/Resources/Adobe AIR Updater failed (1)

    is a bit of a red herring. Since we can't write the flag that shows the eula has been accepted, we try to show the eula when you launch your application. That EULA also can't write the flag, and we have a mess. It just happens that the EULA is displayed with the same executable that does updates

     

    Sorry you've been having some much trouble, but I hope that takes some of the mystery away

    |
    Mark as:
  • Currently Being Moderated
    Adobe Employee
    Jan 31, 2011 11:08 AM

    Hi Sean,

    I'm currently tracking a couple of open bugs related to the Mac installer.  The first, bug #2756259, deals with the possibility of a file named "Adobe" existing in the user's Applications folder.  This is another legacy issue, possibly caused by beta installs of CS applications.

     

    The second bug, #2756424, deals with the installering being unable to seemlessly handle incorrect folder permission levels.

     

    I understand what a pain this can be support wise, to help ease the burden on the customer I've put together a small applescript application that looks to rename the bogus file for the first bug, and fix the permission levels for the typical folder locations.  I consider this a temporary stop-gap until we can make changes in the runtimer installer.  Please feel free to take a look and let me know if it helps you out.

     

    Chris

     

    Edit: Remove the out of date AppleScript.  Instead, please see this post for the latest repair script details.

    |
    Mark as:
  • Currently Being Moderated
    Community Member
    Nov 18, 2010 9:30 AM

    Chris,

     

    Thank you!!  That Apple Script worked!  I've been baning my head against this for a while.

     

    Here's what's odd though.  I didn't have any CS4 apps on my machine, but I did have that /Applications/Adobe folder (which I renamed).  I only had the CS5 Master Collection installed (I recently reformatted and installed OS X fresh too, so I can guarantee there were no upgrades).  The only CS4-related apps I have on my machine (using the old installers, updaters, and licensing engine) are Flash Builder 4 Premium and ColdFusion Builder 1.  So I'd suggest looking into those.

     

    I had tried setting the folder permissions to 755 manually, but it didn't seem to work (I'm sure I must have missed one or something).  Also, what's odd is that the installer previously would not create the folder (and data) for /Users/Shared/Library/Application Support/Adobe/AIR, however it would if I ran the installer from terminal using sudo (and in that case the installer would complete without an error window or in the system logs), yet the install would still be hosed.

     

    Feel free to ping me offline if you want me to help test with anything else regarding the possibility of Flash Builder 4 or CF Builder 1 installer possibly causing any permission issues (I'll be happy to offer any testing you want to run by me).

     

    --

    Jeff Coughlin (ACP)

    jeff [at] jeffcoughlin .dot. com

    |
    Mark as:
  • Currently Being Moderated
    Adobe Employee
    Nov 22, 2010 4:41 PM

    Hi Jeff,

    Thanks for letting me know it helped!  I'm going to work on getting this added to our tech doc and we'll also address these problems in an upcoming release.

     

    Chris

    |
    Mark as:
  • Currently Being Moderated
    Adobe Employee
    Dec 6, 2010 1:58 PM

    Hi Sean,

    This Mac only update was created to address a camera API bug first reported on this thread.  The mac installer bugs are still on track to be fixed in an upcoming release.

     

    Chris

    |
    Mark as:
  • Currently Being Moderated
    Adobe Employee
    Jan 31, 2011 12:12 PM

    Hi Sean,

    Thanks for bringing this up again.  I just took a look at the status for both 2756259 and 2756424 and they are both marked Closed / Fixed for AIR 2.6 which is scheduled for release in the next several weeks. 

     

    Bug 2756259 ("Cryptic error message when the runtime installer fails with the file "Adobe" present in /Applications") has been addressed by having the AIR installer now giving a detailed and understandable error so that users can manually deal with the presence of this file themselves.  The silent install will fail, but the log message is now more readable.  We did not want to alter an existing file on the user's machine, so this seemed the best option available.

     

    Bug 2756424 ("Runtime installer is unable to work around folders with insufficient permissions during installation").  The AIR Installer will now automatically correct the permissions level for the "~/Library/Application Support/Adobe", "/Users/Shared/Library/Application Support/Adobe" and "~/Library/Preferences/Macromedia/Flash Player/www.macromedia.com" folders.  This will work in both gui and silent modes.

     

    In the interim, please feel free to forward people to this post which contains a small AppleScript which attempts to address these issues.

     

    Thanks,

    Chris

    |
    Mark as:
  • Currently Being Moderated
    Apr 9, 2011 8:02 AM

    need help!!!

     

    tried everything in this post and others that refer to the same installation issues and still keep getting the "An error occurred while installing Adobe AIR. Installation may not be allowed by your administrator. Please contact your administrator."

     

    I would really like this to resolve since I like my adobe air products and would like to have them work on my new mac without any issues...

    can you suggest anything else?

    |
    Mark as:
  • Currently Being Moderated
    Adobe Employee
    Apr 11, 2011 5:14 PM

    Hi traknon1,

    I'm sorry your having problems installing AIR.  Would you mind creating a new post and include the AIR install log from your system so we could investigate further?

     

    Thanks,

    Chris

    |
    Mark as:
  • Currently Being Moderated
    Community Member
    Apr 11, 2011 5:32 PM

    chris,

    i resolved the problem.

    thanks.

    traknon

    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points