SAS ODBC Driver User's Guide and Programmer's Reference

S1000 Communications Access Method Errors

The S1000 (SAS API Error) return code is often accompanied by error messages that are returned by your communications software. The following tables list some of these message texts and provide explanations for them.

In addition to these error messages and return codes, some additional information can sometimes be found in a "trace" file that is created in the working directory of the ODBC client application that fails a connection to a SAS server. This trace file has the name WQExxxxx.TRC, where xxxxx is the process ID of the ODBC client application at the time of failure.

S1000 Communication Access Method Errors
Message Text Explanation

Memory failure Not enough memory is available.

Network failure An unspecified network failure occurred.

No server found The remote server was not found.

Remote closed connection The SAS server disconnected.

Remote refused connection The remote system disallowed a connection. Check the remote services file.

Start SAS failure - please check your SAS server parameters The ShellExecute statement failed when starting SAS. Check to see whether the SAS paths are specified properly.

TCP method Winsock API <function-name> failed with WSAGetLastError <rc> A TCP/IP Winsock return code (rc) was returned. Even though it is impossible to document all the possible reasons one might get one of these return codes, they are listed in TCP/IP Winsock Return Codes to provide some indication of where the Winsock transport is having a problem.

Timeout waiting for the SAS server - check the startup options A SAS server did not register itself as a DDE server within the specified time period.

Unable to locate remote host TCP/IP could not find the remote host name.

Unable to locate service TCP/IP could not find the server name in the services file.

Userid.password security failure User ID and password verification failed on the remote machine.

You must connect to SAS/SHARE on a remote machine You must select the SAS/SHARE button in the SAS ODBC Servers page (Servers Page) in order to connect to a remote machine.

***S1000 Communication Access Method Errors***
Message Text	Explanation
Memory failure	Not enough memory is available.
Network failure	An unspecified network failure occurred.
No server found	The remote server was not found.
Remote closed connection	The SAS server disconnected.
Remote refused connection	The remote system disallowed a connection. Check the remote services file.
Start SAS failure - please check your SAS server parameters	The ShellExecute statement failed when starting SAS. Check to see whether the SAS paths are specified properly.
TCP method Winsock API <function-name> failed with WSAGetLastError <rc>	A TCP/IP Winsock return code (rc) was returned. Even though it is impossible to document all the possible reasons one might get one of these return codes, they are listed in TCP/IP Winsock Return Codes to provide some indication of where the Winsock transport is having a problem.
Timeout waiting for the SAS server - check the startup options	A SAS server did not register itself as a DDE server within the specified time period.
Unable to locate remote host	TCP/IP could not find the remote host name.
Unable to locate service	TCP/IP could not find the server name in the services file.
Userid.password security failure	User ID and password verification failed on the remote machine.
You must connect to SAS/SHARE on a remote machine	You must select the SAS/SHARE button in the SAS ODBC Servers page (Servers Page) in order to connect to a remote machine.

Chapter Contents
Previous
Next
Top of Page