ServerController=1 and TCPIP_ControllerTcpipAddress= lines go missing from the Notes.ini

HCL Domino Domino Forum
1

This has happened twice now in 2 different environments where I had a problem where the Domino server wouldn’t start as a service after Windows was rebooted and the issue was that the lines were missing from the notes.ini for TCPIP_ControllerTcpIpAddress= ServerController=1 . The servers are different versions of 14.x

I know the fix, but I need to know what was the cause for them to be cleared in the first place. Anyone?

2

Hi Dave,

Regarding your concern, could you please provide the following information so we can better assist you:

  1. Just to confirm, once these parameters are added to the notes.ini file:
    TCPIP_ControllerTcpIpAddress=:
    ServerController=1
    does the Domino server start successfully as a Windows service after a reboot?
  2. In Windows Services, what startup type is currently configured for the Domino server: Automatic (Delayed Start) or Automatic? - If it is currently set to Automatic, would you be able to change it to Automatic (Delayed Start) and monitor whether the issue recurs?
  3. When did the issue first occur?
  4. Were there any changes made to the Domino server or operating system configuration, or any recent upgrades or updates, prior to the issue occurring?
  5. Is there any third-party software or automation that could potentially modify the Domino configuration, such as scheduled batch files or scripts that modify the notes.ini file?
  6. Were you able to check the Windows Event Viewer Application and System logs when the issue occurred? If so, were there any relevant errors or warnings recorded around the time of the failed service startup?

Thank you.

Best regards,
Kaycery

3

Thank you Kaycery.

  1. Yes, adding the lines back into the notes.ini it launches properly as a service.
  2. The service is set to Automatic (delayed) on both servers that the problem occurred on.
  3. The “When” was after a power outage in one of the two instances, about a month ago. If you have access, see case CS1464531. For the second incident (a different server in a different environment) it was yesterday. One case is V14.0FP5 and the other is V14.0FP4.
  4. In both cases these servers are rarely even touched and there were no changes to their configurations for many months.
  5. No. Both servers are just used for email. Vanilla configurations. Boring even.
  6. I didn’t see anything in Event Viewer that would give a clue to the cause, but in both cases, the servers had not been rebooted in a month or more, so the cause may have happened long before and only became an issue when the servers were finally rebooted.

I am tempted to open another case with HCL to get this investigated. I am hearing others who have had a similar problem. Cause is unknown. They all just fixed the notes.ini and moved on. But for me this is not acceptable because these servers are not managed that closely to detect that Domino didn’t come back up right away.

4

Hi Dave,

Thank you for providing the requested information.

In this case, yes, we would recommend opening a case so that we can further investigate the issue.

Thank you.

Best regards,
Kaycery

5

Have you tried adding the entries using the Notes Configuration or that there is some old entries there that removes them ?
Not a fix but maybe an walkaround

6

That is actually a good workaround. But I don’t want to have to go and add that to every configuration document in the anticipation that those lines might disappear some day. And it wouldn’t work too well for shared config docs if I’m putting in the server IP address. Unless I use 127.0.0.1.