Problem: I am getting error 146 in my InterBase.log file when I try to connect to InterBase. What are possible causes? Solution: /*******************************************************************************/ Note: The information in this article applies to InterBase v5.x /********************************************************************************/ One can find the verbal message to this numeric error code in a file called errno.h. This file can be found on most Unix systems under the directory /usr/include/. For Solaris, it is in /usr/include/sys directory. 1. In the Solaris errno.h file, error 146 points to connection refused. This usually means that no one is listening on the server side. To see if gds_db process is listening, do the command : netstat -a | grep gds_db at the UNIX prompt. This command asks the system to show us the state of all sockets. This includes server processes. This will show if gds_db was there. We need to be sure that gds_db was in listen mode. 2. hosts.equiv file has to have localhost in it for IB 5.0. 3 . Error number 146 is defined as connection reset in the interbase source code. This is equivalent to the TCP/IP error of 10054, that the machine on the other end was abnormally terminating the connection. Abnormally terminating the connection could be such an occurrance as: the user turning off the system or rebooting while being connected. 4. Check to be sure that the inetd.conf file is present and has the proper information in it. It should have an entry for gds_db in it for InterBase 4.0. 5. Check and ensure that /etc/services has the entry of: gds_db 3050
Last Modified: 27-OCT-00