Backup Failed in SQL server 2008

Backup is failing for only one database on the server.
Msg 3201, Level 16, State 1, Line 1
Cannot open backup device 'F:\databasename_backup_2014_07_29.bak'.
Operating system error 5(failed to retrieve text for this error. Reason: 15105).
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
** SAME DATABASE BACKUP IS COMPLETED SUCCESSFULLY ON OTHER DRIVE **
we have tried the below steps but still it is failed.
Microsoft SQL Server 2008 R2 (SP2) - 10.50.3720.0 (X64) Apr 27 2012 13:51:37 Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
1.checked for any spaces is th database name --No space
2.added service account to administrator .
3.provided full access to backup folder.
4.Compatibilty is 80 .
5.created backup devide to same location and tried still it got failed.
10 percent processed.
20 percent processed.
30 percent processed.
40 percent processed.
50 percent processed.
60 percent processed.
70 percent processed.
Msg 3202, Level 16, State 1, Line 1
Write on "F:\Data\Backup\New_Backup_databasename.bak" failed: 665(failed to retrieve text for this error. Reason: 15105)
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
6.Changed the database ower to service account,NO luck

Hi,
How big is database ? Does F drive has enough space on it. Issue does not seems with SQL Server backup it is with F drive or network connecting Server to drives.
Can you give more information about F drive is it a SAN, Local disk ?
If SQL server backup would have been issue it would have not processed uptill 70 % ( unles its bug). First error message with OS error 5 means access denied. Ater then you gave necessary rights and now backup issue is not due to SQL Server but while writing
to F drive some unusual thing is happeing which is causing backup to fail.Can you also involve SAN team as well.
** SAME DATABASE BACKUP IS COMPLETED SUCCESSFULLY ON OTHER DRIVE **
Does this mean backup of same database completes successfully on other drive if so it is a SAN issue or connection issue between SAN and server
Is SQL server 2008 updated to latest service pack ? Why do you use 80 compatibility mode. Although these questions are not realted to backup
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Similar Messages

Cannot open database " " requested by the login. The login failed. SQL Server 2008 Express

I am getting this message when I try to create a path to a work file from my application.
Cannot open database " " requested by the login. The login failed.
SQL Server 2008 is installed. I have placed the computer name and instance in the application's config file as connection source.
The database is also not showing up in SQl Server Management Studio in list of databases.
Thanks.

Hello,
Can you please confirm login exist in the sql server and its mapped to particular database.
Are you directly connecting to SSMS?
Or using any 4 part query?
Please share how you are accessing the DB and screen hots of error messages.
Thank You.
Regards, Pradyothana DP. Please Mark This As Answer if it solved your issue. Please Mark This As Helpful if it helps to solve your issue. ========================================================== http://www.dbainhouse.blogspot.in/

Backup Restore With SQL Server 2008 R2 although it succeeded with SQL Server 2008

Dears;
I have a Full backup of some DB of around 417 GB within SQL Server 2008 R2 , and when I tried to restore it , i get stuck several times with the error below :
Restore failed for Server (Microsoft.SqlServer.SmoExtended)
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider
running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical
Although I have restored
successfully other several Full+ Deferential backups for the same DB while it was in SQL Server 2008 not 2008 R2.
And so I have rounded all different possible assumptions for such common know error by Microsoft for SQL Server 2000, 2005, 2008 but
no way as next:
1-
I have attempted to restore it within 2 environments clustered and non-clustered of SQL Server 2008 R2.
2-
I have attempted to restore verify it and it was so fine .
3-
I have attempted to restore it using Continue_after_error ,no_checksum but no way.
4-
I have attempted to move Backup file to another Storage but no way.
5-
I have scheduled jobs to DBCC
Checkdb the live DB and it wasn’t any errors since long time right now
6-
I have also DBCC check all master +msdb+model+Tempdb ,and they are so fine
7-
I have also checked all I/O subsystem of SAN and Network controllers , but they are fine evidenced much more by my trial on 2 different environments.
8-
I have also checked Memory and it is so fine all the time since I have 128 GB memory and I control it also so well.
For DB Design +Structure :
It has 20 Files containing tables partitioned horizontal +Vertically
(Schema Partitioning +File Stream partitioning ) through these 20 files.
I have Data compression of the required tables only.
I have one table of more than 300 GB alone which is partitioned as mentioned above.
I have implemented Read Committed Snapshot isolation level using row versioning integrated so well with File stream technology since it is a new feature of SQL 2008 R2.
DB is in simple recovery model for garbage collection of all file stream data as a result of much Delete /update in images themselves.
So any one has any idea about such case..How to solve it…?

Hi Ashwin,
When i searched with no answers these are listed out. So i thought this is still existing. Now on wards let me check the data and time of latest reply. Thanks for guidance.
It was happening by oversight. Thanks for guidance.
Regards, Pradyothana DP. Please Mark This As Answer if it solved your issue. Please Mark This As Helpful if it helps to solve your issue. ========================================================== http://www.dbainhouse.blogspot.in/

Upgrating SQL Server 2008 R2 SP2 to SQL Server 2014 Standard "UpgradeFeatureSpecificRules: KJRTMUpgradeBlockRule"

I've been searching for HOURS how to resolve this issue:
I am trying to upgrade SQL Server 2008 R2 (Express Edition with advanced services) to SQL SERVER 2014 Standard edition, my first issue was to update the 2008 R2 to Service pack 2 on the first FEATURE RULE TEST, at this time on it's keep saying this:
======================================================================================
Rule Check Result
Rule "SQL Server 2008 R2 Service pack 2 or later is requered for upgrade.: failed.
This SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the require service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or lager to the selected instance and the shared features.
=====================================================================================
This is the Configuration Report issue:
Microsoft SQL Server 2014 - System Configuration Check Report
UpgradeFeatureSpecificRules: SQL Server 2014 Setup configuration checks for rules group 'UpgradeFeatureSpecificRules'
KJRTMUpgradeBlockRule
Checks if the currently selected SQL Server 2008 R2 features to upgrade are at the supported service pack. Failed The SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the
required service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or later to the selected instance and the shared features.
====================================================================================
I try after hours and finally did install the Upgrade Advisor and got not issues, the last choice I was to uninstall the Management Studio because in other upgrade express versions got blocked, but in this new version of SQL Server 2014 I don't see any way
out!!!
Thanks.

Hi again
This is the scenario:
-I have installed the SQL SERVER 2008 R2 With Advanced services (version 10.50.1600.1), and now my guest decide to upgrade to an STARNDARD version which nowadays Microsoft is offering the 2014 version.
-As all IT Support and DBA I try to upgrade to SQL 2014 to check and see with requirements were missing or updates. The first check report only ask to upgrade to SQL SERVER 2008 R2 SP2 (version 10.51.2500.0) which I found in the optional update list and
resolved immediately with the Windows Update service.
-Finally, I realise doing the discovery report (suggested in the last post) is that Windows update only download the service pack 2 for SQL Server 2008 instead of the 2008 R2 (I downloaded manually) then the version was upgrade to 10.52.4000.0
Next time I might download the updates manually and not loosing a lot hours with Windows Update, another point very important is that when SQL Server 2008 R2 is installed, create the Microsoft SQL Server 2008 folder at all programas in the Startup menu:
with the SQL Server Installation Center, but there is not one R2, when you execute this one just show the 2008 installed features.
Now we are on 12.0.2000.8
Thanks anyway and all of you for your interest!!!

SQL Server 2008 R2 Backup jobs are failing

I have a problem with SQL Server 2008 R2. First the management studio package is failing to load. backup jobs on that server are failing to run. The server won't accept any installation. The Installation of .Net Framework failed, the Installation of SQL
server 2008 R2 SP2 also failed, Trying to repair SQL Server through the CD also failed. Actually the server cannot install anything on it. When you try to initiate the installation it comes back and say check online for solution or close the program.
I am desperate here as I cannot backup

When you try to initiate the installation it comes back and say check online for solution or close the program.
Are you sure this is the error, I updated SP2 last week and I got the same message but if I remember correctly there was a continue button as well. Could you post the errors.
SP2 not installing, .net framework not installing, ssms not loading up and backups not running all could be due to different issues. Consider these as different and post error message that you are receiving for the issue which is most important for you.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Setting Expiration period for Maintenance Plan Backups fails to work in sql server 2008

I have created a Maintenance Plan to do a nightly full backup and set the backup
set to expire after 4 days in sql server 2008 R2.
Weeks later, old backups are sitting on the hard drive.Please do the needful.

I have created a Maintenance Plan to do a nightly full backup and set the backup
set to expire after 4 days in sql server 2008 R2.
Weeks later, old backups are sitting on the hard drive.Please do the needful.
Can any one please explain what is the use of BACKUP Expiration ???
I created a backup with expiration date but still am using the same backup file to restore databases?? Then what is the use of Expiration date?

SQL Server 2008 Express Installation fails.

I am trying to install SQL server 2008 Express edition on my desktop (OS: Win 7 HP - 64 bit). I have been unable to do so on all of my 3 attempts.
The installation gets to the end and then gives a error with an installation failed message.
Here is the installation summary - Installation Summary
Here is the core DB Engine Install Log - DB Engine Install Log this log is copied from the location referenced in the summary document.
System Config Check Report - Sys Config Check Report
Any and all help is welcome. Let me know if I can provide any additional information.
I already have MySQL 5.5 installed on the same machine - would that be a problem and conflict with the MS SQL installation.
Abhi Oommen

Hello,
Please try to uninstall all SQL Server components using Control Panel -> Add/Remove Programs.
If you have already uninstalled SQL Server before trying to reinstall, please perform the following steps to manually uninstall SQL Server:
1. Uninstall all SQL Server components you can using Control Panel -> Programs and Features
2. Backup the registry.
3. Delete the following keys in regedit:
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server.
5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
6. Rename all the SQL Server folders in the computer like
C:\Program Files\Microsoft SQL Server and subfolders.
Once you have uninstalled, please try to reinstall again.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server 2008 R2 & 2008 R2 SP1 installation fails in Windows server 2012

Hi All,
I have a strange issue here. I have a Windows server 2012 VM where i want to deploy SQL 2008 R2 Enterprise edition.
When i Run the setup every thing goes fine and during the installation wizard i get this error " The Folder path Program files contains invalid characteristics. I get this error 3 - 4 times during the installation wizard and the installation fails.
Below is the screenshot for the same.
So i checked few articles regarding the compatibility issue and found the below article and upgraded my setup to SQL 2008 R2 SP1 using the below article.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
Again i still see the same above errors and with that a new error related to a MOF File.
Below are the contents of the error logs. Can some one assist on this issue.
======================================================
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): -2068052692
Exit facility code: 1212
Exit error code: 1324
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: 2015-01-15 13:53:03
End time: 2015-01-15 14:04:29
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\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.2500.0%26EvtType%3d0xA60E3551%400xD3BEBD98%401211%401
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
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: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
Installation location: D:\SQLServer2008R2_SP1\x64\setup\
Installation edition: ENTERPRISE
Slipstream: True
SP Level 1
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: E2KLAB\SCOMAC
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
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: Automatic
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
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 (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE: D:\SQLServer2008R2_SP1\SP
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: E2KLAB\SCOMAC
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: E2KLAB\SCOMAC
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr,E2KLAB\SCOMAC,E2KLAB\SCOM Admins
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\sql_common_core_loc_Cpu64_1033_1.log
MSI error description: The folder path 'Program Files' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\SystemConfigurationCheck_Report.htm
Gautam.75801

Hi Alberto,
Still the same issue.
I installed the SQL 2008 R2 without SP1 and changed the service accounts to system account and repaired the .NET using the .NET Repair tool
Also changed the installation directory to D:\ Drive this time. Still same issue.
log file:
===============
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): -2068052692
Exit facility code: 1212
Exit error code: 1324
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: 2015-01-15 22:55:37
End time: 2015-01-15 23:07:32
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SQLSysClrTypes_Cpu64_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
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: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 1
Installation location: D:\SQL Server 2008 R2 Datacenter edition for only Windows server 2008 R2\x64\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
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\20150115_225416\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: D:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: D:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: D:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
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
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SystemConfigurationCheck_Report.htm
Any other suggestion i can try ?
Gautam.75801

Sql Server 2008 R2 setup status failed

Hi guys, plz help me when i install Sql2008 i get this error.... plx help me if you have solution...
Thanks in Advance...
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):           -2068052377
Exit facility code:            1212
Exit error code:               1639
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:                    2014-03-14 18:21:32
End time:                      2014-03-14 18:30:00
Requested action:              Install
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182056\sql_engine_core_inst_Cpu64_1.log
Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name:                  NIRMAL-PC
Machine processor count:       8
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:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:         E:\Software _2\Software _2\SQL2008\x64\setup\
Installation edition:          DEVELOPER
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      True
AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Manual
ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.SQL2008\OLAP\Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.SQL2008\OLAP\Config
ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.SQL2008\OLAP\Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS10_50.SQL2008\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            NIRMAL-PC\sdfg
ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.SQL2008\OLAP\Temp
BROWSERSVCSTARTUPTYPE:         Automatic
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182056\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
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD:                 *****
HELP:                          False
IACCEPTSQLSERVERLICENSETERMS: False
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:                    SQL2008
INSTANCENAME:                  SQL2008
ISSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
NPENABLED:                     0
PASSPHRASE:                    *****
PCUSOURCE:
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
ROLE:                          AllFeatures_WithDefaults
RSINSTALLMODE:                 DefaultNativeMode
RSSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  Latin1_General_CI_AS
SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
SQLSVCPASSWORD:                *****
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           NIRMAL-PC\sdfg
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  True
TCPENABLED:                    0
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182056\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182056\sql_engine_core_inst_Cpu64_1.log
MSI error description:
Configuration status:          Passed
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:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182056\sql_engine_core_inst_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182056\sql_engine_core_inst_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Analysis Services
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182056\sql_as_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182056\sql_engine_core_inst_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Reporting Services
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182056\sql_engine_core_inst_Cpu64_1.log
MSI error description:
Configuration status:          Passed
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
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140314_182056\SystemConfigurationCheck_Report.htm

Hello,
Please try to uninstall SQL Server using YoyoYu suggestions on the following thread:
http://social.msdn.microsoft.com/Forums/en/sqlexpress/thread/4d6158a1-b601-428c-aad4-a1716e76de1a
When finish, re-install SQL Server again.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server 2008 & 2012 Database backup on a shared loaction

Hi,
I have to plan for the Database backup on SQL Server 2008 & 2012 on a shared Path.
We are building a new Maintenance plan &  specify the Database which needs to be backup & at the Folder location we specify the Shared Path Location. These steps I have followed using the below link,
http://social.msdn.microsoft.com/Forums/en-US/be138ca3-4b2f-4464-8115-9a0a6f2e0fe6/sql-database-backup-on-network-share-using-maintenance-plan?forum=sqldatabasemirroring
But the operation fails & throws the below error:
Message
Executed as user Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started: 12:27:17 PM Progress: 2014-02-13 12:27:19.13
Source: {B6CEBA00-4BD1-4931-AF23-B633BEDBEE4A}      Executing query "DECLARE @Guid UNIQUEIDENTIFIER      EXECUTE msdb..sp...".: 100% complete End Progress Error: 2014-02-13 12:27:20.63
Code: 0xC002F210     Source: Back Up Database Task Execute SQL Task     Description: Executing the query "BACKUP DATABASE DB TO DISK ..." failed with the following error: "Cannot open backup device
'\\DBBackup\SharePoint_backup\DB_backup_2014_02_13_122719_5314660.bak'. Operating system error 5(Access is denied.). BACKUP DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not
set correctly, parameters not set correctly, or connection not established correctly. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 12:27:17 PM Finished: 12:27:20 PM Elapsed: 2.843 seconds.
The package execution failed. The step failed.
Note: But when I open the shared path in the Windows Explorer it opens successfully.
Regards,
Purvish Shah

Hello,
>>'\\DBBackup\SharePoint_backup\DB_backup_2014_02_13_122719_5314660.bak'. Operating system error 5(Access is denied.).
This clearly points out to fact that your SQL Server service account does not have permission of read/write on shared location,simple.
>>But when I open the shared path in the Windows Explorer it opens successfully.
This is because when you are browsing through explorer your windows login credential is used to access that folder but when you are running backup your SQL Server service account permission is used to write backup on shared folder ( which I assume it does
not have ) so the access denied error.
Hope this helps
PS: I reffered the link its maily how you specify backup path its not about access denied error due to SQL server service acount not having privilege
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL Server 2008 R2 Management Studio (express) install fails (Management Tools Basic Failed) - Error 1316. The Specific account already exists.

Hi,
I try to install, the SQL Express 2008 R2 with Advanced
The installation has only one error (Error 1316. The Specific account already exists.) and the Management Tools Basic setup is failed.
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): -2068052700
Exit facility code: 1212
Exit error code: 1316
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: 2015-01-02 16:17:17
End time: 2015-01-02 16:24:01
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap
\Log\20150102_161500\SSCRuntime_Cpu32_1.log
Exception help link: http://go.microsoft.com/fwlink?
LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.4000.0
Machine Properties:
Machine name: KHPNHSI_BNANG
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: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
Installation location: g:\41bee43707e62fab54ec\x64\setup\
Installation edition: EXPRESS_ADVANCED
Slipstream: True
SP Level 2
User 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:
CUSOURCE:
ENABLERANU: True
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,SSMS,SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
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: SQLExpress
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE: g:\41bee43707e62fab54ec\PCUSOURCE
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: PSI\ssamnang
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
UIMODE: AutoAdvance
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap
\Log\20150102_161500\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
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\20150102_161500\SystemConfigurationCheck_Report.htm
Please help!
Samnang.

Hi SSamnang,
According to your description, you come across the error that the specific account already exists. Please help to share the complete error log in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150102_161500\SSCRuntime_Cpu32_1.log. You could
use google drive to upload the error log following the steps in the article:
https://support.google.com/drive/answer/2424368?hl=en
From the exception help link, we notice that, the issue could be due to that an attempt fails to install SQL Server Native Client on a computer where SQL Server Native Client is already installed.
I recommend you to check if there is already an existing SQL Server Native Client on your computer. If there is an existing one, you could uninstall it and install SQL Server again.
In addition, there is a similar thread for reference:
https://social.technet.microsoft.com/Forums/en-US/dc31bffd-c9e2-4630-b5d7-9252b03c24fe/sql-2008-r2-management-tools-install-fails-the-specified-account-already-exists?forum=sqltools.
Regards,
Michelle Li

SQL Server 2008 KB2977321 Failed with Error code 1642

As part of application of security patches via windows update, sql server KB2977321 was applied along with a number of OS security patches.
Prior to applying the patches, I stopped the agent, engine, reporting, analysis and full text services.
The Sql server build prior to windows update was (for both instances):
ProductVersion
ProductLevel
Edition
10.0.5500.0
SP3
Standard Edition (64-bit)
After the update process, my main instance is showing (the second instance is not in use yet and I have left it in its stopped state)
Microsoft SQL Server 2008 (SP3) - 10.0.5520.0 (X64)
Jul 11 2014 16:11:50
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (VM)
In the Administrative Logs after the OS patches were applied (and all were reported as successful by windows update), I found the following errors listed:
Log Name:
Application
Source:
MsiInstaller
Date:
11/18/2014 7:16:45 PM
Event ID:
1024
Task Category: None
Level:
Error
Keywords:
Classic
User:
SYSTEM
Computer:
SJCDB3.intranet.co.st-johns.fl.us
Description:
Product: Microsoft SQL Server 2008 Database Engine Services - Update '{9145CF54-462E-4A28-8FB5-A44C93AD3716}' could not be installed. Error code 1642. Windows Installer can create logs to help troubleshoot
issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">1024</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-11-19T00:16:45.000000000Z" />
<EventRecordID>1764186</EventRecordID>
<Channel>Application</Channel>
<Computer>SJCDB3.intranet.co.st-johns.fl.us</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data>Microsoft SQL Server 2008 Database Engine Services</Data>
<Data>{9145CF54-462E-4A28-8FB5-A44C93AD3716}</Data>
<Data>1642</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>
</Data>
<Binary>7B38373544383436332D313135422D343444322D414432352D3731454337453833423843437D207B39313435434635342D343632452D344132382D384642352D4134344339334144333731367D2031363432</Binary>
</EventData>
</Event>
In the C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141118_191448\Detail.txt file I found the following around the time the error was reported
2014-11-18 19:16:30 Slp: Baseline Package Id sql_engine_core_inst_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_engine_core_inst_Cpu64 - NotInstalled on the baseline msi package sql_engine_core_inst_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_engine_core_inst_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_engine_core_inst_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_engine_core_inst_Cpu32
BaselineVersion=10.3.5500.0; PatchFileName=sql_engine_core_inst.msp PatchCode={9145CF54-462E-4A28-8FB5-A44C93AD3716}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_rs_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_rs_Cpu64 - NotInstalled on the baseline msi package sql_rs_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - The baseline msi is not installed.
The patch package is ignored.
2014-11-18 19:16:30 Slp: Patch Id: KB2977321_sql_rs_Cpu32 - Detail description of this patch package is: PatchId=KB2977321_sql_rs_Cpu32 PatchVersion=10.3.5520.0 BaselinePackageId=sql_rs_Cpu32 BaselineVersion=10.3.5500.0;
PatchFileName=sql_rs.msp PatchCode={2296F7DD-2D3D-4802-B61A-AE7460EFB767}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_is_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_is_Cpu64 - NotInstalled on the baseline msi package sql_is_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_is_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_is_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_is.msp PatchCode={E870296C-24CC-4D82-BB59-CD136692E2BD}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_bids_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_bids_Cpu64 - NotInstalled on the baseline msi package sql_bids_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_bids_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_bids_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_bids.msp PatchCode={EA407FA6-C2D1-4D3D-9227-B9E06DDDEFD0}
2014-11-18 19:16:30 Slp: Baseline Package Id sql_ssms_Cpu64 - The highest patch version is 10.3.5500.0
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_ssms_Cpu64 - NotInstalled on the baseline msi package sql_ssms_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_ssms_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_ssms_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_ssms.msp PatchCode={8A81B870-E8F0-415D-AC80-13BEAA3EC8C8}
2014-11-18 19:16:30 Slp: Baseline Package Id: sql_common_core_Cpu64 - No patches are found by SQL Discovery on the installed package whose ProductCode is {5340A3B5-3853-4745-BED2-DD9FF5371331}
2014-11-18 19:16:30 Slp: Patch Id KB2977321_sql_common_core_Cpu64 - NotInstalled on the baseline msi package sql_common_core_Cpu64.
Detail description of this patch package is: PatchId=KB2977321_sql_common_core_Cpu64 PatchVersion=10.3.5520.0 BaselinePackageId=sql_common_core_Cpu64 BaselineVersion=10.3.5500.0; PatchFileName=sql_common_core.msp PatchCode={CF023E0F-3A19-4DBF-BCA3-0F664B447EDB}
The instance came up successfully and seems to be operating normally. Was there an error or was the KB installed correctly as the result of the windows update process indicated?
Is there a way I can verify this?

I did some research on this particular KB article and it seems to be related to Master Data Services which I am not using. The KB was pushed automatically and I am not sure that it was a required update in our situation. I'd like to understand exactly
what caused the error message before initiating a repair as this is a production and not a test environment. Everything appears to be functioning properly and I have received direction from Microsoft in the past that information in some logs identified
as level 'error' are in fact to be ignored. I checked the windows update and this KB shows 'Successful' rather than failed or cancelled.
I would also like more information on why sql server services should not be stopped prior to allowing the OS patches to be applied.   I have received messages in the past that stopping the services before service packs are applied
prevent the necessity for a reboot of the machine. I've never heard before that it is a best practice not to stop Sql service prior to applying patches. Once the services are stopped, I have our infrastructure admin start a VM snapshot on
the machine then kick off the windows update process. When done, I reboot the machine, test out Sql Server processes and then if all goes well give the ok to release the VM snapshot. I've supported various databases for 12 years, Sql Server for 5
years and this is the first time I've heard stopping the service manually can cause problems. If that is the case, I will certainly change how I do things....
I did run the discovery report and the results follow:
Microsoft SQL Server 2008 Setup Discovery Report
Product
Instance
Instance ID
Feature
Language
Edition
Version
Clustered
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
SQL Server Replication
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
MSSQLSERVER
MSSQL10.MSSQLSERVER
Full-Text Search
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSAS10.MSSQLSERVER
Analysis Services
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
MSSQLSERVER
MSRS10.MSSQLSERVER
Reporting Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
EVAULT
MSSQL10.EVAULT
Database Engine Services
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Basic
1033
Standard Edition
10.3.5520.0
No
Sql Server 2008
Management Tools - Complete
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Connectivity
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools Backwards Compatibility
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Client Tools SDK
1033
Standard Edition
10.3.5500.0
No
Sql Server 2008
Integration Services
1033
Standard Edition
10.3.5520.0
No

SQL Server 2008 Express SP1 installation failed

Hello guys,
System Info:
Windows 7 64Bit.
Scenario: I have an application, while installation it installs SQLServer 2008 instance with some xyz database name.
Issue: The system already has the SQLServer 2008 R2, and now I am trying to install the application but the SQLServer instance of my application is not getting installed, its giving error saying that the installation failed.
The error code is :
0x84B40000
The below is the log file data.
07/07/2014 16:15:14.283 ======================================================================
07/07/2014 16:15:14.283 Setup launched
07/07/2014 16:15:14.298 Attempting to determine media source
07/07/2014 16:15:14.298 Media source value not specified on command line argument.
07/07/2014 16:15:14.298 Setup is launched from media directly so default the value to the current folder.
07/07/2014 16:15:14.298 Media source: c:\80424454fe36892978\
07/07/2014 16:15:14.298 Attempt to determine media layout based on file 'c:\80424454fe36892978\mediainfo.xml'.
07/07/2014 16:15:14.361 Media layout is detected as: Core
07/07/2014 16:15:14.361 Media LCID is detected as: 1033
07/07/2014 16:15:14.361 Media is a slipstream package
07/07/2014 16:15:14.361 Only patch related actions can run patch setup.exe, so continuing to run setup.exe from media.
07/07/2014 16:15:14.361 /? or /HELP or /ACTION=HELP specified: false
07/07/2014 16:15:14.361 Help display: false
07/07/2014 16:15:14.361 Checking to see if we need to install .Net version 2.0
07/07/2014 16:15:14.376 Determining the cluster status of the local machine.
07/07/2014 16:15:14.376 The local machine is not configured as a cluster node.
07/07/2014 16:15:14.376 Attempting to find media for .Net version 2.0
07/07/2014 16:15:14.376 .Net version 2.0 is installed
07/07/2014 16:15:14.376 RedistMSI::GetExpectedBuildRevision - Setup expects MSI 4.5.6001.22159 at the minimum
07/07/2014 16:15:14.376 Attempting to get Windows Installer version
07/07/2014 16:15:14.376 Windows Installer version detected: 5.0.7601.17807
07/07/2014 16:15:14.376 RedistMSI::IsVistaRTM - Not Vista RTM build
07/07/2014 16:15:14.392 Required version of Windows Installer is already installed
07/07/2014 16:15:14.392 Current running setup.exe full path: c:\80424454fe36892978\setup.exe
07/07/2014 16:15:14.392 Media setup.exe file version detected: 2007.100.2731.23
07/07/2014 16:15:14.392 Locally installed setup.exe full path: c:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Release\setup.exe
07/07/2014 16:15:14.408 Local setup.exe file version detected: 2007.100.2731.23
07/07/2014 16:15:14.408 Local setup.exe version 2007.100.2731.23 is equal or greater than media version 2007.100.2731.23, so re-launching setup.exe from local
07/07/2014 16:15:14.408 Media source: c:\80424454fe36892978\
07/07/2014 16:15:14.408 Install media path: c:\80424454fe36892978\x86\setup\
07/07/2014 16:15:14.423 Media layout: Core
07/07/2014 16:15:14.423 Attempting to get execution timestamp
07/07/2014 16:15:14.423 Timestamp: 20140707_161514
07/07/2014 16:15:14.439 Attempting to launch local setup.exe
07/07/2014 16:15:14.439 Attempting to launch process c:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Release\setup.exe
07/07/2014 16:15:38.962 Process returned exit code: 0x84B40000
07/07/2014 16:15:38.962 Local setup.exe returned exit code: 0x84B40000
07/07/2014 16:15:38.962 Setup closed with exit code: 0x84C40013
07/07/2014 16:15:38.962 ======================================================================
Please do reply if anyone knows how to fix this issue.
Thanks,
Shiv
0x84B40000

Hi,
You can install SQL server express 2008 on machine having SQL Server 2008 r2 is supported. From what you posted I guess SQL server 2008 r2 is default instance so you need to install SQL server 2008 express SP1 as named instance. Your error matches problem
mentioned in below thread
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/1e8cfab3-4b99-4b4d-82bf-97799dabe34c/failure-when-installing-from-command-prompt-config-file?forum=sqlexpress
If issue is not solved please post complete log files from location
%programfiles%\Microsoft SQL Server\100\Setup Bootstrap\Log\.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

The unattended installation failed while installing SQL Server 2008 R2 ????

Hi gurus,
I got an error while installing SQL Server 2008 R2 in Windows 2008 R2 standard 64 bit operating system.
LOG file*
Customized installation of SQL Server 2008R2 for SAP *
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlWriter_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Client Tools SDK
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SystemConfigurationCheck_Report.htm
1/16/2012 10:13:34 PM
Message Box "Installation failed"
The unattended installation failed.
Installation Step: The unattended installation failed.
Return Code:       -2068052377
Log File:          C:\Windows\SQL4SAP.log
Check the log file above.
See SAP note 1144459 for known issues.
Result: vbOK
Registry settings (2/2):
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
WRITE(REG_DWORD): 4
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{2b9034f3-b661-4d36-a5ef-60ab5a711ace}
WRITE(REG_DWORD): 4
1/16/2012 10:37:32 PM
Quit script with return code 1
Please help me out with this issue.
REGARDS,
Raj

Hello Raj,
MS SQL DB installation specific steps for SAP system is clearly documented in SAP Installation guide. Please download from SMP, read it carefully and install as mentioned in the guide.
Hope it helps.
Thanks,
Siva Kumar

Installation issue : sql server 2008 r2 some services failed to installed on windows 7

I have been facing this problem while installing sql server 2008 r2.. i tried so many times but same result .. it shows sql server installed with some errors
database engine service : failed
SQL Server Replication : failed
Full-Text Search : failed
Analysis Services : failed
Reporting Services : failed
And my Log file (or) summary file is (it is in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log):
Overall summary:
Final result:                  User cancelled
Exit code (Decimal):           -2068380094
Exit facility code:            1207
Exit error code:               1602
Exit message:                  User has cancelled.
Start time:                    2014-08-14 21:15:26
End time:                      2014-08-14 21:23:58
Requested action:              AddNode
Machine Properties:
Machine name:                  MANJU-PC
Machine processor count:       4
OS version:                    Windows Vista
OS service pack:
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
Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services
1033                                      10.0.1600.22
No
Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            SQL Server Replication
1033                                      10.0.1600.22
No
Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Full-Text Search
1033                                      10.0.1600.22
No
Sql Server 2008      MSSQLSERVER          MSAS10.MSSQLSERVER             Analysis Services
1033                                      10.0.1600.22
No
Sql Server 2008      MSSQLSERVER          MSRS10.MSSQLSERVER             Reporting Services
1033                                      10.0.1600.22
No
Sql Server 2008
Management Tools - Basic                 1033                 Developer Edition
10.0.1600.22    No
Sql Server 2008
Management Tools - Complete              1033                 Developer Edition    10.0.1600.22
No
Sql Server 2008
Client Tools Connectivity                1033                 Developer Edition    10.0.1600.22
No
Sql Server 2008
Client Tools Backwards Compatibility     1033                 Developer Edition    10.0.1600.22    No
Sql Server 2008
Client Tools SDK                         1033
Developer Edition    10.0.1600.22    No
Sql Server 2008
Integration Services                     1033                 Developer Edition
10.0.1600.22    No
Package properties:
Description:                   SQL Server Database Services 2008
SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName:                   SQL2008
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:         D:\Softwares\JAVA & .NET SW\SQL Server 2008\SQL Server 2008\x86\setup\
Installation edition:          DEVELOPER
User Input Settings:
ACTION:                        AddNode
AGTSVCACCOUNT:                 <empty>
AGTSVCPASSWORD:                *****
ASSVCACCOUNT:                  <empty>
ASSVCPASSWORD:                 *****
CONFIGURATIONFILE:
FAILOVERCLUSTERGROUP:
FAILOVERCLUSTERNETWORKNAME:    <empty>
FTSVCACCOUNT:                  <empty>
FTSVCPASSWORD:                 *****
HELP:                          False
INDICATEPROGRESS:              False
INSTANCENAME:                  <empty>
MEDIASOURCE:                   D:\Softwares\JAVA & .NET SW\SQL Server 2008\SQL Server 2008\
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
SQLSVCACCOUNT:                 <empty>
SQLSVCPASSWORD:                *****
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140814_210558\ConfigurationFile.ini
Detailed results:
Feature:                       Integration Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools SDK
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140814_210558\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
    Message:
        User has cancelled.
    Stack:
        at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
        at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
        at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
        at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
        at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)

Requested action:              AddNode
OS architecture:               x86
Process architecture:          32 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services
1033                                      10.0.1600.22
No
Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            SQL Server Replication
1033                                      10.0.1600.22
No
Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Full-Text Search
1033                                      10.0.1600.22
No
Sql Server 2008      MSSQLSERVER          MSAS10.MSSQLSERVER             Analysis Services
1033                                      10.0.1600.22
No
Sql Server 2008      MSSQLSERVER          MSRS10.MSSQLSERVER             Reporting Services
1033                                      10.0.1600.22
No
Sql Server 2008
Management Tools - Basic                 1033                 Developer Edition
10.0.1600.22    No
Sql Server 2008
Management Tools - Complete              1033                 Developer Edition    10.0.1600.22
No
Sql Server 2008
Client Tools Connectivity                1033                 Developer Edition    10.0.1600.22
No
Sql Server 2008
Client Tools Backwards Compatibility     1033                 Developer Edition    10.0.1600.22    No
Sql Server 2008
Client Tools SDK                         1033
Developer Edition    10.0.1600.22    No
Sql Server 2008
Integration Services                     1033                 Developer Edition
10.0.1600.22    No
Instead of installing SQL server instance you selected add node which is to be selected when SQL server installation is to be made on Node which is being added to cluster. Since your OS is not clustered I am sure you selected worng option.
Please right click on setup file and select run as administrator. Now installation window which pops up on that on left hand side select
installation and then on page that appears select 'New server standalone installation or add feature to existing installation'.
You already have SQL server 2008 installed on your machine as per feature discovery report
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Backup Failed in SQL server 2008

Similar Messages

Maybe you are looking for