kne*_*els 7 sql-server sql-server-2012
我正在一台新的 Windows 8.1 机器上安装 SQL Server 2012 SP1。
在安装过程中,我收到此错误:(类似于此问题的屏幕截图)
标题:Microsoft SQL Server 2012 Service Pack 1 安装程序
发生了以下错误:
等待数据库引擎恢复句柄失败。检查 SQL Server 错误日志以了解潜在原因。
如需帮助,请单击:http : //go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%2625405BA100000000000000000
当我单击“确定”时 - 它会继续安装,但不会实际安装数据库引擎服务、报告服务 - 本机、数据质量服务或全文和语义提取。其余部分被勾选为绿色。
我尝试了各种解决方案(例如在配置管理器中使用 SQL Server 下的“登录身份”选项;关闭防火墙等),但还没有任何效果。您的帮助表示赞赏。
完整日志如下:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2014-12-17 00:10:05
End time: 2014-12-17 00:44:12
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
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 DQ: 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.
Machine Properties:
Machine name: [COMPUTER]
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United Kingdom)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: E:\x64\setup\
Installation edition: Enterprise
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x64
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x64
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Hebrew_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: [COMPUTER]\[USER]
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\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\110\Setup Bootstrap\Log\20141217_000419\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, FULLTEXT, DQ, AS, RS, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: 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: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer110
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
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Hebrew_CI_AS
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: [COMPUTER]\[USER]
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20141217_000419\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
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 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: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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, 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: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
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: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20141217_000419\SystemConfigurationCheck_Report.htm
Run Code Online (Sandbox Code Playgroud)
编辑:安装日志位于此处:
https://www.dropbox.com/sh/11a5xp4v414qe67/AABBrQVgD5LzUpKQTp3kYN9sa?dl=0
以下可能是错误消息背后的原因。在安装过程中找不到数据库引擎启动句柄错误一文中提到了排除此类错误的过程
用户在服务器配置页面窗口(安装期间)上选择的帐户不知何故无法使 SQL Server 数据库引擎服务联机。要么缺少特权,要么已损坏。在安装数据库引擎服务期间,SQL Server 尝试将联机数据库服务作为内部进程,但由于启动帐户损坏或没有适当的权限,它无法这样做,最终安装失败。
另一个原因是当由于某种原因第一次安装失败并且用户从添加删除程序中卸载失败的安装时,卸载会使帐户处于损坏状态,因此任何进一步的安装尝试都会闪烁此错误消息。
原因也可能是 SQL Server 安装成功安装了 SQL Server 及其服务,但由于系统中的某些其他限制或其他系统相关错误,SQL Server 无法联机。在“查看 SQL Server 错误日志”一节中讨论了相同的内容
请尝试以下解决方案
从添加删除程序中完全卸载 SQL Server。确保您的系统上不存在以前失败的安装片段。请使用此链接卸载 SQL Server 的现有实例
开始全新安装。在可安装的 SQL Server 中找到 Setup.exe 文件。它会像下面这样。始终右键单击安装文件并选择以管理员身份运行以启动安装程序。
please select startup account for Database Engine services as NT Authority\SYSTEM
,该页面也称为本地系统帐户。请看截图如果以上仍然没有帮助,您能否在该位置找到 SQL Server 日志
驱动器:\Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG 和 ERRORLOG.n 文件。并发布有问题的内容。
其中 Drive 是安装 SQL Server 的系统驱动器。它可以是系统驱动器 C 或任何用户驱动器 (D,E,F...)。MSSQLn 在这里是指 SQL Server 的版本号
对于 SQL Server 2008/2008 R2,n=10
对于 SQL Server 20012,n= 11
对于 SQL Server 2014,n=12。
有关此问题的更多详细信息,请阅读此链接
编辑:重要说明
请不要使用滑流方法安装带有 SP1 的 SQL Server 2012 SP1 的滑流过程中存在问题,导致安装失败。仅安装 SQL Server 2012,您可以在安装过程中取消选中 SP1 设置。该问题已通过 SP2 滑流消除
编辑:以下来自您提供的日志
错误:5172,严重性:16,状态:15。2014-12-20 22:37:58.01 spid5s
文件“C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\MSDBData.mdf”的标头不是有效的数据库文件头。PageAudit 属性不正确。2014-12-20 22:37:58.25 spid9s 启动数据库“模型”。
2014-12-20 22:37:58.29 spid9s 错误:5172,严重性:16,状态:15。
2014-12-20 22:37:58.29 spid9s 文件“C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\model.mdf”的标头不是有效的数据库文件标头。PageAudit 属性不正确。
2014-12-20 22:37:58.39 spid9s ex_raise2:引发异常,主要 = 52,次要 = 43,状态 = 8,严重性 = 22,试图创建症状转储
2014-12-20 22:37:58.60 spid9s 使用“dbghelp.dll”版本“4.0.5”
2014-12-20 22:37:58.67 spid9s **转储线程 - spid = 0,EC = 0x0000000276576B90
2014-12-20 22:37:58.71 spid9s ***堆栈转储被发送到 C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\LOG\SQLDump0001.txt 2014-12-20 22:37:58.71 spid9s * **************************************************** ******************************** 2014-12-20 22:37:58.71 spid9s * 2014-12-20 22: 37:58.71 spid9s
* 开始堆栈转储:2014-12-20 22:37:58.71 spid9s * 12/20/14 22:37:58 spid 9
SQL Server 已安装,但由于 MSDB 损坏,模型数据库无法上线。如果模型数据库无法联机,则不会创建 tempdb,因此 SQL Server 不会联机。该错误还包括堆栈转储,这是非常奇怪的 SQL Server 正在安装并检测系统数据文件中的损坏。可能有两种可能
master、model 和 msdb 文件所在的硬件(底层磁盘)格式不正确或已损坏。您需要验证存储。
这可能是错误(我不相信,实际上某些外部因素正在阻止 SQL Server 上线,这可以通过分析转储来了解)
您有两种可能的解决方案
使用此Microsoft BOL 文档重建系统数据库。你也可以使用这个文档,因为它有截图,所以更容易参考。看看这是否有帮助
请联系 Microsoft CSS(客户支持),他们是分析生成的转储的最佳人选。转储文件的位置是 C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\LOG\SQLDump0001.txt。
就个人而言,我会尝试将此转储发布给我的一位 MS 朋友,如果他有空,他可能会看看,但不要期望太多。
归档时间: |
|
查看次数: |
88625 次 |
最近记录: |