Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 12.0.1 » SQL Anywhere Server - Database Administration » Starting and connecting to your database » SQL Anywhere database connections » Troubleshooting connections


A checklist of common problems

The following list presents some common problems and their solutions.

For information about troubleshooting connections to the database or database server, see Troubleshooting connections and Troubleshooting database server startup.

If you receive an error message indicating that the database server cannot be found when trying to connect, the client cannot find the database server on the network. See Database server not found.

Check for the following problems:

  • Specify the server name in the connection string.


    Your computer may be running software that has an embedded SQL Anywhere server, in which case there could be multiple servers running without you realizing it. You should always specify the server name (ServerName=server-name).

  • For remote database servers, it is recommended that you specify the Host connection parameter and provide the TCP/IP host name or address of the computer running the database server. Verify that the specified address is correct. If the server is using a port other than the default 2638, you may need to specify Host=tcpip-address:port-number. See Host connection parameter.

    If you are using the advanced CommLinks connection parameter, packets used to find the database server may not be getting to the database server. It is recommended that you use the Host connection parameter unless you need to use TCP/IP protocol options other than Host, ServerPort, or DoBroadcast. If you are using the CommLinks connection parameter without specifying the HOST protocol option, UDP broadcasts or requests may be limited to the current subnet or be blocked by a router, gateway, or firewall.

  • A firewall between the client and server may be preventing the connection. See Connecting across a firewall.

  • The personal server only accepts connections from the same computer. If the client and server are on different computers, you must use the network server.

  • Your network drivers are not installed properly or the network wiring is not installed properly. Use the ping utility to verify that the client computer can communicate with the server computer.

  • The server must use the TCP/IP protocol if you are connecting via jConnect or Sybase Open Client.

  • If you are using an administration tool, ODBC, or the OLE DB Connect window and you are trying to connect to a database server on your local computer, click Connect To A Running Database On This Computer in the Connect window. You can click Connect To A Running Database On Another Computer if you are trying to connect to a database server running on a computer other than your local computer.

 See also