|Parameter 1||The number of bytes that could not be read.|
Unable to read the given number of bytes from the network layer. Note that reads may occur as part of any larger network operation. For example, some network layers have sub-layers that perform several reads and writes as part of a basic operation in the upper layer. The cause of a read error is usually one of the following: 1) The network had a problem that caused the read to fail. Reconnect and retry the operation. 2) The connection timed out. Reconnect and retry the operation. 3) The other side of the connection cleanly terminated the connection. Consult the client and/or server logs for errors that indicate why the connection has been dropped. Consult the output-log errors and fix the cause, then retry the operation. 4) The process at the other side of the connection was aborted. Consult the client and/or server output logs for errors that indicate why the process was aborted. If the process was shut down by other than normal means, there may not be any errors in its output log. Reconnect and retry the operation. 5) The system is low on resources, and cannot perform the read. Free up system resources, reconnect and retry the operation. If subsequent retry attempts fail, consult your network administrator.
|Discuss this page in DocCommentXchange.
Send feedback about this page using email.
|Copyright © 2009, iAnywhere Solutions, Inc. - SQL Anywhere 11.0.1|