Powered by Zoomin Software. For more details please contactZoomin

DataDirect OpenAccess SDK Help

Connection Handshaking

  • Last Updated: June 26, 2026
  • 2 minute read
    • OpenAccess SDK
    • Version 8.1
    • Documentation

If you are experiencing problems during handshaking after the low-level TCP/IP connection has been made to an OpenAccess SDK Server, follow these recommendations:

  • You may have specified a TCP/IP port that is not used by an OpenAccess SDK service.

    • If the specified port is serviced by an OpenAccess SDK Server of an earlier, incompatible version, the following errors can occur:

      • Error 2200. The client did not receive a reply from the server within the specified time frame. This error occurs only if a connection timeout is specified.
      • Error 2300. The server closed the transport connection.
    • If the specified port is serviced by a server that is not an OpenAccess SDK Server, the following errors can occur:

      • Error 2200. The client did not receive a reply from the server within the specified time frame. This error occurs only if a connection timeout is specified.
      • Error 2300. The server closed the transport connection.
      • Error 2310. The server went down while trying to process the handshake request. The connection was closed.
      • Error 2315. The server received the handshake request and returned a non-IIOP reply that the client could not understand.
    • The client receives an error message that informs you that the server has closed the connection during the initial handshake.

    • If the specified port is serviced by an OpenAccess SDK 7.0 Server, the following errors can occur:

      • Error 2200. The client did not receive a reply from the server within the specified time frame. This error occurs only if a connection timeout is specified.
      • Error 2312. A connection was established with the server, but no data was received on the server within the keep alive period. Increase the keep alive setting on the server.
Alert