Search Engine: Elastic

Article ID: 128416, created on Feb 22, 2016, last review on Feb 22, 2016

  • Applies to:
  • Operations Automation 6.0


Office365 sync script fails with the error:

2015-08-03 14:51:34,997 ERROR   Subscription 1234567: error by data comparison: not well-formed (invalid token): line 2, column 281
2015-08-03 14:51:34,999 ERROR   Traceback (most recent call last):
File "/officesync/O365-Import4-16-11/", line 1391, in compareSubscriptions
File "/officesync/O365-Import4-16-11/", line 746, in loadAppSettings
self.account_id = self.api.pem.getSubscription(subscription_id = int(self.subId), get_resources = False)["owner_id"]
File "/officesync/O365-Import4-16-11/modules/", line 145, in __call__
resp = getattr(self.api.server,
  File "/usr/lib64/python2.4/", line 1096, in __call__
return self.__send(self.__name, args)
  File "/usr/lib64/python2.4/", line 1383, in __request
File "/usr/lib64/python2.4/", line 1147, in request
return self._parse_response(h.getfile(), sock)
  File "/usr/lib64/python2.4/", line 1281, in _parse_response
File "/usr/lib64/python2.4/", line 527, in feed
self._parser.Parse(data, 0)
ExpatError: not well-formed (invalid token): line 2, column 281


® symbol in the name of OA subscription due to APSA-12272.


Please contact your TAM or PTA to trace the status of APSA-12272. To workaround the issue, please remove the problem symbol from subscription's name and repeat the sync attempt.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF