Unable to Access Remote Server

SAP ASE issues error message 11206 when you cannot access a remote server.

SAP ASE returns this message when you cannot access a remote server:
11206 Unable to connect to server server_name.

The message is preceded by one of these Client-Library messages:

Requested server name not found

The server is not defined in the interfaces file when the following messages display:
11206 Unable to connect to server server_name.

When a remote server is added using sp_addserver, the interfaces file is not checked. It is checked the first time you try to make a connection to the remote server. To correct this problem, add the remote server to the interfaces file that is being used by Component Integration Services.

Driver call to connect two endpoints failed

If the remote server is defined in the interfaces file, but no response was received from the connect request, the following messages are displayed:
Driver call to connect two endpoints failed
11206	 Unable to connect to server server_name.
  • Verifying that your environment is set up correctly. To test this, try to connect directly to the remote server using isql or a similar tool:
    1. Log in to the machine where Component Integration Services is running.
    2. Set the SYBASE environment variable to the same location that was used when Component Integration Services was started. Component Integration Services uses the interfaces file in the directory specified by the SYBASE environment variable, unless it is overridden in the runserver file by the -i argument.

      These first two steps are important to ensure that the test environment is the same environment that Component Integration Services was using when you could not connect to the remote server.

    3. Use isql or a similar tool to connect directly to the remote server.

    If the environment is set up correctly and the connection fails, continue through this list. If the connection is made, there is a problem with the environment being used by Component Integration Services.

  • Verify that the remote server is up and running. Log in to the machine where the remote server is located to verify that the server is running. If the server is running, continue through this list. If the server is not running, restart the server and try your query again.
  • Verifying that the entry for the remote server in the interfaces file is correct.
    • Verify that the machine name is the correct name for the machine the software is loaded on.
    • Verify that if the interfaces file is a text file, the query and master lines start with a tab and not spaces.
    • Verify that the port number is available. Check the services file in the /etc directory to ensure that the port number is not reserved for another process.

Login Failed

If you can access the remote server, but the login name and password are correct, the following messages display:
Login failed
11206 Unable to connect to server server_name.
See if there is an external login established for the remote server by executing:
exec sp_helpexternlogin server_name

If no external login is defined, Component Integration Services uses the user login name and password that was used to connect to SAP ASE. For example, if the user connected to SAP ASE using the “sa” account, Component Integration Services uses the login name “sa” when making a remote connection. Unless the remote server is another SAP ASE, the “sa” account probably does not exist, and an external login must be added using sp_addexternlogin.

If an external login is defined, verify that the user’s login name is correct. Remote server logins are case sensitive.Is the case correct for the user login name you are using and the entry in externlogins?

If the login name is correct, the password might be incorrect. You cannot display the password. If the user login name is incorrect or if the password might be incorrect, drop the existing external login and redefine it by executing the commands:
exec sp_dropexternlogin server_name, login_name
go
exec sp_addexternlogin server_name, login_name, remote_login, remote_password
go