Non-ActiveSync requests blocked after updating to Mobility Pack 1.2.3

  • 7008004
  • 24-May-2012
  • 30-May-2012


Novell Data Synchronizer Mobility Pack 1.2.3


Non-ActiveSync requests blocked after updating to Mobility Pack 1.2.3
ERROR: " Invalid request. Not an activesync device" in /var/log/datasync/connectors/default.pipeline1.mobility-AppInterface.log
Users unable to connect after updating to Mobility Pack 1.2.3


In addition to bug fixes, Mobility Pack 1.2.3 blocks all non-ActiveSync requests in order to improve performance and to provide additional security. If there are any solutions in the environment that make make non-ActiveSync requests, Mobility Pack 1.2.3 will block those requests and if the solution/application is frontended for the devices, devices may not be able to connect. If these Applications are still required, please follow the steps listed below after applying 1.2.3. Please be sure to contact NTS after following the steps listed below. This is a temporary work-around. In the future builds, all non-ActiveSync requests will continue to be blocked 
  1. Shutdown Mobility by typing "rcdatasync stop" and press Enter.
  2. Browse to /opt/novell/datasync/syncengine/connectors/mobility/lib/device and rename DeviceInterface.pyc to DeviceInterface.orig.
  3. Download and extract DeviceInterface.pyc from
  4. Copy Extracted DeviceInterface.pyc to /opt/novell/datasync/syncengine/connectors/mobility/lib/device.
  5. Start Mobility by typing "rcdatasync start" and press Enter.