Skip to main content

I received this error message on 5 machines this morning.
I'm assuming that our policy to recon tried to run but couldn't because the user terminated their connection in the middle of it.
I just wanted to see if anybody else has seen this before.
Thanks



Executing Policy JAMF Recon
Running script JAMF Recon...
Script exit code: 1
Script result: Retrieving inventory preferences from https://
Finding extension attributes...
Locating applications...
Locating accounts...
Locating software updates...
Locating package receipts...
Locating plugins...
Locating printers...
Locating hard drive information...
Searching path: /Library/Internet Plug-Ins
Searching path: /Users/[domain username]/Applications
Searching path: /Users/[Local Admin Username]/Applications
Searching path: /Applications
Locating hardware information (Mac OS X 10.14.5)...
Gathering application usage information...
Submitting data to https://**
There was an error.



Connection failure: "The operation couldn’t be completed. ( error 502.)"
Error running script: return code was 1.

This issue started happening to us as well, we have an open case CS0995650 and already escalated to the highest level of support, but no one can figure out the fix or the root cause at least.  I searched Jamf Nation as well, but can't find a Solved post.  Please, if one of you resolved this, and you have case number I can share with Jamf Support, please be so kind as to share it with me.  School is about to start and we have hundreds of machines still need to be re-provisioned. Thank you!

This issue started happening to us as well, we have an open case CS0995650 and already escalated to the highest level of support, but no one can figure out the fix or the root cause at least.  I searched Jamf Nation as well, but can't find a Solved post.  Please, if one of you resolved this, and you have case number I can share with Jamf Support, please be so kind as to share it with me.  School is about to start and we have hundreds of machines still need to be re-provisioned. Thank you!


Hi Eigger this happened to us about a year ago; there weren't any solutions we could administer ourselves. I believe the solution was a restart of our instance done by Jamf Support. 

Thank you @lesleyannv ! I shared this whole thread with our Jamf Support, I hope they can review previous cases mentioned here and your response and come up with a solution.

They fixed our issue by moving us to a new node. CS0851866 was our case

Thank you,@ladygreyjedi.I appreciate the case number.  I hope they can review this case and help resolve our issue. 

Reply


Terms & ConditionsCookie settings