SQL Server Dev Environment for Windows 8 Tab

I recently received a Windows 8 Asus tablet running Windows 8 and wanted to know if there was a light weight version of SQL Server that I can use for development when traveling. I am writing alot of stored procedures and am tired of taking my laptop
on trips.

Hi sawyerdad,
According to your description, we need to verify the type of your Asus tablet, windows 8 Surface RT or Surface Pro.
If it is Surface Pro, you can install SQL Server in the tablet base on window 8, Personally, I recommend you install the version of SQL Server according to the hardware and software of the device. Such as the developer version, the developers
can build any kind of application on top of SQL Server. It includes all the functionality of Enterprise edition, but is licensed for use as a development and test system, not as a production server. SQL Server Developer is an ideal choice
for people who build and test applications. If it is Surface RT, it could not install the traditional desktop apps.
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Similar Messages

Free Download Sql Server 2012 Full for windows 7 64 bit

hi,
im new here and i want to download sql server 2012 complete for windows 7 64 bit.
If any one help me to find it.

You need to buy SQL Server 2012 Developer Edition for 50$ or as Shanky_621 suggested
download a free edition named SQL EXPRESS which has some limitations.
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

SQL Server Management Express for Windows 8

Is there an SQL Server Management Express version for Windows 8? I tried using the 2005 and 2008 Express version but get an error indicating Windows 8 is not compatible. Thanks

Hello,
Please download it from the following URL fully compatible with Windows 8.x.
http://www.microsoft.com/en-us/download/details.aspx?id=29062
ENU\x64\SQLManagementStudio_x64_ENU.exe
ENU\x86\SQLManagementStudio_x86_ENU.exe
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

How to fix Login failed for user ''. (Microsoft SQL Server, Error: 18456)in windows 2008?

Hi All,
we are facing the Login fails issue .
how to resolve the bellow error , could you please suggested the possible ways .. ASAP
TITLE: Connect to Server
Cannot connect to ..
ADDITIONAL INFORMATION:
Login failed for user ' domain\name'. (Microsoft SQL Server, Error: 18456)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
BUTTONS:
OK
Log Name: Application
Source: MSSQLSERVER
Date: 10/6/2011 1:56:28 PM
Event ID: 18456
Task Category: Logon
Level: Information
Keywords: Classic,Audit Failure
User: domain\name
Computer:
Description:
Login failed for user ' domain\name'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]
RAM

I was hitting myself in the head with this problem for a couple of minutes.... Everything was fine on the DC and Domain itself.. I added the Domain admins Group Principal for which I am part of... I was getting this error ... Long History... Short
(Right Click and Run as Administrator took care of this for me..) UAC was the cause of the problem.
Cannot connect to XX-DB-XX3.
===================================
Login failed for user 'XXXXS\XXas'. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
Server Name: XX-DB-XX3
Error Number: 18456
Severity: 14
State: 1
Line Number: 65536
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

SQL Server 2012 Express on Window 8.1 64 bit version?

Hi,
I´m trying to install SQL Server 2012 Express on Windows 8.1 64 bit version. When I reach the point of "Installing Setup Files", of the installation process, the installation seems to halt. I´ve tried both the 32 bit and 64 bit versions of SQL 2012
Express. I´ve installed SQL 2012 Express several times before on other Windows versions but I´ve never encountered this problem. Is it a known SQL Server 2012 Express/Windows 8.1 64 bit compability problem?
Thanks in advance!
Martin

SQL Server 2012 express can be installed in windows 8.1 all you need to take care is that you meet
hardware and software requirements . Please read the article in hyperlink carefully.Make sure you have internet connection because it is required. Make sure you meet all .net
framework requirements
Below link would be helpful as well.
How to use SQL server on Windows 8 environment
Please remove any previous failed installation of SQL server from add remove program. If you still face issue please refer to Solution section of
this link for manual un installation.
Finally you can locate log files present at location
C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\summry.txt for details about log
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Need to convert DTS packages to SQL Server 2012 environment.

Hi Friends,
As Part of the Project Requirement,we need to convert DTS packages to SQL Server 2012 environment.
Please sugest me best approach.
Thanks

Best approach is to re-design the packages in SSIS 2012 directy if it is feasible. Because most of the DTS feaures are discontinued and also you will have to clean up all errors that you are going to get after migration.
Discontinued Integration Services Functionality in SQL Server 2012
Otherwise you need to migrate it first to 2008R2 and then 2012 version.
Below ones would be helpful for you:
Migrate DTS packages to SSIS (SSIS2008R2)
Support of DTS packages in 2008 R2
Known DTS Package Migration Issues
Cheers,
Vaibhav Chaudhari

Is it possible to have two or more virtual machines point to a shared instance of SQL Server 2008 R2 for systems administration?

Hello All,
I am the Systems Admin for a production box running SQL Server 2008 R2. I have been ask to do the following and and trying to figure out if it's even possible.
1. The Production Server is named ProductionA
2. Create 3 Administrator accounts on ProductionA each with access to the SQL Server instance on ProductionA. Use Standard SQL Server login for credentials. i.e. Username/Password and assign the role sysadmin.
3. Install 3 Virtual Machines on ProductionA each with Windows 2008 R2 64 bit operating system.
4. For each Virtual Machine, Install SQL Management Studio and write down the IP Address assigned to each VM.
5. Using Remote Desktop Connection, connect to each virtual machine to be able to manage the SQL Server.
Is this possible? And, why am i doing it? Because I DO NOT want the three people who will be having access to the production SQL Server to also have access to the primary host ProductionA. Since I have to allow them to RDC into the box
to manage the SQL Server, I figure why not create a separate VM for each one of them and they can RDC into those instead.
Does this make any sense?
Any tips are greatly appreciated. The main reason for doing this is because the three people who will be accessing the box, I need to isolate each one of them and at the same time keep them off of the primary ProductionA.
Thanks for your help.
M

Because I DO NOT want the three people who will be having access to the production SQL Server to also have access to the primary host ProductionA. Since I have to allow them to RDC into the box to manage the SQL Server, I figure why not create
a separate VM for each one of them and they can RDC into those instead.
Does this make any sense?
Any tips are greatly appreciated. The main reason for doing this is because the three people who will be accessing the box, I need to isolate each one of them and at the same time keep them off of the primary ProductionA.
Thanks for your help.
M
Hello M,
Since you dont want the 3 guys to have access to Production machine A.You can install SQL Server client .By client i mean SQL server management studio(SSMS) on there local desktop and then create login for them in SQL Server.Open port on which your SQL server
is running for three of the machines so that they can connct.Now with SSMS installed on each machine each can connect to SQL server from there own machine.
I would also like you to be cautious with giving Sysadmin privilege to all three of them ,first please note down what task they would do and then decide what rights to be provided.
Your option will also work but you need to create 3 VM for that .Which is more tedious task.
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

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

SQL Server Express compatibility with Windows 8.1 - Which version(s) are compatible?

We have purchased a new computer that has Win 8.1 Pro. We are migrating an application from a Win 7 Pro machine we are currently successfully using (the vendor migrates it for us) and they have said that the application will require the installation of SQL
Server 2008 Express (which we do have on our Win 7 machine).
In looking at the requirements for SQL Server 2008 Express (on the download page for it), it does not mention it being compatible with Win 8.1
In addition, Installation Instructions says that it requires:
Microsoft .Net Framework 3.5 SP1
Windows Installer 4.5.
Windows PowerShell 1.0
I see that 3.5 is already listed as a program feature of Win8.1 and I've enabled it. Do I need to install SP1? I downloaded it, and launched it, and nothing happened.
I also looked at the Windows Installer 4.5 download page, and it's not clear if that is compatible with 8.1. Do I need to download and install it?
Power Shell 2.0 is already installed. I assume that will be backwards compatible with PowerShell 1.0; is that correct?
I saw another question about SQL Server Express Compatibility with Win 8.1 (http://social.technet.microsoft.com/Forums/windows/en-US/038ec00e-4fc1-41ba-9fdc-21c022aad67e/action?threadDisplayName=sql-server-express-compatibility-with-windows-81) and the response
said that SQL Server Express 2012 will work, but the link contained in the answer led to a page for SQL Server Express 2014.
My vendor has told me that SQL SERver Express 2012 will be backwards compatible with their product. But they said that I would first have to install 2008 first. Is that correct for Win 8.1?
So, the ultimate questions are:
1. What is the link for Sql Server 2012 Express for Win 8.1?
2. Will the SQL Server 2012 Express download require prior install of the 2008 version
3. What other component requirements are required for SQL Server 2012 Express, and how can I determine if they have already been installed. (This is a brand new computer with a clean Win8.1 Install).
4. Finally, can we use the 2014 version of SQL Server Express for Win 8.1? If so, questions 1, 2 and 3 apply, too.
Thanks for your help on this!! HIGH ANXIETY.

Hello,
The following article provides which updates are required to make SQL Server versions compatible with Windows 8 or 8.1:
http://support.microsoft.com/kb/2681562/en-us
1. You can use the product updates feature on SQL Server 2012 to make it compatible with Window 8.1. Apply SP1 as described on the following
article:
http://www.sqlcoffee.com/SQLServer2012_0008.htm
2. No.
3. Download and install .NET Framework 4.0 and enable .NET Framework 3.5. For more information:
http://www.sqlcoffee.com/SQLServer2012_0017.htm
4. Yes, you can use SQL Server 2014 with Windows 8.1. Please refer to the Support article provided above.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

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

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

Wait on the Database Engine recovery handle failed. Check the SQL server error log for potential causes in SQL Server 2012 Developer Edition

I m using SQL Server 2012 Developer Edition. Even I tried 2012 express and enterprise edition but all
gave same error. I browsed msdn blog. But nothing help me out.
Below is the error log details--
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2013-10-21 12:58:05
End time: 2013-10-21 13:52:30
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: CROY-TOSH
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: C:\Users\CRoy\Downloads\SQL Server 2012 Developer Edition (x86 and x64) - DVD (English)\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AI
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: CRoy-TOSH\CRoy
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: ROY
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: CRoy-TOSH\CRoy
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK, MDS
FILESTREAMLEVEL: 2
FILESTREAMSHARENAME: MSSQLSERVER
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
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 Service\MsDtsServer110
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AI
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: CRoy-TOSH\CRoy
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131021_125116\SystemConfigurationCheck_Report.htm

Hi,
This 3rd time I followed this link. But nothing new, same error.
Can you please tell me how to do follow, I cannt do the 1st step, how to change the local system to windows level account, vice-versa. It is shown mine as
Server Configuration Manager(Local)
From here I folllowed the steps ---[I cannt insert link/image :-(]
SQL 2008/R2 setup fails with "Wait on the database engine recovery handle failed"
If I right clicked on SQL Server Service, there is no option to change the account.
Hello,
Thanks for your patience,did you tried stesp mentioned in below article
http://blogs.msdn.com/b/sqljourney/archive/2012/03/16/sql-2008-r2-setup-fails-with-quot-wait-on-the-database-engine-recovery-handle-failed-quot.aspx
To resolve it, follow these steps:-
When the installation throws this error, click on OK and allow it to proceed. It will fail for Database Engine, but the SQL Server service should have
been created. Check the Services console.
If the service is present, perform the following steps:-
1. Go to SQL Server Configuration manager, right click on the SQL Server service, and change the service account (if it is local system, give
it a windows level account, and vice-versa). It might throw a WMI error but you will see the account getting updated anyway. If not, then use the Services console. Change the account for SQL Agent as well.
Use this link to change sql server service account
http://technet.microsoft.com/en-us/library/ms345578.aspx
2. Next, try to start the service. It should come online.
3. However, you will not be able to log in to the SQL Server
4. Now stop the service and start it from the command prompt using -m -c -T3608 parameters.
5. Now try logging in to the server using admin connection from sqlcmd (sqlcmd admin:<server name>\<instance name> ...)
6. Once logged in, use the sp_addsrvrolemember '<domain\username>','sysadmin'.
Also add the builtin/administrators to the sysadmin role
7. Now stop the service from the command prompt and start it from SQL Server configuration manager
You should be able to log in to the server now.
Hope this helps someone.
Please revert if it helps or even if it does not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

SQL Server 2000 Driver for JDBC - Error establishing sockets

Hi there
I am using Microsoft SQL Server 2000 Driver for JDBC to connect to SQL Sever 2000. It is just a test application to see if it would connect to the datacase successfully. But I got the following errors. I already set up the classpath and installed all SQL Server 2000 Driver for JDBC sp 3. Dont know why it still failed...can anyone help me out of this? Thanks.
When i am using simple JDBC-ODBC bridge Driver it's working fine.
For this Server Pack3 , i have checked every thing like--
TCP / IP Poart is Enable.
I am working in client machine, my MSSQLServer 2000 Placed in server Machine.
when i am giving Telnet ServerIP 1433 it's giving following response.
connecting to ServerIP ....... could not open connection to the host , on port 1433:connection Failed
My Sample Code is :--
String user="sa";
String password="imcindia";
Connection con1 = null;
CallableStatement cstmt = null;
Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver").newInstance();
con1=DriverManager.getConnection("jdbc:microsoft:sqlserver://ServerName:1433;DatabaseName=dmo1o2d",user,password);
Statement st=con1.createStatement();
st.execute("use dm0102d");
st.execute("setuser 'dm01012'");
cstmt = con1.prepareCall("{?=Call dms_ex_create_folder('ABC','18753','NB21','u')}");
cstmt.execute();
Here are Error Code :
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
     at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
     at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
     at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
     at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
     at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
     at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
     at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
     at java.sql.DriverManager.getConnection(Unknown Source)
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Connection refused: connect
     at java.sql.DriverManager.getConnection(Unknown Source)
     at TestConnection1.main(TestConnection1.java:24)
one can help me to over come this problm,
Thanks in advance.
venkat

hey i also have this problem i have been looking for solution for this problem for along time i tried every possible solution i tried every service pack for the SQL but it didn't connect to the port!!!
it's a network problem ur java code is correct dont worry about it.
finally i had to install MySQL and it's work fine now but if u insist on usning SQL u have to use the JDBC-ODBC Bridge it will work by :
first add data source database , follow these steps
1- go to Administrative tools
2-Data Sources(ODBC)
3-System DNS tab and add then choose SQL SERVER the last option then finish
4-write the name; Note: this name is the one that u will write in ur URL for example if u write Hello the URL will be "jdbc:odbc:Hello"
5- choose the server, its recommended to write "." or (local)
6-change the database to its an important step to choose the database that u want to use, choose northwind if u want to use it
finish
second
adding this code:
import java.sql.*;
class JdbcTest1 {
public static void main (String[] args) {
try {
// Step 1: Load the JDBC driver.
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
// Step 2: Establish the connection to the database.
String url = "jdbc:odbc:Hello";
Connection conn = DriverManager.getConnection(url,"user1","password");
} catch (Exception e) {
System.err.println("Got an exception! ");
System.err.println(e.getMessage());
it will work without any problems

Regarding Microsoft SQL Server 2000 Driver for JDBC (2.2.0019)

I have downloaded and installed Microsoft SQL Server 2000 Driver for JDBC (2.2.0019). Now i have to configure it for my development purpose. Can i use this driver for my development purpose or not. If yes does it create any kind of problem in future when i change the platform. My development should not depend on driver and database.
Can i use any other driver provided by sun microsystem. If yes let me know where can i download and configure it.
Waiting for the updates ASAP

See, the bridge, being a type 1 driver has
river has all the inherent limitations of that type
drivers, due to the extra levels the data must
passthrough inthe journey between the DB and the
client. Also the use of native code.. makes it
unsuitable to be used in applets.. the odbc should be
configured in the client for this driver to work. etc.
etc.
It may be stable and useful for some
for some applications.. but for sccenarios where one
needs the solution tobe platform independent, ...By definition that would be the case. Of course the odbc-bridge does work on Windows, Solaris and Linux. So what other platform were you thinking about?
... less dependent on the user configuration,The bridge doesn't need any configuration. Or at least not any more than any other driver. The ODBC driver of course does need configuration.
...needs the minimum preparations from theuser, and above all give
the fastest response time for him, the bridge cannot
beat type 4 drivers. You are going to have to provide a link for that particular performance quote. Given that performance is impact most severely by requirements then design and finally by round trip time to the database I doubt that for applications (rather than benchmarks) that any difference is going to be significant.
the problem i think was my use of
my use of 'commercial' that u pointed out..
anyway.. u are of course right if what u intended was
stability only. but what i intended with that word was
different .. sorry for creating the confusion.
And it still seems like you are implying that it is not suitable for deployment in production systems. And as I pointed out I did deploy it in a large scale production system.
I am not saying that type 4 drivers do not have a place nor that they do not have advantages, but their mere existance does not prove that they are a better choice for all installations.

Problems! MS SQL Server 2000 Driver for JDBC.

In Dos-promt ill got only this message: com.microsoft.jdbc.sqlserver.SQLServerDriver
What is wrong and is there someone that can help me out?
I have installed Microsoft SQL Server 2000 Driver for JDBC and set the path like this in the system, advance, environment variable:
.;D:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msbase.jar;D:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\msutil.jar;D:\Program Files\Microsoft SQL Server 2000 Driver for JDBC\lib\mssqlserver.jar
This is the source code i use to test the connection:
import java.sql.*;
public class Exercise2_1 {
static String driver = ("com.microsoft.jdbc.sqlserver.SQLServerDriver");
static String url= "jdbc:microsoft:MinTest;ah;modeerf";//sqlserver://H:1433;user=ah;password=modeerf";
public static void main(String[] args) {
try {
     Class.forName(driver).newInstance();
     System.out.println("Loaded driver");
     Connection conn = DriverManager.getConnection(url);
     System.out.println("Connected to database");
     conn.close();
     System.out.println("Closed connection");
catch (Throwable e) { System.err.println(e.getMessage()); }

You printed the error message associated with the exception but didn't print the type of the exception. com.microsoft.jdbc.sqlserver.SQLServerDriver was probably a ClassNotFoundException meaning that the VM couldn't find the jars.
You say you put the jars in the path. They should actually be in the class path. Either set the CLASSPATH environment variable or pass it in to the Java VM via the -cp option.
One more thing. Seeing as the paths that you installed the JDBC driver into contain spaces you may need to put quotes around the path names or use the MSDOS short names for those directories.
Col

SQL Server Dev Environment for Windows 8 Tab

Similar Messages

Maybe you are looking for