Problem: When an inet error is written to the interbase.log file it is accompanied with an unknown errno. Example: ----------------- Statement failed, SQLCODE = -902 Unable to complete network request to host "nuschler". -Failed to establish a connection. -unknown Win32 error 10061 Solution: These unknown errnos are platform specific. This means that you will have to use resources from the machine where the errno was produced. Where to find information: Windows Platforms -------------------------------- On Windows platforms all the inet errors are greater than 10000 (ie. 10061). The TCP/IP stack for Windows platforms is called winsock. A file with information on all inet (winsock) errors does not come with the operating system. The file does come as part of most compilers. You can also download winsock development kits that include the information. Files to look for: [C compilers] - look in the compiler's include directory for the header file winsock.h. This file contains a listing of all the inet/winsock errno codes. [Delphi] - Search the delphi directories for the file winsock.pas. This file serves the same function as the winsock.h file. UNIX ------------ On Unix systems all errnos are kept in either: * /usr/include/errno.h * /usr/include/sys/errno.h All flavors of Unix are not consistent in associating an errno with a type of error. It is important to remember to look in the errno.h file for the platform on which the error was produced.
Last Modified: 17-OCT-00