JMFCommons.JamfKeychain.JamfKeychainSecurityError.failedToReadJmfKeychainPassword

[cnixon14]

I am trying to troubleshoot some problems I am having with a few of my machines. 

I keep seeing this error in the log files and am not sure exactly what it means

JMFCommons.JamfKeychain.JamfKeychainSecurityError.failedToReadJmfKeychainPassword

 is what I keep seeing and I believe it is the root of all the other errors I am seeing. 

Can anyone shed some light on what causes this problem and how I can fix it. Thank you in advance

[cnixon14]

shortly after the JMFCommons error I see this error. Im thinking it could be network related..

Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service on pid 0 named com.jamf.management.daemon.binary was invalidated from this process." UserInfo={NSDebugDescription=The connection to service on pid 0 named com.jamf.management.daemon.binary was invalidated from this process.}

[TeqJack]

I am getting the same error during DEP enrollment. Did you find a solution or any additional context?

[shukla2009]

JMFCommons.JamfKeychain.JamfKeychainSecurityError.failedToReadJmfKeychainPassword
Error Domain=com.jamf.jamfsecurity.error Code=-50 "unlockWithPassword:error: : One or more parameters passed to a function were not valid." UserInfo={NSLocalizedDescription=unlockWithPassword:error: : One or more parameters passed to a function were not valid.}

Behaviour after my restart it works for 10 minutes and then start giving error

[nberanger]

I am working with a user right now running into this same issue. MacBook Air M2, running 14.3.0.

JMFCommons.JamfKeychain.JamfKeychainSecurityError.failedToReadJmfKeychainPassword
JMFCommons.JamfKeychain.JamfKeychainSecurityError.failedToReadJmfKeychainPassword
The device certificate was created successfully.
Error Domain=com.jamfsoftware.task.errors Code=1 "(null)"
No container info found for disk with ID disk4
Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.jamf.management.daemon.binary was invalidated from this process." UserInfo={NSDebugDescription=The connection to service named com.jamf.management.daemon.binary was invalidated from this process.}

The Mac goes as far as getting the user to turn on location services, then just sits at a black screen for a long time... the gets to the login screen, but with only our local admin account created.

Anyone have any luck sorting this out?

[jezza]

Same issue here.. No clue what the problem might be. We also have on prem jamf. 

[manuelamunozb]

i have the same problem today, anyone of you found a solution? thanks a lot for your help!

[cnixon14]

For me it ended up being a database issue. When upgrading the jamf instance jamf had created another entry into the computer-inventory-collection-settings table. I went into the sql db and deleted one of the entries and the whole instance went back to normal. I feel like the JAMF keychains issue might be a very obscure symptom of this issue but I would suggest playing around with the jamf API to see what kind of errors pop up. It definitely helped me finally find the root cause of my issue.

Jamf Pro API OverviewJamf Developer Portalhttps://developer.jamf.com › jamf-pro › docs › jamf-pro...

[jezza]

Can you go into it a little bit more on how you leverage the API to find that this was the root cause of your issue? I would love to know your troubleshooting steps.

[nberanger]

For this client, this is with Jamf Cloud. So I had no access to the DB.

The client has also now migrated to Kandji... So I guess that is one way to get around the error 😜

[Johnny_Kim]

 I had Macbooks (m2 on Sonoma) showing this error. Did a chat support with jamf and they said this was normal. 

 "this is expected and is nothing out of the norm. The error: JMFCommons.JamfKeychain.JamfKeychainSecurityError.failedToReadJmfKeychainPassword
This message represents an event where the JamfDaemon was unable to read the unique value from the System Keychain and it is a normal step at the start of the process that generates the new password. Seeing a message like that in the log does not directly mean that something went wrong or unexpected events occurred. In most cases, it is simply logging the results of the JMF's attempt to read the item prior to it being regenerated. A subsequent retry will occur automatically and successful attempts are not logged. Noteworthy for troubleshooting observations: keychain access provides the Date Modified attribute of the object stored in keychain. "

[nberanger]

Funny that many of us had also opened tickets with Jamf on this, an none of the support agents knew anything about the error 😉