- Remove From My Forums
-
Вопрос
-
Приветствую участников! Нужна помощь разобраться с ошибкой при установке SQL Server 2012 Express SP1 with Tools появляется «Ошибка при ожидании дескриптора восстановления компонента Database Engine».
Картинка тут s2.ipicture.ru/uploads/20140202/JxT7Obvn.png
Журнал ошибок SQL Server прилагается rghost.ru/52153650
Ранее на данном компьютере уже была установлена и нормально работала эта же версия SQL Server, удалилась корректно вот по этой инструкции technet.microsoft.com/ru-ru/library/ms143412.aspx, конфигурация не менялясь, ошибка возникла
при повторной установке с аналогичными параметрамиБуду весьма признателен за оперативную помощь
-
Изменено
2 февраля 2014 г. 18:41
-
Изменено
Ответы
-
Проблема решена. При настроке установки у служб SQL Server и Агент SQL Сервера выставил системную учетную запись NT AUTHORITYсистема, вместо тех что были по умолчанию. После этого установка прошла без ошибок.
-
Помечено в качестве ответа
dmshush
3 февраля 2014 г. 8:37
-
Помечено в качестве ответа
I m using SQL Server 2012 Developer Edition. Even I tried SQL Server 2012 Express and Enterprise edition but all gave same error. I browsed msdn blog as well as few post on stackoverflow.
But nothing helped me out from this!
Here is the error log details
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
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.
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: CROY-TOSH
Machine processor count: 4
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
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:UsersCRoyDownloadsSQL Server 2012 Developer Edition (x86 and x64) - DVD (English)x64setup
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT ServiceSQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:Program FilesMicrosoft SQL ServerMSAS11.MSSQLSERVEROLAPBackup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:Program FilesMicrosoft SQL ServerMSAS11.MSSQLSERVEROLAPConfig
ASDATADIR: C:Program FilesMicrosoft SQL ServerMSAS11.MSSQLSERVEROLAPData
ASLOGDIR: C:Program FilesMicrosoft SQL ServerMSAS11.MSSQLSERVEROLAPLog
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT ServiceMSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSHCRoy
ASTEMPDIR: C:Program FilesMicrosoft SQL ServerMSAS11.MSSQLSERVEROLAPTemp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:Program Files (x86)Microsoft SQL ServerDReplayClientResultDir
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT ServiceSQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:Program Files (x86)Microsoft SQL ServerDReplayClientWorkingDir
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:Program FilesMicrosoft SQL Server110Setup BootstrapLog20131021_125116ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT ServiceSQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSHCRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT ServiceMSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: C:Program Files (x86)Microsoft SQL Server
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT ServiceMsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT ServiceReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT ServiceMSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSHCRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:Program FilesMicrosoft SQL Server110Setup BootstrapLog20131021_125116ConfigurationFile.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: 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: 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: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
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 FilesMicrosoft SQL Server110Setup BootstrapLog20131021_125116SystemConfigurationCheck_Report.htm
Here is few links
Blog MSDN
StackOverflow1
StackOverflow2
Can someone please guide me on how to overcome the following error. I am trying to install SQL Server 2012 Express on my win7 32bit system. I had SQL Server 2008 R2 32 bit installed in this system, which was removed by the previous user (this is an official system (laptop) I am using).
Here is the log file generated after unsuccessful installation:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893607
Start time: 2013-07-12 15:43:20
End time: 2013-07-12 15:55:46
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: FSLTECYOUBRAJ
Machine processor count: 4
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: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: D:New folderMSI'sExcelSQLEXPRWT_x86_ENUx86setup
Installation edition: Express
Product Update Status:
User selected not to include product updates.
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: true
FEATURES: SQLENGINE
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:Program FilesMicrosoft SQL Server
INSTALLSHAREDWOWDIR: <empty>
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:Program FilesMicrosoft SQL Server
INSTANCEID: SQLEXPRESS2012
INSTANCENAME: SQLEXPRESS2012
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: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT ServiceMSSQL$SQLEXPRESS2012
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CADOMAINyoubarajs
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: false
UpdateSource: MU
X86: false
Configuration file: C:Program FilesMicrosoft SQL Server110Setup BootstrapLog20130712_154108ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
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.2100.60&EvtType=0xE53883A0%400xBE03358B%401306%4025&EvtType=0xE53883A0%400xBE03358B%401306%4025
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:Program FilesMicrosoft SQL Server110Setup BootstrapLog20130712_154108SystemConfigurationCheck_Report.htm
marc_s
729k175 gold badges1327 silver badges1455 bronze badges
asked Jul 12, 2013 at 10:42
Youbaraj SharmaYoubaraj Sharma
1,3053 gold badges17 silver badges34 bronze badges
1
Ok, after 6 hours of struggle and ‘googling’ I could finally get this work. The problem was due to some account name conflict. Here are the steps I followed to set it right
1) Un-installed the SQLserver
3) Re-installed it back with following changes
- In the server configuration section, I changed the account name
details to «NT AUTHORITY/LOCALSERVICE» (during the installation process)
Please remember to set it as «NT AUTHORITY/NETWORKSERVICE» if LOCAL SERVICE is not allowed.
answered Jul 12, 2013 at 16:49
Youbaraj SharmaYoubaraj Sharma
1,3053 gold badges17 silver badges34 bronze badges
4
The problem is with the new account creation after Windows 8.1 Update 1 for me. If you are trying to install on Win8.1.1 try the instructions found here
Basically you need to reset the permissions on the default account. I remember someone having problems with creating new child accounts after this update as well.
answered May 10, 2014 at 11:18
2
Столкнулся с интересной ошибкой при установке 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).
Following can be the reason behind the error message. The process of troubleshooting such errors is mentioned in article Could Not find database engine startup handle error during Installation
-
The account which user selected on Server Configuration page window ( during installation) is somehow not able to bring SQL Server database engine services online. Either is lacks privilege or it is corrupted. During installation of database engine services SQL Server tries to bring online database services as a internal process but due to startup account either corrupt or not having appropriate privileges it fails to do so and ultimately installation fails.
-
Other reason is when installation fails first time due to some reason and user uninstall failed installation from add remove program, the un-installation leaves account in broken state so any further attempt to install flashes this error message.
-
The reason can be also that SQL Server installation was successful in installing SQL Server and its services but due to some other limitation in system or other system related errors SQL Server is not able to come online. The same has been discussed in section ‘Looking at SQL Server errorlog’
Please try below solution
-
Uninstall SQL Server completely from add remove program. Make sure no previous failed installation fragments are present on your system. Please use this link for uninstalling existing instance of SQL Server
-
Start a fresh installation. Locate Setup.exe file in SQL Server installable. It would be something like below. Always Right click on Setup file and select Run As Administrator to launch the setup.
- After launching the setup and providing necessary details you would reach to Server Configuration page as below. When you reach this page
please select startup account for Database Engine services as NT AuthoritySYSTEM
which is also called as Local System account. Please see screenshot
- I hope this will resolve your issue. After installation completes change Service account of SQL Server to some low privileged domain account you can use this link for configuring service account for SQL Server
If above still does not helps can you find SQL Server logs at location
Drive:Program FilesMicrosoft SQL ServerMSSQL.nMSSQLLOGERRORLOG and ERRORLOG.n files.And post the contents in question.
Where Drive is system drive on which you installed SQL Server. It can be system drive C or any user drive (D,E,F…) . MSSQLn here means version number of SQL Server
n=10 for SQL Server 2008/2008 R2
n= 11 for SQL Server 20012
n=12 for SQL Server 2014.
For more details about this issue please read this link
EDIT: IMPORTANT NOTE
Please don’t install SQL Server 2012 with SP1 with slipstream method there was issue in slipstreaming process with SP1 which caused setup to fail. Only install SQL Server 2012 you can uncheck the SP1 setup during installation. The issue was removed with SP2 slip stream
Edit: Following are from logs you provided
Error: 5172, Severity: 16, State: 15. 2014-12-20 22:37:58.01 spid5s
The header for file ‘C:Program FilesMicrosoft SQL
ServerMSSQL11.MSSQLSERVERMSSQLDATAMSDBData.mdf’ is not a valid
database file header. The PageAudit property is incorrect.2014-12-20 22:37:58.25 spid9s Starting up database ‘model’.
2014-12-20 22:37:58.29 spid9s Error: 5172, Severity: 16, State:
15.2014-12-20 22:37:58.29 spid9s The header for file ‘C:Program
FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLDATAmodel.mdf’
is not a valid database file header. The PageAudit property is
incorrect.2014-12-20 22:37:58.39 spid9s ex_raise2: Exception raised,
major=52, minor=43, state=8, severity=22, attempting to create symptom
dump2014-12-20 22:37:58.60 spid9s Using ‘dbghelp.dll’ version ‘4.0.5’
2014-12-20 22:37:58.67 spid9s **Dump thread — spid = 0, EC =
0x0000000276576B902014-12-20 22:37:58.71 spid9s ***Stack Dump being sent to
C:Program FilesMicrosoft SQL
ServerMSSQL11.MSSQLSERVERMSSQLLOGSQLDump0001.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
* BEGIN STACK DUMP: 2014-12-20 22:37:58.71 spid9s * 12/20/14 22:37:58 spid 9
SQL Server is installed but due to corruption in MSDB, Model database it is not able to come online. If model database is not able to come online tempdb wont be created hence SQL Server would not come online. The error is also includes stack dump this is very strange SQL Server is getting installed and detecting corruption in system data files. There might be two possibilities
-
The hardware( the underlying disk) on which master,model and msdb file resides is incorrectly formatted or corrupt. You need to get the Storage verified.
-
This might be bug ( Which I dont believe, actually some external factor is preventing SQL Server from coming online which can be known by analyzing dump )
You have two possible solutions
-
Use this Microsoft BOL document to rebuild system databases. You can also use this documents its more easy to refer because it has screenshots. See if this helps
-
Please contact Microsoft CSS ( Customer support) they are the best person to analyze dump which got generated. The location of dump file is C:Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLLOGSQLDump0001.txt.
Personally I will try to post this dump to one of my MS friend if he is free he might have a look, but dont expect much.