Recon failing "Error running recon: *** setObjectForKey: object cannot be nil (key: _NSTaskOutputFileHandle)"

I've seen it in small quantities as I've gone through every single version of Casper 9.x that has ever existed. We've run through many many fixes and upgrades and are now running relatively smoothly. What's your setup like? Perhaps I can make some recommendations?

Hi Chris,
In our environment, we are running JSS 9.2 on a Red Hat server and our DP off of an OS X server. Is that what you were looking for?

Stephen

Wow, sorry I lost track of this thread. Are you still having issues?

Hi!
We see the same error on some of our 10.8 macs.
---------------

An error occurred while running the policy "Update Inventory" on the computer "BIBM1-10168".

Actions from policy log:
        Executing Policy Update Inventory...
        Running Recon...
        Retrieving inventory preferences from https://jss.hh.se:8443/...
        Locating accounts...
        Searching path: /Applications
        Locating package receipts...
        Gathering application usage information...
        Locating printers...
        Locating plugins...
        Error running recon: *** setObjectForKey: object cannot be nil (key: _NSTaskOutputFileHandle)
        The results of this policy were not logged at the time of execution.
        The actual execution time was Mon Jan 20 08:59:03 CET 2014.

Running the command manually in verbose mode gives:

BIBM1-10168:~ admin$ sudo jamf recon -verbose
Password:
verbose: Timeout: 10
verbose: Checking availability of https://jss.hh.se:8443/...
verbose: The JSS is available.
Retrieving inventory preferences from https://jss.hh.se:8443/...
Finding extension attributes...
verbose: Running script for the extension attribute EFI Password Mode
verbose: Running script for the extension attribute Get Office 2011 Version
verbose: Running script for the extension attribute Java Vendor
verbose: Running script for the extension attribute McAfee EPO version
Locating hard drive information...
verbose: Finding CoreStorage information...
Locating hardware information (Mac OS X 10.8.5)...
verbose: Checking AD status...
Locating accounts...
verbose: Finished with user.
verbose: Finished with user.
verbose: Finished with user.
Locating applications...
Searching path: /Applications
verbose: Found app: /Applications/Adobe Acrobat XI Pro/Acrobat Distiller.app
verbose: Found app: /Applications/Adobe Acrobat XI Pro/Adobe Acrobat Pro.app
<snip>
verbose: Found app: /Applications/Utilities/X11.app
verbose: Found app: /Applications/VLC.app
Locating package receipts...
Gathering application usage information...
verbose: Looking in 2014-01-17
verbose: Reading annkal12.plist...
verbose: Reading anntov13.plist...
verbose: Reading carrai11.plist...
verbose: Reading jenlor12.plist...
verbose: Reading martwe10.plist...
verbose: Reading nadper12.plist...
verbose: Reading sarjan11.plist...
verbose: Looking in 2014-01-18
verbose: Looking in 2014-01-20
verbose: Reading casperscreensharing.plist...
verbose: Reading dantor13.plist...
verbose: Reading dsess5.plist...
verbose: Reading itadmin.plist...
verbose: Reading klaran13.plist...
verbose: Reading sandaf11.plist...
verbose: Reading sanfer12.plist...
verbose: Reading sarelk12.plist...
verbose: Reading sarjan11.plist...
verbose: Locating running services...
Locating printers...
Locating plugins...
Searching path: /Library/Internet Plug-Ins
verbose: Error executing command: (
"/usr/bin/profiles",
"-L",
"-U",
sandaf11
)
verbose: *** setObjectForKey: object cannot be nil (key: _NSTaskOutputFileHandle)
There was an error.
*** setObjectForKey: object cannot be nil (key: _NSTaskOutputFileHandle)

If you run the profiles command with sudo you get a valid response:

BIBM1-10168:~ admin$ sudo /usr/bin/profiles -L -U sandaf11
There are no configuration profiles installed for user 'sandaf11'

But if run without sudo you get an error:

BIBM1-10168:~ admin$ /usr/bin/profiles -L -U sandaf11
profiles: the user could not be found

Is it possible the jamf command run the profiles command with out admin rights? And then can't handle the error.

/Peo

Interesting. I've had to strip our entire installation of any profiles beyond the basic MDM/management profiles due to a huge number of issues. We're down to only a few issues similar to this but still have unknown recon errors until a re-enroll occurs.