Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
-
Friday, September 03, 2010 1:00 AM
Attempting to upgrade from SQL 2005 EE to SQL 2008 EE on Vmware ESX 3.5 virtual server.
below is info from Detail.txt related to successful install with failures...
2010-09-02 13:50:46 Slp: Sco: Attempting to check if file 'D:\Data\MSSQL.1\MSSQL\LOG\ERRORLOG' exists
2010-09-02 13:50:46 Slp: Sco: Returning security descriptor O:BAG:SYD:AI(A;ID;FA;;;S-1-5-21-3788118842-658835432-3441893140-1006)(A;ID;FA;;;S-1-5-21-3788118842-658835432-3441893140-1007)(A;ID;FA;;;BA)(A;ID;FA;;;SY)S:AI(AU;IDFA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)
2010-09-02 13:50:46 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
2010-09-02 13:50:46 Slp: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
2010-09-02 13:50:46 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
2010-09-02 13:50:46 Slp: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
2010-09-02 13:50:46 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql)
2010-09-02 13:50:46 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters)
2010-09-02 13:50:46 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerStartup.StartSQLServerForUpgrade()
2010-09-02 13:50:46 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.UpgradeSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean fShutdown)
2010-09-02 13:50:46 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.Upgrade_ConfigRC(Version fromVersion, EffectiveProperties properties, Boolean shutdownRightAway)
2010-09-02 13:50:46 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.Upgrade(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent, Version fromVersion)
2010-09-02 13:50:46 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.PrivateConfigurationBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
2010-09-02 13:50:46 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SqlFeatureConfigBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent)
2010-09-02 13:50:46 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
2010-09-02 13:50:46 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
2010-09-02 13:50:46 Slp: Exception: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException.
2010-09-02 13:50:46 Slp: Source: Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.
2010-09-02 13:50:46 Slp: Message: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes..
2010-09-02 13:50:47 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100902_133715\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2010-09-02 13:50:47 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100902_133715\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2010-09-02 13:50:47 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100902_133715\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2010-09-02 13:50:51 Slp: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
2010-09-02 13:50:52 Slp: Watson bucket for exception based failure has been created
2010-09-02 14:17:56 Slp: Completed Action: SqlEngineDBStartConfigAction_upgrade_configrc_Cpu32, returned False
2010-09-02 14:17:56 Slp: Sco: Attempting to get instance feature flag UpgradeIncomplete for feature SQL_Engine_Core_Inst, instance MSSQL10.MSSQLSERVER
2010-09-02 14:17:56 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2010-09-02 14:17:56 Slp: Sco: Attempting to open registry subkeyWindows event log shows:
MSSQLSERVER error Event ID: 928
During upgrade, database raised exception 3699, severity 25, state 2, address 029B2122. Use the exception number to determine the cause.
Any ideas?
All Replies
-
Monday, September 06, 2010 9:26 AMModerator
Hi DI38,
Based on my research, this issue might be caused by that sa account is renamed.
In the situation that sa account is renamed, please try the workaround provided in the following links:
http://support.microsoft.com/kb/960781
http://support.microsoft.com/kb/968829
After trying the workaround provided by the above links, if this issue still exists, please feel free to let me know.
Regards,
Tom Li -
Wednesday, October 13, 2010 1:54 PM
Hi ,
I have the same problem while installing it in a cluster windows 2008 cluster .
The instance is new
Any Ideas ?
thanks
-
Wednesday, October 13, 2010 2:12 PMModerator
Hi Stefano_C,
Thanks for your post.
I would like to recommend that you ask it in a new thread and you will get quicker support.
Regards,
Tom Li -
Thursday, October 14, 2010 4:45 AMAnswerer
There are two scenarios.
1 - SQL being upgraded from 2005 - 2008
2 - You install a new sql 2008 or r2 install (incl clustered installs)
The suggestion below is specific to 2nd scenario ONLY -
Your current install is too bad to be repaired. Uninstall and reinstall.
What caused this failure? - I am yet to find out the complete details but the main suspects are
1. Some Hardware issue (check the disk response time).
2. Corrupt install media. Possibly ISO extraction which did not work as expected. [KB coming shortly for this issue]
- Marked As Answer by Vijay SirohiMicrosoft Employee, Editor Friday, October 29, 2010 3:57 AM
-
Friday, October 29, 2010 5:14 AM
I got the same error when I tried to install SQL SERVER2008 R2 on Windows 7 Home premium. I am trying to figure out but did not reach to any conclusion yet. I am not doing upgrade its an install.
This is the error log. Any help?
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2061893608
Exit facility code: 1306
Exit error code: 24
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2010-10-27 22:23:34
End time: 2010-10-27 22:49:09
Requested action: Install
Log with failure: C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20101027_222137\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0xE53883A0%400xBE03358B%401306%4024Machine Properties:
Machine processor count: 4
OS version: Windows 7
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 32 Bit
OS clustered: NoProduct features discovered:
Product Instance Instance ID Feature Language Edition Version ClusteredPackage properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: C:\Downloads\SQL Server 2008 R2 Developer (x86, x64, ia64) - DVD (English)\x86\setup\
Installation edition: DEVELOPERUser Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: C:\Program Files (x86)\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files (x86)\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files (x86)\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files (x86)\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: NT AUTHORITY\SYSTEM
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: Niraj-PC\Niraj
ASTEMPDIR: C:\Program Files (x86)\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20101027_222137\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
UIMODE: Normal
X86: TrueConfiguration file: C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20101027_222137\ConfigurationFile.ini
Detailed results:
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xBE03358B@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20101027_222137\Detail.txtFeature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xBE03358B@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20101027_222137\Detail.txtFeature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xBE03358B@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20101027_222137\Detail.txtFeature: Analysis Services
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xBE03358B@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20101027_222137\Detail.txtFeature: Integration Services
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Client Tools Connectivity
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Client Tools SDK
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Client Tools Backwards Compatibility
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Business Intelligence Development Studio
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: SQL Server Books Online
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Microsoft Sync Framework
Status: Passed
MSI status: Passed
Configuration status: PassedRules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20101027_222137\SystemConfigurationCheck_Report.htm
-
Sunday, October 31, 2010 5:52 PMI find the solution to install it. I restored my PC to factory image and I installed it. I am not sure about the cause of the error but my best guess is I installed SQL Server 2005 before so, some file is not deleted when i uninstall it or it make some changes in regestry that block the instalation of SQL Server 2008 R2.
any comments or suggestion is appriciated. -
Thursday, September 01, 2011 9:23 AMInstead of having to restore your system to a previous version etc... I tried REVO Uninstaller Pro - it has a full version trial and with a few simple clicks, it located ALL of the bits of registry fragments and files left behined that stops the SQL Server Installer from successfully completing.
If Revo can find the crap left behind - I don't understand why Microsoft programmers cant program their software to do a proper uninstall script / or create a warning at the start of a new install module and option of a clean of old fragments etc. Lazy Programming on behalf of Microsoft. -
Saturday, April 14, 2012 9:54 AM
There are two scenarios.
1 - SQL being upgraded from 2005 - 2008
2 - You install a new sql 2008 or r2 install (incl clustered installs)
The suggestion below is specific to 2nd scenario ONLY -
Your current install is too bad to be repaired. Uninstall and reinstall.
What caused this failure? - I am yet to find out the complete details but the main suspects are
1. Some Hardware issue (check the disk response time).
2. Corrupt install media. Possibly ISO extraction which did not work as expected. [KB coming shortly for this issue]
Hi Vijay sir, Puneet here
I am posting my error report here...pls help..its giving me the same error again and again. Just to let you know, i had installed and later uninstalled sql 2005 express edition and currently have vs 2008 professional edition+.net framework 3.5 installed..pls help
Following is the full error log report that i received latest
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068643839
Exit facility code: 1203
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2012-04-14 12:49:49
End time: 2012-04-14 13:22:30
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120414_124745\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xE53883A0%400xBE03358B%401306%4024
Machine Properties:
Machine name: MENKA-PC
Machine processor count: 2
OS version: Windows Vista
OS service pack: Service Pack 2
OS region: India
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
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: E:\x86\setup\
Installation edition: DEVELOPER
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: NT AUTHORITY\SYSTEM
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: menka-PC\menka
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120414_124745\ConfigurationFile.ini
ENABLERANU: False
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
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: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: E:\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: menka-PC\menka
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120414_124745\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xBE03358B@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120414_124745\Detail.txt
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xBE03358B@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120414_124745\Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xBE03358B@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120414_124745\Detail.txt
Feature: Analysis Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0xBE03358B@1306@24
Configuration error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120414_124745\Detail.txt
Feature: Integration Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Books Online
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Passed
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\20120414_124745\SystemConfigurationCheck_Report.htmI have done a majority of diagonistics mentioned in the msdn website but to no avail. When the installation completes it shows errors on Database engine services and also i am unable to start the services manually
puneet

