I Am Getting Failed Notifications When Installing SQL SERVER 2008 can any one suggest me Wt can i do
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068643839
Exit facility code: 1203
Exit error code: 1
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2014-03-07 08:24:10
End time: 2014-03-07 09:07:13
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.1600.22%26EvtType%3d0xC71AA851%400x73BA6908
Machine Properties:
Machine name: HOME
Machine processor count: 1
OS version: Windows XP
OS service pack: Service Pack 3
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 0
Installation location: E:\Projects\Sqlserver2008\x86\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: NT AUTHORITY\SYSTEM
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: HOME\Administrator
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\ConfigurationFile.ini
ENABLERANU: False
ERRORREPORTING: False
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,SNAC_SDK,OCS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
MEDIASOURCE: E:\Projects\Sqlserver2008\
NPENABLED: 0
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: HOME\Administrator
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: Analysis Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_as_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_as_Cpu32_1.log
MSI error description:
MSI status: Failed: see details below
MSI error code: 0xB8A6B4FA
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\sql_engine_core_inst_Cpu32_1.log
MSI error description:
Configuration status: Failed: see details below
Configuration error code: 0xEEBAE95A
Configuration error description: Unable to get installer types in the C:\Program Files\Microsoft SQL Server\100\Tools\Binn\Microsoft.SqlServer.Management.PSSnapins.dll assembly.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\Detail.txt
Feature: Integration Services
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: 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: Passed
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Books Online
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140307_082135\SystemConfigurationCheck_Report.htm
Hello,
Please check below link
http://support.microsoft.com/kb/955403/en-gb
SQL Server enterprise edition is not supported on Windows XP.You can install but its not supported by Microsoft.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
Similar Messages
-
Error received when installing SQL Server 2008 R2 Express
I receive the following error when I try to install SQL Server 2008 R2 Express-
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. (C:\Users\rhaas\AppData\Local\Microsoft_Corporation\LandingPage.exe_StrongName_ryspccglaxmt4nhllj5z3thycltsvyyx\10.0.0.0\user.config line 5) ---> System.IO.FileNotFoundException:
Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
File name: 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
at System.Configuration.TypeUtil.GetTypeWithReflectionPermission(IInternalConfigHost host, String typeString, Boolean throwOnError)
at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.Init(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.InitWithRestrictedPermissions(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory..ctor(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
at System.Configuration.RuntimeConfigurationRecord.CreateSectionFactory(FactoryRecord factoryRecord)
at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
--- End of inner exception stack trace ---
at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey, Boolean getLkg, Boolean checkPermission)
at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
at System.Configuration.ConfigurationManager.GetSection(String sectionName)
at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
at System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName)
at System.Configuration.SettingsBase.get_Item(String propertyName)
at System.Configuration.ApplicationSettingsBase.GetPropertyValue(String propertyName)
at System.Configuration.ApplicationSettingsBase.get_Item(String propertyName)
at Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings.get_WindowPlacement()
at Microsoft.SqlServer.Configuration.LandingPage.LandingPageForm.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase:
file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
LandingPage
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase:
file:///c:/976a3a4150b5ddedc8968e5dee63fa41/x86/LandingPage.exe
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase:
file:///C:/windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase:
file:///C:/windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase:
file:///C:/windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
Microsoft.SqlServer.Configuration.Sco
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase:
file:///c:/976a3a4150b5ddedc8968e5dee63fa41/x86/Microsoft.SqlServer.Configuration.Sco.DLL
Microsoft.SqlServer.Chainer.Infrastructure
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase:
file:///c:/976a3a4150b5ddedc8968e5dee63fa41/x86/Microsoft.SqlServer.Chainer.Infrastructure.DLL
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase:
file:///C:/windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase:
file:///C:/windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
Microsoft.SqlServer.Management.Controls
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase:
file:///c:/976a3a4150b5ddedc8968e5dee63fa41/x86/Microsoft.SqlServer.Management.Controls.DLL
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase:
file:///C:/windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Does anyone have any ideas on how to proceed? Installing will not complete.Hi Balmukund!
Thanks for your help. I did rename both folders to a generic name (rename_folder_1 & rename_folder_2) and the install failed again. Did I rename the folders in a correct manner? Below is a copy of the user.config file referenced in
your post above. Any additional direction would be very helpful.
Thanks!
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
<section name="Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
allowExeDefinition="MachineToLocalUser" requirePermission="false" />
</sectionGroup>
</configSections>
<userSettings>
<Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings>
<setting name="WindowPlacement" serializeAs="Xml">
<value>
<WINDOWPLACEMENT xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<showCmd>3</showCmd>
<ptMinPosition>
<x>-1</x>
<y>-1</y>
</ptMinPosition>
<ptMaxPosition>
<x>-1</x>
<y>-1</y>
</ptMaxPosition>
<rcNormalPosition>
<left>0</left>
<top>0</top>
<right>800</right>
<bottom>600</bottom>
</rcNormalPosition>
</WINDOWPLACEMENT>
</value>
</setting>
</Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings>
</userSettings>
</configuration> -
Unhandled exception when installing SQL Server 2008 R2
I tried to download SQL Server 2008 R2 Express it ran for about 30 minutes and then gave a Net Framework error stating that "an Unhandled exception has occurred in your
application. If you click Continue, the application will ignore this error and attempt to continue....." Once I clicked Continue and it did continue to run and then brought up an info screen with no semblance of the download having worked. I had successfully
installed SQL Server 2005 Express previously. I uninstalled it along with the Studio Manager. Do I need to uninstall .NET Framework 3.5 SP1 and .NET Framework 4 Client Profile which are still currently installed before I can install 2008?Sorry I have to reopen this. But I have a similar, but not the same problem.
I have Windows 7 64bit Ultimate, with VS 2010 professional on my notebook, quad core processor with 8gb of ram and plenty of disk space. I am trying to install SQL Server 2008 R2 Developer edition on my computer. .Net 4.0 was installed, as was .Net 3.5.1
(from the "Turn Windows Features On/Off" of Programs and Features Control Panel applet).
When I try to install, I get a Dialog labelled "Microsoft .NET Framework", then the error is "Unhandled exception has occurred in your application. If you click on Continue, the application will ignore this error and attempt to continue. If you click Quit,
the application will close immediately. <p> An error occurred create the configuration section handler for userSettings/Microsoft.SqlServer. Configuration.LandingPage.Properties.Settings: Could not load file or assembly 'System.Version=4.0.0.0.Culture-neutral.
PublicKey Token-b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. (C:\users\myname\AppData\Local\Microsoft_Corporation\Landing Page.exe_StrongName_rspccglaxmt4nhlj5z3thycltsvyyx\10.0.0.0\user. config
I have removed .Net 4, I have removed .Net 3.5.1 and readded it, rebooting after each step.
any help on this would be appreciated.
Thanks -
Error when installing SQL Server 2008 R2 after downloading
Hi -I hope somebody can help me.
I have tried to install nopCommerce with no luck. I am not able to establish the SQL database. I have tried to solve the problem for a very long time, also with no luck. Now I think it has to do with an error that come when I installed the SQL Server 2008
R2.
I have tried to load a picture here, but was denied.
with hopes for help
Regards Egil Ryengen
The error text is as followed:
Unhandled exception has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. You click Quit, the application will close immediately.
An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer/Configuration/LandingPage/Properties.Settings: not load file or assambly "System, Version =4.0.0.0,
Culture=neutral. Public Key Token=b77a5c561934e089" or one of its dependencies. The system cannot find the file specified.
(C:/Users/EgilRyengen/AppData/Local/Microsoft_Corporation/LandingPage.exe_StrongName_ryspccglaxmt4nhllj5z3thycltsvyyx/10.0.0.0/user.coUnhandled exception has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. You click Quit, the application will close immediately.
An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer/Configuration/LandingPage/Properties.Settings: not load file or assambly "System, Version =4.0.0.0,
Culture=neutral. Public Key Token=b77a5c561934e089" or one of its dependencies. The system cannot find the file specified.
(C:/Users/EgilRyengen/AppData/Local/Microsoft_Corporation/LandingPage.exe_StrongName_ryspccglaxmt4nhllj5z3thycltsvyyx/10.0.0.0/user.co
Did you read hardware and software requirements before installing SQL Server 2008 R2. I guess you are missing .Net framework. AS per
This Doc
You need to download and install .Net framework 3.5 SP1 and requirement is more if you are installing express edition. Its all mentioned in link
You can also refer to
this Thread it has same issue as you are having
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 Article
MVP -
Facing problem when install sql server 2008 on windows7
Hi I installed sqlserver 2008 on windows7 ultimate sp1 then i got one error like below
MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{64CDE8F2-3791-46F5-BAD2-72FFF5252FAB}'. Error code: 1608..
how to rectify this error please help me...
Thanks in advanceThere are some blogs/msdn posts talking about the same issue and below are the links
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/66a2044c-7251-466b-9b22-40d155ed949b/sql-server-2008-setup-fails-on-windows-7-enterprise-error-code-1608?forum=sqlgetstarted
http://superuser.com/questions/414795/error-code-1608-during-sql-server-install
http://gaurangpatel.net/solving-msigetproductinfo-failed-to-retrieve-productversion-for-package-with-product-code-8bdd006d-d5f0-4aaa-ba13-65995063ec44-error-code-1608
Hope it Helps!! -
In that system Microsoft Framework 4.o and 3.5.1 is installed even then i am getting the error then i uninstalled and again installed framework same error occurring.
Hi Chandra,
As other post, please help to post the summary and detail logs for analysis.
Based on my knowledge, the error “unhandled exception has occurred in your application” always happens along with the following message when installing SQL Server 2008 R2:
“An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
or one of its dependencies. The system cannot find the file specified. “
If you encounter such issue, please perform the following steps to solve it.
1.Go to your app data directory by going to start > run > %appdata% .
2.This will by default take you to the "roaming" folder, go up one directory and move into the "Local" folder.
3. Go to the "Microsoft_Corporation" folder.
4. Delete the relevant folders from the "Microsoft_Corporation" folder.
For more details, please review the following blog.
SQL Server 2008 R2 will not install - Unhandled Exception has occurred in your application
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support -
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: Passedmy 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 -
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 bitHi 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 -
Error message when installing SQL Server 2014 Express
When installing SQL Server 2014 Express,
I get the error shown below.
Why do I get this and how to correct for it?
TITLE: Microsoft SQL Server 2014 Setup
The following error has occurred:
An error occurred during the installation of assembly 'Microsoft.VC80.MFC,version="8.0.50727.4027",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'. Please refer to Help and Support for more
information. HRESULT: 0x80070422.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xDF039760%25401201%25401
BUTTONS:
OK
ThanksHi,
here is the log file:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068052081
Start time: 2015-04-14 10:25:00
End time: 2015-04-14 10:38:21
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for Conn: Use the following information to resolve the error, and then try the setup process again.
Next step for SDK: Use the following information to resolve the error, and then try the setup process again.
Next step for BC: Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Next step for Browser: Use the following information to resolve the error, and then try the setup process again.
Next step for ComponentUpdate: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: BRENDA-PC-HOME
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: italiano (Italia)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Users\Brenda\Downloads\SQLEXPRWT_x64_ENU\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\SERVIZIO DI RETE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, CONN, BC, SDK, SSMS, ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
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\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: Brenda-PC-Home\Brenda
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: true
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: SQL Browser
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Feature: Setup Support Files
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Setup Support Files
Component error code: 1935
Component log file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SqlSupport_Cpu64_1.log
Error description: An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.6229",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32"'.
Please refer to Help and Support for more information. HRESULT: 0x80070422.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=SqlSupport.msi%40CreateShortcuts%401935%3a0x80070422
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150414_102458\SystemConfigurationCheck_Report.htm -
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 -
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,
RajHello 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 -
When installing SQL Server under feature selection you are given the option to change the Shared feature directories. When you choose to change from the default OS drive it seems that the installation
process still installs a large amount of files on the OS drive and then additional files under a similar drive structure on the alternative drive. Is there any real benefit to changing the default location?
Additional is there benefit to changing the default location for the installed features, database engine etc. We are trying to create some clean templates that we can bring up in our production
environment so we are provisioning separate drives for data, logs, backups, tempdbs but as we use the prepare image it seems like splitting the installation of sql server into two separate locations to safe minimally on file space seems counterproductive.
I have searched for best practices and this area seems glossed over in most articles, I found a few that indicate later installation of features on a machine that use a non-standard shared component
drive has caused issues. I would like to know there are benefits to taking such actions.
Thanks in advance,
DirkHello,
The best reason I can think about installing SQL Server binaries on another drive different than the system drive is the
fact the page file (pagefile.sys) is located on the system drive by default. The more I/O I can prevent happening on that drive the better for the performance of operating system.
SQL Server still installs some binaries on the system drive anyway, and creating a partition for SQL Server binaries alone
may seem like a waste.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Unable to install SQL server 2008 r2 standard edition on windows server 2008 r2 sp1
I am unable to install sql server 2008 r2 standard edition on windows server 2008 r2 sp1.
On the Setup Support Files page, choose Install this step I don't get any other window i.e. nothing happens I waited for 5-10 min. Then I checked the log file.
Final result: Failed: see details below
Exit code (Decimal): -2068053929
Exit facility code: 1212
Exit error code: 87
Exit message: Failed: see details below
Start time: 2014-03-18 14:59:31
End time: 2014-03-18 15:00:25
=== Verbose logging started: 3/19/2014 9:45:47 Build type: SHIP UNICODE 5.00.7601.00 Calling process: E:\SQL Server 2008 R2 Standard\x64\setup100.exe ===
MSI (c) (10:34) [09:45:47:496]: Note: 1: 2203 2: E:\SQL Server 2008 R2 Standard\x64\redist\watson\dw20sharedamd64.msi 3: -2147287038
MSI (c) (10:34) [09:45:47:496]: MsiOpenPackageEx is returning 2.
=== Verbose logging stopped: 3/19/2014 9:45:47 ===
Please help As i am running out of time as i have to upgrade TFS for that first step is to install SQL server.Hello,
The following are a few things you can try:
Copy the media to the local disk drive, unzip it (in case you are installing from an ISO file, and run SQL Server setup from there.
Try to unregister and register the Windows Installer with the following two commands:
msiexec /unregister
msiexec /regserver
Try to use Process Monitor to log the detailed error produced when the installation of dw20sharedamd64.msi fails. You can download Process Monitor from the following link:
http://technet.microsoft.com/en-us/sysinternals/bb896645
Share with us the error captured by Process Monitor.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
I've been trying fresh installation of SQL Server 2008 R2 enterprise on Windows Server 2012 R2 standard VM server several times for two weeks, but always get the error "Attempted to perform an unauthorized operation". At first, I attempted
to install all features, but failed several times. So I decided to try install just Database Engine service, and still fail at the SqlBrowserConfigAction_Install_ConfigNonRC_Cpu32, with the error "Attempted to perform an unauthorized operation".
I remote login to server with my admin domain account. This account is in server local Administrators group. I
1. Right-click on setup.exe file | properties | Compatibility tab | select compatibility to Windows 8.Then click OK.
2. Right-click on setup.exe file | Run as Administrator, to start the Installation Center.
I have the document of my installation steps and zip file of the installation logs, if you need to take a look.
Appreciate for any help!
ntthHi ntth,
"Attempted to perform an unauthorized operation"
The above error is always related to the Windows account SID mapping. I recommend you login into Windows using another Windows account which has administrative privileges and run SQL Server setup using that Windows account.
Besides, please note that we need to apply SQL Server 2008 R2 Service Pack 2 or a later update when installing SQL Server Windows Server 2012 R2. For more information, please review this
KB article.
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support -
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 ManneHi 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
Maybe you are looking for
-
How many Apps can I install on my iPhone at the same time?
I've installed over 100 apps (108 exactly) & do not know how many Apps can be installed on iPhone? does it have a limit of amount of Apps can be installed on iPhone?
-
HI, I am facing a problem of gc buffer busy waits and log file switch completion on my live rac database of two nodes. Thank you for your cooperation. Regards, Adnan Hamdus Salam
-
Changing the Name of Text Links to a File
I happily discovered that iWeb will create download links to files such as text, spreadsheet, word processing, PDF, and the like, if you zip them. However, when I create a text link to a file, the linked text takes on the name of the file, such as Yo
-
How do I remove a blank page from a section of 4 pages? (Pages)
1 page (page 4) in a section of 4 pages is blank. How do I remove that page only? I followed the help instructions; but was asked if I was sure I want to delete pages 1-4.
-
Crashes when importing any video format
Hello! So I recently (Christmas last year) got a new computer Windows 7 8GB Ram 64bit and well I installed Premiere Pro (Creative cloud) but there is a slight issue which is very annoy and should not happen at all Premiere crashes whenever I try to i