Skip to Content

SQL Anywhere / Mobilink

Downloading data from the Mobilink server using tcpip results in error:

Data read failed. Requested 2 bytes but got 0 bytes. Operation interrupted.

This seems to occur when a lot of data is downloaded. I tried to open the log file, but it was 313Gb so I had to delete it.

How can we find out why this error occurs and how to solve it.

If info from the log file is needed, is there a particular line to look at? Posting the complete log is not possible due to the size.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on May 21, 2013 at 02:38 PM

    Hi Eric,

    Where do you see this error - on the client or on the MobiLink server? Generally this means that one side of the connection was waiting to receive a response and the response was never seen within the timeout (and/or TCP/IP socket) interval.

    If info from the log file is needed, is there a particular line to look at?

    There are lots of reasons a network connection can drop, and many of them can be related to physical network stability and operating system configuration. Network tracing on the MobiLink server and client requires a hidden switch to be enabled - we can walk you through that configuration through technical support and help you look through the reseulting debug logs, but a network expert from your end will also be required to help you understand your network and help us debug any points in between the client and the server. It may be that you will need to trace out the network connection at the actual network protocol level (which is primarily controlled by the operating system), using a tool such as WireShark to find the cause. As an example where this would be required, I have previously seen cases where the MTU set by the OS has been too big between the client and server and have caused the situations you describe - "small" synchronizations work, where "big" synchronizations drop off because the MTU value is exceeded when larger data packets try and move through the network. This was only discovered by using WireShark at the operating system level - MobiLink does not control that behaviour.

    Every situation is different to resolve network connection drops and typically requires a large amount of packet tracing to finally get a better picture of what's happening. Be prepared to examine multiple levels: application, operating system and physical link layer - to get to the bottom of the issue. You will most likely want to open a technical support case with us to help evaluate your options for tracing on the MobiLink client and server and help guide you through how to set up a tracing session.

    Jeff Albion

    SAP Active Global Support

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.