Adobe CS 5.5 package error

[#1]

Hello,

It sounds like several folks here have had good luck creating and deploying a package for Adobe CS 5.5. I have not, and I hope someone can tell me what I'm doing wrong.

I'm creating a package for CS 5.5 Design Premium using the AAMEE ver 2.0 tool, and I've been careful to follow all the instructions in both Adobe's manual and in the Jamf whitepaper (http://jamfsoftware.com/libraries/pdf/white_papers/Simplifying-Adobe-CS5-Administration-with-the-Casper-Suite.pdf).

If I deploy this package manually by clicking on it, or silently through the command line (sudo installer...), it always works perfectly. However, if I try to install it using Casper remote, it only works about 1/3 of the time, and if I try to install install it as part of a configuration with Casper imaging, it never works. I've tried re-creating and re-uploading the package a couple times, with the same results.

When it fails, I see the following in the jamf.log file:

Tue Jul 19 20:18:22 Image_Drv_X jamf[1629]: Installing SCS-app-Adobe_CS5.5_Design_Prem.pkg...
Tue Jul 19 20:19:20 Image_Drv_X jamf[1629]: Installation failed. The installer reported: installer: Package name is Adobe Setup
installer: Installing at base path /Volumes/Mac_Cluster
installer:PHASE:Preparing for installation…
installer:PHASE:Preparing the disk…
installer:PHASE:Preparing Adobe Setup…
installer:PHASE:Waiting for other installations to complete…
installer:PHASE:Configuring the installation…
installer:STATUS:
installer:PHASE:Writing files…
installer:%7.754527
installer:PHASE:Running package scripts…
installer:%14.730719
installer:PHASE:Running package scripts…
installer:%21.145954

(and so on, until...)

installer:PHASE:Running package scripts…
installer:%88.504174
installer:%97.750000
installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)

It seems odd that the second line there says "Installation failed", yet it keeps on running with the percentage ticking up for a couple minutes after that. I can't find any other logs that indicate what specifically went wrong. Does anyone have any ideas?

Thanks,
Kevin Graham
OIT Student Computing Services

[ernstcs]

Is the PKG the tool created set to install to the boot volume at imaging time, is that option checked in Casper Admin? Might need that for Casper Imaging to work.

What options did you choose for AIR?

Craig E

[RobertHammen]

Which version of Casper? Deploying via http or AFP/SMB (override the policy defaults and try the other one)? What options have you chosen (disable EULA/AIR/et. al.) in AAMEE? Can you try via policy (i.e. scope it to a particular machine) instead of Casper Remote? That might help narrow things down a little bit...

[talkingmoose]

When creating the package, did you opt to not install the Adobe Air
On 7/19/11 7:59 PM, "Kevin Graham" <ktgraham at princeton.edu> wrote:
components? They can cause problems and should be installed separately.

--

William Smith
Technical Analyst
Merrill Communications LLC
(651) 632-1492

[SeanA]

Both Robert and Craig raised excellent questions. My questions relate to
the "Installation failed. The
installer reported: installer: Package name is Adobe Setup" error.
Depending on your answers to everybody's questions, this error may (or may
not) be relevant to your situation. (My thanks and credit goes to Don
Montalvo for providing me this successful solution to an "Adobe Setup"
problem I recently had).

The "Adobe Setup" error is usually related when Acrobat 9 or Acrobat X are
deployed via snapshot feature of Casper Suite. The error is caused because
the snapshot method causes aliases to be converted to folders and that
causes problems. In Acrobat's case, in a normal installation, Acrobat
creates aliases for Profiles and Recommended (within
/Library/ColorSync/Profiles); however, if a snapshot-created Acrobat is
used, then these aliases actually are folders. If a Creative Suite install
occurs afterwards while Profiles and Recommended are folders, then the
Creative Suite install will fail (the predominant workaround is to
remove/rename these folders beforehand, either in the Finder or in the
Acrobat snapshot package).

The "Adobe Setup" error can also happen when the PKG becomes corrupt as
well. This can happen when uploading to JSS via Casper Admin hiccups, or
when replicating shares. If you do an exact size comparison (Get-Info >
General > Size > look for byte size in parenthesis) between a working
package and what you have in JSS, do they match? If not, re-upload to JSS
and try again. If they do, check for permissions issues in JSS.

Sean
~~~~~~~~~
Sean Alexander
Desktop Analyst
Macintosh Services Delivery
Lockheed Martin - Enterprise Business Services
~~~~~~~~~

[#6]

This script should help fix the symlinks issue. Run it after the snapshots but before building the package.

#!/usr/bin/python

import os, sys

def join(paths):
paths = list(paths)
for i, path in enumerate(paths):
if i > 0:
while path.startswith('/'):
path = path[1:]
paths = path
return os.path.join(*paths)

def remove(item):
if os.path.isdir(item) and not os.path.islink(item):
os.rmdir(item)
else:
os.remove(item)

def delItem(item):
if os.path.isdir(item) and not os.path.islink(item):
for container, dirs, files in os.walk(item, topdown = False):
for i in files + dirs:
remove(join(container, i))
remove(item)

def fix(pkgRoot, fsRoot = '/'):
for container, dirs, files in os.walk(pkgRoot):
container = container.split(pkgRoot, 1)[1]
while container.startswith('/'):
container = container[1:]
for item in dirs:
try:
link = os.readlink(join(fsRoot, container, item))
except OSError: # [Errno 22] Invalid argument: 'whatever'
pass
else:
if not os.path.islink(join(pkgRoot, container, item)):
print "Fixing %s => %s" % (join(pkgRoot, container, item), link)
delItem(join(pkgRoot, container, item))
os.symlink(link, join(pkgRoot, container, item))
else:
del dirs[dirs.index(item)]
for item in files:
try:
link = os.readlink(join(fsRoot, container, item))
except OSError: # [Errno 22] Invalid argument: 'whatever'
pass
else:
if not os.path.islink(join(pkgRoot, container, item)):
print "Fixing %s => %s" % (join(pkgRoot, container, item), link)
remove(join(pkgRoot, container, item))
os.symlink(link, join(pkgRoot, container, item))

if name == 'main':
if 1 < len(sys.argv) < 4:
fix(*sys.argv[1:])
else:
print "Usage: sudo %s PKGROOT [FSROOT]" % (sys.argv[0], )
sys.exit(2)

[sean]

I have seen this exact same error, 97.75% and then fail, yet local installs fine. Problem, no BOM! Casper Admin should automatically create a BOM when adding, but sometimes it doesn't. Pushing a newer version of the package wont make any difference if Casper Admin still doesn't create the BOM.

Quit Casper Admin and then re-open. If there is no BOM, then you should be prompted to create missing BOM files. Okay that and you should be good to go. Drove me mad for a little while.

Sean

[jake_snyder]

What is BOM? We're also failing at 97.75%.