Failure to install Database Enginee Service for SQL Server Standard 2012 on Windows 10

Question

question

MabelTe-0750 asked Sep 1, '20 saldana-msft edited Sep 15, '20

Failure to install Database Enginee Service for SQL Server Standard 2012 on Windows 10

I have problem in getting Database Engine Services installed for SQL Standard 2012 on Window 10. Have google and tried many ways, but encounter many different error.
I am writing this post after 2 weeks of research.... appreciate all help
1. Complete uninstall and fresh install again (that means remove program from Control Panel, delete regedit related to SQL Server 2012, delete all Microsoft SQL folder)
2. Install SQL Standard 2012 SP1, SP2, SP3, SP4, setting server configuration for SQL Server Database Engine to NT Service\System
3. Install 2018 to ensure a instance can be created. But when I installed 2012, encounter error "The service did not respond to the start or control request in a timely fashion" (I then tried to add DWORD - ServicesPipeTimeout to set as 180000
4. Install SQL 2012 Cumulative Update 3 and .Net 3.5 SP1
5. Install via command Setup.exe /ConfigurationFile= ConfigurationFile.ini

I just did another fresh install again (uninstall and install with regedit clear and SQL folder deleted) to prepare for any help. Following is what I have installed
- Under Apps & features, I have the following SQL version installed
- Microsoft SQL Server 2008 R2 (64 bit)
- Microsoft SQL Server 2012 (64 bits) with SP 1 to 4 installed
- .Net version 3.5 with SP1
- Windows Update has all the latest update i.e. "Check for update" has no outstanding program

Please advise. Thanks

sql-server-general windows-10-application-compatibility

· 5

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AmeliaGu-msft · Sep 02, 2020 at 03:23 AM

Hi MabelTe-0750,

Could you please share us SQL Server Setup log within %programfiles%\Microsoft SQL Server\110\Setup Bootstrap\Log? Please refer to View and Read SQL Server Setup Log Files.
Please make sure to disable any antivirus software temporarily and turn off the firewall on the machine for the time that the installation is running.

Best Regards,
Amelia

1 ·

Shashank-Singh · Sep 01, 2020 at 11:11 AM

Please post the output of summary.txt file.

0 ·

NOBTA · Sep 01, 2020 at 06:04 PM

What are errors you have confirmed in the latest ERRORLOG file on SQL Server 2012?

0 ·

MabelTe-0750 NOBTA · Sep 03, 2020 at 04:36 AM

There is no files in the folder.... so there is no ERRORLOG

0 ·

ErlandSommarskog · Sep 01, 2020 at 09:59 PM

"Install 2018 to ensure a instance can be created. " What is 2018 in this context=

0 ·

Answer 1 · 2020-09-04T09:48:42.38Z

ErlandSommarskog answered Sep 4, '20

I'm leaning towards that Avecto Defendpoint Service (which is what appears to have produced that event log message) decided that it was not approriate to start SQL Server 2012. Maybe it needs to be white-listed?

I think you need to talk with your internal IT folks at NCS to get this sorted out.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 2 · 2020-09-02T06:25:59.38Z

MabelTe-0750 answered Sep 2, '20 MabelTe-0750 published Sep 2, '20

Summary.txt

Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2147467259
Start time: 2020-09-01 00:34:32
End time: 2020-09-01 00:52:15
Requested action: Install

Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.

Machine Properties:
Machine name: NCS-270720DN02
Machine processor count: 8
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No

Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services 1033 Standard Edition 10.50.1600.1 No Yes

Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: F:\x64\setup\
Installation edition: Standard

Slipstream: True
SP Level 4

Product Update Status:
Success: KB 4018073

Product Updates Selected for Installation:
Title: Service Pack 4
Knowledge Based Article: KB 4018073
Version: 11.4.7001.0
Architecture: x64
Language: 1033

Update Source: D:\software\SQLUpdate

User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD:
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20200901_003220\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, SSMS, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server
INSTANCEID: MSSQL2012
INSTANCENAME: MSSQL2012
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID:
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: NCS\P0102881
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: D:\software\SQLUpdate
X86: false

Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20200901_003220\ConfigurationFile.ini

Detailed results:
Feature: Management Tools - Complete
Status: Passed

Feature: Management Tools - Basic
Status: Passed

Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x80004005
Error description: The service did not respond to the start or control request in a timely fashion.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.7001.0&EvtType=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325

Feature: SQL Browser
Status: Passed

Feature: SQL Writer
Status: Passed

Feature: SQL Client Connectivity
Status: Passed

Feature: SQL Client Connectivity SDK
Status: Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20200901_003220\SystemConfigurationCheck_Report.htm

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 3 · 2020-09-02T07:43:14.683Z

Shashank-Singh answered Sep 2, '20 Shashank-Singh commented Sep 3, '20

There could be 2 things causing this issue

Permission issue
Due to previous failed installation some components are not removed and hence the issue is coming.

Can you remove the installation from "Add remove program" also remove the SQL Server files and folder. Do not touch registry if installation via add remove program finishes successfully.

Other thing is DO NOT slip stream SP4 just install SQL Server 2012 and let me know. This is strange request but please try it and let me know.

· 2

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MabelTe-0750 · Sep 02, 2020 at 04:40 PM

Reinstall done without touching regedit and also disable firewall

0 ·

Shashank-Singh MabelTe-0750 · Sep 03, 2020 at 06:07 AM

@MabelTe-0750 so did it succeeded, or it failed again ?

0 ·

Answer 4 · 2020-09-02T08:08:14.51Z

AmeliaGu-msft answered Sep 2, '20 MabelTe-0750 commented Sep 2, '20

Hi MabelTe-0750,

Could you please check the detailed error message in the detail.txt?
Please refer to workaround in this article which might help.

Best Regards,
Amelia

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MabelTe-0750 · Sep 02, 2020 at 06:29 PM

I have gone through the article and unfortunately, I don't have detailed "Exception error". My detailed.txt is a very general repeated statements as below. Meanwhile, as there is no instance created, so the logs directory (C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log) is empty

(01) 2020-09-03 00:34:18 Slp: Sco: Attempting to start service MSSQLSERVER
(01) 2020-09-03 00:34:18 Slp: Sco: Attempting to open SC Manager
(01) 2020-09-03 00:34:18 Slp: Sco: Attempting to open service handle for service MSSQLSERVER
(01) 2020-09-03 00:34:18 Slp: Sco: Attempting to close service handle for service MSSQLSERVER
(01) 2020-09-03 00:34:18 Slp: Sco: Attempting to close SC Manager
(01) 2020-09-03 00:34:18 SQLEngine: --SqlServerServiceSCM: Exception generated: The service did not respond to the start or control request in a timely fashion

0 ·

Answer 5 · 2020-09-02T16:44:21.113Z

MabelTe-0750 answered Sep 2, '20

Summary.txt

Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893608
Start time: 2020-09-03 00:27:35
End time: 2020-09-03 00:35:18
Requested action: Install

Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.

Machine Properties:
Machine name: NCS-270720DN02
Machine processor count: 8
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No

Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered

Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: e:\x64\setup\
Installation edition: Standard

Product Update Status:
User selected not to include product updates.

User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD:
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20200903_002611\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID:
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: NCS\P0102881
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: false
UpdateSource: MU
X86: false

Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20200903_002611\ConfigurationFile.ini

Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0018
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024

Feature: SQL Browser
Status: Passed

Feature: SQL Writer
Status: Passed

Feature: SQL Client Connectivity
Status: Passed

Feature: SQL Client Connectivity SDK
Status: Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20200903_002611\SystemConfigurationCheck_Report.htm

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 6 · 2020-09-02T21:03:08.007Z

ErlandSommarskog answered Sep 2, '20 MabelTe-0750 edited Sep 3, '20

" Could not find the Database Engine startup handle."

This means the same thing as the error in the original attempt. But it is more familiar to me. :-)

It means that SQL Server did not start properly when Setup wanted to start SQL Server. There are several possible reasons, although one appears to be more common than others, which will cause some people jump the gun and say "do this!".

But before we do there, we need to see the contents of C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\LOG\ERRORLOG. This file will tell us why SQL Server did not start.

· 2

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MabelTe-0750 · Sep 03, 2020 at 12:09 AM

The folder is empty

0 ·

Shashank-Singh MabelTe-0750 · Sep 03, 2020 at 06:21 AM

The location would be C:\Program Files\Microsoft SQL Server\MSSQL.11\MSSQL\LOG\ERRORLOG . Refer to this link for correct location.

Plus Erland is correct the error means SQL Server was able to install the services but could not bring it online and error is written in the errorlog file. I have blogged about this in this article

1 ·

Answer 7 · 2020-09-03T04:38:31.277Z

MabelTe-0750 answered Sep 3, '20 MabelTe-0750 commented Sep 3, '20

Dear All,
There is no files in the folder: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log

So, I have no ERRORLOG to share for findings.

· 4

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ErlandSommarskog · Sep 03, 2020 at 06:51 AM

You have an ERRORLOG file somewhere. Use Windows Explorer to search for it. The exact path depends on the options you selected when you installed.

I see now that in your first attempt you appeared to already have had SQL 2008 R2 installed and tried to install a named instance MSSQL2012. But in the most recent file, there is on trace of SQL 2008 R2, and you seem to have attempted to install a default instance. Did you uninstaill SQL 2008 R2 inbetween?

1 ·

MabelTe-0750 ErlandSommarskog · Sep 03, 2020 at 10:07 AM

Yes, I uninstall SQL2008 R2. Then delete all related folder to SQL Server.
I did a search of my C:\ & D:\, there is no ERRORLOG....
should i install SQL2008 R2 and then install standard 2012

0 ·

Shashank-Singh MabelTe-0750 · Sep 03, 2020 at 10:20 AM

Since you have deleted it you cannot find it.

0 ·

Show more comments

Answer 8 · 2020-09-03T10:21:14.04Z

MabelTe-0750 answered Sep 3, '20

Hi All,
Following shows I do not have ERRORLOG. I have also search my C and D drive, but could not find any ERRORLOG also. For your kind advise. Thanks

errorlog.png (19.0 KiB)

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 9 · 2020-09-03T13:53:35.377Z

MabelTe-0750 answered Sep 3, '20 MabelTe-0750 commented Sep 3, '20

Hi All, I have start all over again.
Upon installed SQL 2008, MSSQLSERVER instance is created
Next, I installed SQL Standard 2012 and it fails again "Could not find the Database Engine startup handle"

Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893608
Start time: 2020-09-03 21:31:20
End time: 2020-09-03 21:48:54
Requested action: Install

Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.

Machine Properties:
Machine name: NCS-270720DN02
Machine processor count: 8
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No

Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services 1033 Standard Edition 10.50.1600.1 No
SQL Server 2008 R2 Client Tools Connectivity 1033 10.50.1600.1 No

Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: e:\x64\setup\
Installation edition: Standard

Product Update Status:
User selected not to include product updates.

User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD:
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20200903_212833\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, CONN, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQL2012
INSTANCENAME: MSSQL2012
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID:
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: NCS\P0102881
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: false
UpdateSource: MU
X86: false

Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20200903_212833\ConfigurationFile.ini

Detailed results:
Feature: Client Tools Connectivity
Status: Passed

Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0018
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.2100.60&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4024

Feature: SQL Browser
Status: Passed

Feature: SQL Writer
Status: Passed

Feature: SQL Client Connectivity
Status: Passed

Feature: SQL Client Connectivity SDK
Status: Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20200903_212833\SystemConfigurationCheck_Report.htm

· 5

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Shashank-Singh · Sep 03, 2020 at 02:25 PM

Can you go to SQL Server configuration manager 2012 and see if there are new services installed. Or go to services.msc and see if new SQL Server 2-12 instance with name MSSQL2012 is present.

1 ·

MabelTe-0750 Shashank-Singh · Sep 03, 2020 at 02:33 PM

Yes, there is
- SQL Server (MSSQLSERVER) Running (Local System)
- SQL Server (MSSQL2012) not running (Local System)
When I try to start MSSQL2012, it prompt "Window cannot start SQL Server (MSSQL2012) service on Local Computer. Error:1053: The service did snot response to the start or control request in a timely fashion"

0 ·

Shashank-Singh MabelTe-0750 · Sep 03, 2020 at 03:04 PM

@MabelTe-0750 Ok fine, this is expected. Please go to event viewer and see what error message has come. Check for the time when you tried starting SQL Server 2012, at same time look for events related to SQL Server in event viewer applications and system logs. Please post complete details here.

1 ·

Show more comments

MabelTe-0750 Shashank-Singh · Sep 03, 2020 at 02:38 PM

I don't have "SQL Server configuration manager"... I only install Database Enginee Services to avoid the long tedious installation process.... Can I do that?

0 ·

Answer 10 · 2020-09-03T14:01:11.007Z

MabelTe-0750 answered Sep 3, '20 MabelTe-0750 published Sep 3, '20

There is no file in the directory: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQL2012\MSSQL\Log

However there is ERRORLOG under the directory: C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log

2020-09-03 21:25:18.55 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )

2020-09-03 21:25:18.55 Server (c) Microsoft Corporation.
2020-09-03 21:25:18.55 Server All rights reserved.
2020-09-03 21:25:18.55 Server Server process ID is 3928.
2020-09-03 21:25:18.55 Server System Manufacturer: 'HP', System Model: 'HP ProBook 430 G5'.
2020-09-03 21:25:18.55 Server Authentication mode is WINDOWS-ONLY.
2020-09-03 21:25:18.55 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2020-09-03 21:25:18.55 Server This instance of SQL Server last reported using a process ID of 4204 at 9/3/2020 9:24:33 PM (local) 9/3/2020 1:24:33 PM (UTC). This is an informational message only; no user action is required.
2020-09-03 21:25:18.55 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2020-09-03 21:25:18.56 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2020-09-03 21:25:18.56 Server Detected 8 CPUs. This is an informational message; no user action is required.
2020-09-03 21:25:18.77 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2020-09-03 21:25:18.82 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2020-09-03 21:25:18.87 spid6s Starting up database 'master'.
2020-09-03 21:25:18.89 spid6s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2020-09-03 21:25:18.91 spid6s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2020-09-03 21:25:18.94 spid6s SQL Trace ID 1 was started by login "sa".
2020-09-03 21:25:18.94 spid6s Starting up database 'mssqlsystemresource'.
2020-09-03 21:25:18.95 spid6s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2020-09-03 21:25:18.97 spid10s Starting up database 'model'.
2020-09-03 21:25:18.97 spid6s Server name is 'NCS-270720DN02'. This is an informational message only. No user action is required.
2020-09-03 21:25:18.97 spid6s Informational: No full-text supported languages found.
2020-09-03 21:25:18.97 spid6s Starting up database 'msdb'.
2020-09-03 21:25:18.99 spid10s Clearing tempdb database.
2020-09-03 21:25:19.02 spid10s Starting up database 'tempdb'.
2020-09-03 21:25:19.02 Server A self-generated certificate was successfully loaded for encryption.
2020-09-03 21:25:19.03 Server Server is listening on [ 'any' <ipv6> 1433].
2020-09-03 21:25:19.03 Server Server is listening on [ 'any' <ipv4> 1433].
2020-09-03 21:25:19.03 Server Server local connection provider is ready to accept connection on [ \.\pipe\SQLLocal\MSSQLSERVER ].
2020-09-03 21:25:19.03 Server Server local connection provider is ready to accept connection on [ \.\pipe\sql\query ].
2020-09-03 21:25:19.03 Server Server is listening on [ ::1 <ipv6> 1434].
2020-09-03 21:25:19.03 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2020-09-03 21:25:19.03 Server Dedicated admin connection support was established for listening locally on port 1434.
2020-09-03 21:25:19.03 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2020-09-03 21:25:19.03 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2020-09-03 21:25:19.04 spid13s The Service Broker protocol transport is disabled or not configured.
2020-09-03 21:25:19.04 spid13s The Database Mirroring protocol transport is disabled or not configured.
2020-09-03 21:25:19.05 spid13s Service Broker manager has started.
2020-09-03 21:25:19.05 spid6s Recovery is complete. This is an informational message only. No user action is required.
2020-09-03 21:26:29.62 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 63420, committed (KB): 128216, memory utilization: 49%.
2020-09-03 21:32:01.99 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 332 seconds. Working set (KB): 63368, committed (KB): 128144, memory utilization: 49%.
2020-09-03 21:36:33.60 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 603 seconds. Working set (KB): 63396, committed (KB): 128144, memory utilization: 49%.
2020-09-03 21:41:59.66 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 930 seconds. Working set (KB): 63520, committed (KB): 128144, memory utilization: 49%.
2020-09-03 21:46:31.11 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 1201 seconds. Working set (KB): 63232, committed (KB): 128144, memory utilization: 49%.
2020-09-03 21:51:57.39 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 1527 seconds. Working set (KB): 63596, committed (KB): 128144, memory utilization: 49%.
2020-09-03 21:57:29.39 spid1s A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 1859 seconds. Working set (KB): 63624, committed (KB): 128144, memory utilization: 49%.

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

question