This repo contains a list of messages which can appear in the JAMFSoftwareServer.log, with a note as to what action might be required due to the messages being generated.
Please reach out to Jamf Support if any questions, & Pull Requests accepted to add more messages.
The log message snippets are displayed in the 1st column, scroll to the right for any recommended steps.
The messages have an assigned status, as per:
| Status | Description |
|---|---|
| 💥 | Severe events which needs immediate attention. |
| 💣 | Events which if left unchecked can lead to service disruption. |
| An event that needs attention, but is not service affecting. | |
| 🆗 | Non-issue, an informative event. |
| Log Message Snippets | Status | PI | Detail |
|---|---|---|---|
Fatal error logged during server initialization |
💥 | JPS failed to startup, further investigation needed as to why. | |
APNs Certificate is expired. |
💥 | Renew the APNS certificate. | |
[llmentProgramDeviceHelper] - 403 The organization has not accepted latest Terms and Conditions of the program |
💣 | Login to ABM/ASM to accept the new terms & conditions. | |
[ntInstanceSyncCommService] - DeviceEnrollmentProgramException[responseCode=403, responseBody='T_C_NOT_SIGNED', message='An error occurred during oauth token refresh'] |
💣 | Login to ABM/ASM to accept the new terms & conditions. | |
DeviceEnrollmentProgramException[responseCode=500, message='The DEP service reported an error.'] |
💣 | Download a new token from ABM/ASM & upload into the JPS. | |
[ntInstanceSyncCommService] - com.jamfsoftware.jss.objects.streamlinedenrollment.service.DeviceEnrollmentProgramException: An error occurred during oauth token refresh |
💣 | Either renew DEP token or login to ABM/ASM to accept the new terms & conditions. | |
DeviceEnrollmentProgramException[responseCode=403, responseBody='FORBIDDEN', message='An error occurred during oauth token refresh'] |
💣 | Either renew DEP token or login to ABM/ASM to accept the new terms & conditions. | |
[VppServiceTokenObject ] - Error parsing service token |
💣 | Either a DEP token has been uploaded in place of a VPP token, or a VPP token has expired. | |
[CMSCipher ] - Unable to decrypt data |
💣 | PI-006374 | macOS - Configuration Profile - Security & Privacy Payload - FileVault Recovery Keys cannot be viewed if Certificate expired. Observation : Filevault 2 recovery keys are displayed in the JPS as a long string with hundreds of characters starting with 'MIAGCSqGSIb3DQEHA6CAMIACAQAxgg'. Jamf Pro has a FILEVAULT2COMM certificate in the database, and it is valid for 5 years. In case it needs to be renewed we hit this issue. Fixed with JPS 10.10. Can be manually resolved by we creating a new configuration profile with Security & Privacy Payload with Enable Escrow Personal Recovery Key selected and use a reissue script (https://github.com/JAMFSupport/FileVault2_Scripts/blob/master/reissueKey.sh) |
[eEnrollmentProgramRequest] - javax.net.ssl.SSLHandshakeException: Received fatal alert: decode_error |
💣 | PI-007508 | TLS 1.3 needs to be disabled in JAVA_OPTS or CATALINA_OPTS, fixed with OpenJDK 11.0.5 |
[licationListUpdateService] - Unable to compare the catalog version '1.5.1' with the ApplicationVersion '' or ApplicationShortVersion '' for the app 'com.adobe.rush', so not updating |
💣 | PI-007928 | Catalog version and app name can vary. VPP Apps are unable to be updated on devices due to unknown version comparision issue. Contact Jamf Support |
[ERROR] [eralPool-82] [rtificateRequestProcessor] - Certificate request ID xxx has failed. (Unable to build an ADCS Connector client.) |
💣 | Jamf Pro cannpt contact ADCS or the CA it's acting as a SCEP proxy for and as such certificate requets asre failing. Re-establish contact to resolve. | |
[VppCommService] Client context for admin account doesn't match |
💣 | The VPP token may be in use by another server. The VPP token can be reclaimed. | |
[LDAP: error code 49 - Invalid Credentials] |
💣 | LDAP password incorrect. | |
Error during download of remote software title summaries |
💣 | The issue is related to connectivity to a Patch definitions source. Proceeding the above log text, there will be the name of the patch definition source as it appears within Jamf Pro. Login to Jamf Pro to get the needed details and investigate. | |
[ERROR] [na-exec-876] [GetBootstrapToken ] - Computer ComputerShell [ID=<computer_id>, Name=<computer_name>] requested Bootstrap token but no token was found |
💣 | The device, identified by <computer_id> and/or <computer_name>, is an Apple Silicon device. There is KEXT profile being pushed to the device by Jamf Pro, but the device hasn't escrowed a bootstrap token with Jamf Pro and so cannot lower the devices boot security to install the KEXT profile. This can lead to thousands of failed MDM commands for each affected device, which impacts the DB and performance etc. The fix is to amend the prestage(s) for the instance to have an account created at setup assistant, OR if using Jamf Connect then don't create any admins via a policy until after the 1st user is created via Jamf Connect. | |
[llmentProgramDeviceHelper] - 403: token_expiredForbidden |
Remove or renew the offending token. | ||
[llmentProgramDeviceHelper] - 403: token_rejectedForbidden |
Remove or renew the offending token. | ||
[ntInstanceSyncCommService] - DeviceEnrollmentProgramException[responseCode=403, responseBody='token_rejectedForbidden', message='An error occurred during oauth token refresh'] |
Remove or renew the offending token. | ||
[ntInstanceSyncCommService] - com.jamfsoftware.jss.objects.streamlinedenrollment.service.DeviceEnrollmentProgramException: Cannot create a connection for an expired token |
Remove or renew the offending token. | ||
[ntInstanceSyncCommService] - DeviceEnrollmentProgramException[message='Cannot create a connection for an expired token'] |
Remove or renew the offending token. | ||
[llmentProgramDeviceHelper] - 400 response from Device Enrollment Program indicating one of the following: |
DEP token has been downloaded from ABM/ASM but not uploaded to JPS. Remove or renew the offending token. | ||
[VppAccountCreator ] - Failed to register user com.jamfsoftware.vpp.User@6f7dd030[id=xxx,managedAppleId=some@appleid] to VPP invitation |
The some@appleid needs to login to ABM/ASM & accept the Terms & Conditions for their account | ||
[llmentProgramDeviceHelper] - 403: SERVER_INACTIVE |
There is a DEP PreStage with a token in use which no longer has a location in ABM/ASM. Remove the offending PreStage | ||
[llmentProfileSynchronizer] - com.jamfsoftware.jss.objects.streamlinedenrollment.service.DeviceEnrollmentProgramException: The DEP service reported that invalid options were submitted. |
An ABM DEP token has been assigned to a DEP PreStage for Shared iPad, correct the DEP token in use by the PreStage or remove the Shared iPad settings. | ||
Error parsing iTunes ID: String index out of range |
PI-000867 | This is due to self hosted iBooks being added to Jamf Pro. To stop getting these messages: Disable Populate Purchased VPP Content from Settings > Global > VPP > Content, for each token in use. | |
[Root exception is javax.net.ssl.SSLHandshakeException: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed] |
LDAPS certificate validity check failed. Check certificate presented to JPS | ||
[Root exception is javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target] |
LDAPS certificate validity check failed. Check certificate presented to JPS | ||
[Root exception is javax.net.ssl.SSLHandshakeException: NotAfter: |
LDAPS certificate has expired. | ||
javax.naming.AuthenticationNotSupportedException: [LDAP: error code 8 - 00002028: LdapErr: DSID-0C09023C, comment: The server requires binds to turn on integrity |
LDAP connection requires SSL/TLS | ||
javax.naming.CommunicationException: <ldap.server:port> [Root exception is java.net.SocketTimeoutException: connect timed out] |
Connection to LDAP ldap.server:port timed out. Up LDAP time out time & investigate if persists. | ||
[Root exception is java.net.ConnectException: Connection timed out (Connection timed out)] |
Connection to LDAP ldap.server:port timed out. Up LDAP time out time & investigate if persists. | ||
[ComputerHelper ] java.lang.IllegalArgumentException: Invalid UUID string: |
A macOS device has an invalid record in Jamf Pro. If no smart groups calculate correctly, then this would be an issue with a managed device. If smart groups are fine, but searches fail then look for any unmanaged devices. Delete the offending device once found. | ||
[Root exception is java.net.SocketException: Connection reset] |
Connectivity issue with to LDAP(s), investigation needed. | ||
[Root exception is java.net.ConnectException: Connection refused (Connection refused)] |
Connectivity issue with to LDAP(s), investigation needed. | ||
[Root exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target] |
LDAP SSL certificate not trusted by JPS | ||
javax.naming.CommunicationException: <ldap server fqdn>:<ldap server port> [Root exception is javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: javax.net.ssl.SSLException: hostname in certificate didn't match: <ldap server fqdn> != <ldap server fqdn> OR <ldap server fqdn>] |
FQDN for LDAPS does not match FQDN entries within cert. | ||
[VppCommService ] - Error clearing email for user: |
Error is due to aother MDM trying to assign content to the user or having tried previously. This might be cleared via the VPP API directly but can also be ignored. | ||
[lientCommunicationServlet] - Comm Device null. |
A device which is no longer managed via the JPS is contacting the JPS. The message body cointains MAC & remote IP details so might be traceable if a concern, but can also be ignored. | ||
[JAMFPushProxyConnection ] - Jamf Push Proxy returned status of: 400 |
Informational message, can be ignored as long as Push Proxy is correctly renewing. | ||
[WARN ] [neralPool-0] [PushQueueManager ] - Unable to flush connection com.jamfsoftware.jss.pushnotification.connections.JAMFPushProxyConnection |
Informational message, can be ignored as long as Push Proxy is correctly renewing. | ||
CSRF risk found. Denying request. |
PI-007743 | “Jamf Pro CloudDataSupplier configuration points to a URL that is no longer in service” | |
com.jamfsoftware.mdm.api.MdmCommandException: Cannot cancel an individual command within a group. Use cancelCommandGroup instead. |
Enable debug mode, find the device ID for the mobile device that is triggering the issue and remove from Jamf Pro. | ||
java.lang.RuntimeException: The Signature object is in an invalid state |
PI-005954 PI-006889 | Self Service for macOS does not renew expired session with JPS. Usually caused by users leaving Self Service open for long periods of time whilst the Mac enters sleep. Also, “MacOS Self Service requesting device info from Jamf Pro every 2 seconds if left open and device sleeps past UAPI token renewal and can cause large selfservice_debug.log files”. | |
"[ERROR]" "There was a problem determining membership of device" "in Computer group" "Comparing the value on the device was problematic when compared to the" "This device will not be included in this group because of this criteria error." |
Issue with Smart Computer Group criteria, check the log for mre details & correct. | ||
Outer initWithXML error: java.lang.NullPointerException |
One or more profiles has an issue with it's XML. Replace the offending profile. | ||
[AbstractMetadataProvider ] - Metadata provider failed to properly initialize, fail-fast=true, halting |
SSO is enabled for Self Service login, but a Signing Cetificate is not in place. Login to Jamf Pro, navigate to System Settings > Single Sign On. Under "Security" change "No Certificate" to "Generate Certificate". No need to make changes to the idp etc for this once done. | ||
Generating metadata without signing key, KeyStore doesn't contain any default private key, or the signingKey specified in ExtendedMetadata cannot be found |
Single Sign-On has been enabled, but no Jamf Pro signing ceritificate has been generated. To do so: Login to Jamf Pro then navigate to System Settings > Single Sign-On > Jamf Pro Signing Certificate > Generate Certificate, then click "Generate Certificate" | ||
[VppEmailMonitor ] - Running email monitor |
🆗 | Informational message, not actionable. | |
[VppEmailMonitor ] - Email monitor completed after x.xx seconds |
🆗 | Informational message, the seconds taken can be of use when troubleshooting. | |
[PushNotificationUtility ] - x invalid tokens were submitted to be pushed. |
🆗 | Informational message, not actionable. | |
[FeedbackTokenFactory ] - 1 feedback tokens were found: |
🆗 | Informational message, not actionable. | |
[EduMonitor1] [ucationProfileFactoryImpl] - Computer is not the correct macOS Version to have Edu Profile: |
🆗 | Informational message, not actionable. | |
[EduMonitor1] [ucationProfileFactoryImpl] - Device is not the correct iOS Version to have Edu Profile: |
🆗 | Informational message, not actionable. | |
[rentProfileCleanupMonitor] - Running parent profile cleanup |
🆗 | Informational message, not actionable. | |
[org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1139; cvc-complex-type.2.4.a: Invalid content was found starting with element |
🆗 | A device is checking into Jamf Pro which is not enrolled. See this FR to change logging behaviour: https://www.jamf.com/jamf-nation/feature-requests/9799/change-logging-message-when-a-device-checks-in-which-is-not-enrolled | |
Found path to duplicate InstalledCertificates. Unique certs: |
🆗 | Jamf Pro has de-duped certificates in a device record. See this FR to change logging behaviour: https://www.jamf.com/jamf-nation/feature-requests/9809/change-log-message-when-certificates-are-de-duped-for-a-record | |
[WARN ] [erverThread] [AdvancedSearchHelper ] - Unable to match recon field Enrolled via DEP |
🆗 | macOS devices older than 10.13.2 within Jamf Pro, delete or update the macOS devices to make this message go away | |
[ERROR] [lina-exec-5] [AppleMDMCapableService ] - Incorrect result size: expected 1, actual 0 |
🆗 | No issue, except for the log spam. Resolved in Jamf Pro 10.23+ | |
"Self Service created com.jamfsoftware.jss.dal.entity.SelfServiceEntity" |
🆗 | Informational message, not actionable. | |
[AzureGroupServiceImpl ] - No Azure AD configuration found under id: |
🆗 | PI-010412 - misleading error logging from Cloud Identity Provider for customers who have configured and use only LDAP. | |
[AzureMembershipService ] - No Azure AD configuration found under id: |
🆗 | PI-010412 - misleading error logging from Cloud Identity Provider for customers who have configured and use only LDAP. | |
[AzureGroupIdService ] - Group id has incorrect format |
🆗 | PI-010412 - misleading error logging from Cloud Identity Provider for customers who have configured and use only LDAP. | |
[AzureGroupIdService ] - Group id is null or empty |
🆗 | PI-010412 - misleading error logging from Cloud Identity Provider for customers who have configured and use only LDAP. | |
[CloudIdPMembershipProxy ] - Membership could not be calculated, because at least one argument was empty |
🆗 | PI-010412 - misleading error logging from Cloud Identity Provider for customers who have configured and use only LDAP. | |
[UniqueIDSSMCache ] - An error has occurred for cache JSSCache and key redacted::SelfServiceBookmarks-findAll: Non-serializable object |
🆗 | PI-104623 - Self Service Bookmarks fails and causes the lookup to happen at every call instead of caching the results. |