This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


~Wei Asatoopulakol
Mar 12, 2015, 10:05 PM
37 Posts

Domino server service fails to start on Windows Server 2012 R2 Standard

  • Category: Domino Server
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator
  • Tags: service,domino 9.0.1,windows server 2012
  • Replies: 14

I have just installed Domino 9.0.1 on a brand new Windows 2012 R2 server.

Everything went perfectly, and the server runs as expected.

 

However, every time I restart the box, the IBM Domino service fails to start.

I see nothing in the O/S 'event log'.

I see no issues recorded in the Domino server log (it is never started when the box is re-started).

The service is certainly configured as 'Automatic'.

I can start the service manually without a problem each time.

For some reason, the service simply fails to start when the Windows server is restarted.

 

Is there something obvious that I'm missing here?

Has anyone else encountered such an issue?

 

Any ideas/ assistance would be greatly appreciated!

~Wei Asatoopulakol
Mar 13, 2015, 7:53 AM
37 Posts
Thanks for the pointer Chad! Didn't work though...

Thanks very much for pointing me in the right direction!

 

I have tried everything suggested in that thread, but all to no avail.

Domino is installed on a single server with two local disk volumes.

I tried specifying the 'TcpipControlerAddress' in NOTES.INI.

I've even tried disabling other Microsoft services that I thought might be interfering - no such luck.

 

Will continue to try other avenues - Cheers!

~Dexter Deswechekynds
Mar 13, 2015, 11:57 AM
191 Posts
Reply
If the service starts manually but not automatically, it would seem there is some error condition that occurs at system start that causes the autostart to fail. I'd take another look at the System event log and look for anything from the Service Control Manager source.
~Dexter Deswechekynds
Mar 16, 2015, 11:30 AM
191 Posts
Try extending the service timeout threshold
It may be that Domino simply needs more time to complete startup processing than is allowed by default (30 seconds). You can see if this is the issue by commenting out the ServerTasks line in notes.ini. I don't know offhand when Domino posts a message to the OS that it has completed startup processing, but commenting out the server tasks that load by default will likely shorten that time and indirectly tell us that is the issue. If it is, you can add the ServerTasks line back and adjust the timeout period. See Step 3 here:

http://support.microsoft.com/en-us/kb/824344
~Wei Asatoopulakol
Mar 14, 2015, 3:23 AM
37 Posts
Yep - You were right Chad...

A closer review of the 'System' event log showed the following issue...

A timeout was reached (30000 milliseconds) while waiting for the IBM Domino Server (EIBMDominoData) service to connect.

A cursory Internet search revealed no immediate resolution to this problem.

 

I tried changing the credentials so that service operates as an 'Admin' user, but that didn't resolve it.

I tried turning Windows UAC off and re-starting the box, but that didn't do it either.

 

The search continues!

 

~Wei Asatoopulakol
Mar 15, 2015, 4:33 AM
37 Posts
Thanks Bradley, but...

Thanks for the suggestion Bradley!

 

I tried that out, and removed the service using ntsvinst.

I then created a new service using 'sc':  sc create "IBM Domino Server" binpath= "C:\IBM\Domino\nservice.exe -jc =C:\IBM\Domino\notes.ini"

I could then start the service manually without an issue, and could use the IBM Domino Console to access the server on that box.

I reset the service as 'Automatic' and re-started the box.

 

This time, it STILL wouldn't start the Domino service and there were two errors audited in the O/S system log...

 

A timeout was reached (30000 milliseconds) while waiting for the IBM Domino Server service to connect.

The IBM Domino Server service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

 

This is getting really frustrating now!  I will forge ahead...

~Yentl Umhipibergnivu
Mar 25, 2015, 8:02 AM
40 Posts
What does the console log and Domino og say
You've researched the OS events, but I am curious why the OS would think Domino has not started in 30 seconds.
You can start by comparing timelines using the info from log.nsf  after a manual and an automatic start.

If that doesn't provide any clues, look at the console log (<Domino Data directory>\IBM_TECHNICAL_SUPPORT\Console*.log files) and find out what it is doing or if it is waiting on anything

Please share your findings, so we can all learn.
~Wei Asatoopulakol
Mar 27, 2015, 2:09 AM
37 Posts
I WISH the console.log file had a record of any activity....

... but there is nothing recorded at all. I don't believe it even gets that far!       Here's the thing...

 

I can start the server manually 'as a regular application' using the server desktop icon without an issue

 

When I start the server manually 'as a Windows service' using the server desktop icon it must shut down straight away (it used to work!!) and there's a one-line entry left in the console.log file (the name of the log) - nothing in the Windows event log.

 

When I start the server manually using 'Windows Services' the service starts and then stops immediately (again, nothing in the Windows event log), and the following dialog box is displayed...

'The IBM Domino Server service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.'

 

I created a new service using:  ntsvinst -c -t"IBM Domino Server" (so it does NOT run as a java controller).

I can then start the server manually using 'Windows Services' and that service.

I switched the new service to 'Automatic' and re-started the box - The Domino server started fine.

 

So, it would seem that the issue is with the Domino Server Controller and not the serve itself.

I will continue in that vein and see what else I can determine - Thanks for sticking around everyone!!

 

~Vera Ekjumisterobu
Sep 15, 2015, 11:16 AM
8 Posts
Exactly the same problem

I have built a completely clean Win 2012 -R2 box (in vmware) and installed Domino 9.0.1.

Install and Server set up all goes fine.

Launching the server for the first time a a windows service all good.

However, after a reboot the service will not restart. I have followed all suggestions here and nothing works.

This seems to be specific to Win 2012-R2 as an identical on Win 2012 works fine.

Please tell me is if there is asolution to this problem.

MAny thanks

~Hank Lopvelutergon
Sep 16, 2015, 12:12 PM
100 Posts
Same here

I have the same setup (9.0.1 + Server 2012 R2 on a VM) and also have to manually start the service when the OS boots.

~Rebecca Prekrokonyobu
Sep 30, 2015, 1:02 PM
1 Posts
solved for me

not sure if this is still an open topic...

I just solved this problem on one of our server by rebuilding the folder "IBM_TECHNICAL_SUPPORT" in the data-folder.
Renamed the original folder to IBM_TECHNICAL_SUPPORT_old and created a new empty folder...

 

~Ted Kilupulakol
Nov 19, 2015, 8:52 PM
3 Posts
reinstall Domino
Had the same issue but with 901 FPs, Tried resinstalling the Domino server on another path (from C:\Domino to C:\DominoNew) and worked for me on win2012r2

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal