Article

Client-Server connections fail with Error 1432 with a Personal Database License

« Go Back

Information

 
Article Number000020547
EnvironmentProduct: Progress
Version: 9.x
Product: OpenEdge
Version: All supported versions
OS: All supported platforms
Question/Problem Description
Error 1432 when trying to connect to the Database as a remote user
Trying to connect to a database with -H, -S
Database started on a machine that has only a development license installed

Client-Server connections fail with error 1432 when connecting from either a remote machine or the same machine with:
  • -H <machine name> -S <service name>
  • -H <machine IP> -S <port number>
Steps to Reproduce
Clarifying Information
There is no firewall restricting ports
There are no issues found with DNS resolution
Development licenses include: 4GL Development, ProVision/OpenEdge Studio, Progress Developer Studio for OpenEdge all of which include the Personal Database License
Error MessageClient-side:
** Could not connect to server for database <DATABASE>, errno <ERRNO>. (1432)
Could not connect to server for database <DATABASE>, errno 0. (1432)

Database:
This server is licensed for local logins only. (4393)
Defect/Enhancement Number
Cause
When running Personal Database, 4GL Development, or OpenStudio/Provision licenses, the database server will accept local logins only as all these licenses contain the Personal Database.

It is not the Progress client that is license restricted, it is able to connect to any server that has remote logins enabled. The restriction is in the database server component where  the server is bound to the loopback interface to prevent it from allowing network connections from clients on other machines. 
That means that any client connecting must be running on the same machine, and must be connecting using -H localhost / -H 127.0.0.1.
Using any other hostname, it appears as though the server is not running, causing error 1432.
Resolution
A.  When databases are started with Personal Development Licenses:

The 'Personal' database can be run in client server mode, by starting the database server on the local machine and connect to it as a remote client from that same machine using -H -S parameters. There are specific limitations on the startup parameters as this licenses does not allow remote logins:

1. You cannot use the system name as the -H parameter when connecting from the client. 

2. You must use "-H localhost" to connect the client to the Personal Database. The code was changed in Progress 9 on the server side to force the IP address of 127.0.0.1, when the database license does not allow remote connections. This is what limits the -H to localhost. 

3. The database server is then 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 error
1432 Could not connect to server for database <DATABASE>, errno <ERRNO> or
704  There is no server active for database <database> on -H <hostname> -S <servicename> 
 
4. It is not the Progress client that is license restricted, it is able to connect to any server that has remote logins enabled. The restriction is in the database server component. In other words, after starting the database multi-user mode with an OESTUDIO license (or any of the development licenses): 

$  proserve dbname -S 4545 
 
Two kinds of client connections are then allowed from the same server the database is started on: 
  • self service connections: mpro dbname 
  • client server connections: mpro dbname -S 4545 -H localhost 
B.  If connections from remote machines must be possible, install and start the database with a Workgroup or Enterprise Database License.
Workaround
Notes
References to Other Documentation:

Progress Article(s):
000030188, Remote clients getting error 1432 when connecting to a database.
Attachment 
Last Modified Date6/19/2017 8:03 AM


Feedback
 
Did this article resolve your question/issue?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025