Kbase 19550: 1432 Error When Trying To Connect Remote Client w/ Provision
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/18/2003 |
|
SUMMARY:
This Solution applies to Progress Version 9.
When running Personal Database, 4GL Development, or Provision licenses, you can start a database server for local logins only. You might run in a client server mode, starting a server on the local machine and connect as a remote client from that same machine using -H -S and -N. However, because they do not enable remote logins, there are limitations on the startup parameters.
You cannot use the system name as the -H parameter when connecting from the client. You must use -H localhost. This was changed in the Version 9 code to put in the IP address of 127.0.0.1 if the license is not for remote connections. This is what limits the -H to localhost.
The server is bound to the loopback interface to prevent it from allowing network connections from clients on other machines. The only way to connect to the server is to use a host name that will resolve to the address 127.0.0.1 (localhost). The server is not listening on the normal "hostname" address to any client using -H "hostname", either local or remote, so it appears as though the server is not running, causing the following error:
** Could not connect to server for database <DATABASE>, errno
<ERRNO>. (1432)
The Progress client is not license restricted, it should be able to connect to any server that has the remote logins enabled. The restriction is in the database server component.
SOLUTION:
When you start a database with development licenses, make sure you specify -H localhost in the client connection parameters.