This drove me crazy because the only reason given was Fatal error during installation

 

 

 

 

 

 

 

 

 

 

The system event logs show

Timeout (30000 milliseconds) waiting for the SQL Server (MSSQLSERVER) service to connect.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

and

The SQL Server (MSSQLSERVER) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I finally found that the problem is with the hardware having an odd number of cores

The answer is (from the article)

  1. At the time you get the failure to start SQL Sevrver during setup you are presented with a retry option.At this time replace the SQLSERVR.exe and SQLOS.dll into the BINN folder at your install location from an Service Pack 2 installation and then Retry.  This allows the SQL Server to start and complete the setup. YOU ARE NOW IN A PRODUCTION UNSUPPORTTED SITUATION.
  2. Immediately apply SQL Server SP2 and you are back in a supported configuration.

 

Unfortunately I quit and the install did not rollback so I have to

  1. Do a manual un-install
  2. Set the NUMPROC=1 in boot.ini
  • Click Start, click Run, type msconfig, and then click OK.
  • In the System Configuration Utility dialog box, click the BOOT.INI tab.
  • On the BOOT.INI tab, click Advanced Options.
  • In the BOOT.INI Advanced Options dialog box, click to select the /NUMPROC= check box.
  • In the list that is next to the /NUMPROC= check box, click 1, and then click OK.
  • In the System Configuration Utility dialog box, click OK.
  • Restart the server.
       3. Install SQL SP4
       4. Remove NUMPROC parameter from boot.ini
       5. Reboot and back in business