Looking for MS SQL Server(2012 or older versions) all commands
HI,
Looking for MS SQL Server(2012 or older versions) all commands, i.e., all available sql server commands.
Is there any reference manual or MS KL to get all commands in SQL Server ?
Thanks in advance
Thanks for link
Sean Gallardy and Jingyang Li.
This is is not usefull for my requirement.
What i am looking is..SQL Server commands like examples... DDL/DML comands...create/alter
Examples: Insert/update/delete,truncate.......etc
Create database,create procedure.......etc
Alter database,shutdown,drop,create....etc
Looking for list of all commands in one place/doc in SQL Server.
Thanks
Similar Messages
-
How to test basic sql queries online(for Sql Server 2012 and up versions) ?
Hi,
I need to test basic sql queries using sql server without installing Sql Server on to the system.
Do we have such readymade online help, which can solve such difficulties ?
Please sugest some of url's.
Thanks.Thanks for reply.
I am looking specific Sql Server.
Hi Maggy,
I strongly recommend you install SQL Server 2012 express edit and test your T-SQL queries. We can download it from the following site:
Microsoft® SQL Server® 2012 Express:
http://www.microsoft.com/en-hk/download/details.aspx?id=29062
Regards,
Elvis Long
TechNet Community Support -
Download Links Broken for english Sql Server 2012 Express
Hi,
it seems that the download links for Sql Server 2012 Express Edition is broken for the english version.
None of the links on the microsoft download center works.
I am able to download a german version from:
http://www.microsoft.com/de-de/download/details.aspx?id=29062
But changing the language to english results in a "We are sorry, the page you requested cannot be found."
Take care,
MartinHello,
I created the following Microsoft Connect item about this issue:
https://connect.microsoft.com/SQLServer/feedbackdetail/view/958840/download-links-are-broken-for-sql-server-2012-express-and-sql-server-2008-r2-express
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
How to download SQL Server 2012 Standard Trial Version?
Hello,
I would like to try Standard Edition of SQL Server 2012. Where I can download it?
I followed this link www.microsoft.com/en-us/sqlserver/get-sql-server/try-it.aspx and downloaded and installed. But when I check in SQL Server Management Studio (Mangement Studio->Server->Properties->Generals->Product), it shows "Microsoft
SQL Server Enterprise Evaluation (64-bit)".
As I don't need Enterprise Edition for my project, I would like to test with Standard Edition for few days before purchasing.
Please advise.
Thanks in advanced.Hello,
There is no edition specific to evaluation edition.Its same as enterprise but you can use it maximum for 6 months and you cnanot use it in production.Use below link for Eval edtn
http://www.microsoft.com/en-gb/download/details.aspx?id=29066
Now there is no standard evaluation edition.If you want to specifically test on Stand. edition you need to buy a license copy.But i guess you want to test some non enterprise features so you need to by stand for it.
Can you tell me what you want to test specifically I will tell you whether stand or ent will make any differnce or not
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
Hi all,
Has anyone come across SQL Server 2012 SP1 CU8/9 failing to install with a “Failed to retrieve data for this request.” error.
The error is too generic for a useful search on web, for me at least anyway.
Had no problems patching a whole bunch of other servers in the same environment.
I’m no good at reading these error logs. For some reason the primary replica is referenced in the detailed log???
The CU8/9 patch has been run by both Domain Admins and local Admin with no luck.
We are trying to patch a secondary failover replica. (SharePoint 2013 is installed on this server.)
This is from the summary log:
Overall summary:
Final result: The patch installer has failed to update the shared features. To determine the reason for failure,
review the log files.
Exit code (Decimal): -2146233088
Exit facility code: 19
Exit error code: 5376
Exit message: Failed to retrieve data for this request.
Start time: 2014-04-10 11:51:11
End time: 2014-04-10 11:51:49
Requested action: Patch
Exception help link:
http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3412.0&EvtType=0xB2652E58%400xDC80C325&EvtType=0xB2652E58%400xDC80C325
Machine Properties:
Machine name: VMSPDB2
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: Australia
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: Yes
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered Configured
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database
Engine Services 1033 Enterprise Edition
11.1.3000.0 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server
Replication 1033 Enterprise
Edition 11.1.3000.0 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text
and Semantic Extractions for Search 1033 Enterprise Edition 11.1.3000.0 No
Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data
Quality Services 1033
Enterprise Edition 11.1.3000.0 No Yes
SQL Server 2012
Management Tools - Basic 1033
Enterprise Edition 11.1.3000.0 No Yes
SQL Server 2012
Management Tools - Complete 1033 Enterprise Edition
11.1.3000.0 No Yes
SQL Server 2012
Client Tools Connectivity 1033 Enterprise Edition
11.1.3000.0 No Yes
SQL Server 2012
SQL Server Data Tools 1033
Enterprise Edition 11.1.3000.0 No Yes
SQL Server 2012
Integration Services 1033
Enterprise Edition 11.1.3000.0 No Yes
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 1
KBArticle: KB2931078
KBArticleHyperlink:
http://support.microsoft.com/?kbid=2931078
PatchType: QFE
AssociatedHotfixBuild: 0
Platform: x64
PatchLevel: 11.1.3412.0
ProductVersion: 11.1.3000.0
GDRReservedRange: 10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0
PackageName: SQLServer2012-KB2931078-x64.exe
Installation location: e:\90a192411a98d1f6dc\x64\setup\
User Input Settings:
ACTION: Patch
ALLINSTANCES: false
CLUSTERPASSIVE: false
CONFIGURATIONFILE:
ENU: false
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTANCEID: <empty>
INSTANCENAME: <empty>
QUIET: false
QUIETSIMPLE: false
SQMREPORTING: false
UIMODE: Normal
X86: false
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: The rule result report file is not available.
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException
Message:
Failed to retrieve data for this request.
HResult : 0x80131500
Data:
HelpLink.ProdName = Microsoft SQL Server
HelpLink.BaseHelpUrl =
http://go.microsoft.com/fwlink
HelpLink.LinkId = 20476
HelpLink.EvtType =
0xB2652E58@0xDC80C325
DisableWatson = true
Stack:
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.ProcessDTbl(DataTable dt, Int32 level)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectSqlDiscoveryData(String machineName)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectDiscoveryData(String machineName)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
Inner exception type: System.ComponentModel.Win32Exception
Message:
Not all privileges or groups referenced are assigned to the caller.
HResult : 0x80004005
Error : 1300
Stack:
at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege.SetPrivilege(Boolean enable)
at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege..ctor(String privilege)
at Microsoft.SqlServer.Configuration.Sco.SqlRegistry.GetLocallyCachedLocalMachineSubKey(ServiceContainer ctx, String machineName, SqlRegistryKey
key)
at Microsoft.SqlServer.Discovery.DiscoveryUtils.TryLocallyCacheRegistryKey(ServiceContainer ctx, String machineName, SqlRegistryKey
machineKey, String registryPath, RegistryView regView, String regPath, RegistryAccess registryAccess, Boolean& alreadyCached)
at Microsoft.SqlServer.Discovery.DiscoveryUtils.GetLocalMachineSubKey(ServiceContainer ctx, String machineName, RegistryView regView,
String regPath, RegistryAccess registryAccess)
at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String machineName, RegistryView regView)
at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String machineName)
at Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
And the tail of the detailed log:
(01) 2014-04-10 11:51:29 Slp: Completed Action: InitializeMsiExtension, returned True
(01) 2014-04-10 11:51:30 Slp: ----------------------------------------------------------------------
(01) 2014-04-10 11:51:30 Slp: Running Action: AddPackageModifierSourcesAction
(01) 2014-04-10 11:51:30 Slp: Completed Action: AddPackageModifierSourcesAction, returned True
(01) 2014-04-10 11:51:30 Slp: ----------------------------------------------------------------------
(01) 2014-04-10 11:51:30 Slp: Running Action: InitializeConfigAction
(01) 2014-04-10 11:51:30 Slp: Completed Action: InitializeConfigAction, returned True
(01) 2014-04-10 11:51:30 Slp: ----------------------------------------------------------------------
(01) 2014-04-10 11:51:30 Slp: Running Action: RunRemoteDiscoveryAction
(01) 2014-04-10 11:51:31 Slp: Running discovery on local machine
(01) 2014-04-10 11:51:33 Slp: Discovery on local machine is complete
(01) 2014-04-10 11:51:33 Slp: Running discovery on remote machine: VMSPDB1
(01) 2014-04-10 11:51:35 Slp: Discovery on VMSPDB1 failed due to exception
(01) 2014-04-10 11:51:36 Slp: Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException: Failed to retrieve data for this request. ---> System.ComponentModel.Win32Exception: Not all privileges or groups referenced are
assigned to the caller.
at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege.SetPrivilege(Boolean enable)
at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege..ctor(String privilege)
at Microsoft.SqlServer.Configuration.Sco.SqlRegistry.GetLocallyCachedLocalMachineSubKey(ServiceContainer ctx, String machineName, SqlRegistryKey key)
at Microsoft.SqlServer.Discovery.DiscoveryUtils.TryLocallyCacheRegistryKey(ServiceContainer ctx, String machineName, SqlRegistryKey machineKey, String registryPath, RegistryView regView, String regPath, RegistryAccess
registryAccess, Boolean& alreadyCached)
at Microsoft.SqlServer.Discovery.DiscoveryUtils.GetLocalMachineSubKey(ServiceContainer ctx, String machineName, RegistryView regView, String regPath, RegistryAccess registryAccess)
at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String machineName, RegistryView regView)
at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String machineName)
at Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
--- End of inner exception stack trace ---
at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.ProcessDTbl(DataTable dt, Int32 level)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectSqlDiscoveryData(String machineName)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectDiscoveryData(String machineName)
at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
(01) 2014-04-10 11:51:36 Slp: Error: Action "Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction" threw an exception during execution.
(01) 2014-04-10 11:51:36 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Failed to retrieve data for this request. ---> Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException: Failed to
retrieve data for this request. ---> System.ComponentModel.Win32Exception: Not all privileges or groups referenced are assigned to the caller.
(01) 2014-04-10 11:51:36 Slp: at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege.SetPrivilege(Boolean enable)
(01) 2014-04-10 11:51:36 Slp: at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege..ctor(String privilege)
(01) 2014-04-10 11:51:36 Slp: at Microsoft.SqlServer.Configuration.Sco.SqlRegistry.GetLocallyCachedLocalMachineSubKey(ServiceContainer ctx, String machineName, SqlRegistryKey key)
(01) 2014-04-10 11:51:36 Slp: at Microsoft.SqlServer.Discovery.DiscoveryUtils.TryLocallyCacheRegistryKey(ServiceContainer ctx, String machineName, SqlRegistryKey machineKey, String registryPath, RegistryView
regView, String regPath, RegistryAccess registryAccess, Boolean& alreadyCached)
(01) 2014-04-10 11:51:36 Slp: at Microsoft.SqlServer.Discovery.DiscoveryUtils.GetLocalMachineSubKey(ServiceContainer ctx, String machineName, RegistryView regView, String regPath, RegistryAccess registryAccess)
(01) 2014-04-10 11:51:36 Slp: at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String machineName, RegistryView regView)
(01) 2014-04-10 11:51:36 Slp: at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String machineName)
(01) 2014-04-10 11:51:36 Slp: at Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
(01) 2014-04-10 11:51:36 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
(01) 2014-04-10 11:51:36 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
(01) 2014-04-10 11:51:36 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
(01) 2014-04-10 11:51:36 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
(01) 2014-04-10 11:51:36 Slp: --- End of inner exception stack trace ---
(01) 2014-04-10 11:51:39 Slp: Received request to add the following file to Watson reporting: C:\Users\HS2\AppData\Local\Temp\tmp6614.tmp
(01) 2014-04-10 11:51:39 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2014-04-10 11:51:39 Slp: Inner exceptions are being indented
(01) 2014-04-10 11:51:39 Slp:
(01) 2014-04-10 11:51:39 Slp: Exception type: Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException
(01) 2014-04-10 11:51:39 Slp: Message:
(01) 2014-04-10 11:51:39 Slp: Failed to retrieve data for this request.
(01) 2014-04-10 11:51:39 Slp: HResult : 0x80131500
(01) 2014-04-10 11:51:39 Slp: Data:
(01) 2014-04-10 11:51:39 Slp: HelpLink.ProdName = Microsoft SQL Server
(01) 2014-04-10 11:51:39 Slp: HelpLink.BaseHelpUrl =
http://go.microsoft.com/fwlink
(01) 2014-04-10 11:51:39 Slp: HelpLink.LinkId = 20476
(01) 2014-04-10 11:51:39 Slp: Stack:
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.ProcessDTbl(DataTable dt, Int32 level)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectSqlDiscoveryData(String machineName)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectDiscoveryData(String machineName)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath,
String clusterDiscoveryDocRootPath)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer
context)
(01) 2014-04-10 11:51:39 Slp: Inner exception type: System.ComponentModel.Win32Exception
(01) 2014-04-10 11:51:39 Slp: Message:
(01) 2014-04-10 11:51:39 Slp: Not all privileges or groups referenced are assigned to the caller.
(01) 2014-04-10 11:51:39 Slp:
(01) 2014-04-10 11:51:39 Slp: HResult : 0x80004005
(01) 2014-04-10 11:51:39 Slp: Error : 1300
(01) 2014-04-10 11:51:39 Slp: Stack:
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege.SetPrivilege(Boolean
enable)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege..ctor(String privilege)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Configuration.Sco.SqlRegistry.GetLocallyCachedLocalMachineSubKey(ServiceContainer
ctx, String machineName, SqlRegistryKey key)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Discovery.DiscoveryUtils.TryLocallyCacheRegistryKey(ServiceContainer ctx,
String machineName, SqlRegistryKey machineKey, String registryPath, RegistryView regView, String regPath, RegistryAccess registryAccess, Boolean& alreadyCached)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Discovery.DiscoveryUtils.GetLocalMachineSubKey(ServiceContainer
ctx, String machineName, RegistryView regView, String regPath, RegistryAccess registryAccess)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String
machineName, RegistryView regView)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String machineName)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
(01) 2014-04-10 11:51:39 Slp: at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
(01) 2014-04-10 11:51:44 Slp: Watson Bucket 2
Original Parameter Values
(01) 2014-04-10 11:51:44 Slp: Parameter 0 : SQL Server
2012@RTM@KB2931078
(01) 2014-04-10 11:51:44 Slp: Parameter 1 : Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process
(01) 2014-04-10 11:51:44 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege.SetPrivilege
(01) 2014-04-10 11:51:44 Slp: Parameter 3 :
Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException@-2146233088
(01) 2014-04-10 11:51:44 Slp: Parameter 4 :
System.ComponentModel.Win32Exception@-2147467259
(01) 2014-04-10 11:51:44 Slp: Parameter 5 : RunRemoteDiscoveryAction
(01) 2014-04-10 11:51:44 Slp: Parameter 8 : 1300
(01) 2014-04-10 11:51:44 Slp:
Final Parameter Values
(01) 2014-04-10 11:51:44 Slp: Parameter 0 : SQL Server
2012@RTM@KB2931078
(01) 2014-04-10 11:51:44 Slp: Parameter 1 : 0x6785B09D
(01) 2014-04-10 11:51:44 Slp: Parameter 2 : 0xB2652E58
(01) 2014-04-10 11:51:44 Slp: Parameter 3 : 0x74E34741
(01) 2014-04-10 11:51:44 Slp: Parameter 4 : 0xDC80C325
(01) 2014-04-10 11:51:44 Slp: Parameter 5 : RunRemoteDiscoveryAction
(01) 2014-04-10 11:51:44 Slp: Parameter 8 : 0xA05EFA62
(01) 2014-04-10 11:51:45 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140410_115053\Registry_SOFTWARE_Microsoft_Microsoft SQL
Server.reg_
(01) 2014-04-10 11:51:45 Slp: The following exception occurred while preparing registry logs during Watson failure processing: Not all privileges or groups referenced are assigned to the caller.
(01) 2014-04-10 11:51:45 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140410_115053\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2014-04-10 11:51:45 Slp: The following exception occurred while preparing registry logs during Watson failure processing: Not all privileges or groups referenced are assigned to the caller.
(01) 2014-04-10 11:51:45 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140410_115053\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
(01) 2014-04-10 11:51:45 Slp: The following exception occurred while preparing registry logs during Watson failure processing: Not all privileges or groups referenced are assigned to the caller.
(01) 2014-04-10 11:51:45 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140410_115053\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft
SQL Server.reg_
(01) 2014-04-10 11:51:45 Slp: The following exception occurred while preparing registry logs during Watson failure processing: Not all privileges or groups referenced are assigned to the caller.
(01) 2014-04-10 11:51:45 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140410_115053\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2014-04-10 11:51:45 Slp: The following exception occurred while preparing registry logs during Watson failure processing: Not all privileges or groups referenced are assigned to the caller.
(01) 2014-04-10 11:51:45 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140410_115053\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
(01) 2014-04-10 11:51:45 Slp: The following exception occurred while preparing registry logs during Watson failure processing: Not all privileges or groups referenced are assigned to the caller.
(01) 2014-04-10 11:51:46 Slp: Failed to retrieve data for this request.
(01) 2014-04-10 11:51:46 Slp: Watson bucket for exception based failure has been created
(01) 2014-04-10 11:51:46 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
(01) 2014-04-10 11:51:46 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\110
(01) 2014-04-10 11:51:46 Slp: Sco: Attempting to get registry value EnableErrorReporting
(01) 2014-04-10 11:51:46 Slp: WER: Successfully read app consent from registry Software\Microsoft\Microsoft SQL Server\110\EnableErrorReporting=0.
(01) 2014-04-10 11:51:46 Slp: WER: Application level consent value '0' was mapped to consent status 'WerConsentDenied'
(01) 2014-04-10 11:51:46 Slp: WER: Result of the submission:: 'WerDisabled'
(01) 2014-04-10 11:51:46 Slp: WER: Submitted 1 of 1 failures to the Watson data repository
(01) 2014-04-10 11:51:46 Slp: Sco: File 'C:\Windows\system32\Cluster.exe' does not exist
(01) 2014-04-10 11:51:46 Slp: Failed to collect cluster logs, cannot find Cluster.exe under system directory.
(01) 2014-04-10 11:51:46 Slp: Dumping final cluster state.
(01) 2014-04-10 11:51:49 Slp: Completed dumping final cluster state.
(01) 2014-04-10 11:51:51 Slp:
(01) 2014-04-10 11:51:51 Slp: ----------------------------------------------------------------------
(01) 2014-04-10 11:51:51 Slp:
(01) 2014-04-10 11:51:51 Slp: Error result: -2146233088
(01) 2014-04-10 11:51:51 Slp: Result facility code: 19
(01) 2014-04-10 11:51:51 Slp: Result error code: 5376
(01) 2014-04-10 11:51:51 Slp: SQM Service: Sqm does not have active session.Hello SQL Ranger,
Thanks for posting the detailed log. I dont have exact solution for this but I can give you some hint what could be reason patch has failed below message points to fact that there is some issue with account which is used to install CU patch.Have alook at
below log.It says that when patch was trying to get details from other node in cluster it was not able to.
01) 2014-04-10 11:51:33 Slp: Discovery on local machine is complete
(01) 2014-04-10 11:51:33 Slp: Running discovery on remote machine: VMSPDB1
(01) 2014-04-10 11:51:35 Slp: Discovery on VMSPDB1 failed due to exception
(01) 2014-04-10 11:51:36 Slp: Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException: Failed to retrieve data for this request. ---> System.ComponentModel.Win32Exception: Not all privileges or groups referenced are assigned to the caller.
IMO I strongly feel it is issue with the account. Microsoft has also documented about this for SQL Server 2008 .Have a look at following links
http://support.microsoft.com/default.aspx?scid=kb;en-US;2000257
Please also assign privilege mentioned in below link
http://www.bradg.co.za/?p=12
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
I am installing SQL Server 2012 Developer (from ISO image written on DVD), my machine has Windows 7 (Edit: Windows 7 with service pack 1) on it. This machine already has SQL Express and SQL 2008 R2 Express installed in it.
On running 2012 setup it goes fine from Setup Support Rules to Installation Progress. In Installation Progress after some progress installation fails.
Windows show the following components couldn't installed:
Managment Tools Complete Failed. Client Tools Connectivity Failed. Client Tools SDK Failed. Client Tools Backwards Compantibility Failed. Managment Tools Basic Failed. SQL Server Data Tools Failed. Reporting Services -Native Failed. Database Engine
Services Failed. Data Quality Services Failed. full-Text and Semantic Extractins for Search Failed. SQL Server Replication Failed. Integration Services Failed. Analysis Services Failed. SQL Client Connectivity SDK Failed.
In detail for failure of every component it provide these details:
Action required:
Use the following information to resolve the error, and then try the setup process again.
Feature failure reason:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.
In summary log file it provide the following details:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068643839
Start time: 2012-07-31 16:23:37
End time: 2012-07-31 16:33:32
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for Conn: Use the following information to resolve the error, and then try the setup process again.
Next step for SDK: Use the following information to resolve the error, and then try the setup process again.
Next step for BC: Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS: Use the following information to resolve the error, and then try the setup process again.
Next step for BIDS: Use the following information to resolve the error, and then try the setup process again.
Next step for RS: Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for DQ: Use the following information to resolve the error, and then try the setup process again.
Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
Next step for Replication: Use the following information to resolve the error, and then try the setup process again.
Next step for IS: Use the following information to resolve the error, and then try the setup process again.
Next step for AS: Use the following information to resolve the error, and then try the setup process again.
Next step for SNAC_SDK: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: Haansi-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 2005 SQLEXPRESS MSSQL.1
Database Engine Services 1033 Express Edition
9.4.5000 No
SQL Server 2005 SQLEXPRESS MSSQL.1
SQL Server Replication 1033 Express Edition
9.4.5000 No
SQL Server 2005 SQLEXPRESS MSSQL.1
SharedTools 1033
Express Edition 9.4.5000 No
SQL Server 2005
Tools 1033
Express Edition 9.4.5000 No
SQL Server 2005
ToolsClient 1033
Express Edition 9.4.5000 No
SQL Server 2005
ToolsClient\Connectivity 1033 Express Edition
9.4.5000 No
SQL Server 2008 R2 SQLSERVER08EXPR2 MSSQL10_50.SQLSERVER08EXPR2 Database Engine Services 1033
Express Edition 10.50.1617.0 No
SQL Server 2008 R2 SQLSERVER08EXPR2 MSSQL10_50.SQLSERVER08EXPR2 SQL Server Replication 1033
Express Edition 10.50.1617.0 No
SQL Server 2008 R2
Management Tools - Basic 1033 Express Edition
10.50.1617.0 No
SQL Server 2012
LocalDB 1033
Express Edition 11.0.2318.0 No
SQL Server 2012
Reporting Services - SharePoint
11.0.2100.60 No
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: F:\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$SS2012
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: TABULAR
ASSVCACCOUNT: NT Service\MSOLAP$SS2012
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Manual
ASSYSADMINACCOUNTS: PC\Haansi
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, BIDS, CONN, IS, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SS2012
FTSVCPASSWORD: <empty>
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: SS2012
INSTANCENAME: SS2012
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: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SS2012
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Manual
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SS2012
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: Haansi-PC\Haansi
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\20120731_161013\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Connectivity
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools SDK
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Client Tools Backwards Compatibility
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Management Tools - Basic
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Server Data Tools
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
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, and then try the setup process again.
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
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, and then try the setup process again.
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, and then try the setup process again.
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Integration Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: Analysis Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Client Connectivity SDK
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\SystemConfigurationCheck_Report.htmPlease help.
I did what you suggested, but, still got error message to install SQL server data tools: Here is the log.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068037632
Start time: 2014-09-29 15:05:38
End time: 2014-09-29 15:15:55
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SSDTBI_VS2012: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: MSBI
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
SQL Server 2008 Management Tools - Basic
1033 Express Edition 10.0.1600.22 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server Replication 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Basic
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Complete
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Connectivity
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Backwards Compatibility
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools SDK
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 SQL Server Data Tools
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Integration Services
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Reporting Services - SharePoint
11.0.2100.60 No Yes
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: C:\9f7a58aa5d6d76ffe6be968a4ad339f5\x86\setup\
Installation edition: Express
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x86
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x86
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SSDTBI_VS2012, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTANCEID: <empty>
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: true
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\ConfigurationFile.ini
Detailed results:
Feature: SQL Server Data Tools - Business Intelligence for Visual Studio 2012
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft Visual Studio Tools for Applications 2012
Component error code: 0x80044000
Component log file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\VSTA2012_LangsSupport_Cpu32_1.log
Error description: VS Shell 2012 installation has failed with exit code -2147205120.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3436.0&EvtType=VSTA2012_LangsSupport%40Install%400x-2147205120
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 (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\SystemConfigurationCheck_Report.htm -
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.htmHi,
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 -
<p>Hi,</p><p>Please could anybody help me how to do ad-hoc reports by using SSRS 2012.</p><p>I am able to create ad-hoc reports using Report Builder3.0 and SQL Server 2008 R2. </p><p>I have built the report Model
in for the instance 2008 R2 </p><div class="t-paste-container">Using Report Manager 2012 </div>Hi Gowri,
From your description, you can create create ad-hoc reports using Report Builder 3.0 and SQL Server 2008 R2, and now you want to know how to how to do ad-hoc reports by using SSRS 2012, right? In SQL Server 2012, the default version of Report Builder is
3.0, so you can create create ad-hoc reports using Report Builder 3.0 as before.
If you have any questions, please feel free to ask.
Regards,
Charlie Liao
TechNet Community Support -
SSMS for SQL Server 2012 Express on Windows Embedded 8 Standard
Hello,
I have installed SQL Server 2012 Express with Advanced Tools (SQLEXPRADV_x64_ENU.exe, downloaded from MS website) on Windows Embedded 8 Standard 64-bit. But, when I try to find SQL Server Management Studio, I realized it's not installed (same installation
package works fine on my Windows 8.1 Pro 64-bit laptop, where SSMS gets installed). How do I fix this? And any other ways for trouble-shooting DBs on Windows Embedded 8 Standard?
Thanks,
JayBelow is the content of a summary file for the installation. BTW, I also try to find its ConfigurationFile.ini file for future installation on other computers, but it's not in the folder specified in the summary file either (see below).
Thanks.
Overall summary:
Final result: Passed
Exit code (Decimal): 0
Start time: 2014-04-15 13:57:59
End time: 2014-04-15 14:13:29
Requested action: Install
Machine Properties:
Machine name: AIMB-584
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: c:\e089c9dde791653620\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS, BIDS, BOL, SSMS, SNAC_SDK, LOCALDB
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SQLEXPRESS
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: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SQLEXPRESS
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: AIMB-584\User
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140415_135512\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Basic
Status: Passed
Feature: SQL Server Data Tools
Status: Passed
Feature: Reporting Services - Native
Status: Passed
Feature: Database Engine Services
Status: Passed
Feature: Full-Text and Semantic Extractions for Search
Status: Passed
Feature: SQL Server Replication
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: LocalDB
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\20140415_135512\SystemConfigurationCheck_Report.htm -
1.Can any one provide the detailed steps for multi-subnet HA for Always ON Groups.
--SQL Server 2012 AlwaysOn for Multi-subnet geographical HA solution steps
2.Do we need VLAN or not for SQL Server 2012 on win 2012 ? provide details for this VLAN required or not.
--I read MS links, sql server 2012 and above VLAN not required.
Env:
SQL Server 2012
Windows 2012 R2(2 servers different location)
Non-Shared storage (stand-alone servers)
Always ON Availability Group
I have seen white papers,but did not have detail step by steps.
ThanksHi SQLDBA321,
As your post, SQL Server 2012 or higher version has removed that requirement of virtual local area network (VLAN). For more details, please review this similar blog:
What you need for a Multi Subnet Configuration for AlwaysOn FCI in SQL Server 2012.
And you can perform the steps in the following similar blog to set up an AlwaysOn Availability Group with multiple subnets.
http://www.patrickkeisler.com/2013/07/setup-availability-group-with-multiple.html
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support -
Rule "SQL Server 2012 feature Upgrade" Failed
I am doing an in-place upgrade of SQL Server 2008 R2 SP2 > SQL Server 2012 SP1, both 64-bit, installed on Windows Server 2008 R2.
I ran the SQL Server Upgrade Advisor tool prior to upgrade which reported no issues.
The error I am getting is:
In the detailed.txt log I can see the following:
(11) 2013-12-29 12:28:10 Slp: Initializing rule : SQL Server 2012 Feature Upgrade
(11) 2013-12-29 12:28:10 Slp: Rule is will be executed : True
(11) 2013-12-29 12:28:10 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.SkuUpgradeRule
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_as_Cpu64'.
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Found feature package 'sql_as_ctp6_Cpu64' with SkuValue=ENTERPRISE (Enterprise) ProductVersion=10.52.4000.0
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 10.0 and edition ENTERPRISE for feature package 'sql_as_Cpu64'.
(11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=10.0 sourceEdition=ENTERPRISE (Enterprise) sourceArchitecture=X64 targetEdition=STANDARD (Standard) targetArchitecture=X64
(11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
(11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix did not find a match in sku matrix .
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_as_Cpu64' is blocking upgrade.
(11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' detection result: IsValidFeatureUpgrade=False
(11) 2013-12-29 12:28:10 Slp: Evaluating rule : FeatureUpgradeMatrixCheck
(11) 2013-12-29 12:28:10 Slp: Rule running on machine: TAUPE-SERVER
(11) 2013-12-29 12:28:10 Slp: Rule evaluation done : Failed
(11) 2013-12-29 12:28:10 Slp: Rule evaluation message: The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2012 version and edition upgrade in Books Online.
(11) 2013-12-29 12:28:10 Slp: Send result to channel : RulesEngineNotificationChannel
Prior to upgrade:
From Summary.txt file:
Overall summary:
Final result: Passed
Exit code (Decimal): 0
Start time: 2013-12-29 12:04:28
End time: 2013-12-29 12:08:02
Requested action: RunRules
Machine Properties:
Machine name: TAUPE-SERVER
Machine processor count: 1
OS version: Windows Server 2008 R2
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 Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER Analysis Services
1033 Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER Reporting Services - Native
1033 Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2
Management Tools - Basic 1033 Enterprise Edition 10.52.4000.0
No
SQL Server 2008 R2
Management Tools - Complete 1033 Enterprise Edition 10.52.4000.0
No
SQL Server 2008 R2
Client Tools Connectivity 1033 Enterprise Edition 10.52.4000.0
No
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location:
\\dovekie\drop\TFS2013\SQLServer2012SP1\x64\setup\
Installation edition: Standard
Slipstream: True
User Input Settings:
ACTION: RunRules
CONFIGURATIONFILE:
ENU: true
FEATURES:
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTANCENAME: <empty>
PID: *****
QUIET: false
QUIETSIMPLE: false
RULES: GlobalRules
UIMODE: Normal
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131229_120425\ConfigurationFile.ini
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131229_120425\SystemConfigurationCheck_Report.htm
As far as I'm aware, the upgrade path I am following is a supported one, any suggestions will be much appreciated!
Thank you.Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Database Engine Services
1033 Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2 MSSQLSERVER MSSQL10_50.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2 MSSQLSERVER MSAS10_50.MSSQLSERVER Analysis Services
1033 Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2 MSSQLSERVER MSRS10_50.MSSQLSERVER Reporting Services - Native
1033 Enterprise Edition 10.52.4000.0 No
SQL Server 2008 R2
Management Tools - Basic 1033 Enterprise Edition 10.52.4000.0
No
SQL Server 2008 R2
Management Tools - Complete 1033 Enterprise Edition 10.52.4000.0
No
SQL Server 2008 R2
Client Tools Connectivity 1033 Enterprise Edition 10.52.4000.0
No
Package properties:
Description: Microsoft SQL Server 2012
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location:
\\dovekie\drop\TFS2013\SQLServer2012SP1\x64\setup\
Installation edition: Standard
Slipstream: True
User Input
Hello ,
You are trying to upgrade to SQL 2012 standard edition which is not supported .you can only upgrade from SQL server 2008 R2 Sp2 Enterprise edition to SQL 2012 Enterprise or business intellgience. see below link for supported upgrade paths
http://technet.microsoft.com/en-us/library/ms143393.aspx
If you want to move ahead you should try Side by side approach.Create new SQL server 2012 box and restore backup.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
SQL Server 2012 DB Engine does not start (clean install with server 2012 and 2008 R2)
I'm trying to do clean installation of SQL server 2012 on Server 2012 (which is runnning as a VM on ESX server) and getting this "wait on the DB engine recovery failed" message. Initially, I though this issue was related to some permission issues
but changing the permission or service accounts didn't help. I'm not seeing any "denied" messages in the log files either. Even with Server 2008 R2 (clean built VM), the installation gives the exactly the same error messages.
My setup is purely for test purpose; so, the security is not a concern. Can someone help or give me a clue where to look?
(Summary)
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2014-05-28 17:12:12
End time: 2014-05-28 17:19:47
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: WIN-1V3VKPV5Q19
Machine processor count: 1
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: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: E:\x64\setup\
Installation edition: Evaluation
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x64
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x64
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$TESTDB
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: TESTDB
INSTANCENAME: TESTDB
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$TESTDB
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: WIN-1V3VKPV5Q19\Administrator
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\ConfigurationFile.ini
Detailed results:
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: SQL Browser
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\20140528_170909\SystemConfigurationCheck_Report.htm
(Error Log)
2014-05-28 17:17:26.64 spid8s 0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2014-05-28 17:17:26.73 spid9s Starting up database 'model'.
2014-05-28 17:17:28.24 spid9s Error: 9004, Severity: 23, State: 6.
2014-05-28 17:17:28.24 spid9s An error occurred while processing the log for database 'model'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
2014-05-28 17:17:28.24 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
(Details)
(01) 2014-05-28 17:17:28 Slp: Exception type: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException
(01) 2014-05-28 17:17:28 Slp: Message:
(01) 2014-05-28 17:17:28 Slp: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
(01) 2014-05-28 17:17:28 Slp: HResult : 0x851a001a
(01) 2014-05-28 17:17:28 Slp: FacilityCode : 1306 (51a)
(01) 2014-05-28 17:17:28 Slp: ErrorCode : 26 (001a)
(01) 2014-05-28 17:17:28 Slp: Data:
(01) 2014-05-28 17:17:28 Slp: SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2014-05-28 17:17:28 Slp: WatsonConfigActionData = INSTALL@CONFIGRC@SQL_ENGINE_CORE_INST
(01) 2014-05-28 17:17:28 Slp: WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2014-05-28 17:17:28 Slp: Stack:
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.ConfigSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean useInstallInputs)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.DoCommonDBStartConfig(ConfigActionTiming timing)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2014-05-28 17:17:28 Slp: Watson Bucket 1
Original Parameter Values
(01) 2014-05-28 17:17:28 Slp: Parameter 0 : SQL Server 2012@RTM@
(01) 2014-05-28 17:17:28 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart
(01) 2014-05-28 17:17:28 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart
(01) 2014-05-28 17:17:28 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
(01) 2014-05-28 17:17:28 Slp: Parameter 6 : INSTALL@CONFIGRC@SQL_ENGINE_CORE_INST
(01) 2014-05-28 17:17:28 Slp:
Final Parameter Values
(01) 2014-05-28 17:17:28 Slp: Parameter 0 : SQL Server 2012@RTM@
(01) 2014-05-28 17:17:28 Slp: Parameter 1 : 0xD15B4EB2
(01) 2014-05-28 17:17:28 Slp: Parameter 2 : 0xD15B4EB2
(01) 2014-05-28 17:17:28 Slp: Parameter 3 : 0x4BDAF9BA@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 4 : 0x4BDAF9BA@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
(01) 2014-05-28 17:17:28 Slp: Parameter 6 : 0x9C5770A6Hi Nababoya:
As you are telling this is a test installation process...
In the logs i m seeing the error message "An error occurred while processing the log for database 'model'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.".
1) If the SQL Services was installed successfully and SQL Service was not able to start because of model database issue...
1.1) If you have model database SQL back file, start the SQL Server in single user mode with minimum configuration and try to restore MODEL database
http://blogs.msdn.com/b/sqlserverfaq/archive/2011/05/11/inf-hey-my-sql-server-service-is-not-starting-what-do-i-do.aspx
1.2) If you don't have backups., try to rebuild the system databases but make sure that you are not losing any data critical data on master and SQL Jobs on MSDB
http://msdn.microsoft.com/en-us/library/dd207003%28v=sql.110%29.aspx#RebuildProcedure
2) As if this is a new installation try to repair the instance with the help of setup media file
3) If the repair option fails., the last option wipe out the complete SQL Server components from Services.msc and Registries and start new installation.
4) Make sure when you are doing un-installation all the required SQL Server components on services.msc should be in stop state.
Hope this helps and let me know any questions...
Thanks,
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :) -
Using SQL Server 2012 SSIS to Extract Data From SAP
Hi
What is the current best practice for using SQL Server 2012 SSIS to extract data from SAP R3? Please note we are looking for a solution that does not use SAP BW or SAP OHS.
Ideally we would like to build our ETL SSIS process to make a .NET call to an SAP RFC procedure and avoid using web services.
With SS2012 can we use any of these without using SAP BW:
- SAP .NET Connector
- MS ADO .NET
- BizTalk .NET 3.0 Adapter
Thanks and take care,
ShayneHi Shayne,
You can use the .NET Framework Data Provider for mySAP Business Suite along with SQL Server Integration Service (SSIS) to import data from an SAP system into SQL Server database tables, flat files, or other compatible destination types. You can create an SSIS
package that can be executed to import data from an SAP system.
You must use the SQL Server Import and Export wizard to import data into the SQL Server database. You must provide a select query to specify data to be imported. The query must confirm to the semantics supported by the Data Provider for SAP. You can start the
SQL Server Import Export Wizard either from the SQL Server Management Studio or from an Integration Service project in Visual Studio. Detail steps please see:
Importing SAP Data Using SQL Server Management Studio:
http://msdn.microsoft.com/en-us/library/cc185161(v=bts.10).aspx
Importing SAP Data Using Visual Studio:
http://msdn.microsoft.com/en-us/library/cc185254(v=bts.10).aspx
Please feel free to ask if you have any question.
Thanks,
Eileen
Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread. -
SQL Server 2012- Memory Leak Issue
Team,
We are running a Mission Critical Application on SQL Server 2012 SP2(11.0.5058) which is configured on Always ON Synchronous mode. Offlate due to heavy development work, Application team have come up with stating memory issues. I have analysed all the areas
and everything looks normal. Please suggest if we have to patch the latest CU4 for SQL Server 2012 SP2.
The checks were performed on the below areas:
- Errorlog, System Logs - No errors reported.
- There are close to 8 Databases hosted on the instances which are all configured for AlwaysON. SQL Server is running on VM Infrastructure and the total physical memory allocated is 96GB out of which SQL is capped for 92GB.
-The Page Life Expectancy is healthy and is showing a greater number. There are no Signal waits either or pending memory grants.
- The writes are more than reads for one of the databases which is flagged with application team. There are no blockings & Deadlocks.
Please suggest me the future course of action and your inputs are much appreciated.
Best Regards,
SharathActual issue is- Application team have reported a memory leak and their builds have significantly slowed down. They suspect that its Database memory leak. However I have verified from database end and gave the above inputs.
The AOAGs are good. I was looking for any pointers whether there are any bugs which is related to memory leaks in SQL Server 2012. I know all of them are addressed with SQL Server 2012 SP2.
Application team has NO idea about SQL Server do they ? And to say SQL Server has memory leak you have to actually prove it did they showed any proof. Its common for application team to say SQL Server is leaking memory because they are unaware about fact
by default SQL Server would take as much memory as possible and would release when SQLOS asks it to do so. This might give sign that it is leaking memory BUT IT IS NOT.
As you already said AOAG is working fine so I am presuming there is nothing much to worry. To monitor memory usage in SQL Server 2012 you can use below counters
SQL Server: Memory Manager-- Target Server Memory (KB)
SQL Server: Memory Manager--Total Server Memory (KB)
SQL Server: Memory Manager- Free Memory (KB)
SQL Server: Memory Manager--Database Cache Memory (KB)
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP -
Installing SQL Server 2012 on Linux Ubuntu
Hello, Can I install SQL Server 2012 on Linux Ubuntu? So far I can only find downloads of ODBC for Red Hat. Any ideas?
Hi Mike,
Please also take a look at the following article regarding the Operating System requirement to install SQL Server:
Hardware and Software Requirements for Installing SQL Server 2012:
http://technet.microsoft.com/en-us/library/ms143506.aspx
As Sean said, we can connect to SQL Server via ODBC from Linux Ubuntu. Here are some articles for your reference, please see:
SQL Server ODBC Driver:
http://www.easysoft.com/products/data_access/odbc-sql-server-driver/index.html
Connecting to Microsoft SQL Server using ODBC from Ubuntu Server:
http://blog.jamesrossiter.co.uk/2011/03/08/connecting-to-microsoft-sql-server-using-odbc-from-ubuntu-server/
Regards,
Elvis Long
TechNet Community Support
Maybe you are looking for
-
DATA_DEFAULT In ALL_TAB_COLUMNS...
Hi all, I'm working in an existing codebase (VB.Net) that is using an Oracle Database. One of the things the application is doing is getting a copy of the default value for the different columns. It looks something like this: If Not String.IsNullOrEm
-
JTable Height Relative to JScrollPane's Height?
Is there a way to set the height of the JTable equal to the height of the JScrollPane? And as the JScrollPane resizes in height, I also want the JTable to resize relative to the height of the JScrollPane. I am putting the JScrollPane to a JPanel with
-
After effects CC annoying transparency grid ghosting problem
I just installed after effects CC on the new mac pro. Using a brand new asus monitor. Have a annoying problem with the transparency grid coming in as white can't see the grey checkerboard part. Whats stranger is the grey checkers come up with a me
-
Access to undefined global: newGrainSeed(1)
Downloaded LR 5.4. Now cannot email, get message: access to undefined global: newGrainSeed(1). Help!
-
I cannot open facebook app on my iphone 3gs with 5.1.1 framwork
Hi I use my iphone 3gs 5.1.1 ios few days back i accidently update to 6.1.3 and then downgrade to 5.1.1 after that i cannot open facebook application .I even ddi DSU mode and then installed from itune but that does not work ..What should i do?????? S