- Remove From My Forums
-
Question
-
I Cannot Install SQL Server 2014 Express on Windows 10, the error msg occurred such as «…cannot start SQLBrowser service…». How to fix it?
Answers
-
Hi Ifray,
Please share with us the Summary.txt log file created by SQL Server setup. The following
articles may help you locate the file on disk:
https://msdn.microsoft.com/en-us/library/ms143702(v=sql.120).aspx (SQL
Server 2014)Meanwhile, let me share with you some information. Windows 10, while SQL Server 2014
requires SP1. For more information, please read the following article:https://support.microsoft.com/en-us/kb/2681562
Please Dont forget to mark as answer and Helpful Post. It helps others to find relevant posts to the same question. Milan Das
-
Proposed as answer by
Sunday, October 30, 2016 11:52 AM
-
Marked as answer by
pituachMVP
Sunday, October 30, 2016 7:54 PM
-
Proposed as answer by
-
Hello,
Please review the installation log file for more details about the issue, they are located in folder
C:Program Files (x86)Microsoft SQL Server120Setup BootstrapLog<Time Stamp>
Olaf Helper
[ Blog] [ Xing] [ MVP]
-
Proposed as answer by
Ed Price — MSFTMicrosoft employee
Sunday, October 30, 2016 11:52 AM -
Marked as answer by
pituachMVP
Sunday, October 30, 2016 7:54 PM
-
Proposed as answer by
- Remove From My Forums
-
Question
-
I Cannot Install SQL Server 2014 Express on Windows 10, the error msg occurred such as «…cannot start SQLBrowser service…». How to fix it?
Answers
-
Hi Ifray,
Please share with us the Summary.txt log file created by SQL Server setup. The following
articles may help you locate the file on disk:
https://msdn.microsoft.com/en-us/library/ms143702(v=sql.120).aspx (SQL
Server 2014)Meanwhile, let me share with you some information. Windows 10, while SQL Server 2014
requires SP1. For more information, please read the following article:https://support.microsoft.com/en-us/kb/2681562
Please Dont forget to mark as answer and Helpful Post. It helps others to find relevant posts to the same question. Milan Das
-
Proposed as answer by
Sunday, October 30, 2016 11:52 AM
-
Marked as answer by
pituachMVP
Sunday, October 30, 2016 7:54 PM
-
Proposed as answer by
-
Hello,
Please review the installation log file for more details about the issue, they are located in folder
C:Program Files (x86)Microsoft SQL Server120Setup BootstrapLog<Time Stamp>
Olaf Helper
[ Blog] [ Xing] [ MVP]
-
Proposed as answer by
Ed Price — MSFTMicrosoft employee
Sunday, October 30, 2016 11:52 AM -
Marked as answer by
pituachMVP
Sunday, October 30, 2016 7:54 PM
-
Proposed as answer by
SQL Server 2008 R2 Service Pack 2 SQL Server 2012 Analysis Services SQL Server 2012 Business Intelligence SQL Server 2012 Developer SQL Server 2012 Enterprise SQL Server 2012 Express SQL Server 2012 Standard SQL Server 2012 Web SQL Server 2012 Enterprise Core SQL Server 2014 Enterprise SQL Server 2014 Developer SQL Server 2014 Standard SQL Server 2014 Express Еще…Меньше
Проблемы
При попытке установить Microsoft SQL Server с помощью InstallShield или загрузочного приложения процесс установки зависает.Примечание.Эта проблема также возникает в Microsoft SQL Server 2012 с пакетом обновления 2 (SP2).
Причина
Это связано с тем, что при запуске программы установки SQL Server Программа InstallShield или загрузочное приложение открывает некоторые обработчики установщика Windows. Таким образом, процесс установки замораживается.
Решение
Эта проблема впервые устранена в следующем накопительном обновлении SQL Server: накопительный пакет обновления 2 для SQL server 2014 SP1, накопительный пакет обновления 9для SQL Server 2014 накопительный пакет обновления 7 для SQL Server 2012 с пакетом обновления 2 (SP2)
Обходное решение
Чтобы обойти эту ошибку, запустите программу установки SQL Server непосредственно с установочного носителя SQL Server, не подключив программу установки в InstallShiled или загрузочное приложение. Для сервера SQL Server 2014 и SQL 2012 Server с пакетом обновления 2 (SP2) и более поздних версий запустите программу установки SQL Server вместе с параметром командной строки SkipInstallerRunCheck , чтобы пропустить проверку дескриптора установщика Windows:Setup.exe /SkipInstallerRunCheck
Статус
Корпорация Майкрософт подтверждает наличие этой проблемы в своих продуктах, которые перечислены в разделе «Применяется к».
Ссылки
В этой статье упомянуты программные продукты независимых производителей. Корпорация Майкрософт не дает никаких гарантий, подразумеваемых и прочих, относительно производительности и надежности этих продуктов.
Нужна дополнительная помощь?
Hi,
I’m trying to install SQL server 2014 Express Adv on a windows 10 laptop. The installation fails repeatedly with multiple errors (contents from log file are included below). I have tried several options based on feedback on the forums, including
disabling firewall, enabling .NET framework 3.5 and WMI in control panel. I have uninstalled completely and re-installed several times. SQL server during installation reports that some modules are missing. I would really
appreciate it, if someone could help me here.
Thanks,
Bhavana
—————————————————————————————————————-
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2147467259
Start time: 2015-12-18 16:42:40
End time: 2015-12-18 16:58:09
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, uninstall this feature, and then run the setup process again.
Next step for Conn: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for BC: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SSMS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for RS: 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 FullText: 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: DESKTOP-8FD87FS
Machine processor count: 2
OS version: Windows 8
OS service pack:
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 Configured
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:UsersbhavaDesktopSQL server 2014 AdvSQLEXPRADV_x86_ENUx86setup
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITYNETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
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:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS, CONN, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL: 3
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT ServiceMSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: <empty>
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITYNetwork Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT ServiceReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT ServiceMSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: DESKTOP-8FD87FSbhava
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20151218_164230ConfigurationFile.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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Common Files
Component error code: 0x80004005
Error description: The specified module could not be found.
Error help link:
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Common Files
Component error code: 0x80004005
Error description: The specified module could not be found.
Feature: Client Tools SDK
Status: Passed
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Common Files
Component error code: 0x80004005
Error description: The specified module could not be found.
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Common Files
Component error code: 0x80004005
Error description: The specified module could not be found.
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, uninstall this feature, and then run the setup process again.
Component name: SQL Server Common Files
Component error code: 0x80004005
Error description: The specified module could not be found.
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 specified module could not be found.
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, 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 specified module could not be found.
Feature: SQL Server Replication
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, 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 specified module could not be found.
Feature: SQL Browser
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Feature: SQL Writer
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:Program FilesMicrosoft SQL Server120Setup BootstrapLog20151218_164230SystemConfigurationCheck_
—————————————————————————————————————————————-
Приветствую. Просьба помочь, уже неделю мучаюсь, никак не могу ничё установить (( Устанавливаю SQL Server как показано в любой инструкции, но по окончании установки выдаёт ошибки.
Не удалось установить:
— Службы компонента Database Engine
— Полнотекстовый и семантический поиск
— Репликация SQL Server
Ну и соотв-но после такой установки ничё не работает, SQL Server не запускается через менеджер.
Ошибки:
1.
2015-08-11 18:58:21.62 Server Microsoft SQL Server 2014 — 12.0.2000.8 (X64)
Feb 20 2014 20:04:26
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.3 <X64> (Build 10240: )
2015-08-11 18:58:21.62 Server UTC adjustment: 7:00
2015-08-11 18:58:21.62 Server (c) Microsoft Corporation.
2015-08-11 18:58:21.62 Server All rights reserved.
2015-08-11 18:58:21.62 Server Server process ID is 9944.
2015-08-11 18:58:21.62 Server System Manufacturer: ‘ASUSTeK COMPUTER INC.’, System Model: ‘X550EP’.
2015-08-11 18:58:21.62 Server Authentication mode is WINDOWS-ONLY.
2015-08-11 18:58:21.62 Server Logging SQL Server messages in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLLogERRORLOG’.
2015-08-11 18:58:21.62 Server The service account is ‘NT ServiceMSSQLSERVER’. This is an informational message; no user action is required.
2015-08-11 18:58:21.62 Server Registry startup parameters:
-d C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLDATAmaster.mdf
-e C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLLogERRORLOG
-l C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLDATAmastlog.ldf
2015-08-11 18:58:21.63 Server Command Line Startup Parameters:
-s «MSSQLSERVER»
-m «SqlSetup»
-T 4022
-T 4010
-T 1905
-T 3701
-T 8015
2015-08-11 18:58:22.69 Server SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-08-11 18:58:22.69 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-08-11 18:58:22.69 Server Detected 5572 MB of RAM. This is an informational message; no user action is required.
2015-08-11 18:58:22.69 Server Using conventional memory in the memory manager.
2015-08-11 18:58:22.73 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2015-08-11 18:58:22.79 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2015-08-11 18:58:22.91 Server Query Store settings initialized with enabled = 1,
2015-08-11 18:58:22.93 Server The maximum number of dedicated administrator connections for this instance is ‘1’
2015-08-11 18:58:22.93 Server This instance of SQL Server last reported using a process ID of 4148 at 10.08.2015 13:34:49 (local) 10.08.2015 6:34:49 (UTC). This is an informational message only; no user action is required.
2015-08-11 18:58:22.95 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.
2015-08-11 18:58:22.96 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.
2015-08-11 18:58:22.96 Server Database Mirroring Transport is disabled in the endpoint configuration.
2015-08-11 18:58:22.96 Server Software Usage Metrics is disabled.
2015-08-11 18:58:22.96 spid8s Warning ******************
2015-08-11 18:58:22.96 spid8s SQL Server started in single-user mode. This an informational message only. No user action is required.
2015-08-11 18:58:22.97 spid8s Starting up database ‘master’.
2015-08-11 18:58:23.10 spid8s The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes. 1024 bytes at offset 347136 in file C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLDATAmastlog.ldf
will be written.
2015-08-11 18:58:23.38 Server CLR version v4.0.30319 loaded.
2015-08-11 18:58:24.84 spid8s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-08-11 18:58:25.03 spid8s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-08-11 18:58:25.89 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:WindowsMicrosoft.NETFramework64v4.0.30319.
2015-08-11 18:58:26.41 spid8s SQL Trace ID 1 was started by login «sa».
2015-08-11 18:58:26.55 spid8s Server name is ‘MYPC’. This is an informational message only. No user action is required.
2015-08-11 18:58:26.92 spid14s Password policy update was successful.
2015-08-11 18:58:27.13 spid14s Error: 17190, Severity: 16, State: 1.
2015-08-11 18:58:27.13 spid14s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2015-08-11 18:58:27.22 spid14s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2015-08-11 18:58:27.43 spid14s Error: 17182, Severity: 16, State: 1.
2015-08-11 18:58:27.43 spid14s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2015-08-11 18:58:27.44 spid14s Error: 17182, Severity: 16, State: 1.
2015-08-11 18:58:27.44 spid14s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2015-08-11 18:58:27.44 spid14s Error: 17826, Severity: 18, State: 3.
2015-08-11 18:58:27.44 spid14s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2015-08-11 18:58:27.46 spid14s Error: 17120, Severity: 16, State: 1.
2015-08-11 18:58:27.46 spid14s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
2.
2015-08-11 18:58:31.02 Server Microsoft SQL Server 2014 — 12.0.2000.8 (X64)
Feb 20 2014 20:04:26
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.3 <X64> (Build 10240: )
2015-08-11 18:58:31.02 Server UTC adjustment: 7:00
2015-08-11 18:58:31.02 Server (c) Microsoft Corporation.
2015-08-11 18:58:31.02 Server All rights reserved.
2015-08-11 18:58:31.02 Server Server process ID is 4544.
2015-08-11 18:58:31.02 Server System Manufacturer: ‘ASUSTeK COMPUTER INC.’, System Model: ‘X550EP’.
2015-08-11 18:58:31.02 Server Authentication mode is WINDOWS-ONLY.
2015-08-11 18:58:31.03 Server Logging SQL Server messages in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLLogERRORLOG’.
2015-08-11 18:58:31.03 Server The service account is ‘NT ServiceMSSQLSERVER’. This is an informational message; no user action is required.
2015-08-11 18:58:31.03 Server Registry startup parameters:
-d C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLDATAmaster.mdf
-e C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLLogERRORLOG
-l C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLDATAmastlog.ldf
2015-08-11 18:58:31.03 Server Command Line Startup Parameters:
-s «MSSQLSERVER»
-m «SqlSetup»
-T 4022
-T 4010
-T 1905
-T 3701
-T 8015
2015-08-11 18:58:31.75 Server SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-08-11 18:58:31.75 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-08-11 18:58:31.75 Server Detected 5572 MB of RAM. This is an informational message; no user action is required.
2015-08-11 18:58:31.75 Server Using conventional memory in the memory manager.
2015-08-11 18:58:31.78 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2015-08-11 18:58:31.83 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2015-08-11 18:58:31.85 Server Query Store settings initialized with enabled = 1,
2015-08-11 18:58:31.87 Server The maximum number of dedicated administrator connections for this instance is ‘1’
2015-08-11 18:58:31.87 Server This instance of SQL Server last reported using a process ID of 9944 at 11.08.2015 18:58:22 (local) 11.08.2015 11:58:22 (UTC). This is an informational message only; no user action is required.
2015-08-11 18:58:31.87 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.
2015-08-11 18:58:31.88 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.
2015-08-11 18:58:31.88 Server Database Mirroring Transport is disabled in the endpoint configuration.
2015-08-11 18:58:31.88 Server Software Usage Metrics is disabled.
2015-08-11 18:58:31.88 spid8s Warning ******************
2015-08-11 18:58:31.89 spid8s SQL Server started in single-user mode. This an informational message only. No user action is required.
2015-08-11 18:58:31.89 spid8s Starting up database ‘master’.
2015-08-11 18:58:31.97 spid8s 6 transactions rolled forward in database ‘master’ (1:0). This is an informational message only. No user action is required.
2015-08-11 18:58:31.99 Server CLR version v4.0.30319 loaded.
2015-08-11 18:58:32.05 spid8s 0 transactions rolled back in database ‘master’ (1:0). This is an informational message only. No user action is required.
2015-08-11 18:58:32.05 spid8s Recovery is writing a checkpoint in database ‘master’ (1). This is an informational message only. No user action is required.
2015-08-11 18:58:32.09 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:WindowsMicrosoft.NETFramework64v4.0.30319.
2015-08-11 18:58:32.27 spid8s Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
2015-08-11 18:58:32.36 spid8s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-08-11 18:58:32.36 spid8s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-08-11 18:58:32.42 spid8s SQL Trace ID 1 was started by login «sa».
2015-08-11 18:58:32.43 spid8s Server name is ‘MYPC’. This is an informational message only. No user action is required.
2015-08-11 18:58:32.44 spid14s Error: 17190, Severity: 16, State: 1.
2015-08-11 18:58:32.44 spid14s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2015-08-11 18:58:32.45 spid14s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2015-08-11 18:58:32.45 spid14s Error: 17182, Severity: 16, State: 1.
2015-08-11 18:58:32.45 spid14s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2015-08-11 18:58:32.45 spid14s Error: 17182, Severity: 16, State: 1.
2015-08-11 18:58:32.45 spid14s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2015-08-11 18:58:32.45 spid14s Error: 17826, Severity: 18, State: 3.
2015-08-11 18:58:32.45 spid14s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2015-08-11 18:58:32.45 spid14s Error: 17120, Severity: 16, State: 1.
2015-08-11 18:58:32.45 spid14s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
3.
2015-08-11 18:58:35.54 Server Microsoft SQL Server 2014 — 12.0.2000.8 (X64)
Feb 20 2014 20:04:26
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.3 <X64> (Build 10240: )
2015-08-11 18:58:35.55 Server UTC adjustment: 7:00
2015-08-11 18:58:35.55 Server (c) Microsoft Corporation.
2015-08-11 18:58:35.55 Server All rights reserved.
2015-08-11 18:58:35.55 Server Server process ID is 6596.
2015-08-11 18:58:35.55 Server System Manufacturer: ‘ASUSTeK COMPUTER INC.’, System Model: ‘X550EP’.
2015-08-11 18:58:35.55 Server Authentication mode is WINDOWS-ONLY.
2015-08-11 18:58:35.55 Server Logging SQL Server messages in file ‘C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLLogERRORLOG’.
2015-08-11 18:58:35.55 Server The service account is ‘NT ServiceMSSQLSERVER’. This is an informational message; no user action is required.
2015-08-11 18:58:35.55 Server Registry startup parameters:
-d C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLDATAmaster.mdf
-e C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLLogERRORLOG
-l C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLDATAmastlog.ldf
2015-08-11 18:58:35.56 Server Command Line Startup Parameters:
-s «MSSQLSERVER»
-m «SqlSetup»
-T 4022
-T 4010
-T 1905
-T 3701
-T 8015
2015-08-11 18:58:37.04 Server SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-08-11 18:58:37.04 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-08-11 18:58:37.04 Server Detected 5572 MB of RAM. This is an informational message; no user action is required.
2015-08-11 18:58:37.04 Server Using conventional memory in the memory manager.
2015-08-11 18:58:37.06 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2015-08-11 18:58:37.12 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2015-08-11 18:58:37.14 Server Query Store settings initialized with enabled = 1,
2015-08-11 18:58:37.15 Server The maximum number of dedicated administrator connections for this instance is ‘1’
2015-08-11 18:58:37.16 Server This instance of SQL Server last reported using a process ID of 4544 at 11.08.2015 18:58:31 (local) 11.08.2015 11:58:31 (UTC). This is an informational message only; no user action is required.
2015-08-11 18:58:37.16 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.
2015-08-11 18:58:37.16 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.
2015-08-11 18:58:37.17 Server Database Mirroring Transport is disabled in the endpoint configuration.
2015-08-11 18:58:37.17 Server Software Usage Metrics is disabled.
2015-08-11 18:58:37.17 spid8s Warning ******************
2015-08-11 18:58:37.17 spid8s SQL Server started in single-user mode. This an informational message only. No user action is required.
2015-08-11 18:58:37.18 spid8s Starting up database ‘master’.
2015-08-11 18:58:37.22 spid8s 1 transactions rolled forward in database ‘master’ (1:0). This is an informational message only. No user action is required.
2015-08-11 18:58:37.23 spid8s 0 transactions rolled back in database ‘master’ (1:0). This is an informational message only. No user action is required.
2015-08-11 18:58:37.27 Server CLR version v4.0.30319 loaded.
2015-08-11 18:58:37.39 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:WindowsMicrosoft.NETFramework64v4.0.30319.
2015-08-11 18:58:37.40 spid8s Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
2015-08-11 18:58:37.51 spid8s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-08-11 18:58:37.53 spid8s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-08-11 18:58:37.58 spid8s SQL Trace ID 1 was started by login «sa».
2015-08-11 18:58:37.61 spid8s Server name is ‘MYPC’. This is an informational message only. No user action is required.
2015-08-11 18:58:37.62 spid14s Error: 17190, Severity: 16, State: 1.
2015-08-11 18:58:37.62 spid14s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2015-08-11 18:58:37.63 spid14s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2015-08-11 18:58:37.63 spid14s Error: 17182, Severity: 16, State: 1.
2015-08-11 18:58:37.63 spid14s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2015-08-11 18:58:37.63 spid14s Error: 17182, Severity: 16, State: 1.
2015-08-11 18:58:37.63 spid14s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2015-08-11 18:58:37.63 spid14s Error: 17826, Severity: 18, State: 3.
2015-08-11 18:58:37.63 spid14s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2015-08-11 18:58:37.63 spid14s Error: 17120, Severity: 16, State: 1.
2015-08-11 18:58:37.63 spid14s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
-
Перемещено
13 августа 2015 г. 6:00
-
Изменен тип
Иван ПродановMicrosoft contingent staff, Moderator
31 августа 2015 г. 6:59
The file really might not be there. Or it might be corrupt. The first thing to try is to get a new copy of the media. Unblock it after the download if required.
https://www.microsoft.com/en-US/download/details.aspx?id=42299
When you run it, it will want a location to extract the files. Put it in a location to which you have full access. The setup dialog will open automatically. If not, run the setup.exe in the top level of the folder you extracted. This might be all that you need.
There is a «Tools» option for «Installed SQL Server features discovery report» that might be of use. If other editions of SQL 2014 are already present, they can be a problem…but not the problem you have yet. (I never install express because it can cause issues installing DEV or STD editions. It might become an upgrade instead of an install.)
The SQL 2019 DEV edition is free and can be found at https://www.microsoft.com/en-us/sql-server/sql-server-downloads. The discovery report in 2019 will be more inclusive (all versions up to 2019).
Check the «C:Program FilesMicrosoft SQL Server120Setup BootstrapLog» to see if there is more info in the log files. The Summary.txt file will be the short version for the last run of setup.exe. Sometimes there will be instructions on what to do (e.g., uninstall and retry).
Also check the Event Logs for messages that might relate to the install.
Sometimes a virus checker can quarantine valid files.
If it really is permissions, then try taking ownership (recursively) of the install media.
There are endless reasons for things to fail. I hope it’s just bad media.
I have taken on a new client and the network/server is a mess. Updates not done since November 2016. No AV or Security Software. Half the computers not joined to domain. Only windows image backup running and 2 other Backup solutions havent run since the server was created despite the client paying $000 for Backup & Storage.
So now you have an idea on the background I am trying to accomplish a couple of ‘obvious’ things so the client sees some value.
3. Install Avast Managed Workplace RMM and AV. The subject of this question.
I have tried to install Avast Managed Workplace Onsite Manger on 2 separate computers. Both failed with the same error related to MS SQL Server 2014 Express.
«Failed to install Microsoft SQL Server 2014 Express. You need to fix the environment and restart the Onsite Manager Installer. If you want to install it manually please make sure to install a named instance — LPIMWOMEXPRESS»
I then tried to install MS SQL Server 2014 Express standalone and also got an error 0x80240438.
I have seen some reference to the installer not being able to find the windows 10 source files.
If anyone can provide some sort of help or advice it would be much appreciated.
Столкнулся с интересной ошибкой при установке MS SQL Server 2014 на новом сервере Windows Server 2012 R2. Установка SQL Server прерывается почти в самом конце с ошибкой «Не найден дескриптор запуска компонента Database Engine» (Could not find the Database Engine startup handle).
В логе установки Summary.txt при этом присутствует ошибка:
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: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Данная ошибка установки MS SQL Server связана с тем, что используются стандартные настройки установки, при котором служба SQL Server запускается под непривилегированной учетной записью NT ServiceMSSQL$V2014. У данной учетной записи может быть недостаточно полномочий для запуска службы SQL Server, поэтому запустить службу невозможно, и установщик завершается с ошибкой «Could not find the Database Engine startup handle». Также эта ошибка может указывать на то, что ранее на компьютере уже пытались установить SQL Server и не очистили файлы и службы, оставшиеся от предыдущей установки.
Чтобы исправить ошибку установки SQL Server:
- Корректно деинсталлируйте все программы, связанные с SQL Server через Панель управления и перезагрузите сервер (проверьте, что не осталось файлов и папок в каталоге C:Program FilesMicrosoft SQL ServerMSSQL12.xxx);
- Запустите чистую установку из дистрибутива SQL Server. На вкладке «Server Configuration» убедитесь, что служба SQL Server Database Engine запускается под учетной записью NT ServiceMSSQLSERVER;
- Измените эту учетную запись на NT AUTHORITYSYSTEM;
- Продолжите установку SQL Server. Ошибка больше не должна появляться.
После окончания установки настоятельно рекомендуем изменить учетную запись, под которой запускается служба SQL Server Database Engine на непривилегированную учетную запись. Эта учетная запись не обязательно должна обладать правами локального администратора сервера (вполне достаточно полномочий внутри SQL Server). Можно использовать аккаунты с правами sysadmin — NT ServiceMSSQLSERVICE или NT ServiceSQLSERVERAGENT. Чтобы изменить учетную запись, под которой работает SQL Server:
- Запустите SQL Server Configuration Manager и перейдите в раздел SQL Server Services;
- Щелкните по SQL Server (MSSQLSERVER), нажмите кнопку Browse и в поле This account укажите учетную запись, под которой нужно запускать службу или используйте управляемую учетную запись — gMSA (Group Managed Service Accounts). Укажите пароль пользователя и сохраните изменения;
- Перезапустите службы SQL Server.
Этот способ поможет вам исправить ошибку «Не найден дескриптор запуска компонента Database Engine» при установке любых версий SQL Server (2016, 2014, 2012 или 2008).