I tried a sudo jamf enroll on the system, and it got stuck at Locating Package receipts again...

This is a system I was planning to do an OS upgrade on, so, I pushed the OS Installer to the system and the user kicked it off. After the restart with the updated OS, Casper started talking again.

(I did not try the remove framework and then run the quick add - to see if that would have fixed the problem.)

Running sudo jamf removeFrameworks, running quickadd pkg and running sudo jamf recon did not work for me. The solution that worked for me was to remove all items from /Library/Receipts and then run sudo jamf recon.

@ G-Lo I have some Macs that they are checking in but not reporting.
I have put these in to smart group. I have created a policy scoping to this group running this command:

mv Receipts/ ReceiptsOLD && jamf recon

This way I don't loose the receipt info. As I may need to check the content later on and I may find the rogue receipt etc...

I just ran into this problem a few days ago on a couple of Macs and after speaking with JAMF, we did end up clearing out the /Library/Receipts/ folder.

Clearing /Library/Receipts works but you lose all your receipts history. Does Casper reconstruct the history?

Don

Apologies in advance for reviving this thread, but we're having a problem with receipts info not being inventoried.

Notice how JSS shows no receipts (no installs by Casper; no installs by Installer.app).

Any idea how to fix this? Tried removing/re-installing QuickAdd, 10.6.8 Combo Update (latest), permissions repair...

external image link

external image link

Wow, I tried deleting the computer from JSS, doing anther removal/re-install and recon. Same, same...time to re-image. ;)

Hey guys - sorry to revive again. I was actually having this exact same problem as I've inherited a pretty chaotic Mac environment. Many machines were not able to recon correctly and were generating bare-bones records in the JSS. Like everyone here, tried a disk repair, remove and re-add from the JSS, remove framework, etc... but none of that did the trick. It turns out within /Library/Receipts there were a ton of Office2008_en files that seemed to be the issue. I ran an mv Office2008* /private/tmp to test and recon worked flawlessly after that. Hopefully this helps someone!

We ran into similar issues on Macs that didn't have Office 2008 receipts, I really wish there was a fix for this, rather than using a BFH. :)

Don

Sorry to hear that! I wonder if you could do something similar and see if there are any commonalities in the machines that get stuck in the Receipts section and see if you can find what's causing it. A real PITA though. At least the BFH works.

I have also seen some machines complaining about Office 2008 receipts. I simply deleted all the Office 2008 receipts it was complaining about, and those particular errors went away. In cases where I took the opportunity to uninstall Office 2008 and install Office 2011, the removal of Office 2008 did not remove those erroneous 2008 receipts, so either way it would have required manually removing.

I have also seen some machines complaining about Office 2008 receipts. I simply deleted all the Office 2008 receipts it was complaining about, and those particular errors went away. In cases where I took the opportunity to uninstall Office 2008 and install Office 2011, the removal of Office 2008 did not remove those erroneous 2008 receipts, so either way it would have required manually removing.