Borland Enterprise Server License error:
Sanctuary Runtime Error :Cannot connect to license server
A VisiBroker based CORBA application fails to start-up and prints the following error message to stdout:
Borland Enterprise Server License error: Sanctuary Runtime Error :Cannot connect to license server(4,0)
The error indicates that VisiBroker does not use a local license, but a shared license located on a Belize License Server, and failed to connect to it. A variant of the error message is cannot connect to either main or backup license server(18,0).
Check if the Belize License Server was started and is reachable by the host running VisiBroker.
A concurrent license consists of two parts, the license installed on the Belize Server which holds the number of license leases, and a license installed in each VisiBroker installation which redirects the license requests to the Belize Server. This local license contains the IP and port number of the Belize Server, which you will need to verify if the Server can be reached.
If you do not know the IP and port of your Belize Server, you can use network diagnosis tools ( netstat, tcpdump, etc. ) to check to which IP and port VisiBroker tries to connect. Start a VisiBroker based CORBA Server application, you can use /examples/vbroker/basic/bank_agent bundled with VisiBroker, and check to which host VisiBroker tries to connect. Alternatively you can also contact the support hotline to retrieve the IP and port from your license file.
Login at the host IP where Belize should be running, and verify that the process was actually started and is listening on the expected port ( ps, netstat ).
If the Belize Server is running, run the following commands on the VisiBroker host
- nmap -p <BELIZE_PORT> <BELIZE_IP>
- nmap -sU -p <BELIZE_PORT> <BELIZE_IP>
If both calls report the port to be closed, it indicates that your network configuration - maybe firewalls - block access to the Belize Server.