JAMF Nation! I have a very odd OS X user issue to share with you. A user with a sound JAMF binary and JSS connection is running into an issue where any and all policies from Self Service generates the following error:

To correct this on a case-by-case basis, one must select "Choose Application" and select "Self Service.app" only after selecting the default view from "Recommended Applications" to "All Applications." This immediately corrects the issue and the policy runs, regardless of what the policy actually does.

Take for example a simple "Inventory Check-in." When a "sudo jamf recon" command is run in Terminal, this works without any problems whatsoever. When the "Run Inventory Scan" is performed from Self Service on this user's computer, the above error occurs which requires the user to specify the correct application--Self Service.app--to be selected using the aforementioned workflow. This is not something that I expect this user to go thru each time they want to run a policy so I am hoping to look for a more permanent fix. Is there a way to correct this globally within Self Service?

FWIW: I removed the JAMF framework and re-added the OS X client back on thinking it was related to a corrupt instance of Self Service. The quick add packaged used was received from our user-initiated portal which is tried and true. The machine checks in, sends reports, inventory updates and verifies a sound connection to our JSS.