It seems we are failing to parse some XML correctly for some reason.
Do the same users have the same errors on different devices?
-If you have a test user can you attempt to enroll with that on the same device, does the issue still occur?
Do these devices have any unique settings or software targeting them that others that are working don't?
-Or are working and non working devices getting the same configuration?
Is there anything unique about the devices or iOS version when the issue is seen?
As you know I have the same issue at a customer... We enrolled using a user that is also a LANDESK Console user (not admin). That's the only thing ' unique' about this user... @ Melvin, is the user who's enrollment is failing for you also a LANDESK user?
The strange thing is that one is and one is not.
I am seeing errors in the resolveusergroups.exe.log
RollingLog : Exception in GetGroups: Exception has been thrown by the target of an invocation. at LANDesk.ManagementSuite.UserManagement.Business.LDConsoleUser.GetGroups(ConsoleUser user)
04/29/2016 10:40:56 INFO 26196:1 RollingLog : Exception in GetGroups: Exception has been thrown by the target of an invocation. at LANDesk.ManagementSuite.UserManagement.Business.LDConsoleUser.GetGroups(ConsoleUser user)
i'm seeing in the STS.DLL.log: 04/29/2016 11:05:01 INFO 9732:189 RollingLog : Exception in GetGroups: Exception has been thrown by the target of an invocation. at LANDesk.ManagementSuite.UserManagement.Business.LDConsoleUser.GetGroups(ConsoleUser user)
and in the mdm.dll.log:
4/29/2016 12:27:05 INFO 3000:52 RollingLog : Error constructing SOAP envelope for policy request: System.Xml.XmlException: An error occurred while parsing EntityName. Line 1, position 14569.
at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.LoadXml(String xml)
04/29/2016 12:27:05 INFO 3000:52 RollingLog : PolicyTaskRetriever.GetPolicyInfo() Requesting policies for 97622bca614ca7baf2f76eaccccc25d7c44460e8
04/29/2016 12:27:05 INFO 3000:52 RollingLog : GetAPMServiceResponse: exception - The remote server returned an error: (400) Bad Request.
04/29/2016 12:27:05 ERROR 3000:52 Services.ApplePropertiesManagerBasic : Error processing data from iOS device=97622bca614ca7baf2f76eaccccc25d7c44460e8, command=ManagedApplicationList.
Object reference not set to an instance of an object..
I am having the same issue with the same error on iPhone users, Defect 303717 was created for me but I have not heard back.
Were you able to find out what was causing this issue?
Nope it is getting worse, now everybody which i try to enroll has the same error in the log
1 of 2 people found this helpful
control your mdm port between server and apns\gcm.
I was this issue one Time on case of closed port.
1 of 1 people found this helpful
I worked together with development to get this resolved. It took some time but they spend many effort in heling me.
The issue turned out to be related to Active Directory group membership. In the AD group itself special characters were used and this turned out to be the issue.
What worries me is the fact that Mobility takes the Group Memberships from another Desktop/laptop Inventory record. So if the user doesn't login to his main device for a while, Mobility will never know about updated group memberships and such...