Skip to main content
Participating Frequently
October 21, 2014
Question

CCP built installer random failures on OSX

  • October 21, 2014
  • 3 replies
  • 1651 views

We built and deployed (via Munki) a full CC master collection in late August to all of our labs here at a college, but we're now running into issues that we hadn't realized happened at deploy time.  Quite a lot of the installs seem to randomly fail on certain packages -- namely we're ending up with machines that don't have AIR, Desktop Publishing Tools and Flash Player.

To test things further now that there have been some updates we are building new packages to update and/or deploy as required, but now we're seeing other random failures both when trying to deploy via Munki or manually installing by hand.  These are failures that I've never seen before, like the OSX installer just stopping with the progress bar showing it being less than half way through the install and the button at the bottom right simply showing "Close".

The logs haven't been any kind of help in this so far, I cannot find any actual failures.  When deploying via Munki things all show up that they are installed with no issues, when doing it manually I looked through all of the logs I could find for the installs and didn't see any failures (but all of the installs didn't run).

I'm not sure where we can turn from here, we are in a bit of a stick place right now as our old install mostly works (it often fails at 124 or 127 pkgs in the payload) and any new builds we try to install don't even make it half way through the install.  We've done the CCP builds on different machines, etc but end up with the same results.

Does anyone have any suggestions for how to actually deploy the full master suite and updates in an educational environment?  We do need AIR and AIR based installs as a bunch of our curriculum requires DPS Tools.  Last week I spent days manually installing AIR and related tools on a ton of lab machines (they would fail if the GUI wasn't running when the install happened even following Adobe's directions).

Any help of suggestions would be appreciated.

This topic has been closed for replies.

3 replies

Inspiring
December 1, 2014

MarkGerk,

  Did you get this figured out?  I have a roundabout way that appears to reliably install DPS Desktop Tools for InDesign CC2014, but I'm not sure if it would help InDesign CC or not.

Participant
December 1, 2014

I would love to hear the workaround if possible, I'm trying out CCP for the first time and seem to have the same random-failure problem on certain machines.

Inspiring
December 1, 2014

CCP 1.7 on the Mac starts with the most conservative settings (ignore conflicting processes, do not install AIR-based components).  Are you changing those settings?  More details are needed.

MarkGerkAuthor
Participating Frequently
October 21, 2014

Another note to add to this issue, I think I'm getting closer to figuring out some of the lower level issues here.  CCP is building multiple packages for us (both when we build a single package or when we build one-off packages per product) that are using the same mediaSignature.

Just guessing but I think this is probably the root of all of the issues we're having here.  When using Munki it certainly is, after some digging in the source it seems like Munki is using the mediaSignature as a sort of unique identifier.  Not sure if this is related to the failed manual installations yet ...

Just talking to myself here ... carry on folks

jpeters36
Inspiring
October 28, 2014

im failing out with a manual install of the pkg, on multiple machines. the log file shows an error on "un-intsall installation not present" and yes i am selecting the install package, wondering if the packager is corrupted ive recreated it twice now so its not just a corrupted package

MarkGerkAuthor
Participating Frequently
October 21, 2014

And of note to add to the conversation, the "random" part of the failures if that in one lab, for example, we deployed 27 machines with the exact same Master Collection package that was built with CCP and on almost 2/3 of the machines it failed at pkg 124 (adobe AIR), but on other machines it all ran fine.  None of the machines showed a single error anywhere in the logs but the machines that failed are missing components (namely and most visibly in the /Applications/Adobe folder there is only an AdobePatchFiles folder (and no Adobe Content Viewer or Flash Player).