Re: CLI ODBC Can't Locate Servicename
Posted in 1997
} Scott Ellsworth wrote: } > } > This is a newbie question of the highest order. } > } > Have Informix-CLI 2.5 Ver 2.12.0000 installed on an NT workstation. I can } > ping the Informix server, run Informix DB-Access and 4GL on the server, but } > I can't get ODBC connection to the server. } > } > The error is "-931 Cannot locate servicename service/tcp service in } > /etc/services" } > } > Hostname, service name, server name, protocol type all are apparently } > correct. I and at one time wondered about the hostname being OK but using } > an IP address in place of the hostname yields the same error. } > } > Anything anyone can do to point me in the right direction will be } > appreciated. } > } > TIA I use Informix-CLI 2.5 on Windows NT workstation, no problem. If you're getting 931, then there must be something wrong with your services entries. The services file on NT is located at C:\\WINNT\\SYSTEM32\\DRIVERS\\ETC Put an entry in this file that matches your Informix entry on your UNIX server. i.e. sqlexec 2001/tcp This service name (sqlexec here) must then be used by the database server. Check your sqlhosts file to be sure the database is using the same name: i.e. prodserver onsoctcp hostname sqlexec Then, when you use CLI, run SetNet and under the Server Information tab make sure the Service Name field is filled in with the same name (i.e. sqlexec). This is just the default and can be overridden by the ODBC Data Source Name or the app. As an example, when you run the Test Login program, you can either fill in the Servicename field with sqlexec or you can leave it blank and it will use the default for the Server you defined in SetNet. This should resolve your 931 error. Bruce Farwell Spartan Stores, Inc. Grand Rapids, MI