Hi Nation, I am receiving the following message when trying to upload a package to Jamf Cloud:
Package failed to upload
The package has only 64 KB, I was able to upload other packages before, not really sure about what is going on...
Has anyone been through the same issue ?
I seem to be seeing the same problem over the last couple of weeks. I upload packages, they seem to be stable. I deploy the policy and see it fail, then call it manually and get an error that says the package is not available. After I look at the packages I'm finding most of them are now stating "Upload Failed"
I’ve seen this issue before. I did the following to fix.
After I did this it worked.
From jamf support engineer: “Spaces in file names, mainly packages and script just a bad time with Jamf Pro. Naming files with camelCase, named-with-dashes or named_with_underscores are just better.”
Hope this helps!
+1 to @zachary.fisher 's workaround.
I've been having problems uploading the newest Microsoft Office v16.38 pkg this whole week via the web gui and jamf admin. After deleting all pending pkgs, renaming the local pkg with no spaces and no underscores, I was finally able to successfully upload the 1.64GB Office pkg.
I just finished testing a deployment of this new pkg to my own Mac with great success. Hopefully this can help others get around this annoying issue while Jamf gets around to fixing it properly.
So I also talked to the Jamf Support today and they asked me to simply in Jamf Cloud GUI go to:
Management Settings > System Settings > Activation Code > Edit
and then re-paste the activation code and Save (this resets something, don't know what).
Then uploading packages worked again!
@chrisB I am discovering this as well. Here's what I know:
This means any package definition I have in Jamf cannot be updated, but can only be recreated. This obviously breaks links to existing policies and PreStages. I deploy a lot of zero-payload packages that run scripts in a PKG for the exact reason I can only deploy PKGs in PreStages and Patch Management.
Hope it gets some attention, my day just got a looooot longer 😅
Thank you for this information.
Do you know if the problem is fixed because we still have the problem. We are still unable to upload files (pkg, zip or dmg) from Jamf Admin to the Cloud distribution point.
All our packages are "Upload failed" in the JSS (no error on Jamf Admin).
I can confirm that re-uploading packages to existing definitions in Jamf works. Creating new definitions with names which previously existed in the package list does not work, however. If you rename the package and upload it it should work for now. Long term this is not fixed yet but it's a workaround for the time being.