“Self Service has Encountered a Problem. Unable to contact the jamf binary. Your computer may have become unmanaged. You can make it managed by running Recon locally.”

Standard
UPDATE: We've since updated to JSS 9.3 & we no longer have this issue.

We recently updated our JSS from 8.73  > 9.22 & on the whole it’s been a non-event.

However, we started to find that some Self Service policies were erroring with the below message post the upgrade.

Screen Shot 2014-01-17 at 10.03.00

System.log also had some errors:

Jan 17 10:07:00 COMPUTERNAME secd[680]: securityd_xpc_dictionary_handler jamf[3576] copy_matching The operation couldn't be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements)
Jan 17 10:07:00 COMPUTERNAME jamf[3576]: SecOSStatusWith error:[-34018] The operation couldn’t be completed. (OSStatus error -34018 - Remote error : The operation couldn‚Äôt be completed. (OSStatus error -34018 - client has neither application-identifier nor keychain-access-groups entitlements))
Jan 17 10:07:01 COMPUTERNAME Self Service[2952]: [ERROR] -[JAMFBinaryCommunication handleCommunicationException:withActionSelector:andInfo:] (line:174)
--> Could not notify daemon: connection went invalid while waiting for a reply
Jan 17 10:07:01 COMPUTERNAME Self Service[2952]: [ERROR] -[JAMFPolicyTrigger handleError:sender:] (line:174)
--> Unable to contact the jamf binary. Your computer may have become unmanaged. You can make it managed by running Recon locally.: Error Domain=JAMFSoftware/SelfService Code=10 "NSInvalidReceivePortException" UserInfo=0x2e7370 {NSLocalizedDescription=NSInvalidReceivePortException}
Jan 17 10:07:01 COMPUTERNAME Self Service[2952]: [ERROR] -[InstallerQueueProcessBinder finishProcess] (line:151)
--> Policy Install SAPGUI 7.20rev5 failed with: Error Domain=JAMFSoftware/SelfService Code=20 "Unable to contact the jamf binary. Your computer may have become unmanaged. You can make it managed by running Recon locally." UserInfo=0xaa8f9d0 {NSLocalizedDescription=Unable to contact the jamf binary. Your computer may have become unmanaged. You can make it managed by running Recon locally.}
Jan 17 10:07:09 COMPUTERNAME com.apple.launchd.peruser.735480991[342] (com.jamfsoftware.jamf.agent[3569]): assertion failed: 13C39: launchd + 43276 [425516B6-9F3E-342F-87B3-EC461EBA6A1A]: 0xffffffffffffffff
Jan 17 10:07:09 COMPUTERNAME com.apple.launchd.peruser.735480991[342] (com.jamfsoftware.jamf.agent[3569]): Exited: Terminated: 15

After reaching out to JAMF support & trying things out myself, it appears that we had hit a known defect (D-006071),  “this defect is thought to be a result of a special character being present that is creating issues.”

One of the DMG’s we were having issues deploying was called “012 SAPGUI Settings.dmg.” Via a Policy or Casper Remote it deployed fine, only errored via Self Service.

Even though the name appeared to have no special characters, it looks like the spaces were somehow causing issues. Replacing the spaces with underscores so the DMG read: “012_SAPGUI_7.20rev5_Settings.dmg.” After which it deployed fine via Self Service.

I then checked through & swapped spaces for underscores on the other couple of DMG’s that had issues via Self Service.

 

3 thoughts on ““Self Service has Encountered a Problem. Unable to contact the jamf binary. Your computer may have become unmanaged. You can make it managed by running Recon locally.”

  1. Just ran into the same issue today, and luckily your blog came up as the first result. Sure enough after removing some spaces from a couple test packages, they were working fine from self service. Thanks for posting your discovery!

  2. Justin

    Had the same issue with a few teacher machines today. Went through and changed all of our DMG package names just to be safe.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.