Pro Tools 2018 Package Error

MBrownUoG
Contributor

Hello folks.

Just trying to package up Pro Tools 2018 in the same manner as this guide from last year: https://www.amsys.co.uk/packaging-pro-tools-12-deployment/

All the .pkg files work fine when dropped into Jamf, aside from the main Pro Tools package, which fails and produces the following in the logs:

Installation failed. The installer reported: installer: Package name is Pro Tools 2018.4
installer: Installing at base path /
installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)

However, running the .pkg directly on the Mac in question, it installs without any problem at all. Has anybody else come across this?

Checking the logs on the machine and it's showing the following:

2018-07-30 16:40:08+01 PKPackage002 installd[462]: PackageKit: Extracting file://localhost/Library/Application%20Support/JAMF/Downloads/Install%20Pro%20Tools%202018.4.0.pkg#License_Service.pkg (destination=/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/C/PKInstallSandboxManager/4471F250-FCEC-4944-9D98-E29BBC7FB384.activeSandbox/Root, uid=0)
2018-07-30 16:40:09+01 PKPackage002 installd[462]: PackageKit: prevent user idle system sleep
2018-07-30 16:40:09+01 PKPackage002 installd[462]: PackageKit: suspending backupd
2018-07-30 16:40:09+01 PKPackage002 installd[462]: PackageKit: Executing script "./preinstall" in /private/tmp/PKInstallSandbox.6h88sR/Scripts/com.avid.installer.osx.ProToolsApplication.jYFWk0
2018-07-30 16:40:09+01 PKPackage002 install_monitor[7693]: Temporarily excluding: /Applications, /Library, /System, /bin, /private, /sbin, /usr
2018-07-30 16:40:09+01 PKPackage002 install_monitor[7693]: PackageKit: Locking applications
2018-07-30 16:40:09+01 PKPackage002 installd[462]: ./preinstall: Use of uninitialized value $_[0] in substitution (s///) at /System/Library/Perl/5.18/File/Basename.pm line 341.
2018-07-30 16:40:09+01 PKPackage002 installd[462]: ./preinstall: fileparse(): need a valid pathname at ./install_utils.pl line 260.
2018-07-30 16:40:09+01 PKPackage002 install_monitor[7693]: Re-included: /Applications, /Library, /System, /bin, /private, /sbin, /usr
2018-07-30 16:40:09+01 PKPackage002 installd[462]: PackageKit: releasing backupd
2018-07-30 16:40:09+01 PKPackage002 installd[462]: PackageKit: allow user idle system sleep
2018-07-30 16:40:09+01 PKPackage002 installd[462]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “Install Pro Tools 2018.4.0.pkg”." UserInfo={NSFilePath=./preinstall, NSURL=file://localhost/Library/Application%20Support/JAMF/Downloads/Install%20Pro%20Tools%202018.4.0.pkg#Pro%20Tools%20Application.pkg, PKInstallPackageIdentifier=com.avid.installer.osx.ProToolsApplication, NSLocalizedDescription=An error occurred while running scripts from the package “Install Pro Tools 2018.4.0.pkg”.} { NSFilePath = "./preinstall"; NSLocalizedDescription = "An error occurred while running scripts from the package U201cInstall Pro Tools 2018.4.0.pkgU201d."; NSURL = "file://localhost/Library/Application%20Support/JAMF/Downloads/Install%20Pro%20Tools%202018.4.0.pkg#Pro%20Tools%20Application.pkg"; PKInstallPackageIdentifier = "com.avid.installer.osx.ProToolsApplication"; }
2018-07-30 16:40:09+01 PKPackage002 installd[462]: PackageKit: Running idle tasks
2018-07-30 16:40:09+01 PKPackage002 installer[7690]: install:didFailWithError:Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “Install Pro Tools 2018.4.0.pkg”." UserInfo={NSFilePath=./preinstall, NSURL=file://localhost/Library/Application%20Support/JAMF/Downloads/Install%20Pro%20Tools%202018.4.0.pkg#Pro%20Tools%20Application.pkg, PKInstallPackageIdentifier=com.avid.installer.osx.ProToolsApplication, NSLocalizedDescription=An error occurred while running scripts from the package “Install Pro Tools 2018.4.0.pkg”.}
2018-07-30 16:40:09+01 PKPackage002 installd[462]: PackageKit: Removing client PKInstallDaemonClient pid=7690, uid=0 (/usr/sbin/installer)
2018-07-30 16:40:10+01 PKPackage002 installer[7690]: Install failed: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.

5 REPLIES 5

allanp81
Valued Contributor

I think it's something to do with the account that Jamf uses during imaging, I've always had to just use composer to snapshot Pro Tools in the past and have done the same with the latest version and don't seem to have any issues.

MBrownUoG
Contributor

Ok, thanks Allan. Can I ask, do you just do a regular "New & Modified" snapshot and install with defaults? Do you trim anything out afterwards?

apizz
Valued Contributor

@MBrownUoG Personally I try to avoid repackaging software that's already packaged. Pro Tools has always been a pain because a user needs to be logged into the machine in order for the install to complete successfully. Can't just push it remotely w/ no one logged in.

MBrownUoG
Contributor

Ah ok, thanks for the tip. I'll try triggering the policy from a terminal session tomorrow morning and see if it functions from there. That'd probably work for us as we only need to install once a year before the new term starts.

robertojok
Contributor

Just completed packaging pro tools 2018.
I captured installation using composer and it worked fine.
Yes placing the installer in Casper admin doesn’t work.
I also dropped the dmg (but I guess you could drop the pkg) into a folder I created in /tmp. I then dropped that in composer and created a pkg which I added as a policy in Casper with a script that mounts the pkg, then the command installer -pkg /path to the installer on desktop then target /
On completion I added the unmount command and performed a restart.
That worked too.
I did the same for the extra content
I hope this works for you