Adobe CS 5.5 package error

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

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...

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

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
~~~~~~~~~

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)

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

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