The ArcSDE application server communicates with many client applications using connections that are made through a specified port using TCP/IP protocol. For this to work, there must be matching correct entries in both the ArcSDE services file and the operating system services file.
The system services file is installed with the operating system. It contains a list of TCP and UDP service names and associated port numbers.
The ArcSDE services file contains the service name and the TCP/IP port number that is used to communicate with the ArcSDE Application Server. If there are multiple ArcSDE instances hosted using the same SDEHOME, the ArcSDE services file will contain multiple entries.
On UNIX and Linux, the ArcSDE services file is $SDEHOME/etc/services.sde and the system services file is usually /etc/services.
On Microsoft Windows, the ArcSDE services file is %SDEHOME%\etc\services.sde and the system services file is %SystemRoot%\system32\drivers\etc\Services.
- Check that the entry in the system services file is the same as the entry in the ArcSDE services file. The name should be the same, as should the port number and the protocol (tcp).
- Check that each service file entry is well-formed, using the following pattern, all on a single line per entry. The comment is optional.
<service_name> <port_number>/tcp # comment
For example, if the service name is esri_sde (the default) and the port number is 5151 (the default), the entry should look like this:
esri_sde 5151/tcp # ArcSDE for SQL Server
- Check that the last line of the system services file and the ArcSDE services file end with a line termination character (linefeed on UNIX and Linux, carriage return on Windows). On some systems, the last line of the services file will not be read if it does not end with a line termination character.
- Check that there are not duplicate port numbers assigned in either the system services file or the ArcSDE services file.