Showing posts with label console. Show all posts
Showing posts with label console. Show all posts

Sunday, October 10, 2010

Issues with Windows server 2008 and Lotus Domino java controller service

A special thanks to Pontus Wennergren for posting the following:

Your solution works very well since I had a similar problem. The service just refused to start but application worked fine.

But I prefer to make changes in notes.ini instead of the hosts file and when I found this:

http://www-10.lotus.com/ldd/nd85forum.nsf/5f27803bba85d8e285256bf10054620d/623744895c016a63852577310025230d?OpenDocument

and tried it, it worked just aswell so I am sticking to
TCPIP_ControllerTcpIpAddress=





Below is my original post for those that are interested:

Recently I've had an issue with a Lotus Domino 8.5.1 FP1 server running on Windows Server 2008. The service is setup to run

"d:\lotus\domino\nservice.exe "=d:\lotus\domino\notes.ini" "-jc" "-c"

However when I try to start the service I get this error:

The Lotus Domino Server (DlotusDominoData) service on local computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

No matter what I do I cannot get the server to launch under the service! I can launch the server under my remote desktop session but then I can't log off.

So looking at the d:\lotus\domino\data\dcontroller.ini file I found this entry:

Host_Name=traveler01.theozzyblogger.com

and I decided to ping this address on the same server. When I did that I received the IP6 address! So as a troubleshooting measure I input the IP4 IP and server name in the hosts file ( c:\windows\system32\drivers\etc\hosts ) and the service starts with no issues! I ended up un-checking IP6 and removed my hosts entry and that worked too. It turns out when I un check the IP6 it uses loop back address of

::1:

So I had to put the hosts entry back in to make it work... I think I will call IBM on this one. I will update with what I find.

The strange thing is this has worked all along and just recently became an issue. I wonder if a Windows update is to blame...