Can confirm that the issue is still unfixed in version 14 of Parallels

Installation failed. The installer reported: installer: Package name is Parallels Autodeploy Package
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.)

Any new, news on this issue?

So answer me this, why does it install fine on some computers and no on others?

Installation failed. The installer reported: installer: Package name is Citrix Workspace
installer: Upgrading at base path /
installer: The upgrade failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)

Adobe Acrobat

Installation failed. The installer reported: installer: Package name is Adobe Acrobat DC (Continuous)
installer: Upgrading at base path /
installer: The upgrade failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)

@mhegge: Judging by the fact that it states it's upgrading, it's it could be because the version you are trying to install is the same version, or an older version, than the version currently installed on the computer. I've seen this with Adobe Acrobat due to it's auto-updater running and updating the application, but Jamf Pro not knowing this is the case because a recon hasn't been run to report that update back for policy/patch management scoping purposes.

@taugust04 From what I understand, both the Acrobat (download from Adobe Support ticket) and Citrix (download direct from website) packages are full installers, not upgrades, but I will check the machines getting the errors.

We are now seeing this randomly on various packages and policies. Installs fin on some computer, but other IDENTICAL computers, we get:

installer: The upgrade failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)

@mhegge : I don't have any experience with the Citrix installer, but, my experience with the Acrobat installers is that they will fail if they try to install on a system that already has a version of Acrobat that is the same, or later build, than what is being installed. I think this has to do with some poor (or perhaps intended) logic in their install scripts which do much of the heavy lifting during the install process. This includes the full versions of the packages Adobe makes available, not just the upgrades. Ordinary, Apple packages built in a more standard way would just overwrite the files regardless of versions, but there is a lot of customization done by Adobe in their Apple .pkg bundles that can go sideways very quickly.

I will see if that data correlated with what I have going on. Will involve a little research. I see it happening with a package created to update the AUSST information on Adobe CC installs. Seems to not like one of the faculty computers.

Thanks for a lot of input !

We're experiences the same problems with our Cirrato package (safe printing system).
Hope someone is coming up with something clever!

:)

Greetings all,
I am receiving the same error on many new packages, Chrome, FireFox, etc. This one happens to be VLC Player.
Error message in Self Service reads:
"Installation failed. The installer reported: installer: Package name is VLC Player 3.0.8
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. The package is attempting to install content to the system volume.)"

Updating the old VLC from 2.2.4 to this version. Multiple devices, same error. Cleared the var/log/install.log Trust Level = 100 Says package is not signed. This was created with Composer.
I guess I need to ask, where in the process do I "sign" the package. I am thinking this may have something to do with Integrity Protections in the Catalina and Mojave OS's.
Any and all help or ideas are appreciated.
Thanks all

I have been seeing this lately and there is nothing Jamf could say I have been working with them for over a month now does anyone has any known resolutions for this was anyone able to fix it?

I was seeing this a lot with pkgs that we install from cache where they get cached by a policy for all Macs in scope, then a smart group scoped to all Macs with the pkg cached should install it... there's naught to go by from the errors, but on a hunch I wrote a script that validates the checksum of the package and I run it on both the cache policy AFTER and the install cached pkg policy BEFORE... in all cases where I got this error the pkg did not successfully transfer as indicated by the script's checksum validation failing. Mind you, you may be experiencing this for different reasons in your environment.

Now if I could only get back the time I spent troubleshooting this and get http transfers working reliably. It seems like every time we get them working the server team upgrades the webserver and no one knows how to force the config to work again.

Same issue. "The package is attempting to install content to the system volume."

Hi everyone,

I have the same error with Cybereason...only happening on ONE system.

I have a script to remove the existing instance of Cybereason and then install the newer version.
I even tried caching it and then installing the cached pkg but same error.
I also tried caching it and then using a script to execute the pkg from the Waiting Room directory, same error.

All other systems deployed fine with the policy to remove and the install the newer version, its just this one system!

Script result: installer: Package name is Cybereason Active Probe
installer: Upgrading at base path /
installer: The upgrade failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. An error occurred while running scripts from the package “Cybereason ActiveProbe v19.0.120.0.pkg”.)

Almost 4 years old, probably longer, and no solution in sight?

This happens on a handful of mine for chrome and firefox. I'm stumped