we upgraded our 2nd domino server today to release 8.5.2, we had 8.5.1FP3 before. The server runs fine (although i had to kill the nserver process once because the service wasn’t starting up correctly - fixed with windows restart), clients can work as usual but I’m not able to connect with the Lotus Domino Console and have 2 issues.
1.) Every time I try to connect I receive an “Either the Server Controller is not running on host … or is not listening on port 2050.” error. I checked the server document (port set to 2050), but the port doesn’t seem to be open (checked with “netstat” - nothing on port 2050…). Besides that, it’s possible to connect to the server console via administration client server console without any problems.
2.) All the time I get an “Interactive services dialog detection” window (machine is Windows Server 2008, 32 bit), when I open the message it shows the domino server’s old school console.
On the other server we’ve upgraded a few days ago everything works fine.
Would really appreciate any hints where the problem might be. I’ve also ran the setup another time without any change.
I found the previous suggestions helped (thank you) LocalHost=WindowsServerName:2050
LocalHost=DominoServerCANONICALIZEDName:2050
and sometimes the service started, but not always… so in addition I changed the Lotus Domino start up type in the Windows services panel to “Automatic (Delayed Start)”
Subject: One Fix - Server Controller not running on host or is not listening on port 2050
Test the port 2050 by bringing up a command prompt on the Domino Server and type: netstat -a
Look through the results that scroll by and search for the port 2050. If this port shows up and is in the listening state, then your problem is Not with the port.
Next using the command prompt and type:
telnet localhost 2050
If you get a response on the port you now know that it has nothing to do with the servers local firewall or port 2050 from being blocked locally.
In the Data directory of the Domino Server open the file dconsole using notepad. Find the line that reads: LocalHost=
I had to edit this line in order for the domino java console to work once again.
This fix actually work but are you aware if Lotus Domino console has an issue with team nic. We simulate our production setup to multiple development environment and all of those works fine except for our production server which happen to have NIC teaming.
I get the idea from struggling with a similar problem (Domino 8 on Windows 2008 64 bit) that multiple IP addresses and ports make things confused between the server console, the server controller and domino. Another possible IP issue to look for is if DHCP is running.
Here is an IBM technote with a workaround for a similar problem. Title: "
Unable to start the Domino 852 server as a service and run the Java Controller on Windows 2008 R2 server"