Hi,
I installed a Domino server, running Java Console as service. When I clonned in on another HDD, restart it, it gives me the message :
Unable to bind to port 2050 on host machine servername/2.20.31.13:
Either the host name or address is wrong or the port is already in use.
Domino Server Controller exiting: Listener startup timed out.
Please check if another Server Controller instance is running in the same data directory.
Please press to exit…
i had change the clone server’s IP address, server name. but how do i bind it back to the new ip address?
thanks
Subject: Java Console not working on cloning
I would be happy to help you. However, I don’t know what you meant by cloning.I am assuming you copied the current server installation to another HDD. If this
is what you meant, please go to the new servers data directory on new HDD and
change the following fields in the file “dcontroller.ini”:
Host_Name=
Port_Number=
Domino Controller when started binds to Host_Name and Port_Number specified
here. However, if “notes.ini” of a server has “TCPIP_TcpIpAddress=” set, this
takes precedence over what is in “dcontroller.ini”. Please refer to documentation.
-Mallareddy
Subject: RE: Java Console not working on cloning
Thanks for the help!!! I had the same problem after moving my BES to a new server with an identical host name (switched host names of the two servers after copying the files). BTW, there seem to be multiple copies of the *.ini files, both in the Lotus\Domino and the Lotus\Domino\Data directories. I had to change them all before I could get the Java console to work.
Subject: RE: Java Console not working on cloning
Thanks for the solution.
I clone the harddisk using Ghost to deployed to multiple servers/branches.
I also noticed that there is this dconsole1.ini and dcontroller1.ini, which have same configurations. Can I delete these two files, as I have to make the changes twice. If i make changes on the dconsole.ini with the new server settings, when I start the domino via java, it will appear on top of the console as “old server”. Hence, after changing the two dconsole.ini settings, only it will work.
Thanks!