Self service v10.43.1 "Item Failed" false negatives

trandall
New Contributor II

Since the self service update (updated on my M2 test machine today) my non VPP items in self service are generating false negatives "item failed" errors. Even a simple inventory update will generate a false negative. They execute fine but users will absolutely report these false negatives believing them to be actual negatives.  This doesn't appear to be true for all macs (seems to be fine on my intel) 

What are my next steps?

trandall_0-1675577521811.png
Thank you

 

1 ACCEPTED SOLUTION

trandall
New Contributor II

Support provided a manual solution. Its now resolved on my tester

The issue is around the failed md5 checksum, and due to the policy seeing that fail it is reporting item failed.

Can we try, and test the following workflow on a device experiencing the issue?
-Download jamfHelper.tar.gz and jamfNotificationService.tar.gz attached to this case onto the Mac having errors
-Unzip files by double clicking them in Finder
-Open Terminal and run:
sudo rm -rf "/Library/Application Support/JAMF/bin/jamfHelper.app"

sudo rm -rf "/Library/Application Support/JAMF/bin/Management Action.app"

sudo mv "/path/to/unzipped/jamfHelper.app" "/Library/Application Support/JAMF/bin/"

sudo mv "/path/to/unzipped/Management Action.app" "/Library/Application Support/JAMF/bin/"

sudo chown -R root:wheel "/Library/Application Support/JAMF/bin/jamfHelper.app"

sudo chown -R root:wheel "/Library/Application Support/JAMF/bin/Management Action.app"

sudo jamf update

## Note: change "/path/to/unzipped" to the actual file path, or just drag and drop the files from Finder into Terminal ##

Let us know the results of testing this work flow.

View solution in original post

7 REPLIES 7

Jaykrishna1
Contributor II
  1. Check for updates to the self-service app and make sure you have the latest version installed.

  2. Check for any recent changes to your environment, such as changes to your network settings or the installation of new software, that may have affected the self-service update.

  3. Submit a bug report to the developers of the self-service app with detailed information about the issue, including any error messages that you have received and steps you have taken to troubleshoot the problem.

  4. You may also consider seeking support from a community of users or consulting with a technical expert to get further help.

It's important to note that false negatives can be frustrating for users, so it's important to resolve the issue as soon as possible to maintain the trust of your users.

Loic
New Contributor III

Hello

Same behaviour with the Self Service 10.43.1 (Intel proc.)
All my app installations are working fine but are generating "item failed" errors

trandall
New Contributor II

Support provided a manual solution. Its now resolved on my tester

The issue is around the failed md5 checksum, and due to the policy seeing that fail it is reporting item failed.

Can we try, and test the following workflow on a device experiencing the issue?
-Download jamfHelper.tar.gz and jamfNotificationService.tar.gz attached to this case onto the Mac having errors
-Unzip files by double clicking them in Finder
-Open Terminal and run:
sudo rm -rf "/Library/Application Support/JAMF/bin/jamfHelper.app"

sudo rm -rf "/Library/Application Support/JAMF/bin/Management Action.app"

sudo mv "/path/to/unzipped/jamfHelper.app" "/Library/Application Support/JAMF/bin/"

sudo mv "/path/to/unzipped/Management Action.app" "/Library/Application Support/JAMF/bin/"

sudo chown -R root:wheel "/Library/Application Support/JAMF/bin/jamfHelper.app"

sudo chown -R root:wheel "/Library/Application Support/JAMF/bin/Management Action.app"

sudo jamf update

## Note: change "/path/to/unzipped" to the actual file path, or just drag and drop the files from Finder into Terminal ##

Let us know the results of testing this work flow.

trandall
New Contributor II

running a inventory update from self service a few times (false negative fails) this is what jamf.log is showing>>
Sun Feb 05 10:11:22 W66W257JPQ jamf[8496]: Executing Policy Recon
Sun Feb 05 10:11:22 W66W257JPQ jamf[8496]: Inventory will be updated when all queued actions in Self Service are complete.
Sun Feb 05 10:11:40 W66W257JPQ jamf[8563]: Removing existing launchd task /Library/LaunchDaemons/com.jamfsoftware.task.bgrecon.plist...
Sun Feb 05 14:06:20 W66W257JPQ jamf[545]: Removing existing launchd task /Library/Application Support/JAMF/tmp/com.jamfsoftware.task.policy.startup.plist...
Sun Feb 05 14:06:21 W66W257JPQ jamf[545]: Removing existing launchd task /Library/Application Support/JAMF/tmp/com.jamfsoftware.task.policy.startup.plist...
Sun Feb 05 14:06:21 W66W257JPQ jamf[545]: Removing existing launchd task /Library/Application Support/JAMF/tmp/com.jamfsoftware.task.startssh.plist...
Sun Feb 05 14:06:23 W66W257JPQ jamf[950]: Upgrading jamfHelper.app...
Sun Feb 05 14:06:23 W66W257JPQ jamf[950]: The checksum of /Library/Application Support/JAMF/tmp/jamfHelper.app/Contents/MacOS/jamfHelper did not match. (ea2a2bb5a8df1b4e961c52f4a2cb8140 != 1290fb19780832ae8e23a4407fd3cfda)
Sun Feb 05 14:06:23 W66W257JPQ jamf[950]: Upgrading JAMF notification service...
Sun Feb 05 14:06:24 W66W257JPQ jamf[950]: The checksum of /Library/Application Support/JAMF/tmp/Management Action.app/Contents/MacOS/Management Action did not match. (5073615e23c918c3ab8ceaf1e4b40a9a != 11ba83f688a45f7ef91283ace903fa41)
Sun Feb 05 14:06:24 W66W257JPQ jamf[950]: Checking for policies triggered by "startup" for user "trandall"...
Sun Feb 05 14:06:24 W66W257JPQ jamf[1011]: Checking for policies triggered by "login" for user "trandall"...
Sun Feb 05 14:18:57 W66W257JPQ jamf[1594]: Upgrading jamfHelper.app...
Sun Feb 05 14:18:58 W66W257JPQ jamf[1594]: The checksum of /Library/Application Support/JAMF/tmp/jamfHelper.app/Contents/MacOS/jamfHelper did not match. (ea2a2bb5a8df1b4e961c52f4a2cb8140 != 1290fb19780832ae8e23a4407fd3cfda)
Sun Feb 05 14:18:58 W66W257JPQ jamf[1594]: Upgrading JAMF notification service...
Sun Feb 05 14:18:58 W66W257JPQ jamf[1594]: The checksum of /Library/Application Support/JAMF/tmp/Management Action.app/Contents/MacOS/Management Action did not match. (5073615e23c918c3ab8ceaf1e4b40a9a != 11ba83f688a45f7ef91283ace903fa41)
Sun Feb 05 14:18:58 W66W257JPQ jamf[1594]: Checking for policy ID 50...
Sun Feb 05 14:19:00 W66W257JPQ jamf[1594]: Executing Policy Recon
Sun Feb 05 14:19:00 W66W257JPQ jamf[1594]: Inventory will be updated when all queued actions in Self Service are complete.
Sun Feb 05 14:19:24 W66W257JPQ jamf[1663]: Removing existing launchd task /Library/LaunchDaemons/com.jamfsoftware.task.bgrecon.plist...
Sun Feb 05 14:24:06 W66W257JPQ jamf[1936]: Upgrading jamfHelper.app...
Sun Feb 05 14:24:06 W66W257JPQ jamf[1936]: The checksum of /Library/Application Support/JAMF/tmp/jamfHelper.app/Contents/MacOS/jamfHelper did not match. (ea2a2bb5a8df1b4e961c52f4a2cb8140 != 1290fb19780832ae8e23a4407fd3cfda)
Sun Feb 05 14:24:06 W66W257JPQ jamf[1936]: Upgrading JAMF notification service...
Sun Feb 05 14:24:06 W66W257JPQ jamf[1936]: The checksum of /Library/Application Support/JAMF/tmp/Management Action.app/Contents/MacOS/Management Action did not match. (5073615e23c918c3ab8ceaf1e4b40a9a != 11ba83f688a45f7ef91283ace903fa41)

trandall
New Contributor II

appears to be plenty of checksum errors appearing in the jamf log after Sat Feb 04 04:22:17

The checksum of /Library/Application Support/JAMF/tmp/jamfHelper.app/Contents/MacOS/jamfHelper did not match. (ea2a2bb5a8df1b4e961c52f4a2cb8140 != 1290fb19780832ae8e23a4407fd3cfda)
and
The checksum of /Library/Application Support/JAMF/tmp/Management Action.app/Contents/MacOS/Management Action did not match. (5073615e23c918c3ab8ceaf1e4b40a9a != 11ba83f688a45f7ef91283ace903fa41)

Loycefort
New Contributor

Since the self service update (updated on my M2 test machine today) my non VPP items in self service are generating false negatives "item failed" errors. Even a simple inventory update will generate a false negative. They execute fine but users will.. Panorama Login Charter

You can try the following steps to resolve this

  1. Check logs for any relevant error messages or details that could shed light on the root cause of the issue.

  2. Ensure that your software is up to date and that all relevant patches have been applied.

  3. Try resetting relevant configuration settings to their default values and then reconfigure them as needed.

  4. If the problem persists, you may need to seek assistance from the vendor or community support resources for the software you are using.

I hope this helps! Let me know if you have any additional questions.