Skip to main content

Domino 8.5 Server not starting as a Service on Windows 2008 Server

I came in this morning to find that overnight, my newest server decided to restart itself. At 3:00AM. That was the first clue as to why. Turns out that Windows Update was never disabled. So, nicely, it decided to install its updates and reboot.

Funny thing is, after the reboot, Domino never started up. Rather, it started up, but then shutdown about 9 seconds later. Long enough to send me a Fault Recovery Notification, but not long enough to trigger NSD. So, I end up with an e-mail saying that the server was restarted after a fault, but not why. Very useful.

First thing, I uninstall the 4 updates from last night. (This has worked for me in the past.) One at a time, with a reboot after each one. Each time I get the same e-mail, but nothing further.

Next step, run Domino as a Windows application, to see if I can see anything on screen. Low and behold, I can. It starts perfectly.

Next, shut Domino down and restart the service. No dice. Same story as before.

Quick search of the IBM support site reveals nothing. (Nothing useful to this at least.)

I found this thread on the Domino 8.5 forum on Notes.net. The solution there lead to this technote.
The premise behind it is to statically tie the IP address of the server to the TCPIP port, and to do the same for the server controller. I edited my notes.ini directly as I didn't want anyone to remove it from the server configuration document by accident someday.

TCPIP_TcpIpAddress=0,8.55.128.173:1352
TCPIP_ControllerTcpIpAddress=8.55.128.173:2050

My server is back up and running and I've done a few reboots to make sure it stays that way.

Another lesson learned.

Comments

  1. Thanks for the useful info. It helped me troubleshoot a Domino 8.5.1 server running on Windows 2008 that would not start up.

    -Eddie, Miami

    ReplyDelete
  2. Good stuff John! Was having a very similar issue on a new Win2k8 server with Domino 8.5.1 FP3 not starting as service. After seeing your comment here about setting the TCPIP* lines in notes.ini, it got me to thinking about whether this new server of mine actually knew how to talk to itself. I couldn't ping the hostname as listed in server doc, so after clearing that up the server started fine as a service. So this could be something else for readers to be aware of as a possibility.

    ReplyDelete
  3. Great post. After moving the server to a new location (and IP), I was having the exact same issue. Thanks to your post, you saved me from re-inventing the wheel.

    Thanks for sharing.

    ReplyDelete
  4. THANK YOU very much! This is a very useful hint - I was never able to solve this problem.

    Good job!!!

    Adam

    ReplyDelete
  5. Thank you...this information helped me to end 2 day outage.

    Thanks for sharing.
    Manjeet

    ReplyDelete
  6. Good stuff John! Was having a very similar issue on a new Win2k8 server with Domino 8.5.1 FP3 not starting as service. After seeing your comment here about setting the TCPIP* lines in notes.ini, it got me to thinking about whether this new server of mine actually knew how to talk to itself. I couldn't ping the hostname as listed in server doc, so after clearing that up the server started fine as a service. So this could be something else for readers to be aware of as a possibility.

    ReplyDelete

Post a Comment

Popular posts from this blog

Policies and Controls are King in the IT Security world

I came across an article by Roger Grimes over at Infoworld on how security policies and controls are the real power when it comes to IT security. Roger mentions the SANS 20 Critical Security Controls for Effective Cyber Defence , which are a great read for anyone looking at updating or auditing your policies for completeness. The SANS top 20 controls are a must for any organization: Inventory of Authorized and Unauthorized Devices Inventory of Authorized and Unauthorized Software Secure Configurations for Hardware and Software on Laptops, Workstations, and Servers Secure Configurations for Network Devices such as Firewalls, Routers, and Switches Boundary Defense Maintenance, Monitoring, and Analysis of Security Audit Logs Application Software Security Controlled Use of Administrative Privileges Controlled Access Based on the Need to Know Continuous Vulnerability Assessment and Remediation Account Monitoring and Control Malware Defenses Limitation and Control

Fun Little Earthquake

It's 1:45pm EST in Ottawa, Ontario, Canada. We just had an earthquake.  Not strong enough to damage anything, but enough that I watched people run out of buildings. What a fun Wednesday.

Reminder: Increase the maximum available memory on your Lotus Notes client JVM today!

Yup, that's right.  Public Service Announcement time. If you haven't increased the maximum memory available to your Lotus Notes JVM yet, what are you waiting for? By default, the Notes JVM only has 256mb of memory available to it.  On a system with 4GB+ of memory, you should be easily able to increase it to 1/4 to 1/3 of the system memory and improve the end user performance. Here's how: Shut down Lotus Notes. In order to make sure that all processes are stopped, run this command:  Start -> Run Type: C:\Program Files (x86)\IBM\Lotus\Notes\nsd.exe -kill Open: C:\Program Files (x86)\IBM\Lotus\Notes\framework\rcp\deploy\ Open the "jvm.properties" file in a text editor like notepad.  You will possibly require Administrator permissions. At the beginning of the file, you will see text surrounded by a lot of pound signs ####. The first ‘property’ after the last # sign is: vmarg.Xmx=-Xmx256m Change 256m to 1024m so that the line reads: vmarg.X