In addition to the error
messages in the following sections, information can sometimes be
found in a trace file. A trace file is created in the working directory
of the ODBC client application if it fails to connect to a SAS server.
The trace file has a name in the form WQExxxxx.TRC, where xxxxx is
the process ID of the ODBC client application at the time of failure.
The following trace
file is a sample response for a DSN that does not have the service
name identified in the TCP/IP services file on the client machine.
Add the service name to the TCP/IP services file on the client machine.
Review the task for setting up your connection.
[2786321593]:WQEOpen: Winsock getservbyname failed rc = 11004.
[2786321593]:WQEOpen failed: rc -1005 trc 0x2afc.
The following trace
file is a sample response for a DSN that has the service name identified
in the TCP/IP services file on the client machine, but the same service
name is not found in the TCP/IP services file on the server. Add the
same service name to the TCP/IP services file on the server.
[2788365437]:WQEOpen: Winsock sendrecv failed rc = 0.
[2788365437]:WQEOpen failed: rc -1007 trc 0x0.
The information in the
previous paragraphs provides information about how to use an automatically
generated trace file to assist with diagnosing communications access
errors. A trace file can also be created intentionally to assist with
diagnosing undesirable behavior. Make sure that the ODBC client application
is closed, and then follow the instructions provided at
http://support.microsoft.com/kb/274551.