Skip to main content
Question

Jamf Pro 10.0 virtually killed my JSS

  • November 30, 2017
  • 29 replies
  • 123 views

Show first post

29 replies

Forum|alt.badge.img+10
  • Valued Contributor
  • April 3, 2018

@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).


Forum|alt.badge.img+18
  • Valued Contributor
  • April 3, 2018

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


Forum|alt.badge.img+13
  • Valued Contributor
  • March 11, 2019

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..


Forum|alt.badge.img+9
  • Contributor
  • March 11, 2019

@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