Adobe Acrobat Reader DC Install Failures, "No such file or directory" during postinstall script

pcrandom
Contributor

Has anyone tried to deploy Adobe Acrobat Reader DC, the latest full Continuous version 17.012.20093, and gotten failures like the above? I'm trying to switch ~800 Macs from Adobe Reader 11.x to Reader DC, and I'm getting having a ~40% success rate on installs, pushing through Jamf.

Most of the failures are similar what's seen in this install.log snippet:

Oct 27 08:49:46 hostname installer[75315]: PackageKit: Executing script "./postinstall" in /private/tmp/PKInstallSandbox.CCLu4X/Scripts/com.adobe.acrobat.DC.reader.app.pkg.MUI.CYQSSn
Oct 27 08:49:46 hostname installer[75315]: ./postinstall: /tmp/PKInstallSandbox.CCLu4X/Scripts/com.adobe.acrobat.DC.reader.app.pkg.MUI.CYQSSn/postinstall: line 6: pushd: /Applications/Adobe Acrobat Reader DC.app/Contents/: No such file or directory
Oct 27 08:49:46 hostname installer[75315]: ./postinstall: chmod: decompress: No such file or directory
Oct 27 08:49:46 hostname installer[75315]: ./postinstall: /tmp/PKInstallSandbox.CCLu4X/Scripts/com.adobe.acrobat.DC.reader.app.pkg.MUI.CYQSSn/postinstall: line 8: ./decompress: No such file or directory
Oct 27 08:49:46 hostname installer[75315]: ./postinstall: /tmp/PKInstallSandbox.CCLu4X/Scripts/com.adobe.acrobat.DC.reader.app.pkg.MUI.CYQSSn/postinstall: line 11: popd: directory stack empty
Oct 27 08:49:46 hostname installer[75315]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “AcroRdrDC_1701220093_MUI.pkg”." UserInfo={NSFilePath=./postinstall, NSURL=#application.pkg -- file://localhost/private/tmp/AcroRdrDC_1701220093_MUI.pkg, PKInstallPackageIdentifier=com.adobe.acrobat.DC.reader.app.pkg.MUI, NSLocalizedDescription=An error occurred while running scripts from the package “AcroRdrDC_1701220093_MUI.pkg”.} {
        NSFilePath = "./postinstall";
        NSLocalizedDescription = "An error occurred while running scripts from the package U201cAcroRdrDC_1701220093_MUI.pkgU201d.";
        NSURL = "#application.pkg -- file://localhost/private/tmp/AcroRdrDC_1701220093_MUI.pkg";
        PKInstallPackageIdentifier = "com.adobe.acrobat.DC.reader.app.pkg.MUI";
    }

Seems like files are extracted to /tmp but then disappear by the time the postinstall script runs. There's no apparent commonality amongst the Macs that fail or that succeed, but the frustrating part is that it installs fine on a significant number, and often will succeed on a Mac that it failed on before, after the second (or sometimes third) install attempt.

2 REPLIES 2

CasperSally
Valued Contributor II

Have you timed a manual install?

My experience with Adobe is the updates take ~10 minutes install, and if client loses connectivity or shuts lid, etc, you'll see these kind of failures.

We stopped rolling out Reader and told users to use Preview. Only users who proactively download Acrobat Pro get it, and we patch and still see these errors, but we just keep attempting to patch until it's successful. I'm glad we only have <200 users now with Adobe Pro installed (previously everyone got Reader).

pcrandom
Contributor

We've not had as much of a problem when pushing out Adobe Reader 11.x updates, but when pushing out this switchover to Adobe Acrobat Reader DC, the install failure rate is so significant, but then so is the success rate. That's what's so confounding.