SQL Server Express 2008 SP1 Fails to install as it failed to open registry key
-
Wednesday, May 19, 2010 2:35 PM
Need assistance with troubleshooting a failed install of SQL Server Express 2008 SP1. Why is SQL Server 2008 Express failing to install and what can I do to resolve it?
Is user an admin: Yes, verified
What is the target OS: Windows 7 Enterprise (x86)
User does also have SQL Server Express 2005 installed.
SQL Server Express 2008 install parameters we are using:
/q /hideconsole/action=Install /features=SQL /instancename=<INSTANCENAME> /enableranu=1 /sqlsvcaccount="NT Authority\Network Service" /AddCurrentUserAsSqlAdmin /skiprules=RebootRequiredCheck
Error: Configuration error description: Failed to open the registry key SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.<NAMEDINSTANCE>\MSSQLServer\SuperSocketNetLib or set its security descriptor: Attempted to perform an unauthorized operation..
Full Summary.txt file output:
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: 2010-05-11 17:06:05
End time: 2010-05-11 17:09:38
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100511_170521\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.2531.0%26EvtType%3d0xE32A4906%400x92D13C14Machine Properties:
Machine name: <Machine1>
Machine processor count: 2
OS version: Windows Vista
OS service pack:
OS region: United Kingdom
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: NoProduct features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Sql Server 2005 <NAMEDINSTANCE> MSSQL.1 Database Engine Services 1033 Express Edition 9.3.4053 No
Sql Server 2005 <NAMEDINSTANCE> MSSQL.1 SQL Server Replication 1033 Express Edition 9.3.4053 No
Sql Server 2005 <NAMEDINSTANCE> MSSQL.1 SharedTools 1033 Express Edition 9.3.4053 No
Sql Server 2005 Tools 1033 Express Edition 9.3.4053 No
Sql Server 2005 ToolsClient 1033 Express Edition 9.3.4053 No
Sql Server 2005 ToolsClient\Connectivity 1033 Express Edition 9.3.4053 NoPackage properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
Installation location: c:\e451fe79f162a1df3cea94c603\x86\setup\
Installation edition: EXPRESSSlipstream: True
SP Level 1User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: True
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100511_170521\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: True
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: c:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: <NAMEDINSTANCE>
INSTANCENAME: <NAMEDINSTANCE>
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PCUSOURCE: c:\e451fe79f162a1df3cea94c603\PCUSOURCE
PID: *****
QUIET: True
QUIETSIMPLE: False
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Authority\Network Service
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
X86: FalseConfiguration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100511_170521\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: 0x80656E02@1221@51027
Configuration error description: Failed to open the registry key SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.ADCENTERDESKTOP\MSSQLServer\SuperSocketNetLib or set its security descriptor: Attempted to perform an unauthorized operation..
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100511_170521\Detail.txtFeature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x80656E02@1221@51027
Configuration error description: Failed to open the registry key SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.ADCENTERDESKTOP\MSSQLServer\SuperSocketNetLib or set its security descriptor: Attempted to perform an unauthorized operation..
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100511_170521\Detail.txtRules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100511_170521\SystemConfigurationCheck_Report.htm
All Replies
-
Wednesday, May 19, 2010 2:57 PM
SQL Server Setup team have documented and suggested fix on the following link
Open up the registry and navigate to the registry key with the issue, give the administrator access to the registry key.
- Proposed As Answer by Xiao-Min Tan – MSFTModerator Friday, May 21, 2010 7:43 AM
- Marked As Answer by Xiao-Min Tan – MSFTModerator Thursday, May 27, 2010 9:29 AM

