Are you using Composer to capture the "Install....." in the Applications folder, then uploading it via jamf admin or trying to drag the installer as is in to jamf admin?
The pkg is from the installer file in the applications folder. When run, the pkg just places it back in that same folder. Yes though, we use composer to capture it in the folder.
I had issues with an Adobe CC package. I switched the File Share Distribution Point to a local server, uploaded the package with Jamf Admin, and then replicated to the cloud. It's not convenient but it works.
same issue here.
You may need to reach out to your Jamf buddy to have an engineer look into your instance. We run Jamf on-prem on AWS and ran into these same issues when the web server was not allocated with enough space as it has to cache the file there before it gets placed on your Distribution Point.
@rpayne Did you get this resolved? I am having the same issue.
Also seeing the same issue today with small packages.
Same but luckily I'm on Premise and I can drag them on the SMB share (plus its waaaaaaaaay faster)
Supposedly my issue was sent to Engineering but I have not heard anything at all since yesterday and my replications are still failing.
Was having the same issue on 6/16 for packages of any size. Some would upload properly after the second or third try or after renaming. Are there limitations on name length or other things. I would guess no special characters. I try to limit those to . _ but sometimes a package may have a long version number and contain multiple periods like Chrome usually does.
I've heard back from the escalated support, Engineering is supposedly looking at the issue. We'll see how that goes.
Just heard back again (sorry for spamming this post) and they have identified the failure in the logs.
The evidence in the logs is consistent with the issue now on the rise where we see the FileRecombinationJobCoordinator showing “0% complete” over and over again until we see Recombine task failed for file [<package>] in bucket.
Engineering is on it, I'll update with any further developments.
Just uploaded The Office 16.38 updates out of 5 uploads 2 hang at availibity pending for a long time and then fail. OneNote and Word are the ones that fail and they were the 2nd and 5th upload. So its pretty hit or miss on size and timing.
Magically working today for the same exact packages that failed before. Did not re-download or repackage anything.
I'm still getting the same errors that I have been seeing since Tuesday. @MollySchmidt
Same here. Uploads to the Jamf Cloud Distribution Point have been failing intermittently over the past several weeks but are failing consistently now. This is the case when attempting to upload either via Jamf Admin or the Jamf Pro Console. Tried renaming the packages but that did not help. The weird thing is, the uploads do not error out and appear to complete successfully. The only way to know if the upload was really successful or not, is to display the individual package in the Jamf Pro console, which is tedious. I wish Jamf would fix this to display a green or red dot next to each package in the list so the upload status could be seen at a glance and failures would stand out. We have reported the problem to Tech Support and are waiting to hear back.
I got a response from tech support saying they are working on it, and my ticket has been attached to a "product issue". Maybe it will be fixed with the upgrade roll out over the weekend.
@erichughes That would be nice. Unfortunately I'm a pessimist and expect this weekend's upgrade to add new bugs. LOLOL
Still no change on replication. I have not tried to upload anything new but both issues appear to be related.
It seems my last post was rather prophetic, they pulled the update due to a massive security bug.
I had similar issues with the Office update package. Renamed a couple times, tried admin and the JSS console, neither worked. Tried zipping (per supports recommendation) and uploading that - which failed. Finally renamed again (added a '1' to the end of the filename) and that uploaded and synced fine.
weird.
I had a few failing last week, and all are failing this morning. No change on the Status page though: https://status.jamf.com
Just received this in a response to my open ticket.
"After the surge in cases attached to this issue last week, our Engineering teams will be meeting this week to determine next steps. It is going to take time for them to find a code level resolution to the issues with the file uploader."
So it sounds like nothing at all has been done and they are thinking about maybe doing something sometime in the future but have to have meetings about it. I really can't stand the amount of corporate BS that has become the standard when dealing with Jamf.
Folks,
This "planned" feature gets at the heart of most of these issues
https://www.jamf.com/jamf-nation/feature-requests/6665/facilitate-uploads-to-cloud-distribution-point-via-api-or-other-non-manual-method
Vote it up and ask your support person why it's been "planned" since 2017...
I am having the issue on any size package. I am getting around the problem by first deleting the existing package on Jamf Cloud and recreating a new instance. I also then have to add the new package to any policies that used the previous package.
