The domino server fails to load as a windows service(domino server 8.5 and windows server 2008). The domino server was running perfectly and all of the sudden it stop working. It will not load on automatic or manaul load. It will however load when I run the nserver.exe from the desktop icon. Error code 2351
Subject: Hi
That’s the only thing that’s not working fine there right? I just want to make sure before doing something drastic.
Anyway, I would remove it as a service and then add it again.
You can use the tool ntsvinst.exe which is in the Domino folder to do this. Just run the tool from a command line and it will tell you the options.
After you delete the service, make sure you add it with the same name. It’s not a requirement but it could bring problems in the future.
Hope it helps.
Subject: re:hi
I tried what you said but it has a problem with adding the following pathntsvinst -c -iC:\program files\ibm\lotus\domino\notes “-jc” “-c”
can not seem to get around the quotes or another method to add to do it.
Subject: Rerun the install and it will put your service back
Open a PMR with Lotus Support… Two things that I’m aware of…
-
If you have previously install Notes on the same machine using the same program directory, uninstall the Notes Client and Reinstall Domino…
-
We’ve had customers with conflicts on port 2050 for Domino Server Contor
There are a number of ways you can set this to 2051
From Server Controller Developer:
I am the author of the Domino Console and Controller pieces of domino and here is the explanation for the behavior you are observing. I am listing some files here, importance of them and then explain the sequence of operations.
dcontroller.ini - configuration file for Server Controller
dconsole.ini - configuration file for Domino Console
The above two files normally should not be edited by user. However, right after the fresh installation if you want to run server controller on a different IpAddress and/or port number from the default hostname and 2050, you can edit those two in dcontroller.ini.
admindata.xml - is generated by server when run after the installation.
This file should NEVER be edited as this is generated. This is the source for validation of admins, servers and groups on the controller end. The fields you mentioned in the server document will be written to this file.
notes.ini - domino configuration file. This is where you can specify TCPIP_ControllerTcpIpAddress.
When a Server Controller starts, it reads dcontroller.ini and then reads admindata.xml file. So the values that are in admindata.xml file has higher precedence. That is why when you edit dcontroller.ini with 2051 and run, it will switch to 2050 (as long as that is what you have in admindata.xml). However, you can override these with TCPIP_ControllerTcpIpAddress in notes.ini. The value you set here comes as command line options to the controller which has highest precedence. So as long as you have that notes.ini parameter set, that value is taken irrespective of what you set in server doc or dcontroller.ini. That is why if you want to run on a different port than default 2050 permanently, you should set it in the server doc. Notes.ini parameter was invented for a temporary run so we don’t have to change server doc. But if you leave that parameter in notes,ini permanently, it is equal to setting in server doc, which is the recommended way.
Hope I explained well about the behavior of your server. If you restart again, your environment should work OK because of notes.ini parameter.