Sometimes when using SQL Connection or xfODBC in a client/server configuration, one of the following socket errors occurs:

-- connect:errno:error

-- recv:errno: error

where error is either "Connection reset by peer", 10054, or 54.

The "Connection reset by peer" socket error, which is socket error 10054

(WSAECONNRESET) on Windows and is generally socket error 54 (ECONNRESET) on

UNIX and OpenVMS, indicates that a connection to the server has been closed.

This error could be caused by a fatal error on the server, the server

stopping, a network problem, or even a connection problem.

1. If the error has the form "connect:error text:", use vtxping (or

synxfpng with the -x option) to test your ability to connect to the server.

(For information on vtxping, see "vtxping utility" in the Synergy/DE documentation. For

information on synxfpng, see "synxfpng utility" in the Synergy/DE documentation.)

  The vtxping and synxfpng utilities print reports to the screen. This

  information can be used by your network administrator to resolved TCP/IP

  network socket communication problems.

  -- If you can connect using vtxping, the network, the server, and the SQL

     OpenNet service are working. Continue with step 2.

  -- If you can\'t connect with vtxping, make sure that the server is

     running, the SQL OpenNet service is running on the server, and

     that you either specified the correct port number in the vtxping or

     synxfpng command or are using the default port.

2. Check the following:

  -- If you\'re using Synergy/DE version 6.1.1a on Windows NT 4.0, upgrade to

     a more recent version of Synergy/DE. License Manager for Synergy/DE

     6.1.1a does not accept the required ONET license code on Windows

     NT 4.0. This problem was fixed in Synergy/DE version 6.1.2.

  -- (xfODBC only) If you\'re using a version prior to 7.2.7, make sure you

     include "sdms:" at the correct location in the connect string

     specified in the login dialog box or in the "Appended to Connect

     String" field of the VORTEXodbc Setup dialog box (the dialog box used

     to configure DSNs).

  -- If you\'re using version 7.5.1 of Connectivity Series on a machine with

     Linux 7.1 or higher, either upgrade to Connectivity Series 8.1 or

     higher or obtain libgcc_s.so from the developer of your Linux system.

     Connectivity Series version 7.5.1 incorrectly references libgcc_s.so.

  -- (Windows only) If you\'re using network licensing, make sure License

     Manager is configured as a network server.

  -- Make sure the server was rebooted after the Connectivity Series

     components were installed.

  -- (Windows only) On the server, make sure the GENESIS_HOME environment

     variable is set in the environment or in opennet.srv (not at the user

     level).

  -- Check the system-level PATH on the server. It should include the

     connect directory. For example:

     c:\\synergyde\\connect

  -- Use vtxnetd or vtxnet2 logging and check the resulting tcm_.log

     file. Then check the event log on Windows, syslog on UNIX, or the

     operator log on OpenVMS. (For more information see

"vtxnetd and vtxnet2 programs" in the Synergy/DE documentation. )

  -- (xfODBC only) On the server, make sure the file(s) for the Synergy

     database driver (vtx4) are in the connect directory. On Windows,

     these are vtx4.exe and vtx4.dll. On UNIX, this is vtx4.so. On

     OpenVMS, this is vtx4.exe.

  -- (SQL Connection only) Make sure the file(s) for the database driver

     you\'re using are in the connect directory on the server. On Windows,

     there are two files: an .exe and a .dll (e.g., vtx0.exe and vtx0.dll).

     On UNIX, this is an .so file (e.g., vtx0.so). On OpenVMS, this is an

     .exe file (e.g., vtx0.exe).

  -- Make sure there is no more than one vtxnet2 process running on the

     server. If there\'s more than one, use vtxkill to kill the processes;

     then restart the service.

  -- If the server is a Windows NT system, make sure it has the latest

     service packs. These include a fix for a problem with an incorrect

     error being returned for WSAECONNRESET.

3. If you\'re on Windows or UNIX, run the dltest utility to make sure

  Connectivity Series DLLs or shared libraries are loading properly.

  This is a command line utility (in the synergyde\\connect directory)

  and has no options.

4. Check connection specifications.

  -- For xfODBC, make sure the dictsource and datasource lines in the

     connect file on the server have the correct settings. Then make

     sure the settings in the DSN are correct. For example, if the DSN

     specifies a port, it should be the port that the SQL OpenNet server

     is running on. (If the SQL OpenNet server is running on the port

     that\'s the default for the client, the DSN doesn\'t need to specify

     a port.)

  -- For SQL Connection, make sure the connect string in the client

     application is referencing a valid driver and database.

5. If you get this error again, use vtxnetd/vtxnet2 logging and check

  the event log on Windows, syslog on UNIX, or the operator log on

  OpenVMS.