deprecated pre-10.2 format

beatlemike
Release Candidate Programs Tester

Maybe I'm an idiot, it's highly possible. But recently I started getting errors in my JSS with recent updates I've been doing.

"Installation failed. The installer reported: 2017-09-25 05:31:42.696 installer[10946:69209] Package /Library/Application Support/JAMF/Downloads/AcroRdrDCUpdate-17.012.20098.pkg uses a deprecated pre-10.2 format (or uses a newer format but is invalid).<br/>installer: Package name is Adobe Acrobat Reader DC (17.012.20098)<br/>installer: Upgrading at base path /<br/>installer: The upgrade failed (The Installer could not install the software because there was no software found to install.)"

It's not just limited to Acrobat. I'm pretty sure nothing I am using is a deprecated pre-10.2 format. Occasionally one of these will even go through, but I'm left with 75 other machines failing.

I've looked at past discussions about this problem, and aside from one not so helpful "just retry and it will work" there is no explanation or help with this. I've retried... LOTS of time.

Does anyone have an idea what's going on?

4 REPLIES 4

bvrooman
Valued Contributor

I believe the "uses a deprecated pre-10.2 format" error is caused by a lack of signature on the package itself, and can usually be ignored.

For Acrobat Reader specifically, the main reasons I see it fail to install are a newer or same-as-installer version already being present (whether it's a full install package or just an update), an older version not being present if it's an update package, or the app being open when the installer runs. It looks like you're installing 17.012.20098, which came from Adobe as an update; what version of Reader is already installed on the machines in question?

You can also find better information in the /var/log/install.log file on an affected Mac. That will give you a lot more detail than the JSS policy log.

beatlemike
Release Candidate Programs Tester

The machine in question has Acrobat Reader 17.012.20093 installed.

This is what I see in the log:

2017-10-06 13:38:08-07 ITS-TSC-59061 installer[68899]: Product archive /Library/Application Support/JAMF/Waiting Room/AcroRdrDCUpdate-17.012.20098.pkg trustLevel=202 2017-10-06 13:38:08-07 ITS-TSC-59061 installer[68899]: -[IFDInstallController(Private) _buildInstallPlanReturningError:]: location = file://localhost 2017-10-06 13:38:08-07 ITS-TSC-59061 installer[68899]: -[IFDInstallController(Private) _buildInstallPlanReturningError:]: file://localhost/Library/Application%20Support/JAMF/Waiting%20Room/AcroRdrDCUpdate-17.012.20098.pkg#payload.pkg 2017-10-06 13:38:08-07 ITS-TSC-59061 installer[68899]: -[IFDInstallController(Private) _buildInstallPlanReturningError:]: file://localhost/Library/Application%20Support/JAMF/Waiting%20Room/AcroRdrDCUpdate-17.012.20098.pkg#RdrServicesUpdater.pkg 2017-10-06 13:38:08-07 ITS-TSC-59061 installer[68899]: Set authorization level to root for session 2017-10-06 13:38:08-07 ITS-TSC-59061 installer[68899]: Administrator authorization granted. 2017-10-06 13:38:08-07 ITS-TSC-59061 installer[68899]: Package file://localhost/Library/Application%20Support/JAMF/Waiting%20Room/AcroRdrDCUpdate-17.012.20098.pkg#RdrServicesUpdater.pkg not supported by PK 2017-10-06 13:38:08-07 ITS-TSC-59061 installer[68899]: Unable to use PK session due to incompatible packages. Terminating. 2017-10-06 13:38:08-07 ITS-TSC-59061 installer[68899]: Install failed: The Installer could not install the software because there was no software found to install.

So it IS failing because of the pkg it looks like, but it's just an autopkg pkg, are autopkg installs no longer supported? This isn't the only installer or updated from autopkg I've had fail this way.

bentoms
Release Candidate Programs Tester

@beatlemike If you try to install the pkg manually, what happens?

AutoPkg installs are still fine, this might be an issue downloading the pkg maybe.. which could be corrupting the download.

beatlemike
Release Candidate Programs Tester

@bentoms they pkg works fine manually.

I also tried having it cache the install first, didn't change anything, once it tries to install it gets the same failure,