ERROR: "The connection to the server failed" on iPhone and iPad

  • 7010017
  • 17-Jan-2012
  • 10-Dec-2013

Environment

Novell Data Synchronizer Mobility Pack 1.2.1

Situation

ERROR: "The connection to the server failed" on iPhone and iPad
ERROR: "The connection to the server failed" on iOS Devices
Downloading icon appears and vanishes and gives an error

Resolution

Please follow the steps listed below. These steps are to be followed only on Mobility Pack 1.2.1 (Build 730)
  1. Download and extract wbxml.pyc and DeviceInterface.pyc from the following link.
    ftp://ftp.novell.com/outgoing/741144.zip
  2. Browse to /opt/novell/datasync/syncengine/connectors/mobility/lib and rename wbxml.pyc to wbxml.orig.
  3. Copy extracted wbxml.pyc to /opt/novell/datasync/syncengine/connectors/mobility/lib .
  4. Browse to /opt/novell/datasync/syncengine/connectors/mobility/lib/device and rename DeviceInterface.pyc to DeviceInterface.orig .
  5. Copy extracted DeviceInterface.pyc to /opt/novell/datasync/syncengine/connectors/mobility/lib/device .
  6. Restart DataSync by typing "rcdatasync restart ".

Additional Information

Root Cause:
The sender uses emoticons in the Signature and sent a mail to the Receiver. The Receiver's iOS Devices gets the error message. Emoticons in the signature of the sender causes an issue.
 
Notes:
Error in the /var/log/datasync/connectors/default.pipeline1.Mobility-Appinterface.log file
2012-01-18 11:46:05.404 ERROR_VERBOSE [CP WSGIServer Thread-26] [DeviceInterface:937] [userID:] [eventID:] [objectID:] [Server] Global Exception handler xmlParseCharRef: invalid xmlChar value 56884, line 394, column 83
Traceback (most recent call last):
  File "./mobility/lib/device/DeviceInterface.py", line 875, in ashandler
  File "./mobility/lib/device/DeviceInterface.py", line 945, in fixXMLToWBXMLinSyncRequest
  File "common/lib/superxml.py", line 205, in fromString
  File "common/lib/superxml.py", line 63, in readString
  File "common/lib/superxml.py", line 45, in readFileObject
  File "lxml.objectify.pyx", line 1834, in lxml.objectify.parse (src/lxml/lxml.objectify.c:18721)
  File "lxml.etree.pyx", line 2698, in lxml.etree.parse (src/lxml/lxml.etree.c:49590)
  File "parser.pxi", line 1508, in lxml.etree._parseDocument (src/lxml/lxml.etree.c:71381)
  File "parser.pxi", line 1536, in lxml.etree._parseMemoryDocument (src/lxml/lxml.etree.c:71653)
  File "parser.pxi", line 1415, in lxml.etree._parseDoc (src/lxml/lxml.etree.c:70514)
  File "parser.pxi", line 938, in lxml.etree._BaseParser._parseDoc (src/lxml/lxml.etree.c:67438)
  File "parser.pxi", line 539, in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:63820)
  File "parser.pxi", line 625, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:64741)
  File "parser.pxi", line 565, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:64084)
 XMLSyntaxError: xmlParseCharRef: invalid xmlChar value 56884, line 394, column 83

Feedback service temporarily unavailable. For content questions or problems, please contact Support.