Skip to main content

For the last two weeks I was working with support on an issue that seemed minor at the beginning. QuickAdd failed to complete the enrollment and the logs showed that this was caused by a failed MDM profile install. On the server the logs get flodded with messages like this:

at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:229)
    at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1927)
    ... 15 more
2017-11-30 05:51:28,336 [ERROR] [Tomcat-10  ] [JAXBPlistParser          ] - Error unmarshalling
2017-11-30 05:51:28,336 [ERROR] [Tomcat-10  ] [MDMController            ] - Error processing mdm request, returning 400. Device: Null, CommandUUID: mraNull
2017-11-30 05:51:51,412 [ERROR] [Tomcat-8   ] [JAXBPlistParser          ] - Error unmarshalling
2017-11-30 05:51:51,412 [ERROR] [Tomcat-8   ] [MDMController            ] - Error processing mdm request, returning 400. Device: Null, CommandUUID: mraNull
2017-11-30 05:52:00,296 [ERROR] [Tomcat-3   ] [JAXBPlistParser          ] - Error unmarshalling

Since it took support two weeks to figure that that this is a product bug, the backups of the pre-upgrade database had been overwritten (30 day retention) and I'm basically stuck with a non working JSS and the option to wait for them to fix this or start over from scratch and re-enroll everybody.

I'm sure that they are working on this "critical" bug with high priority but it is really frustrating to hear that this issue is known for a couple of weeks and there is still no eta for a fix. What is even more frustrating is the fact that even week ago I would have had a working backup to restore 9.x.

I guess that's another chapter in my lessons learned book. I'm just glad that I only have 50 Macs and not 5000...

@ssrussell also see https://www.jamf.com/jamf-nation/discussions/27070/error-processing-mdm-request-returning-400-flooding-jamfsoftwareserver-log. i have been keeping an eye on my logs and interestingly enough we generally only see this error during the school day - very rarely at off-peak hours. curious to know if you are (or anyone else is) seeing that as well. also, i've found that if you're in the parent node of the jss (when you would see a * after the text in the browser tab) you can't go back too far, whereas if you're in the child node (only seeing a in the browser tab) you can see back much further. in the parent i can only go back about a day, and in the child node i can see back almost a month (since it doesn't show the chatty license monitor info).

I had to open the www.apple.com range as I mentioned above to get rid of these errors.

I'm getting these.. [ERROR] [Thread-1773] [JAXBPlistParser ] - Error unmarshalling
2019-03-11 12:30:00,035 [ERROR] [Thread-1773] [MDMController ] - Unable to parse device from request
com.jamfsoftware.jss.mdm.actions.exceptions.PlistParsingException: Plist was null when trying to get device UDID at com.jamfsoftware.jss.mdm.actions.MDMActionFactory.getDeviceFromPlist(MDMActionFactory.java:759) at com.jamfsoftware.jss.mdm.enrollment.MDMController.getDeviceFromRequest(MDMController.java:266) at com.jamfsoftware.jss.mdm.enrollment.MDMController.process(MDMController.java:162) at com.jamfsoftware.jss.mdm.enrollment.MDMController.doPut(MDMController.java:107)

I was told it was fixed in 10.9, however, I've just seent he same on my 10.10 webapp..

@kerouak

What is the end result of getting these errors?

I'm seeing similar errors and haven't been able to enroll a macOS device. Just curious if you're seeing the same enrollment problems. iOS enrolls just fine, macOS enrollment is a no go manually, via quickadd, or DEP. Every now and then one does enroll, can't duplicate anything.

Support has been working the case for a while now. We're using 10.10.1

Terms & ConditionsCookie settingsAccessibility statement