SQL Server 2017 Install Issue - Database not in Configuration Manager - sql-server

I'm attempting to do some UDEMY training on SSIS. The course requires me to create an SQL Server environment.
I have a Windows 10 Home edition 64 bit with 8GB of RAM.
I installed the following...
2017 Visual Studio
2017 SQL Server Management Studio
2017 SQL Server Data Tools
2017 SQL Server
When I go into configuration manager 2017 Configuration Manager the only things I see listed under SQL Server Services are 1 - SQL Server Analysis Services (MSSQLSERVER) and 2 - SQL Server Browser.
Configuration Manager Picture
If I run from the command prompt: "sqlcmd - S MSSQLSERVER" I get this message...
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Named Pipes Provider: Could not open a connection to SQL Server [53]. .
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..
This made me think that the SQL Server database didn't get installed at all so I did some additional checking. Here is all my Microsoft programs in my installed programs list (SQL Server is shown - last line in first picture)...
Installed Programs Picture 1
Installed Programs Picture 2
I then went to see what services were running...
Service Picture
Here is a picture of the errors I received at the end of my installation attempt (appears that the database engine didn't install)...
Install Failures Picture
As an FYI here are some other screenshots from the installation (1 warning and screenshots of some stuff that left at default but know nothing about)...
Firewall Warning Picture
Master Node Warning Picture
Worker Node Warning Picture
Because of the install failure notification related to the Database Engine I ran the installation repair. The repair log is below (21st line makes me think that the database is installed properly).
Any assistance is appreciated. NOTE: I have about zero experience with installing this stuff. I'm not a DBA. I'm an IT guy that uses this stuff after it's all setup.
Thanks!
*******************************************************************
REPAIR LOG...
*******************************************************************
Overall summary:
Final result: Passed
Exit code (Decimal): 0
Start time: 2022-08-01 09:06:58
End time: 2022-08-01 09:16:55
Requested action: Repair
Machine Properties:
Machine name: DESKTOP-6KH4TIA
Machine processor count: 4
OS version: Microsoft Windows 10 Home (10.0.19044)
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 2017 MSSQLSERVER MSAS14.MSSQLSERVER Analysis Services 1033 Developer Edition 14.0.2042.3 No Yes
SQL Server 2017 Client Tools Connectivity 1033 14.0.1000.169 No Yes
SQL Server 2017 Client Tools Backwards Compatibility 1033 14.0.1000.169 No Yes
SQL Server 2017 Client Tools SDK 1033 14.0.1000.169 No Yes
SQL Server 2017 Data Quality Client 1033 Developer Edition 14.0.2042.3 No Yes
SQL Server 2017 Master Data Services 1033 Developer Edition 14.0.2042.3 No Yes
Package properties:
Description: Microsoft SQL Server 2017
ProductName: SQL Server 2017
Type: RTM
Version: 14
SPLevel: 0
Installation location: D:\x64\setup\
Installation edition: Developer
User Input Settings:
ACTION: Repair
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASCONFIGDIR: Config
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASTELSVCACCT: NT Service\SSASTELEMETRY
ASTELSVCPASSWORD: <empty>
ASTELSVCSTARTUPTYPE: Automatic
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20220801_090657\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
ENU: true
EXTSVCACCOUNT: <empty>
EXTSVCPASSWORD: <empty>
FAILOVERCLUSTERGROUP: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTPYTHONLICENSETERMS: false
IACCEPTROPENLICENSETERMS: false
INDICATEPROGRESS: false
INSTANCENAME: MSSQLSERVER
ISMASTERSVCACCOUNT: NT AUTHORITY\Network Service
ISMASTERSVCPASSWORD: <empty>
ISMASTERSVCPORT: 8391
ISMASTERSVCSSLCERTCN: <empty>
ISMASTERSVCSTARTUPTYPE: Automatic
ISMASTERSVCTHUMBPRINT: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
ISTELSVCACCT: <empty>
ISTELSVCPASSWORD: <empty>
ISTELSVCSTARTUPTYPE: 0
ISWORKERSVCACCOUNT: NT AUTHORITY\Network Service
ISWORKERSVCCERT: <empty>
ISWORKERSVCMASTER: <empty>
ISWORKERSVCPASSWORD: <empty>
ISWORKERSVCSTARTUPTYPE: Automatic
MRCACHEDIRECTORY:
QUIET: false
QUIETSIMPLE: false
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
SQLTELSVCACCT: <empty>
SQLTELSVCPASSWORD: <empty>
SQLTELSVCSTARTUPTYPE: 0
SUPPRESSPRIVACYSTATEMENTNOTICE: false
UIMODE: Normal
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20220801_090657\ConfigurationFile.ini
Detailed results:
Feature: Master Data Services
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20220801_090657\SystemConfigurationCheck_Report.htm
The following warnings were encountered while configuring settings on your SQL Server. These resources / settings were missing or invalid so default values were used in recreating the missing resources. Please review to make sure they don’t require further customization for your applications:
The SQL Server Browser service was not found on the system. Setup will configure its startup type to 'Disabled'.
The SQL Server Browser service was not found on the system. Setup will configure its startup type to 'Disabled'.
The SQL Server Browser service was not found on the system. Setup will configure its startup type to 'Disabled'.
*******************************************************************
END REPAIR LOG
*******************************************************************

Related

SQL Server Express 2017 fails install [0x851A001A]

Installing SQL Server has been paining me for hours. I can't get anything to work. I setup a VM with a fresh Windows Server 2016 install and tried to install SQL Server Express. I set the user to Network Service as suggested here. Unfortunately I got a message saying "Wait on the Database Engine recovery handle failed..." The error log suggested error code 0x851A001A (which I had gotten before, hence the user change). I've spent a long time trying to install this on various Virtual Machines and just can't seem to get it. I've attached the install log and the error log from when I tried to run it manually.
Install Log:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2018-01-30 15:15:04
End time: 2018-01-30 15:23:05
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: WIN-FPPL0DQQ892
Machine processor count: 4
OS version: Microsoft Windows Server 2016 Standard (10.0.14393)
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
Package properties:
Description: Microsoft SQL Server 2017
ProductName: SQL Server 2017
Type: RTM
Version: 14
SPLevel: 0
Installation location: C:\SQLServer2017Media\ExpressAdv_ENU\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: TABULAR
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTELSVCACCT: <empty>
ASTELSVCPASSWORD: <empty>
ASTELSVCSTARTUPTYPE: 0
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
EXTSVCACCOUNT: <empty>
EXTSVCPASSWORD: <empty>
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, CONN, BC, SDK, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SQLEXPRESS
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTPYTHONLICENSETERMS: false
IACCEPTROPENLICENSETERMS: false
IACCEPTSQLSERVERLICENSETERMS: true
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: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISMASTERSVCACCOUNT: NT AUTHORITY\Network Service
ISMASTERSVCPASSWORD: <empty>
ISMASTERSVCPORT: 8391
ISMASTERSVCSSLCERTCN: <empty>
ISMASTERSVCSTARTUPTYPE: Automatic
ISMASTERSVCTHUMBPRINT: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
ISTELSVCACCT: <empty>
ISTELSVCPASSWORD: <empty>
ISTELSVCSTARTUPTYPE: 0
ISWORKERSVCACCOUNT: NT AUTHORITY\Network Service
ISWORKERSVCCERT: <empty>
ISWORKERSVCMASTER: <empty>
ISWORKERSVCPASSWORD: <empty>
ISWORKERSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
MRCACHEDIRECTORY:
NPENABLED: 0
PBDMSSVCACCOUNT: <empty>
PBDMSSVCPASSWORD: <empty>
PBDMSSVCSTARTUPTYPE: 0
PBENGSVCACCOUNT: <empty>
PBENGSVCPASSWORD: <empty>
PBENGSVCSTARTUPTYPE: 0
PBPORTRANGE: <empty>
PBSCALEOUT: false
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
SQLSVCINSTANTFILEINIT: false
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: WIN-FPPL0DQQ892\Administrator
SQLTELSVCACCT: NT Service\SQLTELEMETRY$SQLEXPRESS
SQLTELSVCPASSWORD: <empty>
SQLTELSVCSTARTUPTYPE: Automatic
SQLTEMPDBDIR: <empty>
SQLTEMPDBFILECOUNT: 1
SQLTEMPDBFILEGROWTH: 64
SQLTEMPDBFILESIZE: 8
SQLTEMPDBLOGDIR: <empty>
SQLTEMPDBLOGFILEGROWTH: 64
SQLTEMPDBLOGFILESIZE: 8
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SUPPRESSPRIVACYSTATEMENTNOTICE: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20180130_151456\ConfigurationFile.ini
Detailed results:
Feature: Full-Text and Semantic Extractions for Search
Status: Failed
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20180130_151456\SystemConfigurationCheck_Report.htm
Error Log:
2018-01-30 15:31:07.97 Server Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64)
Aug 22 2017 17:04:49
Copyright (C) 2017 Microsoft Corporation
Express Edition (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor)
2018-01-30 15:31:07.97 Server UTC adjustment: -8:00
2018-01-30 15:31:07.97 Server (c) Microsoft Corporation.
2018-01-30 15:31:07.97 Server All rights reserved.
2018-01-30 15:31:07.97 Server Server process ID is 4560.
2018-01-30 15:31:07.97 Server Authentication mode is MIXED.
2018-01-30 15:31:07.97 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2018-01-30 15:31:07.97 Server The service account is 'WORKGROUP\WIN-FPPL0DQQ892$'. This is an informational message; no user action is required.
2018-01-30 15:31:07.97 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2018-01-30 15:31:07.97 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2018-01-30 15:31:07.99 Server SQL Server detected 4 sockets with 1 cores per socket and 1 logical processors per socket, 4 total logical processors; using 1 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2018-01-30 15:31:07.99 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-01-30 15:31:07.99 Server Detected 8127 MB of RAM. This is an informational message; no user action is required.
2018-01-30 15:31:07.99 Server Using conventional memory in the memory manager.
2018-01-30 15:31:08.05 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2018-01-30 15:31:08.11 Server Buffer pool extension is already disabled. No action is necessary.
2018-01-30 15:31:08.19 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2018-01-30 15:31:08.19 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2018-01-30 15:31:08.21 Server This instance of SQL Server last reported using a process ID of 2708 at 1/30/2018 3:30:52 PM (local) 1/30/2018 11:30:52 PM (UTC). This is an informational message only; no user action is required.
2018-01-30 15:31:08.21 Server The maximum number of dedicated administrator connections for this instance is '1'
2018-01-30 15:31:08.22 Server Node configuration: node 0: CPU mask: 0x0000000000000001:0 Active CPU mask: 0x0000000000000001:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-01-30 15:31:08.27 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.
2018-01-30 15:31:08.27 Server In-Memory OLTP initialized on lowend machine.
2018-01-30 15:31:08.30 Server Database Instant File Initialization: disabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2018-01-30 15:31:08.32 Server CLR version v4.0.30319 loaded.
2018-01-30 15:31:08.33 Server Query Store settings initialized with enabled = 1,
2018-01-30 15:31:08.36 Server Software Usage Metrics is disabled.
2018-01-30 15:31:08.77 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2018-01-30 15:31:08.78 spid6s Starting up database 'master'.
2018-01-30 15:31:08.80 spid6s There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\DATA\master.mdf.
Reinstall a SQL server instance. When it asks you to supply an instance name, use something unique that you haven't already used (MSSQLSERVER99.) Make the Instance ID the same.
You must be victim of uninstalling and reinstalling. The network service user is giving you permissions trouble. It happens after uninstalling MSSQL server.
I hit the same issue with the FreeBSD Bhyve VM.
The root cause was in sector size.
Solved the issue by adding this option to the VM config (I'm using vm-bhyve):
disk0_opts="sectorsize=512"
Details are here:
https://forums.freebsd.org/threads/bhyve-guest-winsrv-2012-r2-std-and-mssql-error-installation-could-not-find-the-database-engine-startup-handle.72904/

SQL Server Silent installation get error during installation

I want to install SQL Server Express (preferably 2008 or 2014) silently using Advanced Installer. I followed the instructions in two document created by advanced installer online:
How to Install SQL Server Express and here is a sample *.aip file to show what the settings need to install SQL server Express silently.
My scenarios:
Get error during simple installing:
However, I get this error:
I already test manually SQL Server Express setup.exe on the target system. So the file and target system doesn't have any problems.
I'm trying to setup.exe using ConfigurationFile.ini as following in command line:
This is my ConfigurationFile.ini code:
;SQLSERVER2008 Configuration File
[OPTIONS]
; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will reflect the instance ID of the SQL Server instance.
INSTANCEID="BNSDEV"
; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.
ACTION="Install"
; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, and Tools. The SQL feature will install the database engine, replication, and full-text. The Tools feature will install Management Tools, Books online, Business Intelligence Development Studio, and other shared components.
FEATURES=SQLENGINE,REPLICATION
; Displays the command line parameters usage
HELP="False"
; Specifies that the detailed Setup log should be piped to the console.
INDICATEPROGRESS="False"
; Setup will not display any user interface.
QUIET="False"
; Setup will display progress only without any user interaction.
QUIETSIMPLE="False"
; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.
X86="False"
; Detailed help for command line argument ROLE has not been defined yet.
ROLE="AllFeatures_WithDefaults"
; Detailed help for command line argument ENU has not been defined yet.
ENU="True"
; Parameter that controls the user interface behavior. Valid values are Normal for the full UI, and AutoAdvance for a simplied UI.
UIMODE="Normal"
; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.
ERRORREPORTING="True"
; Specify the root installation directory for native shared components.
INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"
; Specify the installation directory.
INSTANCEDIR="C:\Program Files\Microsoft SQL Server"
; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.
SQMREPORTING="False"
; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services (RS).
INSTANCENAME="BNSDEV"
; Agent account name
AGTSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE"
; Auto-start service after installation.
AGTSVCSTARTUPTYPE="Disabled"
; Startup type for Integration Services.
ISSVCSTARTUPTYPE="Automatic"
; Account for Integration Services: Domain\User or system account.
ISSVCACCOUNT="NT AUTHORITY\NetworkService"
; Controls the service startup type setting after the service has been created.
ASSVCSTARTUPTYPE="Automatic"
; The collation to be used by Analysis Services.
ASCOLLATION="Latin1_General_CI_AS"
; The location for the Analysis Services data files.
ASDATADIR="Data"
; The location for the Analysis Services log files.
ASLOGDIR="Log"
; The location for the Analysis Services backup files.
ASBACKUPDIR="Backup"
; The location for the Analysis Services temporary files.
ASTEMPDIR="Temp"
; The location for the Analysis Services configuration files.
ASCONFIGDIR="Config"
; Specifies whether or not the MSOLAP provider is allowed to run in process.
ASPROVIDERMSOLAP="1"
; A port number used to connect to the SharePoint Central Administration web application.
FARMADMINPORT="0"
; Startup type for the SQL Server service.
SQLSVCSTARTUPTYPE="Automatic"
; Level to enable FILESTREAM feature at (0, 1, 2 or 3).
FILESTREAMLEVEL="0"
; Set to "1" to enable RANU for SQL Server Express.
ENABLERANU="True"
; Specifies a Windows collation or an SQL collation to use for the Database Engine.
SQLCOLLATION="SQL_Latin1_General_CP1_CI_AS"
; Account for SQL Server service: Domain\User or system account.
SQLSVCACCOUNT="NT AUTHORITY\SYSTEM"
; Windows account(s) to provision as SQL Server system administrators.
SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS"
; Provision current user as a Database Engine system administrator for SQL Server 2008 R2 Express.
ADDCURRENTUSERASSQLADMIN="True"
; Specify 0 to disable or 1 to enable the TCP/IP protocol.
TCPENABLED="1"
; Specify 0 to disable or 1 to enable the Named Pipes protocol.
NPENABLED="0"
; Startup type for Browser Service.
BROWSERSVCSTARTUPTYPE="Disabled"
; Specifies which account the report server NT service should execute under. When omitted or when the value is empty string, the default built-in account for the current operating system.
; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
; The domain part of RSSVCACCOUNT is a maximum of 254 characters long.
RSSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE"
; Specifies how the startup mode of the report server NT service. When
; Manual - Service startup is manual mode (default).
; Automatic - Service startup is automatic mode.
; Disabled - Service is disabled
RSSVCSTARTUPTYPE="Automatic"
; Specifies which mode report server is installed in.
; Default value: “FilesOnly”
RSINSTALLMODE="FilesOnlyMode"
I think there must be a problem with PCUSOURCE. because as fig1 I getting an error as The system can not find the file specified and system looking the sqlSupport.msi.
can anyone help me to solve this problem?
Edited
Here is the last summery.txt for installation:
Overall summary:
Final result: User cancelled
Exit code (Decimal): -2068380094
Exit facility code: 1207
Exit error code: 1602
Exit message: User has cancelled.
Start time: 2017-10-30 13:27:09
End time: 2017-10-30 13:43:48
Requested action: Install
Machine Properties:
Machine name: WINDOWS7-PC
Machine processor count: 2
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
Installation location: c:\3366571280411213122d3a8c\x86\setup\
Installation edition: EXPRESS
Slipstream: True
SP Level 2
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: True
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20171030_132528\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: True
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: BNSDEV
INSTANCENAME: BNSDEV
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE: c:\3366571280411213122d3a8c\PCUSOURCE
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: windows7-PC\windows7
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20171030_132528\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20171030_132528\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
Message:
User has cancelled.
Stack:
at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
Edited After #herman asnswer
as #herman answer, I deleted sqlserverExpr.exe from file and folder then deleted action command from Action too. after that, I add sqlserverExpr.exe from prerequisites, then on setup File Tabs configured values as #herman said. But I get Error like this:
this is my configuration on setup file:
I think it will be much easier for you to add SQL Server as a prerequisite into your project, instead of launching it using a custom action. Advanced Installer has predefined prerequisites for SQL Server Express. Just go to << Prerequisites >> view into your setup project and add from there the desired prerequisite into your project. Then delete the current setup.exe from << Files and Folders >> view and the action added in << Custom Actions >> view.
Here are the EXE setups you added in << files and folders >>.
To add your config file just add the prereq as a file from disk and add the config file as additional file to the prereq.
Hope this helped.

SQL Server 2016 Error: 18456, Severity: 14, State: 38

While trying to install SQL server 2016 in my machine I came across following error:
Msg 18456, Severity: 14, State: 38
Please have a look at the log:
2017-10-12 11:24:15.51 Server Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64)
Oct 28 2016 18:17:30
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows 10 Enterprise 6.3 <X64> (Build 15063: )
2017-10-12 11:24:15.54 Server UTC adjustment: 5:30
2017-10-12 11:24:15.54 Server (c) Microsoft Corporation.
2017-10-12 11:24:15.54 Server All rights reserved.
2017-10-12 11:24:15.54 Server Server process ID is 4824.
2017-10-12 11:24:15.54 Server System Manufacturer: 'Dell Inc.', System Model: 'Precision Tower 7810'.
2017-10-12 11:24:15.54 Server Authentication mode is WINDOWS-ONLY.
2017-10-12 11:24:15.54 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2017-10-12 11:24:15.54 Server The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
2017-10-12 11:24:15.55 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL13.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2017-10-12 11:24:15.55 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2017-10-12 11:24:17.64 Server SQL Server detected 2 sockets with 6 cores per socket and 6 logical processors per socket, 12 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2017-10-12 11:24:17.64 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-10-12 11:24:17.65 Server Detected 32692 MB of RAM. This is an informational message; no user action is required.
2017-10-12 11:24:17.66 Server Using conventional memory in the memory manager.
2017-10-12 11:24:18.14 Server Default collation: Latin1_General_CI_AI (us_english 1033)
2017-10-12 11:24:18.78 Server Buffer pool extension is already disabled. No action is necessary.
2017-10-12 11:24:19.62 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2017-10-12 11:24:19.62 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2017-10-12 11:24:20.73 Server The maximum number of dedicated administrator connections for this instance is '1'
2017-10-12 11:24:20.75 Server This instance of SQL Server last reported using a process ID of 2476 at 12-10-2017 11:22:51 (local) 12-10-2017 05:52:51 (UTC). This is an informational message only; no user action is required.
2017-10-12 11:24:20.82 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2017-10-12 11:24:20.95 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.
2017-10-12 11:24:21.05 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2017-10-12 11:24:21.38 Server Query Store settings initialized with enabled = 1,
2017-10-12 11:24:21.82 spid5s Starting up database 'master'.
2017-10-12 11:24:24.04 Server CLR version v4.0.30319 loaded.
2017-10-12 11:24:24.57 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2017-10-12 11:24:24.62 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2017-10-12 11:24:25.29 spid5s SQL Trace ID 1 was started by login "sa".
2017-10-12 11:24:25.38 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2017-10-12 11:24:25.41 spid5s Server name is 'I7724\SQLEXPRESS'. This is an informational message only. No user action is required.
2017-10-12 11:24:25.55 spid5s Starting up database 'msdb'.
2017-10-12 11:24:25.56 spid6s Starting up database 'mssqlsystemresource'.
2017-10-12 11:24:25.63 spid6s The resource database build version is 13.00.4001. This is an informational message only. No user action is required.
2017-10-12 11:24:25.99 spid6s Starting up database 'model'.
2017-10-12 11:24:26.22 spid10s A self-generated certificate was successfully loaded for encryption.
2017-10-12 11:24:26.23 spid10s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2017-10-12 11:24:26.24 Server Software Usage Metrics is disabled.
2017-10-12 11:24:26.24 spid10s Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2017-10-12 11:24:26.26 spid10s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2017-10-12 11:24:26.26 spid10s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2017-10-12 11:24:26.26 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2017-10-12 11:24:26.37 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/I7724.ptcnet.ptc.com:SQLEXPRESS ] for the SQL Server service. Windows return code: 0x200b, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2017-10-12 11:24:26.40 spid6s Polybase feature disabled.
2017-10-12 11:24:26.40 spid6s Clearing tempdb database.
2017-10-12 11:24:27.04 spid6s Starting up database 'tempdb'.
2017-10-12 11:24:27.43 spid18s The Service Broker endpoint is in disabled or stopped state.
2017-10-12 11:24:27.43 spid18s The Database Mirroring endpoint is in disabled or stopped state.
2017-10-12 11:24:27.62 spid18s Service Broker manager has started.
2017-10-12 11:24:27.62 spid5s Recovery is complete. This is an informational message only. No user action is required.
2017-10-12 11:29:41.85 spid51 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2017-10-12 11:29:41.98 spid51 Using 'xplog70.dll' version '2015.130.1601' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2017-10-12 11:49:26.09 Logon Error: 18456, Severity: 14, State: 38.
2017-10-12 11:49:26.09 Logon Login failed for user 'PTCNET\I7724$'. Reason: Failed to open the explicitly specified database 'WM'. [CLIENT: <local machine>]
But When I am trying to install SQL Server 2012 just to verify where could be the possible error, I am getting the below log and in this case I am able to install SQl Server 2012.
2017-10-12 15:31:05.57 Server Microsoft SQL Server 2012 - 11.0.2100.60 (Intel X86)
Feb 10 2012 19:13:17
Copyright (c) Microsoft Corporation
Express Edition on Windows NT 6.2 <X64> (Build 9200: ) (WOW64)
2017-10-12 15:31:05.57 Server (c) Microsoft Corporation.
2017-10-12 15:31:05.57 Server All rights reserved.
2017-10-12 15:31:05.57 Server Server process ID is 9680.
2017-10-12 15:31:05.57 Server System Manufacturer: 'Dell Inc.', System Model: 'Precision Tower 7810'.
2017-10-12 15:31:05.57 Server Authentication mode is WINDOWS-ONLY.
2017-10-12 15:31:05.57 Server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2017-10-12 15:31:05.57 Server The service account is 'PTCNET\I7724$'. This is an informational message; no user action is required.
2017-10-12 15:31:05.57 Server Registry startup parameters:
-d C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\master.mdf
-e C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2017-10-12 15:31:05.57 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2017-10-12 15:31:05.84 Server SQL Server detected 2 sockets with 6 cores per socket and 6 logical processors per socket, 12 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2017-10-12 15:31:05.84 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-10-12 15:31:05.84 Server Detected 32692 MB of RAM. This is an informational message; no user action is required.
2017-10-12 15:31:05.84 Server Using conventional memory in the memory manager.
2017-10-12 15:31:05.96 Server This instance of SQL Server last reported using a process ID of 8320 at 10/12/2017 3:31:02 PM (local) 10/12/2017 10:01:02 AM (UTC). This is an informational message only; no user action is required.
2017-10-12 15:31:05.96 Server Node configuration: node 0: CPU mask: 0x0000000f:0 Active CPU mask: 0x0000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2017-10-12 15:31:05.97 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.
2017-10-12 15:31:05.99 Server Software Usage Metrics is disabled.
2017-10-12 15:31:06.00 spid4s Starting up database 'master'.
2017-10-12 15:31:06.07 Server CLR version v4.0.30319 loaded.
2017-10-12 15:31:06.18 spid4s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2017-10-12 15:31:06.18 spid4s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2017-10-12 15:31:06.19 spid4s SQL Trace ID 1 was started by login "sa".
2017-10-12 15:31:06.20 spid4s Server name is 'I7724\SQLEXPRESS'. This is an informational message only. No user action is required.
2017-10-12 15:31:06.21 spid4s Failed to verify Authenticode signature on DLL 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Binn\ftimport.dll'.
2017-10-12 15:31:06.21 spid9s Starting up database 'mssqlsystemresource'.
2017-10-12 15:31:06.21 spid4s Starting up database 'msdb'.
2017-10-12 15:31:06.23 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework\v4.0.30319\.
2017-10-12 15:31:06.27 spid9s The resource database build version is 11.00.2100. This is an informational message only. No user action is required.
2017-10-12 15:31:06.36 spid12s A self-generated certificate was successfully loaded for encryption.
2017-10-12 15:31:06.36 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2017-10-12 15:31:06.36 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2017-10-12 15:31:06.36 spid12s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2017-10-12 15:31:06.36 spid12s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2017-10-12 15:31:06.36 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2017-10-12 15:31:06.38 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/I7724.ptcnet.ptc.com:SQLEXPRESS ] for the SQL Server service. Windows return code: 0x200b, state: 15. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2017-10-12 15:31:06.46 spid9s Starting up database 'model'.
2017-10-12 15:31:06.59 spid9s Clearing tempdb database.
2017-10-12 15:31:06.84 spid9s Starting up database 'tempdb'.
One thing which I observed is the difference in Service account name which is "PTCNET\I7724$" for SQL server 2012 whereas for SQL Server 2016 it is "NT Service\MSSQL$SQLEXPRESS".
Not sure if this is the reason for that and from where it is picking the different Service name. Any input will be highly appreciated.

Sql server (Service) doesn't start

I removed old sql server from PC. Then I installed new sql server. After this sql server service doesn't start. When I am running service from sql server config manager - I receive error msg:
"The request failed or the service did not respond in a timely
fashion. Consult the event log or other applicable error logs for
details."
this command: sqlservr.exe -s MSSQL -e C:\1.txt returned logs:
2017-05-09 18:32:55.05 Server Microsoft SQL Server 2016 (RTM) - 13.0.1601.5 (X64)
Apr 29 2016 23:23:58
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows 10 Enterprise 6.3 <X64> (Build 10586: )
2017-05-09 18:32:55.05 Server UTC adjustment: 3:00
2017-05-09 18:32:55.05 Server (c) Microsoft Corporation.
2017-05-09 18:32:55.05 Server All rights reserved.
2017-05-09 18:32:55.05 Server Server process ID is 7956.
2017-05-09 18:32:55.05 Server System Manufacturer: 'ASUSTeK COMPUTER INC.', System Model: 'X550JX'.
2017-05-09 18:32:55.06 Server Authentication mode is WINDOWS-ONLY.
2017-05-09 18:32:55.06 Server Logging SQL Server messages in file 'C:\1.txt'.
2017-05-09 18:32:55.06 Server The service account is 'USER-PC\User'. This is an informational message; no user action is required.
2017-05-09 18:32:55.06 Server Command Line Startup Parameters:
-s "MSSQL"
-e "C:\1.txt"
2017-05-09 18:32:55.06 Server Error: 17113, Severity: 16, State: 1.
2017-05-09 18:32:55.06 Server Error 3(The system cannot find the path specified.) occurred while opening file 'master.mdf' to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
2017-05-09 18:32:55.07 Server SQL Server shutdown has been initiated
I tried to add permissions for windows user, local system and local service but it didn't help.
The error log gives you the information about the failure: Error 3(The system cannot find the path specified.) occurred while opening file 'master.mdf' to obtain configuration information at startup. An invalid startup option might have caused the error.
You should check your startup parameters.
Start Configuration Manager -> SQL Server Services -> your instance -> Properties -> Advanced -> Startup Parameters.
It should contain paths to master.mdf, mastlog.ldf and errorlog

SQL Server 2014 installation fails: An error occurred for a dependency of the feature causing the setup process for the feature to fail

I'm trying to install SQL Server 2014 Enterprise x64 on a 64-bit machine running Windows 7 SP1. I'm trying to install side-by-side with a SQL Server 2008 R2 installation.
I work through the Setup Wizard with everything looking fine except for a warning about the firewall (which I think I can't resolve until after installation). At the appropriate step, I give the new installation a different name (MSSQLSERVER2014) than the existing MSSQLSERVER.
When I finally start it running, it fails. To be specific, everything fails except for the Data Quality Client and the Documentation.
Here's the log that's created (with personal details removed):
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068643839
Start time: 2014-12-15 11:50:31
End time: 2014-12-15 11:54:42
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for Conn: Use the following information to resolve the error, and then try the setup process again.
Next step for BC: Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for RS: Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for DQ: Use the following information to resolve the error, and then try the setup process again.
Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
Next step for AS: Use the following information to resolve the error, and then try the setup process again.
Next step for SNAC_SDK: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: XXXXXXXX
Machine processor count: 8
OS version: Windows 7
OS service pack: Service Pack 1
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 Enterprise Edition 10.51.2550.0 No Yes
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER SQL Server Replication 1033 Enterprise Edition 10.51.2550.0 No Yes
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033 Enterprise Edition 10.51.2500.0 No Yes
SQL Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER Analysis Services 1033 Enterprise Edition 10.51.2500.0 No Yes
SQL Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER Reporting Services - Native 1033 Enterprise Edition 10.51.2550.0 No Yes
SQL Server 2008 R2 Management Tools - Basic 1033 Enterprise Edition 10.51.2550.0 No Yes
SQL Server 2008 R2 Management Tools - Complete 1033 Enterprise Edition 10.51.2500.0 No Yes
SQL Server 2008 R2 Client Tools Connectivity 1033 Enterprise Edition 10.51.2500.0 No Yes
SQL Server 2008 R2 Client Tools Backwards Compatibility 1033 Enterprise Edition 10.51.2500.0 No Yes
SQL Server 2008 R2 Client Tools SDK 1033 Enterprise Edition 10.51.2500.0 No Yes
SQL Server 2008 R2 Integration Services 1033 Enterprise Edition 10.51.2550.0 No Yes
SQL Server 2014 Data Quality Client 1033 Enterprise Edition 12.0.2000.8 No Yes
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: F:\English\SQLServer2014\EnterpriseEdition\x64\setup\
Installation edition: Enterprise
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$MSSQLSERVER2014
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER2014\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER2014\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER2014\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER2014\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSOLAP$MSSQLSERVER2014
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: XXXXXXXX\xxxxxx
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER2014\OLAP\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\120\Setup Bootstrap\Log\20141215_115030\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, FULLTEXT, DQ, AS, RS, CONN, BC, SSMS, ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$MSSQLSERVER2014
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: D:\SQLData
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER2014
INSTANCENAME: MSSQLSERVER2014
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: NT Service\ReportServer$MSSQLSERVER2014
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$MSSQLSERVER2014
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: XXXXXXXX\xxxxxx
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141215_115030\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Analysis Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Client Connectivity SDK
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, and then try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20141215_115030\SystemConfigurationCheck_Report.htm
Solved my own problem with some more searching. The short version of the solution is that I needed to uninstall the SQL Server 2012 Native Client before doing this installation. (Not sure how that got installed on my machine; best guess is some Windows update.)
The resources that led me to the solution were:
https://social.msdn.microsoft.com/Forums/en-US/889167a7-1e51-4911-87fd-f1ed183fb839/failed-installation-of-sql-server-2014?forum=sqlsetupandupgrade - which led me to the details.txt file telling me exactly what failed.
https://connect.microsoft.com/SQLServer/feedback/details/769695/install-fail-sql-server-2012-developer-edition-an-error-occurred-for-a-dependency-of-the-feature
https://dba.stackexchange.com/questions/24563/not-able-to-install-any-piece-of-sql-server-2012-dev-edition-on-my-windows-7/25832#25832
Well, this is going to sound a little crazy, but if you are installing from a mounted ISO, extracting the ISO out to disk, as recommended on this Error Installing SQL Server 2012 Management Tools MSDN thread, cleared up the error for me. I used 7-Zip to extract it (the thread suggests that it won't work if you use WinZIP to extract it).

Resources