Hey man, I'm having the same issue. I started another thread about this.

I've recreated packages as well. Check with your adobe rep, this may have something to do with adobe licensing.

By the way, I'm going to assume you're using enterprise licensing?

I get the same error code in the logs, 112. Nothing changed.

I started to have a lot on installation failures with the 2017 installer. I have device licenses for education. When erasing a computer and installing everything with a Casper configuration i was getting failures and about half of my computers over winter break. When I de-activated a computer from the Adobe web site it would then complete the installation most of the time.

On some computers where I was just trying to run the installer and not re-image the computer I sometimes get a failure. After deleting everything from the /Application/Adobe folder the installer completing the last couple of time I had a failure.

Adobe's installer cert for Acrobat has expired yesterday.

If you have one mega-package, this could explain why it's now failing. Rebuild as individual app installers.

Could also try changing the date back a couple of days and see if the installers work...

Confirming we're seeing the same issue; I'm on hold with Adobe Support (as chat is closed ???) and will provide an update.

Were seeing the same issues here as well. Seems to effect 2015 and 2017.

CCA Badge CJA Badge
Posted: 18 minutes ago by RobertHammen

Adobe's installer cert for Acrobat has expired yesterday.

If you have one mega-package, this could explain why it's now failing. Rebuild as individual app installers.

Could also try changing the date back a couple of days and see if the installers work...

I had this same thing happen to me. One mega installer was failing at random. Broke out everything to individual installers, and Acrobat was the only one that failed.

My Adobe install policy now has all the individual installers on it instead of a mega installer. More modular - I like it better.

Same again, Acrobat was the culprit. Made a package with about 4 base Apps (excluding Acrobat) and all was good.

Yes, it's enterprise licensing. Now that @ChickenDenders mentions it, I noticed the install stops at Acrobat. Glad I'm not the only one with the problem -- was going nuts.

Looks like our mega-package issue is related to Adobe Scout 1.1.3 which the Adobe rep told me has known installation issues on macOS 10.12.3. (I asked about 10.12.x, but she wasn't sure.)

Apparently, re-building the mega-package sans Adobe Scout resolves the issue.

You can search ~/Library/Logs/PDApp.log for ASCT1.1.3 to see if this applies to your situation.

My case number with Adobe is 018-869-8440 in case that helps shorten your call.

Thanks a bunch, @dan.snelson . I'll build a mega-pcakge sans Adobe Scout and respond.

Acrobat (both XI and DC), Scout, and Lightroom 5 are all signed with the expired developer cert. Adobe is aware of this, no idea on ETA to respond.

@RobertHammen Thanks for the additional details.

Do you happen to have an Adobe case number I could reference with Adobe support?

@RobertHammen Setting the date back to Tuesday seems to have worked for me

A freshly created mega-package sans Adobe Scout just worked for me in our Stage lane.

I'm going to move it to our Production lane for our testers and will advise.

+1 for Scout causing installation failures on macOS 10.12.3.

Yay! So many Adobe installation problems on a single thread!

I just build the Acrobat DC and Lightroom packages and the now seem to install fine again but scout is still causing this issue. Seems like adobe solved it for the first two apps. Hope they fix it for scout soon so we can provide our class rooms with fresh images...

+1 for mega package, minus Scout on 10.12.3. It's either that or the modular approach. Please let us know what you hear from Adobe @dan.snelson

I had the same, It's down to the poxy Adobe CC packaer tool.
It just sucks.

I had to d/l another copy of CC packager and build a new package on a Vanilla mac.

In our production lane, the same freshly created mega-package sans Adobe Scout has worked twice and failed twice. (Worked for my boss, so what else matters?)

We're using Adobe's Log Collector Tool to provide Adobe's tech support additional details.

An update from Adobe …

Your Case Number:0188698440
Case Description:package failure issue

From: Enterprise-Support@adobe.com

Hi Dan,

We're seeing this issue with more customers, so it's been logged as a bug. There are two workarounds: one is to create a package without those applications, at least until the bug is fixed. The second is to backdate the computer to before the 21st. Neither are satisfactory, I understand. I've added your case number and name and email to the bug, and I'm watching the bug, so as soon as I receive data on it, I'll let you know. Please feel free to emailme with any concerns, questions, or requests for updates.

Best regards,

… seeking clarification on without those applications.

Clarification on impacted applications (as previously documented by @RobertHammen):

Your Case Number:0188698440
Case Description:package failure issue

From: Enterprise-Support@adobe.com

Hi Dan,

Apologies. Acrobat, Scout, and Lightroom.

Best regards,

Some strategies and options here, as well as a bit more clarification on what software revisions are affected: Adobe Package Expiration.

Notably Scout is the only affected title that's not currently hidden behind Creative Cloud Packager's "Archive" checkbox and included when the very-tempting checkbox for "all" products is checked.

We tried the following workaround (removing the Scout installer package from the custom package), and it worked because our custom package is relatively new.

(1) Create a dummy package named 'Scout_1_1_3_LREFJ.pkg'. This package is a payload-free package and its postflight script simply returns zero (successful installation).

<postflight>

#!/bin/sh

exit 0

(2) Replace the following package with the above payload-free package

<Package_Root>/Contents/Resources/Setup/ASCT1.1.3/Scout_1_1_3_LREFJ.pkg

Your Case Number:0188698440
Case Description:package failure issue

From: Enterprise-Support@adobe.com

Hi Dan,

The issue has been fixed for Acrobat, so if you clear the packager cache, and make sure you have new copies of everything,you'll beable to make packages with Acrobat. We're working on this issue with regard to Adobe Scout and Lightroom. Please see this technote:https://helpx.adobe.com/creative-cloud/packager/creative-cloud-package-installation-failed-error-message.html

Best regards,