How can install SQL Server 2008 Integration Services without CD?

How can install SQL Server 2008 R2 Integration Services without CD?
The PC with Windows 7 32-bits is far away and poor bandwidth . So, I want to install SQL Server 2008 Integration Services without CD.
Does any installer for SSIS only?

Copy the install media from a memory stick, portable drive or network.
Arthur My Blog

Similar Messages

How to install SQL SERVER 2008 r2 in window 7 home premimum 64bit

how to install SQL SERVER 2008 r2 in home premimum 64bit os. can any say that weather it will support or not in window 7 home premimum os.
my server log file:
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: 2014-03-27 00:52:25
End time: 2014-03-27
00:56:09
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL
Server\100\Setup Bootstrap\Log\20140327_005035\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.1600.1
Machine Properties:
Machine name: SEVALAL-PC
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
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER
Database Engine Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER
SQL Server Replication 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER
Full-Text Search 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER
Analysis Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER
Reporting Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 SEVALAL MSSQL10.SEVALAL
Database Engine Services 1033 Express Edition 10.3.5500.0
No
Sql Server 2008 SEVALAL MSSQL10.SEVALAL
SQL Server Replication 1033 Express Edition 10.3.5500.0
No
Sql Server 2008 R2
Client Tools Connectivity 1033
10.50.1600.1 No
Sql Server 2008 R2
Client Tools Backwards Compatibility 1033
10.50.1600.1 No
Sql Server 2008 R2
Client Tools SDK 1033
10.50.1600.1 No
Package properties:
Description: SQL Server Database Services
2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: G:\01.SQL Server 2008 R2 FullVersion\x64\setup\
Installation edition: STANDARD
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: <empty>
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\20140327_005035\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: IS,SSMS,ADV_SSMS,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
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: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\SYSTEM
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
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\20140327_005035\ConfigurationFile.ini
Detailed results:
Feature: Integration
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: Passed
Configuration status: Passed
Feature: Microsoft Sync
Framework
Status: Failed:
see logs for details
MSI status: Passed
Configuration status: Passed

my summary log file information:
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: 2014-03-27 00:52:25
End time: 2014-03-27 00:56:09
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140327_005035\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.1600.1
Machine Properties:
Machine name: SEVALAL-PC
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
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER SQL Server Replication 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text Search 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER Analysis Services 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER Reporting Services 1033
Standard Edition 10.50.1600.1 No
Sql Server 2008 SEVALAL MSSQL10.SEVALAL Database Engine Services 1033
Express Edition 10.3.5500.0 No
Sql Server 2008 SEVALAL MSSQL10.SEVALAL SQL Server Replication 1033
Express Edition 10.3.5500.0 No
Sql Server 2008 R2 Client Tools Connectivity
1033 10.50.1600.1 No
Sql Server 2008 R2 Client Tools Backwards Compatibility
1033 10.50.1600.1 No
Sql Server 2008 R2 Client Tools SDK
1033 10.50.1600.1 No
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: G:\01.SQL Server 2008 R2 FullVersion\x64\setup\
Installation edition: STANDARD
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: <empty>
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\20140327_005035\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: IS,SSMS,ADV_SSMS,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
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: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\SYSTEM
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
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\20140327_005035\ConfigurationFile.ini
Detailed results:
Feature: Integration 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: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
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\20140327_005035\SystemConfigurationCheck_Report.htm

An error occurred attempting to install SQL Server 2008 Express Service Pack 1

i have Setup application with complete prerequisite requirement package create from Visual Studio 2010 setup application.And yes this setup working fine in windows 7 and windows vista but not working in windows xp service pack 3.and getting error when install "An error occurred attempting to install SQL Server 2008 Express Service Pack 1"Give me solution as soon as possible.I have listed summery.txt and log.txt. please refer it.Summery.txt
===============================================================Component SQL Server 2008 Express has failed to install with the
following error message:
"An error occurred attempting to install SQL Server
2008 Express Service Pack 1."
The following components were successfully
installed:
- Microsoft .NET Framework 4 Client Profile (x86 and
x64)
The following components failed to install:
- SQL Server 2008
Express
See the setup log file located at
'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\install.log' for more
information.Install.log
==========================================================================The following properties have been set:
Property: [AdminUser]
= true {boolean}
Property: [InstallMode] = HomeSite {string}
Property:
[ProcessorArchitecture] = Intel {string}
Property: [VersionNT] = 5.1.3
{version}
Running checks for package 'Windows Installer 3.1', phase
BuildList
The following properties have been set for package 'Windows
Installer 3.1':
Running checks for command
'WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe'
Result of running
operator 'VersionGreaterThanOrEqualTo' on property 'VersionMsi' and value '3.1':
true
Result of checks for command
'WindowsInstaller3_1\WindowsInstaller-KB893803-v2-x86.exe' is
'Bypass'
'Windows Installer 3.1' RunCheck result: No Install
Needed
Running checks for package 'Microsoft .NET Framework 4 Client Profile
(x86 and x64)', phase BuildList
Reading value 'Version' of registry key
'HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Client'
Unable to read
registry value
Not setting value for property
'DotNet40Client_TargetVersion'
The following properties have been set for
package 'Microsoft .NET Framework 4 Client Profile (x86 and x64)':
Running
checks for command 'DotNetFX40Client\dotNetFx40_Client_x86_x64.exe'
Result of
running operator 'ValueEqualTo' on property 'InstallMode' and value 'HomeSite':
true
Result of checks for command
'DotNetFX40Client\dotNetFx40_Client_x86_x64.exe' is 'Bypass'
Running checks
for command 'DotNetFX40Client\dotNetFx40_Client_setup.exe'
Result of running
operator 'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite':
false
Skipping ByPassIf because Property 'DotNet40Client_TargetVersion' was
not defined
Result of running operator 'ValueEqualTo' on property 'AdminUser'
and value 'false': false
Result of running operator 'VersionLessThan' on
property 'VersionNT' and value '5.1.2': false
Result of running operator
'ValueEqualTo' on property 'ProcessorArchitecture' and value 'IA64':
false
Result of checks for command
'DotNetFX40Client\dotNetFx40_Client_setup.exe' is 'Install'
'Microsoft .NET
Framework 4 Client Profile (x86 and x64)' RunCheck result: Install
Needed
Running checks for package 'SQL Server 2008 Express', phase
BuildList
Running external check with command
'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SqlExpressChk.exe' and
parameters '10.0.1600 1033'
Process exited with code 2
Setting value '2
{int}' for property 'SQLExpressChk'
The following properties have been set
for package 'SQL Server 2008 Express':
Property: [SQLExpressChk] = 2
{int}
Running checks for command
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
Result of running operator
'ValueNotExists' on property 'VersionNT': false
Result of running operator
'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
Result of
running operator 'VersionEqualTo' on property 'VersionNT' and value '5.2.0':
false
Result of running operator 'VersionEqualTo' on property 'VersionNT' and
value '5.2.1': false
Result of running operator 'ValueEqualTo' on property
'AdminUser' and value 'false': false
Result of running operator
'ValueEqualTo' on property 'SQLExpressChk' and value '-1': false
Result of
running operator 'ValueEqualTo' on property 'SQLExpressChk' and value '-2':
false
Result of running operator 'ValueEqualTo' on property 'SQLExpressChk'
and value '-3': false
Result of running operator 'ValueEqualTo' on property
'SQLExpressChk' and value '-4': false
Result of running operator
'ValueLessThan' on property 'SQLExpressChk' and value '-4': false
Result of
running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value
'Intel': false
Result of running operator 'ValueNotEqualTo' on property
'SQLExpressChk' and value '1': true
Result of checks for command
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' is 'Bypass'
Running checks for command
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
Result of running operator
'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel':
false
Result of running operator 'ValueNotEqualTo' on property
'SQLExpressChk' and value '2': false
Result of checks for command
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' is 'Install'
Running checks for
command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE'
Result of running operator
'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'amd64':
true
Result of checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE' is
'Bypass'
Running checks for command
'SqlExpress2008\SQLEXPR_x64_ENU.EXE'
Result of running operator
'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'amd64':
true
Result of checks for command 'SqlExpress2008\SQLEXPR_x64_ENU.EXE' is
'Bypass'
'SQL Server 2008 Express' RunCheck result: Install Needed
EULA
for components 'Microsoft .NET Framework 4 Client Profile (x86 and x64)' was
accepted.
EULA for components 'SQL Server 2008 Express' was
accepted.
Copying files to temporary directory
"C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\"
Downloading files to
"C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\"
(11/15/2014 3:59:51 PM)
Downloading 'DotNetFX40Client\dotNetFx40_Client_setup.exe' from 'http://go.microsoft.com/fwlink/?linkid=182804'
to 'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\'
Download completed at
11/15/2014 3:59:53 PM
Verifying file integrity of
C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\DotNetFX40Client\dotNetFx40_Client_setup.exe
WinVerifyTrust
returned 0
File trusted
(11/15/2014 3:59:53 PM) Downloading
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' from 'http://go.microsoft.com/fwlink/?LinkID=153228&clcid=0x409'
to 'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\'
Download completed at
11/15/2014 4:00:22 PM
Verifying file integrity of
C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SQLEXPR32_x86_ENU.EXE
WinVerifyTrust
returned 0
File trusted
Running checks for package 'Microsoft .NET
Framework 4 Client Profile (x86 and x64)', phase BeforePackage
Reading value
'Version' of registry key 'HKLM\Software\Microsoft\NET Framework
Setup\NDP\v4\Client'
Unable to read registry value
Not setting value for
property 'DotNet40Client_TargetVersion'
The following properties have been
set for package 'Microsoft .NET Framework 4 Client Profile (x86 and
x64)':
Running checks for command
'DotNetFX40Client\dotNetFx40_Client_setup.exe'
Result of running operator
'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite':
false
Skipping ByPassIf because Property 'DotNet40Client_TargetVersion' was
not defined
Result of running operator 'ValueEqualTo' on property 'AdminUser'
and value 'false': false
Result of running operator 'VersionLessThan' on
property 'VersionNT' and value '5.1.2': false
Result of running operator
'ValueEqualTo' on property 'ProcessorArchitecture' and value 'IA64':
false
Result of checks for command
'DotNetFX40Client\dotNetFx40_Client_setup.exe' is 'Install'
'Microsoft .NET
Framework 4 Client Profile (x86 and x64)' RunCheck result: Install
Needed
Verifying file integrity of
C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\DotNetFX40Client\dotNetFx40_Client_setup.exe
WinVerifyTrust
returned 0
File trusted
Installing using command
'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\DotNetFX40Client\dotNetFx40_Client_setup.exe'
and parameters ' /q /norestart /ChainingPackage ClientX64ClickOnce /lcid
1033'
Process exited with code 0
Running checks for package 'Microsoft
.NET Framework 4 Client Profile (x86 and x64)', phase AfterPackage
Reading
value 'Version' of registry key 'HKLM\Software\Microsoft\NET Framework
Setup\NDP\v4\Client'
Read string value '4.0.30319'
Setting value
'4.0.30319 {string}' for property 'DotNet40Client_TargetVersion'
The
following properties have been set for package 'Microsoft .NET Framework 4
Client Profile (x86 and x64)':
Property: [DotNet40Client_TargetVersion] =
4.0.30319 {string}
Running checks for command
'DotNetFX40Client\dotNetFx40_Client_setup.exe'
Result of running operator
'ValueNotEqualTo' on property 'InstallMode' and value 'HomeSite':
false
Result of running operator 'VersionGreaterThanOrEqualTo' on property
'DotNet40Client_TargetVersion' and value '4.0.30129': true
Result of checks
for command 'DotNetFX40Client\dotNetFx40_Client_setup.exe' is
'Bypass'
'Microsoft .NET Framework 4 Client Profile (x86 and x64)' RunCheck
result: Install Succeeded
Running checks for package 'SQL Server 2008
Express', phase BeforePackage
Running external check with command
'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SqlExpressChk.exe' and
parameters '10.0.1600 1033'
Process exited with code 2
Setting value '2
{int}' for property 'SQLExpressChk'
The following properties have been set
for package 'SQL Server 2008 Express':
Property: [SQLExpressChk] = 2
{int}
Running checks for command
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
Result of running operator
'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel':
false
Result of running operator 'ValueNotEqualTo' on property
'SQLExpressChk' and value '2': false
Result of checks for command
'SqlExpress2008\SQLEXPR32_x86_ENU.EXE' is 'Install'
'SQL Server 2008 Express'
RunCheck result: Install Needed
Verifying file integrity of
C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SQLEXPR32_x86_ENU.EXE
WinVerifyTrust
returned 0
File trusted
Installing using command
'C:\DOCUME~1\BS\LOCALS~1\Temp\VSD8C9.tmp\SqlExpress2008\SQLEXPR32_x86_ENU.EXE'
and parameters '/q /hideconsole /action=Upgrade /instancename=SQLEXPRESS
/skiprules=RebootRequiredCheck'
Process exited with code
-2068578302
Status of package 'Microsoft .NET Framework 4 Client Profile (x86
and x64)' after install is 'InstallSucceeded'
Status of package 'SQL Server
2008 Express' after install is 'InstallFailed'
S S Manne

Hi Manne,
As your description, you come across an error when trying to install SQL Server 2008 express Service Pack 1 on windows XP Service Pack 3 machine. From your error log, I get the error(unable to read registry value). As my analysis, the issue could be due
to that your account doesn't have access to registry. Below are the recommendations for troubleshooting the issue.
1. Make sure that you log in as an administrator of the machine.
2. Please follow the steps below to make sure that you have granted the right permission to registry.
a. Located HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server in registry.
b. Right click and go to Permission, then you could see user accounts or groups. If your user account is not in the list, you could click Add to add your account there.
c. Select your account and Click on Advance.
d. Check on both check box ('Include inheritable permissions from this object's parent'.
and 'Replace all child object permissions with inheritable permissions from this object'), click OK.
e. Click OK again.
Regards,
Michelle Li

Get error code 0x80070643 when I try to install Sql Server 2008 R2 Service Pack 1 (KB2528583)

I keep getting error code 0x80070643 when I try to install Sql Server 2008 R2 Service Pack 1 (KB2528583)
Operating System is Windows 2008 R2 64 bit

Hi JamesRead,
According to your description, when you install SQL Server 2008 R2 service pack 1, we need to verify if
you must have administrative rights on the computer.
There are multiple files available for the download, you will be prompted to select the files you need. We need to verify if you run the SQLServer2008R2SP1-KB2528583-x64-ENU.exe. Or you can install SQL server updates from the command
prompt and check if it can install successfully.
You can prepare an installation of database engine instance to include product update:
setup.exe /q /IAcceptSQLServerLicenseTerms /ACTION=PrepareImage /UpdateEnabled=True /UpdateEnabled=True /UpdateSource=<path where the update is downloaded> /INSTANCEID=<Instance ID> /FEATURES=SQLEngine
For more information, you can review the following article about installing Updates from the Command Prompt.
http://technet.microsoft.com/en-us/library/dd638066.aspx
Thanks,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

How to install SQL server 2008 express on Windows server 2008 R2 standard OS

Hi,
I have Windows server 2008 R2 Standard edition (64-bit) and trying to install SQL server 2008 express edition since I do not have SQL server 2008. When I install it I am unable to see Management Studio so I am trying to install management studio as well
but still I am facing issue. Please let me know whether SQL server 2008 express edition is compatible with Windows server 2008 R2 Standard. If not then pls let me know the proper steps to install it.
Regds

Hello,
Service Pack 1 for SQL Server 2008 is required to be compatible with Windows Server 2008 R2.
Please download QL Server 2008 Express with SP1 included from the following link:
http://www.microsoft.com/en-us/download/details.aspx?id=25052
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Witch Rol Server Should I Install SQL Server 2008 R3 Service Pack 3

Hello
My enviroment SQL Server has 3 Servers
One Server for DataBase Engine
One Server for SSIS & SSAS
One Server for SSRS
I need to install Service Pack 3 for SQL Server 2008 R2, but have a doubt , Do I need install service pack in each Rol Server or just install over Data Base Engine Server ?
Really Appreciate your help
Regards
CarlosE
Sr .NET, DBA SQL Server MCP, MCTS SQL . Si alguna de las respuesta ha sido util, por favor marcalas. http://sqlnetunamorcompartido.blogspot.com/

I need to install Service Pack 3 for SQL Server 2008 R2, but have a doubt , Do I need install service pack in each Rol Server or just install over Data Base Engine Server ?
HI ,
SP3 for SQL server 2008 r2 is not there I guess you are talking about SQL server 2008.When you install Service pack and reach to 'Select Features ' page please select all the features. You can see SSIS ,SSRS and SSAS listed there as well with database engine
and client tools.
After selecting all features SP will be installed for all and all features will be patched
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

Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"

I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
I tried all the things below;
* I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
* I'm deleting all the keys related with Sql Server from Regedit.
* Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
* My firewall is already closed. And i have not any antivirus software.
* I gave the permission for port 1433 on firewall.
Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.

Here's the ERRORLOG file which i found under the folder;
Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
2014-09-27 03:39:40.15 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2014-09-27 03:39:40.15 Server (c) Microsoft Corporation.
2014-09-27 03:39:40.15 Server All rights reserved.
2014-09-27 03:39:40.15 Server Server process ID is 5768.
2014-09-27 03:39:40.15 Server System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
2014-09-27 03:39:40.15 Server Authentication mode is MIXED.
2014-09-27 03:39:40.15 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-09-27 03:39:40.15 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-09-27 03:39:40.15 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q Turkish_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
2014-09-27 03:39:40.18 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After
the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2014-09-27 03:39:40.18 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-27 03:39:40.18 Server Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-27 03:39:40.31 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-09-27 03:39:40.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-09-27 03:39:40.43 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2014-09-27 03:39:40.45 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
is required.
2014-09-27 03:39:40.45 spid7s Warning ******************
2014-09-27 03:39:40.45 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-09-27 03:39:40.46 spid7s Starting up database 'master'.
2014-09-27 03:39:40.52 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-27 03:39:40.58 spid7s SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
2014-09-27 03:39:40.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:40.59 spid7s Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
2014-09-27 03:39:40.59 spid7s Starting up database 'mssqlsystemresource'.
2014-09-27 03:39:40.61 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2014-09-27 03:39:40.94 spid7s Password policy update was successful.
2014-09-27 03:39:40.94 spid8s Starting up database 'model'.
2014-09-27 03:39:40.95 spid7s Server name is 'CAGATAY'. This is an informational message only. No user action is required.
2014-09-27 03:39:41.21 spid8s Clearing tempdb database.
2014-09-27 03:39:41.21 spid10s A new instance of the full-text filter daemon host process has been successfully started.
2014-09-27 03:39:41.24 Server A self-generated certificate was successfully loaded for encryption.
2014-09-27 03:39:41.24 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2014-09-27 03:39:41.24 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
7806. This is an informational message only. No user action is required.
2014-09-27 03:39:41.28 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2014-09-27 03:39:41.28 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-27 03:39:41.70 spid8s Starting up database 'tempdb'.
2014-09-27 03:39:41.86 spid7s Warning ******************
2014-09-27 03:39:41.86 spid7s Attempting to change default collation to Turkish_CI_AS.
2014-09-27 03:39:41.92 spid7s index restored for master.syspriorities.
2014-09-27 03:39:41.95 spid7s index restored for master.sysbrickfiles.
2014-09-27 03:39:41.96 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:41.96 spid7s index restored for master.sysowners.
2014-09-27 03:39:42.13 spid7s index restored for master.sysdbreg.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s index restored for master.sysschobjs.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.17 spid7s index restored for master.syscolpars.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxlgns.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxsrvs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysnsobjs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.syscerts.
2014-09-27 03:39:42.19 spid7s index restored for master.sysrmtlgns.
2014-09-27 03:39:42.19 spid7s index restored for master.sysxprops.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.31 spid7s index restored for master.sysscalartypes.
2014-09-27 03:39:42.31 spid7s index restored for master.sysidxstats.
2014-09-27 03:39:42.31 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysendpts.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysclsobjs.
2014-09-27 03:39:42.32 spid7s index restored for master.sysremsvcbinds.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysrts.
2014-09-27 03:39:42.33 spid7s index restored for master.sysasymkeys.
2014-09-27 03:39:42.33 spid7s index restored for master.syssqlguides.
2014-09-27 03:39:42.44 spid7s index restored for master.syssoftobjrefs.
2014-09-27 03:39:42.47 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.48 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.49 spid7s index restored for master.spt_values.
2014-09-27 03:39:42.49 spid7s index restored for master.MSreplication_options.
2014-09-27 03:39:42.56 spid7s index restored for tempdb.syspriorities.
2014-09-27 03:39:42.56 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysowners.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysschobjs.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.59 spid7s index restored for tempdb.syscolpars.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysnsobjs.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.syscerts.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysxprops.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysscalartypes.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysidxstats.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysclsobjs.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysremsvcbinds.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysrts.
2014-09-27 03:39:42.62 spid7s index restored for tempdb.sysasymkeys.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssqlguides.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssoftobjrefs.
2014-09-27 03:39:42.75 spid7s index restored for model.syspriorities.
2014-09-27 03:39:42.75 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.75 spid7s index restored for model.sysowners.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s index restored for model.sysschobjs.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.syscolpars.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysnsobjs.
2014-09-27 03:39:43.00 spid7s index restored for model.syscerts.
2014-09-27 03:39:43.00 spid7s index restored for model.sysxprops.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysscalartypes.
2014-09-27 03:39:43.00 spid7s index restored for model.sysidxstats.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysclsobjs.
2014-09-27 03:39:43.01 spid7s index restored for model.sysremsvcbinds.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysrts.
2014-09-27 03:39:43.01 spid7s index restored for model.sysasymkeys.
2014-09-27 03:39:43.01 spid7s index restored for model.syssqlguides.
2014-09-27 03:39:43.01 spid7s index restored for model.syssoftobjrefs.
2014-09-27 03:39:43.02 spid7s Starting up database 'msdb'.
2014-09-27 03:39:43.82 spid7s index restored for msdb.syspriorities.
2014-09-27 03:39:43.85 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.93 spid7s index restored for msdb.sysowners.
2014-09-27 03:39:43.99 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.09 spid7s index restored for msdb.sysschobjs.
2014-09-27 03:39:44.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.syscolpars.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.sysnsobjs.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.25 spid7s index restored for msdb.syscerts.
2014-09-27 03:39:44.25 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s index restored for msdb.sysxprops.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.27 spid7s index restored for msdb.sysscalartypes.
2014-09-27 03:39:44.37 spid7s index restored for msdb.sysidxstats.
2014-09-27 03:39:44.41 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysclsobjs.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysremsvcbinds.
2014-09-27 03:39:44.42 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysrts.
2014-09-27 03:39:44.54 spid7s index restored for msdb.sysasymkeys.
2014-09-27 03:39:44.54 spid7s index restored for msdb.syssqlguides.
2014-09-27 03:39:44.59 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.74 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.85 spid7s index restored for msdb.syssoftobjrefs.
2014-09-27 03:39:44.89 spid7s index restored for msdb.syspolicy_policies_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.sysproxies.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syscollector_execution_stats_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syssubsystems.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_primary_secondaries.
2014-09-27 03:39:44.91 spid7s index restored for msdb.sysdownloadlist.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_monitor_primary.
2014-09-27 03:39:44.92 spid7s index restored for msdb.sysoriginatingservers.
2014-09-27 03:39:44.93 spid7s index restored for msdb.log_shipping_monitor_history_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_monitor_error_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_secondary.
2014-09-27 03:39:44.97 spid7s index restored for msdb.log_shipping_secondary_databases.
2014-09-27 03:39:45.10 spid7s index restored for msdb.log_shipping_monitor_secondary.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysjobs.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_database_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.syscollector_blobs_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysjobsteps.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.logmarkhistory.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_session_statistics_internal.
2014-09-27 03:39:45.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.12 spid7s index restored for msdb.sysdtscategories.
2014-09-27 03:39:45.33 spid7s index restored for msdb.syspolicy_target_sets_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysschedules.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysdac_instances_internal.
2014-09-27 03:39:45.33 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.50 spid7s index restored for msdb.sysssispackages.
2014-09-27 03:39:45.51 spid7s index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
2014-09-27 03:39:45.51 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysssispackagefolders.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysdac_history_internal.
2014-09-27 03:39:45.53 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syscategories.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservers.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservergroups.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syspolicy_policy_category_subscriptions_internal.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysalerts.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysoperators.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syspolicy_system_health_state_internal.
2014-09-27 03:39:45.63 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syscollector_config_store_internal.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s index restored for msdb.sysmanagement_shared_server_groups_internal.
2014-09-27 03:39:45.66 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysmanagement_shared_registered_servers_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.syscachedcredentials.
2014-09-27 03:39:45.79 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.79 spid7s index restored for msdb.syscollector_collection_sets_internal.
2014-09-27 03:39:45.79 spid7s index restored for msdb.sysutility_ucp_dac_health_internal.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms_datatype.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysmail_profile.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysutility_ucp_managed_instances_internal.
2014-09-27 03:39:45.83 spid7s index restored for msdb.syspolicy_management_facets.
2014-09-27 03:39:45.84 spid7s index restored for msdb.sysutility_ucp_mi_health_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syscollector_collector_types_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syspolicy_configuration_internal.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_facet_events.
2014-09-27 03:39:45.87 spid7s index restored for msdb.sysmail_account.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_conditions_internal.
2014-09-27 03:39:45.88 spid7s index restored for msdb.sysutility_ucp_health_policies_internal.
2014-09-27 03:39:45.88 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.88 spid7s index restored for msdb.syscollector_collection_items_internal.
2014-09-27 03:39:45.90 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysmail_servertype.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
2014-09-27 03:39:46.02 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_configuration_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.sysmail_server.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_policy_categories_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_object_sets_internal.
2014-09-27 03:39:46.04 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysmail_configuration.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysdbmaintplan_databases.
2014-09-27 03:39:46.05 spid7s index restored for msdb.log_shipping_primary_databases.
2014-09-27 03:39:46.39 spid7s The default collation was successfully changed.
2014-09-27 03:39:46.39 spid7s Recovery is complete. This is an informational message only. No user action is required.
2014-09-27 03:39:47.17 spid51 Changed database context to 'master'.
2014-09-27 03:39:47.18 spid51 Changed language setting to us_english.
2014-09-27 03:39:47.72 spid51 Setting database option RECOVERY to FULL for database model.
2014-09-27 03:39:47.84 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.84 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:48.27 spid51 Error: 15007, Severity: 16, State: 1.
2014-09-27 03:39:48.27 spid51 '' is not a valid login or you do not have permission.
2014-09-27 03:51:25.13 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:25.13 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:32.67 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:32.67 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:42.11 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:51:42.11 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:52:42.07 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:52:42.07 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:53:01.23 Logon Error: 18461, Severity: 14, State: 1.
2014-09-27 03:53:01.23 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
2014-09-27 03:53:17.57 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:53:17.57 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:53:32.54 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:53:32.54 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:04.29 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:04.29 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:10.36 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:10.36 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:47.18 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:54:47.18 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
Resolve the error, please refer to the following links.
Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
could not register the SPN Kerberos:
http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html
Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server

Attempted to perform an unauthorized operation error on windows 8.1 while installing SQL server 2008

Hi,
I am getting the error "Attempted to perform an unauthorized operation" on windows 8.1 while installing
SQL server 2008.
The specific error is The error is Attempted to perform an unauthorized operation."
at stepSqlBrowserConfigAction_install_ConfigNonRC_Cpu32 .
I have tried everything from copying to the C drive. I am the admin on the machine. I also checked access in registry. It already has acesss to HKLM\System\CurrentControlSet\Control\WMI\security
Can someone comment on how to resolve this issue. I also tried NT
AUTHORITY\SYSTEM but getting the same error.
Any help would be appreciated.

Hello,
Please note that SQL Server 2008 requires Service Pack 3 (SP3) to make it compatible with
Windows 8.1. Please perform an slipstream installation of SQL Server 2008 + SP3:
http://support.microsoft.com/kb/955392
If it fails again, please share with us the Summary.txt log file and the details.txt log file. The following article
may help you locate those files on disk::
http://msdn.microsoft.com/en-us/library/ms143702(v=sql.100).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Cannot install SQL Server 2008 R2 Developer on Windows 8.1

I am unable to install SQL Server 2008 R2 Developer edition on Windows 8.1 Enterprise evaluation and about 3/4 of the way through the installation I get this error msg:
TITLE: SQL Server 2008 R2 Setup
The following error has occurred:
Attempted to perform an unauthorized operation.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.4000.0&EvtType=0x88792597%25400xBB814387
This is my log file:
Overall summary:
Final result: User cancelled
Exit code (Decimal): 0
Exit message: User cancelled
Start time: 2014-04-23 23:49:10
End time: 2014-04-24 00:03:44
Requested action: Install
Machine Properties:
Machine name: PC
Machine processor count: 2
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: F:\My Files\My Downloads\EXISTING\SQLServer2008R2Dev\SQLFULL_ENU\x64\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_50.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: NT AUTHORITY\SYSTEM
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: PC\computername
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\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,OCS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
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:
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: PC\computername
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Analysis Services
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: 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
Feature: SQL Server Books Online
Status: Failed: see logs for details
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\20140423_234604\SystemConfigurationCheck_Report.htm
I tried installing as adminstrator and in compatability mode with Windows 7/Vista but that didn't work. Trying to install from the dvd or from the extracted files in my drive made no difference.
I am now wondering if there is a download link for SQL Server 2008 R2 Developer edition with SP2 included (i.e. not just SP2 but the whole application (5GB+) otherwise I am not sure how to install this.

Hello,
1. Please refer to solution provided in below thread
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/61d56f64-2575-4a58-9503-84579476afaf/sql-server-2008-setup-error-attempted-to-perform-an-unauthorized-operation?forum=sqlsetupandupgrade
2. Make sure you stop antivirus services during running the setup.Make sure you Right click on setup.exe file and select run as administrator.
If above does not works include below as well
3. Please verify WMI service is started.
If WMI is started, consider to repair WMI.
http://windowsxp.mvps.org/repairwmi.htm
Reference
Link
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Error installing sql server 2008 management studio express

Hello,
I need to install sql server 2008 management studio express on a sql server 2k8 R2 instance.
First of all, I've downloaded this one from this link: http://www.microsoft.com/en-us/download/details.aspx?id=7593 (for 32 bits).
Once I've the downloaded file I run this file and choose the first option (New sql server stand-alone...) in the installation part. Finally, in the installation type I choose the option 'Add features to an existing instance of SQL Server 2008' with the instance
selected. I push Next and then I get the following error: 'The instance ID is required but it is missing'.
Can anybody help me?
Thanks a lot.
Regards.

Hello,
What’s the edition of the SQL Server 2008 R2? If you had installed SQL Server 2008 R2 Developer edition, you should install “SQL Server 2008 Express with Tools” edition or “SQL Server 2008 Express with Advanced Services” edition.
Please refer to the following article for more information:
http://www.benlittler.com/2009/06/how-to-install-sql-management-studio-express-2008/
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Xcelsius and SQL Server 2008 Reporting Services

I am totally and utterly p1$$3d off and surely I cannot be the only person to be using a similar setup i.e. Xcelsius along with SQL Server 2008 Reporting Services.
I have installed and tried to get working the XRS gateway and get connectivity to Reporting Services so that SSRS reports can be utilized with Xcelsius... BUT NO...
when trying to configure and use the GetReports command from the xrs.asmx web file I get an error, namely:
<?xml version="1.0" encoding="utf-8" ?>
<ROOT>
<Message>Client found response content type of '', but expected 'text/xml'. The request failed with an empty response.</Message>
<StackTrace>at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.ReportingServices.ReportingService.ListChildren(String Item, Boolean Recursive) at Microsoft.ReportingServices.CatalogManager.CreateXmlNode(XmlDocument Doc, CatalogItem Item, XmlNode ParentNode) at Microsoft.ReportingServices.CatalogManager.SerializeToXML() at Infommersion.XRS.Service.GetReports()</StackTrace>
</ROOT>
Only to be told when I logged a support call, that "SQL Server 2008 Reporting Services is NOT SUPPORTED"
please go back to using 2005!!!
I find this totally and utterly unbelievable, it's not even as if its a new product... and surely i am not the only person using Xcelsius and wanting to utilise 2008Reporting Services Reports...
has anyone come across this error or understand what is not occuring to get this message and how to resolve?
yours eternally grateful if anyone can shed light on the matter
dean

Indeed, got the XRS gateway working but it isn't able to connect to RS2008.
I guess the cause is that for RS2005 the web service connection point is the file ReportService.asmx. In RS 2008 this file is renamed to ReportService2005.asmx and therefor the XRS gateway cannot connect to it.
A fix pack seems to be in the making:
[1400035 - Xcelsius 2008 with MS Reporting Services 2008 Supportability |http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333433303330333033333335%7D.do]

Security Update for SQL Server 2008 R2 Service Pack 2 (KB2977320)

So i have been trying to install this update on one of our servers since it is showing up on our MBSA scans but it has been failing on one of our machines with the error code: 0x80070643
I downloaded the update and tired to install it manually. The installer returned: There are no SQL Server instances or shared features that can be updated on this computer. If that was true then why is SCCM still pushing the update to the machine and why
is the MBSA showing that it needs the update? Any advice would be helpful. Thanks!

Hi David,
Based on my understanding, the error code: 0x80070643 was thrown out when you install KB2977320 with MBSA. And installation also failed when you download and install update manually.
Regarding the error code: 0x80070643, it can be caused if the MSI software update registration has become corrupted, or if the .NET Framework installation on the computer has become corrupted. To fix this issue, we can follow these methods:
Fix MSI software update registration corruption issues
Repair the .Net Framework
Uninstall and reinstall the .Net Framework
For more information, please refer to this link:
http://support.microsoft.com/kb/976982.
Besides, the security update is released for SQL Server 2008 R2 Service Pack 2, please check the version of SQL Server you are using. About how to check the SQL Server version, please refer to this article: How to tell what SQL Server version you are running
(http://www.mssqltips.com/sqlservertip/1140/how-to-tell-what-sql-server-version-you-are-running/). Then please download the Security Update for SQL
Server 2008 R2 Service Pack 2 from this link (http://www.microsoft.com/en-us/download/details.aspx?id=43957), and retry install it manually.
Best regards,
Qiuyun Yu

Install SQL Server 2008 R2 SP 1 on Windows Server 2012

Dear All,
I've downloaded SQL Server SP1 from this link:
http://www.microsoft.com/en-us/download/details.aspx?id=26727
I downloaded :
SQLServer2008R2SP1-KB2528583-x64-ENU.exe
SQLManagementStudio_x64_ENU.exe
SQLServer2008R2SP1-KB2528583-IA64-ENU.exe
when i run SQLServer2008R2SP1-KB2528583-x64-ENU.exe i have error:
There are no SQL Server instances or shared features that can be updated on this computer
what that i missed? is that i must install SQL Server 2008 R2?
because if i run the SQL Server 2008 R2 there are compatible issue. I run this on Windows Server 2012
Please Help.
Best regards,
Surbakti

Hi,
The cause could be an invalid entry in the userSettings section of the Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings file.
Delete this configuartion file or delete the folder "Microsoft_Corporation" and see how it works.
Run the command: rd /s /q %localappdata%\Microsoft_Corporation
For your reference:
http://blogs.msdn.com/b/smondal/archive/2013/07/26/an-error-occurred-creating-the-configuration-section-handler-for-usersettings-microsoft-sqlserver-configuration-landingpage-properties-settings.aspx
Thanks.
Tracy Cai
TechNet Community Support

Install SQL Server 2008 R2 10.50.1600.1 or 10.50.4000.0?

I'm building a new farm and need to install SQL server. I have SQLServer2008R2SP1-KB2528583-x64-ENU.exe on the network, but I'm not sure if this is
only SP1 or the full version of SQL Server 2008 R2 with SP1.
Once SQL is installed, I'll need it to match another server at SP2, 10.50.4000.0. Is there an SQL Server 2008 R2
with SP2?
Thanks,
Scott

1.I'm building a new farm and need to install SQL server. I have SQLServer2008R2SP1-KB2528583-x64-ENU.exe on the network, but I'm not sure if this is
only SP1 or the full version of SQL Server 2008 R2 with SP1.
2. Once SQL is installed, I'll need it to match another server at SP2, 10.50.4000.0. Is there an SQL Server 2008 R2
with SP2?
Thanks,
Scott
1. SQL server installable is never like this so this is installation package for SQL server 2008 R2 SP1 for sure . Just take KB2528583( Knowledge base) and search in Google it will show you.
2. SQL Server is released as RTM( release to manufacture) after its released general user reports or Microsoft team works out on Issues if any and release Service pack. When you apply SP your SQL Server gets upgraded to that SP version.
You can download
SQL server 2008 R2 SP2 here
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

Install SQL Server 2008 R2 in Windows Server 2012 using SQL4SAP Script

Hi guys,
Since we are performing a SAP System Migration from older releases of Windows/SQL Server, as detailed on SAP Note
1780433 - System copy of SAP systems on Windows 2012 : SQL Server
We need to install SQL Server 2008 R2 before upgrading the system
When running SQL4SAP Script it states the following
17/03/2014 08:13:44 p.m.
Message Box "Windows version error"
OS Family "WindowsNT6.3" is not supported by this script.
Result: vbOK
On Windows 2012 should i run the SETUP instead the script?
Thanks!

Hi Sunny
Im following SAP Note 1780433 - System copy of SAP systems on Windows 2012 : SQL Server
in order to migrate a SAP 640 system from Windows 2003/SQL Server 2005 to Windows 2012/ SQL Server 2012
Reason and Prerequisites
This note describes how to migrate the mentioned SAP products to Windows 2012/SQL Server 2008 R2,
in order to prepare an upgrade to SAP releases based on NW 7.0 and higher.
Note, that only SAP upgrade paths are supported, that are supported by the SUM tool. For more
information about the upgrade paths supported by SUM, read the Central SUM Note referred to at
http://www.service.sap.com/SLToolset.
Immediately after the SAP upgrade, your database has to be upgraded to SQL Server 2012. SAP does in general not support SQL Server releases prior to SQL Server 2012 on Windows 2012.
I understand this is not supported from Productive system, we are performing this on a Development system for test purposes.
Nevertheless on the note says Install First SQL Server 2008 R2 and after SAP upgrade, perform upgrade of SQL Server Upgrade, so there is misleasing information.
Im not sure if a 640 System would be able to copied and upgraded in Windows 2012/SQL Server 2012
It doesnt mention that 640_EX2 Kernel Support SQL Server 2012 to install the system.
How would yo recommend a system copy restoring database on these conditions?
640 System (SQL Server 2005,Win 2003) --> 640 System (SQL Server 2012, Win 2012)
(and then Upgrading to 740)
Thanks

How can install SQL Server 2008 Integration Services without CD?

Similar Messages

Maybe you are looking for