Install sql server 2008 r2 in windows xp service pack3 gives error
After Installing Support Files, a pop up occurs stating that Microsoft SQL Server 2008 R2 installation has encountered an error.
Error Signature: EventType : sql100msi P1 : 10.50.1600.1 P2 : 10.50.1600.1
P3 : sqlncli.msi P4 : 0x2d2816fe P5 : 0x1603 P6 : install_sqlncli can anyone help me
Hello people. I am having much problem trying to get the SQL installed on my computer.
I just added half of error log:
=== Verbose logging started: 5/1/2014 13:27:12 Build type: SHIP UNICODE 4.05.6001.00 Calling process: f:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe
===
MSI (c) (94:CC) [13:27:12:770]: Resetting cached policy values
MSI (c) (94:CC) [13:27:12:770]: Machine policy value 'Debug' is 0
MSI (c) (94:CC) [13:27:12:770]: ******* RunEngine:
******* Product: f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi
******* Action:
******* CommandLine: **********
MSI (c) (94:CC) [13:27:12:770]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (94:CC) [13:27:12:770]: Grabbed execution mutex.
MSI (c) (94:CC) [13:27:12:770]: Cloaking enabled.
MSI (c) (94:CC) [13:27:12:770]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (94:CC) [13:27:12:770]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (2C:A0) [13:27:12:833]: Running installation inside multi-package transaction f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi
MSI (s) (2C:A0) [13:27:12:833]: Grabbed execution mutex.
MSI (s) (2C:6C) [13:27:12:848]: Resetting cached policy values
MSI (s) (2C:6C) [13:27:12:848]: Machine policy value 'Debug' is 0
MSI (s) (2C:6C) [13:27:12:848]: ******* RunEngine:
******* Product: f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi
******* Action:
******* CommandLine: **********
MSI (s) (2C:6C) [13:27:12:848]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (2C:6C) [13:27:13:379]: File will have security applied from OpCode.
MSI (s) (2C:6C) [13:27:13:629]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi' against software restriction policy
MSI (s) (2C:6C) [13:27:13:645]: SOFTWARE RESTRICTION POLICY: f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi has a digital signature
MSI (s) (2C:6C) [13:27:13:942]: SOFTWARE RESTRICTION POLICY: f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (2C:6C) [13:27:13:942]: End dialog not enabled
MSI (s) (2C:6C) [13:27:13:942]: Original package ==> f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi
MSI (s) (2C:6C) [13:27:13:942]: Package we're running from ==> f:\WINDOWS\Installer\250ed1.msi
MSI (s) (2C:6C) [13:27:13:958]: APPCOMPAT: looking for appcompat database entry with ProductCode '{4AB6A079-178B-4144-B21F-4D1AE71666A2}'.
MSI (s) (2C:6C) [13:27:13:958]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (2C:6C) [13:27:13:973]: MSCOREE not loaded loading copy from system32
MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'TransformsSecure' is 0
MSI (s) (2C:6C) [13:27:13:989]: User policy value 'TransformsAtSource' is 0
MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'DisablePatch' is 0
MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (2C:6C) [13:27:13:989]: APPCOMPAT: looking for appcompat database entry with ProductCode '{4AB6A079-178B-4144-B21F-4D1AE71666A2}'.
MSI (s) (2C:6C) [13:27:13:989]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (2C:6C) [13:27:14:004]: Transforms are not secure.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'F:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140501_131426\sqlncli_Cpu32_1.log'.
MSI (s) (2C:6C) [13:27:14:004]: Command Line: ADDLOCAL=SQL_SNAC_CORE,SQL_SNAC_SDK INSTALLSQLSHAREDDIR_32=F:\Program Files\Microsoft SQL Server\ IACCEPTSQLNCLILICENSETERMS=YES REBOOT=ReallySuppress MEDIAPACKAGEPATH=\1033_ENU_LP\x86\setup\x86\ EXTERNALMSICONTROL=1
CURRENTDIRECTORY=f:\41ab42c0be4c457100b4 CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=3988
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{79872AB7-3F02-4F99-BDA4-03BBC4644342}'.
MSI (s) (2C:6C) [13:27:14:004]: Product Code passed to Engine.Initialize: ''
MSI (s) (2C:6C) [13:27:14:004]: Product Code from property table before transforms: '{4AB6A079-178B-4144-B21F-4D1AE71666A2}'
MSI (s) (2C:6C) [13:27:14:004]: Product Code from property table after transforms: '{4AB6A079-178B-4144-B21F-4D1AE71666A2}'
MSI (s) (2C:6C) [13:27:14:004]: Product not registered: beginning first-time install
MSI (s) (2C:6C) [13:27:14:004]: Product {4AB6A079-178B-4144-B21F-4D1AE71666A2} is not managed.
MSI (s) (2C:6C) [13:27:14:004]: MSI_LUA: Credential prompt functionality not available on this operating system
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
MSI (s) (2C:6C) [13:27:14:004]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (2C:6C) [13:27:14:004]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (2C:6C) [13:27:14:004]: Adding new sources is allowed.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
MSI (s) (2C:6C) [13:27:14:004]: Package name extracted from package path: 'sqlncli.msi'
MSI (s) (2C:6C) [13:27:14:004]: Package to be registered: 'sqlncli.msi'
MSI (s) (2C:6C) [13:27:14:004]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (2C:6C) [13:27:14:004]: Machine policy value 'DisableMsi' is 0
MSI (s) (2C:6C) [13:27:14:004]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (2C:6C) [13:27:14:004]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (2C:6C) [13:27:14:004]: Product installation will be elevated because user is admin and product is being installed per-machine.
MSI (s) (2C:6C) [13:27:14:004]: Running product '{4AB6A079-178B-4144-B21F-4D1AE71666A2}' with elevated privileges: Product is assigned.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding ADDLOCAL property. Its value is 'SQL_SNAC_CORE,SQL_SNAC_SDK'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding INSTALLSQLSHAREDDIR_32 property. Its value is 'F:\Program Files\Microsoft SQL Server\'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding IACCEPTSQLNCLILICENSETERMS property. Its value is 'YES'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding MEDIAPACKAGEPATH property. Its value is '\1033_ENU_LP\x86\setup\x86\'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding EXTERNALMSICONTROL property. Its value is '1'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'f:\41ab42c0be4c457100b4'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '3988'.
MSI (s) (2C:6C) [13:27:14:004]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
MSI (s) (2C:6C) [13:27:14:004]: DisableAutomaticApplicationShutdown system policy is ignored on this version of Windows.
MSI (s) (2C:6C) [13:27:14:004]: TRANSFORMS property is now:
MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '300'.
MSI (s) (2C:6C) [13:27:14:004]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Application Data
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Favorites
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\NetHood
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\My Documents
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\PrintHood
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Recent
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\SendTo
MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Templates
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Application Data
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Local Settings\Application Data
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\My Documents\My Pictures
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Start Menu\Programs\Startup
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Start Menu\Programs
MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Start Menu
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Desktop
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Start Menu\Programs\Administrative Tools
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Start Menu\Programs\Startup
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Start Menu\Programs
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Start Menu
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Desktop
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Templates
MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\WINDOWS\Fonts
MSI (s) (2C:6C) [13:27:14:051]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
Similar Messages
-
Error while installing SQL Server 2008 R2 in Windows 7 SP1 machine
Hi Team,
Error while installing SQL Server 2008 R2 in Windows 7 SP1 machine. I can confirm this machine has .Net
Feature enabled and with Latest version.
TITLE: Microsoft SQL Server 2008 R2 Setup
The following error has occurred:
Error 25541.Failed to open XML file C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config, system error: -2147024786
Regards,
Muthukumar.S.P.Hi,
Can you follow workaround mentioned in below msdn blog
http://blogs.msdn.com/b/astebner/archive/2007/11/01/5826719.aspx
As per the blog you have to open the msi log files which must be located at
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log
In MSI log files search for the error mentioned in blog. Below link will help you read setup log files
http://msdn.microsoft.com/en-gb/library/ms143702%28v=sql.105%29.aspx
PS: Please read links carefully and patiently and if it does not solves issue please post summary.txt file and details.txt file on skydrive for analysis
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 Articles -
How to install SQL server 2008 express on Windows server 2008 R2 standard OS
Hi,
I have Windows server 2008 R2 Standard edition (64-bit) and trying to install SQL server 2008 express edition since I do not have SQL server 2008. When I install it I am unable to see Management Studio so I am trying to install management studio as well
but still I am facing issue. Please let me know whether SQL server 2008 express edition is compatible with Windows server 2008 R2 Standard. If not then pls let me know the proper steps to install it.
RegdsHello,
Service Pack 1 for SQL Server 2008 is required to be compatible with Windows Server 2008 R2.
Please download QL Server 2008 Express with SP1 included from the following link:
http://www.microsoft.com/en-us/download/details.aspx?id=25052
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
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 -
Install SQL Server 2008 R2 in Windows Server 2012 using SQL4SAP Script
Hi guys,
Since we are performing a SAP System Migration from older releases of Windows/SQL Server, as detailed on SAP Note
1780433 - System copy of SAP systems on Windows 2012 : SQL Server
We need to install SQL Server 2008 R2 before upgrading the system
When running SQL4SAP Script it states the following
17/03/2014 08:13:44 p.m.
Message Box "Windows version error"
OS Family "WindowsNT6.3" is not supported by this script.
Result: vbOK
On Windows 2012 should i run the SETUP instead the script?
Thanks!Hi Sunny
Im following SAP Note 1780433 - System copy of SAP systems on Windows 2012 : SQL Server
in order to migrate a SAP 640 system from Windows 2003/SQL Server 2005 to Windows 2012/ SQL Server 2012
Reason and Prerequisites
This note describes how to migrate the mentioned SAP products to Windows 2012/SQL Server 2008 R2,
in order to prepare an upgrade to SAP releases based on NW 7.0 and higher.
Note, that only SAP upgrade paths are supported, that are supported by the SUM tool. For more
information about the upgrade paths supported by SUM, read the Central SUM Note referred to at
http://www.service.sap.com/SLToolset.
Immediately after the SAP upgrade, your database has to be upgraded to SQL Server 2012. SAP does in general not support SQL Server releases prior to SQL Server 2012 on Windows 2012.
I understand this is not supported from Productive system, we are performing this on a Development system for test purposes.
Nevertheless on the note says Install First SQL Server 2008 R2 and after SAP upgrade, perform upgrade of SQL Server Upgrade, so there is misleasing information.
Im not sure if a 640 System would be able to copied and upgraded in Windows 2012/SQL Server 2012
It doesnt mention that 640_EX2 Kernel Support SQL Server 2012 to install the system.
How would yo recommend a system copy restoring database on these conditions?
640 System (SQL Server 2005,Win 2003) --> 640 System (SQL Server 2012, Win 2012)
(and then Upgrading to 740)
Thanks -
Installing SQL Server 2008 Express on windows 2000 server ?
Is is possible to install SQL Express 2008 on a Windows 2000 machine. Has anybody come across any issues doing this. any advice would appreciated.
Thanks in advance
Jayce.Hi Jayce,
The web page "Hardware and Software Requirements for Installing SQL Server 2008 R2" does not list Windows 2000 as a compatability option as follows; -
http://msdn.microsoft.com/en-us/library/ms143506.aspx#Express32
The earliest desktop operating system listed is Windows XP.
So I understand you can't successfully install SQL Express 2008 on a Windows 2000 machine.
Kind Regards,
Kieran.
If you have found any of my posts helpful then please vote them as helpful. Kieran Wood PGD SoftDev (Open), MBCS http://uk.linkedin.com/in/bileeds -
Is it possible to install Microsoft SQL Server 2008 Express on windows server 2012 (not R2) ?
I read this kb - http://support.microsoft.com/kb/2681562/en-us, but doesn't get exact answer.
I need to install vWorkspace 8 on server w2k12. It install SQL Server 2008 Express during installation and I got error.
So, is it possible to install Microsoft SQL Server 2008 (R2) Express on windows server 2012 (not R2) ?I read this kb - http://support.microsoft.com/kb/2681562/en-us, but doesn't get exact answer.
I need to install vWorkspace 8 on server w2k12. It install SQL Server 2008 Express during installation and I got error.
So, is it possible to install Microsoft SQL Server 2008 (R2) Express on windows server 2012 (not R2) ?
Yes you can install SQL server 2008 express on windows 2012 OS see below link
http://msdn.microsoft.com/en-us/library/ms143506(v=sql.100).aspx#Express32
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
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 -
SQL Server 2008 Installation on Windows 7
I tried to install SQL Server 2008 on a Windows 7 Home Premium 64 bit (Enterprise Edition Trial Edition). The system check was ok and the installation started successfully but at the end there were some errors. In the logfile there were stacktraces describing failures trying write operations on the registry. What can I do to install SQL Server 2008 on my operating system?
Hello ChunSong Feng,
thanks for your advice. Herewith I send you the text parts from detail.txt with the detailed error description. The whole file is too big to send as content.
Thanks in advance:
2009-11-17 21:05:10 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned: D:(A;CI;KR;;;S-1-5-21-2556463381-1186548668-390171815-1028)
2009-11-17 21:05:10 Slp: Prompting user if they want to retry this action due to the following failure:
2009-11-17 21:05:10 Slp: ----------------------------------------
2009-11-17 21:05:10 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2009-11-17 21:05:10 Slp: Inner exceptions are being indented
2009-11-17 21:05:10 Slp:
2009-11-17 21:05:10 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
2009-11-17 21:05:10 Slp: Message:
2009-11-17 21:05:10 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
2009-11-17 21:05:10 Slp: Data:
2009-11-17 21:05:10 Slp: WatsonData = Microsoft SQL Server
2009-11-17 21:05:10 Slp: DisableRetry = true
2009-11-17 21:05:10 Slp: Inner exception type: System.UnauthorizedAccessException
2009-11-17 21:05:10 Slp: Message:
2009-11-17 21:05:10 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
2009-11-17 21:05:10 Slp: Stack:
2009-11-17 21:05:10 Slp: bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
2009-11-17 21:05:10 Slp: bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
2009-11-17 21:05:10 Slp: bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
2009-11-17 21:05:10 Slp: bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
2009-11-17 21:05:10 Slp: bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
2009-11-17 21:05:10 Slp: ----------------------------------------
2009-11-17 21:05:28 Slp: User has chosen to cancel this action
2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2009-11-17 21:05:44 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
2009-11-17 21:05:45 Slp: Watson bucket for exception based failure has been created
2009-11-17 21:05:45 SQLBrowser: SQL Server Browser Install for feature 'SQL_Browser_Redist_SqlBrowser_Cpu32' failed with cancel exception: Microsoft.SqlServer.Configuration.Sco.ScoException: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen. ---> System.UnauthorizedAccessException: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
--- Ende der internen Ausnahmestapelüberwachung ---
bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
bei Microsoft.SqlServer.Configuration.Sco.SqlRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.SetSecurityDescriptorByLocation(String sRegLocation, RegistryView regView, String sSddl, Boolean bOptional)
bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.ApplyRegPermissions(XmlNodeList xmlNodeListRegPermissions, Dictionary`2 dictionaryGroups, Dictionary`2 dicLocationFragments)
bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ApplyRegCommonPermissions(XmlElement xmlRootPermissions, Dictionary`2 dictionaryGroups, Dictionary`2 dicLocationFragments)
bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ApplyPermissions(String sXmlPermissionsFile, String sBrowserPrincipal)
bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ConfigStaticProperties(SqlBrowserPublicConfig publicConfigSqlBrowser)
bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ExecConfigNonRC(SqlBrowserPublicConfig publicConfigSqlBrowser)
bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.SelectAndExecTiming(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig)
bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.ExecWithRetry(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig).
2009-11-17 21:05:45 SQLBrowser: The last attempted operation: Der '(A;CI;KR;;;[SQLServer2005SQLBrowserUser$UTAS-URMEL])'-Zugriffssteuerungseintrag wird dem Registrierungsschlüssel 'SOFTWARE\Microsoft\Microsoft SQL Server' in der 'Wow6432'-Sicht hinzugefügt, um den SQL Server Browser-Dienst zu konfigurieren..
2009-11-17 21:05:45 Slp: Fehler bei der Konfigurationsaktion für Feature SQL_Browser_Redist während der Zeitangabe ConfigNonRC und Szenario ConfigNonRC.
2009-11-17 21:05:45 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
2009-11-17 21:05:45 Slp: Fehler bei der Konfigurationsaktion für Feature SQL_Browser_Redist während der Zeitangabe ConfigNonRC und Szenario ConfigNonRC.
2009-11-17 21:05:45 Slp: Microsoft.SqlServer.Configuration.Sco.ScoException: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen. ---> System.UnauthorizedAccessException: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
2009-11-17 21:05:45 Slp: bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
2009-11-17 21:05:45 Slp: bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
2009-11-17 21:05:45 Slp: --- Ende der internen Ausnahmestapelüberwachung ---
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.Sco.SqlRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.SetSecurityDescriptorByLocation(String sRegLocation, RegistryView regView, String sSddl, Boolean bOptional)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.ApplyRegPermissions(XmlNodeList xmlNodeListRegPermissions, Dictionary`2 dictionaryGroups, Dictionary`2 dicLocationFragments)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ApplyRegCommonPermissions(XmlElement xmlRootPermissions, Dictionary`2 dictionaryGroups, Dictionary`2 dicLocationFragments)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ApplyPermissions(String sXmlPermissionsFile, String sBrowserPrincipal)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ConfigStaticProperties(SqlBrowserPublicConfig publicConfigSqlBrowser)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ExecConfigNonRC(SqlBrowserPublicConfig publicConfigSqlBrowser)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.SelectAndExecTiming(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.ExecWithRetry(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
2009-11-17 21:05:45 Slp: bei Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
2009-11-17 21:05:45 Slp: Ausnahme: Microsoft.SqlServer.Configuration.Sco.ScoException.
2009-11-17 21:05:45 Slp: Quelle: Microsoft.SqlServer.Configuration.Sco.
2009-11-17 21:05:45 Slp: Meldung: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen..
2009-11-17 21:05:45 Slp: Innere Ausnahme:
2009-11-17 21:05:45 Slp: Ausnahme: System.UnauthorizedAccessException.
2009-11-17 21:05:45 Slp: Quelle: mscorlib.
2009-11-17 21:05:45 Slp: Meldung: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen..
2009-11-17 21:05:45 Slp: Completed Action: SqlBro
2009-11-17 21:05:50 Slp: Prompting user if they want to retry this action due to the following failure:
2009-11-17 21:05:50 Slp: ----------------------------------------
2009-11-17 21:05:50 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2009-11-17 21:05:50 Slp: Inner exceptions are being indented
2009-11-17 21:05:50 Slp:
2009-11-17 21:05:50 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
2009-11-17 21:05:50 Slp: Message:
2009-11-17 21:05:50 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
2009-11-17 21:05:50 Slp: Data:
2009-11-17 21:05:50 Slp: WatsonData = 100
2009-11-17 21:05:50 Slp: DisableRetry = true
2009-11-17 21:05:50 Slp: Inner exception type: System.UnauthorizedAccessException
2009-11-17 21:05:50 Slp: Message:
2009-11-17 21:05:50 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
2009-11-17 21:05:50 Slp: Stack:
2009-11-17 21:05:50 Slp: bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
2009-11-17 21:05:50 Slp: bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
2009-11-17 21:05:50 Slp: bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
2009-11-17 21:05:50 Slp: bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
2009-11-17 21:05:50 Slp: bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
2009-11-17 21:05:50 Slp: ----------------------------------------
2009-11-17 21:05:57 Slp: User has chosen to cancel this action
2009-11-17 21:05:58 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2009-11-17 21:06:17 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
2009-11-17 21:06:17 Slp: Watson bucket for exception based failure has been created
2009-11-17 21:06:17 SSIS: Failed to set registry permission on key 'SOFTWARE\Microsoft\Microsoft SQL Server\100' to SID 'S-1-5-21-2556463381-1186548668-390171815-1029'. Error: 'Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.'
2009-11-17 21:06:17 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned: D:(A;OICI;KR;;;S-1-5-21-2556463381-1186548668-390171815-1029)
2009-11-17 21:06:17 Slp: Prompting user if they want to retry this action due to the following failure:
2009-11-17 21:06:17 Slp: ----------------------------------------
2009-11-17 21:06:17 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2009-11-17 21:06:17 Slp: Inner exceptions are being indented
2009-11-17 21:06:17 Slp:
2009-11-17 21:06:17 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
2009-11-17 21:06:17 Slp: Message:
2009-11-17 21:06:17 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
2009-11-17 21:06:17 Slp: Data:
2009-11-17 21:06:17 Slp: WatsonData = SSIS
2009-11-17 21:06:17 Slp: DisableRetry = true
2009-11-17 21:06:17 Slp: Inner exception type: System.UnauthorizedAccessException
2009-11-17 21:06:17 Slp: Message:
2009-11-17 21:06:17 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
2009-11-17 21:06:17 Slp: Stack:
2009-11-17 21:06:17 Slp: bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
2009-11-17 21:06:17 Slp: bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
2009-11-17 21:06:17 Slp: bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
2009-11-17 21:06:17 Slp: bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
2009-11-17 21:06:17 Slp: bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
2009-11-17 21:06:17 Slp: ----------------------------------------
2009-11-17 21:06:24 Slp: User has chosen to cancel this action
2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2009-11-17 21:06:47 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
2009-11-17 21:06:47 Slp: Watson bucket for exception based failure has been created
2009-11-17 21:06:47 SSIS: Failed to set registry permission on key 'SOFTWARE\Microsoft\Microsoft SQL Server\100\SSIS' to SID 'S-1-5-21-2556463381-1186548668-390171815-1029'. Error: 'Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.'
2009-11-17 21:06:47 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib
2009-11-17 21:06:47 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned: D:(A;OICI;KR;;;S-1-5-21-2556463381-1186548668-390171815-1029)(A;CI;KR;;;LU)(A;CI;KR;;;MU)
2009-11-17 21:06:47 Slp: Prompting user if they want to retry this action due to the following failure:
2009-11-17 21:06:47 Slp: ----------------------------------------
2009-11-17 21:06:47 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2009-11-17 21:06:47 Slp: Inner exceptions are being indented
2009-11-17 21:06:47 Slp:
2009-11-17 21:06:47 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
2009-11-17 21:06:47 Slp: Message:
2009-11-17 21:06:47 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
2009-11-17 21:06:47 Slp: Data:
2009-11-17 21:06:47 Slp: WatsonData = Perflib
2009-11-17 21:06:47 Slp: DisableRetry = true
2009-11-17 21:06:47 Slp: Inner exception type: System.UnauthorizedAccessException
2009-11-17 21:06:47 Slp: Message:
2009-11-17 21:06:47 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
2009-11-17 21:06:47 Slp: Stack:
2009-11-17 21:06:47 Slp: bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
2009-11-17 21:06:47 Slp: bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
2009-11-17 21:06:47 Slp: bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
2009-11-17 21:06:47 Slp: bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
2009-11-17 21:06:47 Slp: bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
2009-11-17 21:06:47 Slp: ----------------------------------------
2009-11-17 21:06:52 Slp: User has chosen to cancel this action -
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 -
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 -
Attempted to perform an unauthorized operation error on windows 8.1 while installing SQL server 2008
Hi,
I am getting the error "Attempted to perform an unauthorized operation" on windows 8.1 while installing
SQL server 2008.
The specific error is The error is Attempted to perform an unauthorized operation."
at stepSqlBrowserConfigAction_install_ConfigNonRC_Cpu32 .
I have tried everything from copying to the C drive. I am the admin on the machine. I also checked access in registry. It already has acesss to HKLM\System\CurrentControlSet\Control\WMI\security
Can someone comment on how to resolve this issue. I also tried NT
AUTHORITY\SYSTEM but getting the same error.
Any help would be appreciated.Hello,
Please note that SQL Server 2008 requires Service Pack 3 (SP3) to make it compatible with
Windows 8.1. Please perform an slipstream installation of SQL Server 2008 + SP3:
http://support.microsoft.com/kb/955392
If it fails again, please share with us the Summary.txt log file and the details.txt log file. The following article
may help you locate those files on disk::
http://msdn.microsoft.com/en-us/library/ms143702(v=sql.100).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Install SQL Server 2008 R2 SP 1 on Windows Server 2012
Dear All,
I've downloaded SQL Server SP1 from this link:
http://www.microsoft.com/en-us/download/details.aspx?id=26727
I downloaded :
SQLServer2008R2SP1-KB2528583-x64-ENU.exe
SQLManagementStudio_x64_ENU.exe
SQLServer2008R2SP1-KB2528583-IA64-ENU.exe
when i run SQLServer2008R2SP1-KB2528583-x64-ENU.exe i have error:
There are no SQL Server instances or shared features that can be updated on this computer
what that i missed? is that i must install SQL Server 2008 R2?
because if i run the SQL Server 2008 R2 there are compatible issue. I run this on Windows Server 2012
Please Help.
Best regards,
SurbaktiHi,
The cause could be an invalid entry in the userSettings section of the Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings file.
Delete this configuartion file or delete the folder "Microsoft_Corporation" and see how it works.
Run the command: rd /s /q %localappdata%\Microsoft_Corporation
For your reference:
http://blogs.msdn.com/b/smondal/archive/2013/07/26/an-error-occurred-creating-the-configuration-section-handler-for-usersettings-microsoft-sqlserver-configuration-landingpage-properties-settings.aspx
Thanks.
Tracy Cai
TechNet Community Support -
Cannot install SQL Server 2008 R2 Developer on Windows 8.1
I am unable to install SQL Server 2008 R2 Developer edition on Windows 8.1 Enterprise evaluation and about 3/4 of the way through the installation I get this error msg:
TITLE: SQL Server 2008 R2 Setup
The following error has occurred:
Attempted to perform an unauthorized operation.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.4000.0&EvtType=0x88792597%25400xBB814387
This is my log file:
Overall summary:
Final result: User cancelled
Exit code (Decimal): 0
Exit message: User cancelled
Start time: 2014-04-23 23:49:10
End time: 2014-04-24 00:03:44
Requested action: Install
Machine Properties:
Machine name: PC
Machine processor count: 2
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 1
Installation location: F:\My Files\My Downloads\EXISTING\SQLServer2008R2Dev\SQLFULL_ENU\x64\setup\
Installation edition: DEVELOPER
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data
ASDOMAINGROUP: <empty>
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: NT AUTHORITY\SYSTEM
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: PC\computername
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,OCS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: PC\computername
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Analysis Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Reporting Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Integration Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Connectivity
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools SDK
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Business Intelligence Development Studio
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Books Online
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Feature: Microsoft Sync Framework
Status: Passed
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\SystemConfigurationCheck_Report.htm
I tried installing as adminstrator and in compatability mode with Windows 7/Vista but that didn't work. Trying to install from the dvd or from the extracted files in my drive made no difference.
I am now wondering if there is a download link for SQL Server 2008 R2 Developer edition with SP2 included (i.e. not just SP2 but the whole application (5GB+) otherwise I am not sure how to install this.Hello,
1. Please refer to solution provided in below thread
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/61d56f64-2575-4a58-9503-84579476afaf/sql-server-2008-setup-error-attempted-to-perform-an-unauthorized-operation?forum=sqlsetupandupgrade
2. Make sure you stop antivirus services during running the setup.Make sure you Right click on setup.exe file and select run as administrator.
If above does not works include below as well
3. Please verify WMI service is started.
If WMI is started, consider to repair WMI.
http://windowsxp.mvps.org/repairwmi.htm
Reference
Link
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
hi,
Please help me..
is it possible to install sql server 2008 standard edition in windows server 2008 enterprise edition?
will any problem arise?Hiya,
Yes it it possible. No there will not be any problems.
Short and simple :)
Maybe you are looking for
-
Cenvat Clearing not coming in MIRO in case of Dealer Invoice
Hi, This is a scenario of purchasing from dealer wherein the exact excise duty and VAT/CST is not known while creating a Purchase Order. I did the following steps Created PO with One item of 5 quantity @ 1000 INR (Total Base Value = 5000 INR) Assigne
-
Poor image quality on exported version
I am trying to export versions of my photos to a folder on my external drive. Every time I do this the resulting jpg is washed out and has poor resolution + a ton of noise. The resulting image is substantially lighter than the images in my aperture w
-
Flash ActiveX's CallFunction method always fails (E_FAIL)
Hi, I likely have collected all information in the web, but still facing the problem. I am trying to host the Flash ActiveX in a C# program and establish two-way communication between the host application and the ActionScript contained in my SWF file
-
VOID button on dispute case is greyed out
Hi All, VOID button in a dispute case change mode is greyed out. Pls through some light on how to go over activating VOID button. Thanks Rajanikanth
-
Can i send a song to a friend as a gift
can i send one of my song from my libary to a friend as a gift or can i purchase one and send it as an audio file ?