› Forums › MxLoader NextGen Beta › Unexpected char in ParseObject This topic has 6 replies, 6 voices, and was last updated 5 months ago by Umar Adil. Viewing 7 posts - 1 through 7 (of 7 total) Author Posts 2020-06-10 at 14:51 #19954 email@example.comParticipant Any ideas what could be causing this? It appears when I try to Test Connection 2020-06-16 at 11:47 #19968 mguehiParticipant Hello, I have the same error. It seems to appear only when using LDAP authentication (with OpenLDAP in me case) 2020-07-22 at 15:17 #19999 N.MohammedParticipant I get the same error. However I am using SSO 2020-07-24 at 17:12 #20002 MaximoMillerParticipant Same for me as well.. With and without Registration… 2020-07-24 at 17:41 #20009 MaximoMillerParticipant Eveyone.. This is resolved by now using a new URL… notice his sample.. you go to the /maximo/ on the URL and not the mea path any longer… that slash at n is important…. 2020-08-15 at 16:57 #20016 Willians AndradeParticipant Continues error when trying to connect “Unexpected char in ParseObject”. 2020-09-30 at 14:54 #20090 Umar AdilParticipant “Unexpected char in ParseObject” When try to connect my LDAP https Working fine on Normal http url Author Posts Viewing 7 posts - 1 through 7 (of 7 total) The forum ‘MxLoader NextGen Beta’ is closed to new topics and replies.