January 31, 2011 at 3:46 pm
Yep, SQL rarely uninstalls cleanly.
Google around for manual uninstall directions, which basically just involves removing the entire MS SQL Server branches from the registry. Reboot and try the install again.
I've had SQL 2008 fail to install for me many times for no apparent reason, and then work a couple hours later with no changes as well (not even a reboot). I could go on about more bugs I've run into with the 2008 setup, but just take my word for it that it's far from bulletproof.
Actually just for kicks...I remember one bug in 2008 where you enter the domain groups for a cluster install...if you wanted to use the same group in both boxes, you had to type it in the first, then copy and paste it into the second. If you just free-typed it into the second, you got an error every time, regardless of which group you used (and yes, even if it was identical to the first box). Makes you wonder how it passed QA..
January 31, 2011 at 6:38 pm
Perry Whittle (1/31/2011)
Details will be provided in the setup log, it gives you the path and filename to this log on the failure screen
I looked over the Log myself before making this post... All I keep seeing is "Access Denied," I don't see any useful details.
Below are the contents of the Log, I actually had the "Complete" screen from the Install Wizard still up:
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: 2011-01-30 20:36:04
End time: 2011-01-30 21:37:49
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110130_203211\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%3d0x0CE75128%400x5D9A8C61
Machine Properties:
Machine name: HPXP1
Machine processor count: 1
OS version: Windows XP
OS service pack: Service Pack 3
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: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: C:\Documents and Settings\AG\My Documents\Downloads\x86\setup Installation edition: EVAL
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
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\20110130_203211\ConfigurationFile.ini
ENABLERANU: False
ERRORREPORTING: False
FEATURES: SQLENGINE,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS
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: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: C:\Documents and Settings\AG\My Documents\Downloads NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: HPXP1\AG
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\20110130_203211\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Integration Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x5D9A8C61
Configuration error description: Access is denied
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110130_203211\Detail.txt
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x5D9A8C61
Configuration error description: Access is denied
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110130_203211\Detail.txt
Feature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools SDK
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x5D9A8C61
Configuration error description: Access is denied
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110130_203211\Detail.txt
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x5D9A8C61
Configuration error description: Access is denied
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110130_203211\Detail.txt
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
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110130_203211\SystemConfigurationCheck_Report.htm
February 4, 2011 at 9:53 am
Derrick Smith (1/31/2011)
I remember one bug in 2008 where you enter the domain groups for a cluster install...if you wanted to use the same group in both boxes, you had to type it in the first, then copy and paste it into the second. If you just free-typed it into the second, you got an error every time, regardless of which group you used (and yes, even if it was identical to the first box). Makes you wonder how it passed QA..
I too have encountered this, that is why i always slipstream the SP\CU at install time
Vadon
what is in the file
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20110130_203211\Detail.txt
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 3 posts - 31 through 32 (of 32 total)
You must be logged in to reply to this topic. Login to reply