SCCM 2012 SP1 is Running on SQL Server 2012 with NO CU
I am working in an org that has SCCM 2012 SP1, it is and always has been running on SQL Server 2012 RTM, with NO CU installed it seems (judging by the file versions 11.0.2100.60, which are not the same as as documented here http://support.microsoft.com/kb/2703275).
sigh..........
So before I upgrade to R2 I will ensure I installed SP2 and CU3 onto SQL Server.
However, I am concerned about WHY SCCM 2012 SP1 requires SQL Server 2012 CU2 as a minimum and what damage may have been done as a result of this configuration?
Are there any actions that can be performed as remediation or health check?
Can anyone speculate?
However, I am concerned about WHY SCCM 2012 SP1 requires SQL Server 2012 CU2 as a minimum
Because the Microsoft product group decided it that way. All supported SQL versions are listed here:
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigSQLDBconfig
Damage? Hard (impossible) to tell. You would have seen errors in various components if there were problems.
Torsten Meringer | http://www.mssccmfaq.de
Similar Messages
-
I get one or the other error when i install SQL server 2012 SP1 in my Lab server
I get multiple errors when i install SQL server 2012 SP1 In my lab server.
Not sure why i keep getting different errors all the time when i install SQL server 2012 & 2012 SP1.
Below are error codes, screen shots and also a log of the error.
1. Eror code 0X84B40000
Also dint understand any thing from this article related to the above error
http://social.technet.microsoft.com/Forums/sqlserver/en-US/5b6cc928-0db8-4fe4-a5d3-21672225f0ca/i-get-error-code-0x84b40000-when-trying-to-install-sql-server-mgmt-studio-to-an-existing-sql?forum=sqlexpress
2. Eror code 0x851A001A
Can any one plz help as i always get one or the other error.
====================================
Screen shot:
Please note the below screen shot has given the error code 0x851A001A which is same in case of failure of all the other features which have failed during this installation. Hence i have uploaded only one screen shot.
2. Log file content.
=================================
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2014-05-04 21:15:35
End time: 2014-05-04 21:51:45
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 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: SERVER1
Machine processor count: 2
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 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server Replication 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033
Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Management Tools - Basic
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Management Tools - Complete
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Client Tools Connectivity
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Client Tools Backwards Compatibility
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Client Tools SDK
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Integration Services
1033 Enterprise Edition 11.0.2100.60 No
SQL Server 2012 Reporting Services - SharePoint
11.0.2100.60 No
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: F:\x64\setup\
Installation edition: Enterprise
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: ms\sql
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
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: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SCOM
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: SCOM
INSTANCENAME: SCOM
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: NT Service\ReportServer$SCOM
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: ms\sql
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: MS\Gautam, MS\SCOM Users
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\20140504_204851\ConfigurationFile.ini
Detailed results:
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: 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: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140504_204851\SystemConfigurationCheck_Report.htmSorry about the error in the path, but you find the files that's the main thing.
Indeed it is a certificate problem:
2014-05-04 21:47:43.56 spid12s Error: 17190, Severity: 16, State: 1.
2014-05-04 21:47:43.56 spid12s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2014-05-04 21:47:43.56 spid12s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2014-05-04 21:47:43.57 spid12s Error: 17182, Severity: 16, State: 1.
2014-05-04 21:47:43.57 spid12s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2014-05-04 21:47:43.57 spid12s Error: 17826, Severity: 18, State: 3.
2014-05-04 21:47:43.57 spid12s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-05-04 21:47:43.57 spid12s Error: 17120, Severity: 16, State: 1.
2014-05-04 21:47:43.57 spid12s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I've recall that I've tried to help people with this error before, but I'm sure they were able to sort it out.
Anyway, this blog post,
http://blogs.msdn.com/b/sqljourney/archive/2012/10/09/sql-2008-service-fails-to-come-online-with-a-valid-certificate-could-not-be-found-and-it-is-not-possible-to-create-a-self-signed-certificate.aspx
suggests the issue is a corrupted user profile, and you should try to use a different service account.
This blog also seems to have a simple solution, but I cannot vouch for that it will work:
http://www.beejblog.com/2012/02/sql-server-solved-unable-to-initialize.html
Erland Sommarskog, SQL Server MVP, [email protected] -
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 trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
WSUS Server : Windows Server 2012 R2
Remote SQL Server: 2012 SP1 CU7 hosted on Windows Server 2012 R2
Please let me know if anyone has experienced this issue.We were trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
Same error even after rebooting the server multiple times.
WSUS Server : Windows Server Standard2012 R2
Remote SQL Server: Windows Server 2012 SP1 CU7 hosted on Windows Server 2012 R2
Event ID 7000:
The Windows Internal Database service failed to start due to the following error:
The service did not start due to a logon failure.
Event ID 7041
The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.
Service: MSSQL$MICROSOFT##WID
Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID
This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user
right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated
with this node might be removing the right.
I found following article:
"MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID" error when you install WID in Windows Server 2012
http://support.microsoft.com/kb/2832204/en-us
To work around the issue, use one of the following methods:
Assign the Log on as a service user right to NT SERVICE\ALL SERVICES in the GPO that defines the user right.
Exclude the computer from the GPO that defines the user right.
We moved the SCCM server to OU where no policies were getting applied and then applied the new GPO to that OU. Restarted the server and we were able to install WSUS role.
Regards
PR -
I have an Script mostly that is generated by SSMS which works with-out issue on SQL Server 2008, but when I attempt to run it on a new fresh install of SQL Server 2012 I get an Msg 8631. Internal error: Server stack limit has been reached. Please look for
potentially deep nesting in your query, and try to simplify it.
The script itself doesn't seem to be all that deep or nested. The script is large 2600 lines and when I remove the bulk of the 2600 lines, it does run on SQL Server 2012. I'm just really baffled why something that SQL Server generated with very
few additions/changes AND that WORKS without issue in SQL Server 2008 R2 would suddenly be invalid in SQL Server 2012
I need to know why my script which is working great on our current SQL Server 2008 R2 servers suddenly fails and won't run on an new SQL Server 2012 server. This script is used to create 'bulk' Replications on a large number of DBs saving a tremendous
amount of our time doing it the manual way.
Below is an 'condensed' version of the script which fails. I have removed around 2550 lines of specific sp_addarticle statements which are mostly just copy and pasted from what SQL Management Studio 'scripted' for me went I when through the Replication
Wizard and told it to save to script.
declare @dbname varchar(MAX), @SQL nvarchar(MAX)
declare c_dblist cursor for
select name from sys.databases WHERE name like 'dbone[_]%' order by name;
open c_dblist
fetch next from c_dblist into @dbname
while @@fetch_status = 0
begin
print @dbname
SET @SQL = 'DECLARE @dbname NVARCHAR(MAX); SET @dbname = ''' + @dbname + ''';
use ['+@dbname+']
exec sp_replicationdboption @dbname = N'''+@dbname+''', @optname = N''publish'', @value = N''true''
use ['+@dbname+']
exec ['+@dbname+'].sys.sp_addlogreader_agent @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1, @job_name = null
-- Adding the transactional publication
use ['+@dbname+']
exec sp_addpublication @publication = N'''+@dbname+' Replication'', @description = N''Transactional publication of database
'''''+@dbname+''''' from Publisher ''''MSSQLSRV\INSTANCE''''.'', @sync_method = N''concurrent'', @retention = 0, @allow_push = N''true'', @allow_pull = N''true'', @allow_anonymous = N''false'', @enabled_for_internet
= N''false'', @snapshot_in_defaultfolder = N''true'', @compress_snapshot = N''false'', @ftp_port = 21, @allow_subscription_copy = N''false'', @add_to_active_directory = N''false'', @repl_freq = N''continuous'', @status = N''active'', @independent_agent = N''true'',
@immediate_sync = N''true'', @allow_sync_tran = N''false'', @allow_queued_tran = N''false'', @allow_dts = N''false'', @replicate_ddl = 1, @allow_initialize_from_backup = N''true'', @enabled_for_p2p = N''false'', @enabled_for_het_sub = N''false''
exec sp_addpublication_snapshot @publication = N'''+@dbname+' Replication'', @frequency_type = 1, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 8,
@frequency_subday_interval = 1, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1
-- There are around 2400 lines roughly the same as this only difference is the tablename repeated below this one
use ['+@dbname+']
exec sp_addarticle @publication = N'''+@dbname+' Replication'', @article = N''TABLE_ONE'', @source_owner = N''dbo'', @source_object = N''TABLE_ONE'', @type = N''logbased'', @description = null, @creation_script =
null, @pre_creation_cmd = N''drop'', @schema_option = 0x000000000803509F, @identityrangemanagementoption = N''manual'', @destination_table = N''TABLE_ONE'', @destination_owner = N''dbo'', @vertical_partition = N''false'', @ins_cmd = N''CALL sp_MSins_dboTABLE_ONE'',
@del_cmd = N''CALL sp_MSdel_dboTABLE_ONE'', @upd_cmd = N''SCALL sp_MSupd_dboTABLE_ONE''
EXEC sp_executesql @SQL
SET @dbname = REPLACE(@dbname, 'dbone_', 'dbtwo_');
print @dbname
SET @SQL = 'DECLARE @dbname NVARCHAR(MAX); SET @dbname = ''' + @dbname + ''';
use ['+@dbname+']
exec sp_replicationdboption @dbname = N'''+@dbname+''', @optname = N''publish'', @value = N''true''
use ['+@dbname+']
exec ['+@dbname+'].sys.sp_addlogreader_agent @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1, @job_name = null
-- Adding the transactional publication
use ['+@dbname+']
exec sp_addpublication @publication = N'''+@dbname+' Replication'', @description = N''Transactional publication of database
'''''+@dbname+''''' from Publisher ''''MSSQLSRV\INSTANCE''''.'', @sync_method = N''concurrent'', @retention = 0, @allow_push = N''true'', @allow_pull = N''true'', @allow_anonymous = N''false'', @enabled_for_internet
= N''false'', @snapshot_in_defaultfolder = N''true'', @compress_snapshot = N''false'', @ftp_port = 21, @allow_subscription_copy = N''false'', @add_to_active_directory = N''false'', @repl_freq = N''continuous'', @status = N''active'', @independent_agent = N''true'',
@immediate_sync = N''true'', @allow_sync_tran = N''false'', @allow_queued_tran = N''false'', @allow_dts = N''false'', @replicate_ddl = 1, @allow_initialize_from_backup = N''true'', @enabled_for_p2p = N''false'', @enabled_for_het_sub = N''false''
exec sp_addpublication_snapshot @publication = N'''+@dbname+' Replication'', @frequency_type = 1, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 8,
@frequency_subday_interval = 1, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1
-- There are around 140 lines roughly the same as this only difference is the tablename repeated below this one
use ['+@dbname+']
exec sp_addarticle @publication = N'''+@dbname+' Replication'', @article = N''DB_TWO_TABLE_ONE'', @source_owner = N''dbo'', @source_object = N''DB_TWO_TABLE_ONE'', @type = N''logbased'', @description = null, @creation_script
= null, @pre_creation_cmd = N''drop'', @schema_option = 0x000000000803509D, @identityrangemanagementoption = N''manual'', @destination_table = N''DB_TWO_TABLE_ONE'', @destination_owner = N''dbo'', @vertical_partition = N''false''
EXEC sp_executesql @SQL
fetch next from c_dblist into @dbname
end
close c_dblist
deallocate c_dblist
George P Botuwell, ProgrammerHi George,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
If you have any feedback on our support, please click
here.
Allen Li
TechNet Community Support -
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 -
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 :) -
Cannot uninstall sql server 2012 on Windows 7
This is the error a co-worker gets when trying to uninstall SQL Server 2012. She is running Windows 7 Professional
Service Pack 1, 64 bit OS. She had SQL 2008 installed and then installed 2012 Enterprise as well, because she needed it for a project. The problem is we don't have a license for local instances of Enterprise, so we need to install it. However,
2012 Setup is telling us we don't have the minimum requirements to *install* 2012. Which leads to some interesting questions:
1) Why does the 2012 installer allow you to install but not uninstall when you don't meet system requirements?
2) How does that make any sense?
3) Does she really need to install more software to be able to uninstall? Since SP1 is already installed, what would that be?
Thanks!
JoeHello,
In theory, if Windows 7 has SP1 then it is compatible with SQL Server 2012.
Please try to use the procedure explained on the following article:
http://msdn.microsoft.com/en-us/library/ms143412.aspx
If that article does not help, please perform the following steps to manually uninstall SQL Server 2012:
1. Uninstall all SQL Server 2012 components you can using Control Panel -> Programs and Features
2. Backup the registry.
3. Delete the following keys in regedit:
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
--HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and delete all the sub-keys referencing SQL Server.
5. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
6. Rename all the SQL Server folders in the computer like
C:\Program Files\Microsoft SQL Server and subfolders.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
SQL Server 2012 PowerView & PoverPivot in combination with SharePoint 2013
Hi,
I have been reading articles on the internet about this, and I am little bit confused. I understand this is also changed since in SP2013. Could someone with experience clarify.
1. It looks like Power View has become a part of Reporting Services and can not be installed without Reporting Services, is this correct? If this is true, then what is this
http://www.microsoft.com/en-us/download/details.aspx?id=35577 If not, why do I see a lot of links referring to PowerView as a part of Reporting Services? for example
http://www.codeproject.com/Articles/615462/Configure-Power-View-Reporting-Services-Features-o
2. Do I need Analysis Services in order to use PowerView, is other words is Analysis Services a requirement?
3. Where do I run the SQL Server 2012 Setup? I was assuming that I need to run it on SharePoint in order to add and register dll's on the SP servers, they are needed in order to create Service Applications (PowerView & PoverPivot). However in pictures
on the
http://www.codeproject.com/Articles/615462/Configure-Power-View-Reporting-Services-Features-o link I see they are adding features to SQL instance. So do we run it on SharePoint or SQL server? If we run it on SharePoint server, what to do with instance name?
If on SQL server, how will SharePoint server get dll's in order to create Service Applications?
4. Can SQL 2008 be used for PowerView & PoverPivot configuration databases? I mean a scenario when SharePoint has 2012 versions of PowerView & PoverPivot DLLs (i.e. PowerView & PoverPivot Service Applications created
with SQL2012 version), but configuration databases itself for these applications are in SQL 2008? I know that such a scenario was supported with SSRS on SP2010(you could simply run the SQL2012 setup on SP server and add SQL2012 SSRS, later when you configure
SSRS in SharePoint mode SQL 2008 database could be used as a SSRS configuration database)...
Thanks in advance!
Tofig1. Part of the confusion comes from the fact that there are several versions of powerview: powerview for SharePoint and PowerView for Excel. But yes, for SharePoint integration it's part of SSRS. (If you're not talking about SharePoint, then you can create
and use PowerView in Excel. No SSRS or SharePoint required. But, the link you provided is for PowerPivot for SharePoint. This provides additional functionality for folks that want to surface PowerPivot workbooks in SharePoint. (which is different than PowerView).
(PowerPivot = tabular data mode in excel = the ability to create pivottables/charts with millions of rows of data in Excel with jaw dropping performance (sorry for the advertising speak, but in my experience, it's true). PowerView = the ability to create
dashboards / eye candy / other neat visualizations like maps for data that is stored in a tabular data model (PowerPivot or SSAS in tabular mode)).
2. No. PowerView was originally designed to use "tabular data models" as their source of data. There are two ways to create a tabular data model: An SSAS instance in tabular mode, or an Excel Workbook with a powerPivot data model (PowerPivot is the excel
version of the tabular data model). So, if you have a workbook that has data loaded in through PowerPivot, you can create a PowerView report in that workbook and surface it with excel services, with no SSAS needed.
3. On a SharePoint box. The only way to install SSRS in SharePoint integrated mode is to install SSRS on a SharePoint WFE. (The databases they use will go on the SQL box, but the bits for SSRS go on the SharePoint box)
4. According to the following doc, SharePoint 2013 only supports SSRS 2012 SP1 (which means only SQL 2012):
http://msdn.microsoft.com/en-us/library/gg492257.aspx
Mike G. -
Pre-Requisite Check SQL Server 2012 SP2 TCP Port Enabled Error
When doing the pre-requisite check to install SCCM (CAS) using an instance of SQL Server 2012 SP2, you get the following error even though SQL Server TCP port has been enabled, set to static port 4022 on the IP addresses in use in SQL Server Configuration
Manager under Protocols for <SQLInstanceName>: configuration manager primary site and central administration site require sql server tcp enables and set to static port
To resolve this issue, make sure "4022" is also set in the IPAll node in SQL Server Configuration Manager under Protocols for <SQLInstanceName> then restart the SQL Service and re-run the pre-requisite check and you should be good to go.
To avoid SCCM SQL-related install failure, keep in mind that SCCM SQL Service Broker (SSB) (used to replicate data between database sites) is set to port 4022 by default. This is different from and cannot be same as the tcp static port set in SQL Server
Configuration Manager under Protocols for <SQLInstanceName>. For example SSB can use its default tcp port 4022 while a static tcp port of 4023 can be set in SQL Server Configuration Manager under Protocols for <SQLInstanceName> or vice-versa. The
SCCM SSB port number can be adjusted during SCCM installation on the Database Information page. My take it so change SSB port to 4023 and leave SQL default port at 4022 since SQL serves potentially many apps while SSB is used within/by SCCM.
If you are getting errors relating to SQL Server service running accounts, SQL Server Collation, and/or SQL Server sysadmin rights while attempting to install a primary site, unselect the SCCM installation option to install default settings at the beginning
of the install process.
Also, ensure to install important updates and restart the server.Thank you for sharing.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Can't Install SQL Server 2012 in Windows 8.1 Pro
I have Visual Studio 2010 Ultimate installed on my unit.
I tried installing SQL Server 2012 and it failed because I don't have the SP1 for VS2010.
I installed SP1 successfully, but now I can't install the SQL Server 2012.
Error says: Managed SQL Server 2012 has stopped
I have scanned many forums but cannot find the answer.
I have .Net frameworks 3.5 and 4.0 installed in my laptop, still, no progress.
Please help me with this. Thanks a lot.Check below thread seems to be similar issue
You need to enable .NET Framework 3.5 using Control Panel
Control Panel -> Programs and Features -> Turn on or off features.
Install or enable PowerShell 2.0 also.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/1fe44750-0d6b-46ff-929a-15e616e33546/problem-installing-sql-server-2012-sp1-managed-sql-server-installer-has-stopped-working
Please click the Mark as answer button and vote as helpful if this reply solves your problem -
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 -
EHP2 - EHP7 Upgrade Path using SQL Server 2012/Win Server 2012 R2
Hi Guys.
I have question regarging Upgrade Roadmap for a ERP 6 EHP2 system based on NW 7.01 which I would like to Upgrade to ERP6 EHP7 SP7
Source System is
Windows 2012
SQL Server 2008 R2
EHP2 for ERP 6.0 SPS Level 14
Target System
Windows 2012
SQL Server 2012
EHP7 for ERP 6.0 SP 7 based on NW 7.4 SP 9
During Upgrade checks it says I must Upgrade Database first before continue since DB Release is too low for NW 7.4 SP9 as stated in Note
1951491 - Minimal DB system platform requirements for SAP NetWeaver 7.4 SP08
So, at this point I agree i have to update SQL Server to 2012 before next step
Now, my concern is that my Source System does not have the minimum NW SP level (14) to run under SQL Server 2012 which is 26.
Im currently running SAP Kernel 721 EXT Level 401 which is above mininum
According to Note 1651862 - Release planning for Microsoft SQL Server 2012 that would not be possible
Existing systems of SAP products that are out of SAP maintenance can be upgraded to SQL Server 2012 in order to prepare a SAP upgrade, if they match the SAP NetWeaver Support Package requirements defined below.
SAP products prior to SAP NetWeaver 7.0 are not supported at all on SQL Server 2012.
Required minimum SAP Netweaver Support Package Stacks (SPSs) for SQL Server 2012 (SAP ABAP, SAP ABAP+JAVA stacks)
SAP NETWEAVER 7.0 - SPS 26 (SAP BASIS 26, SAP BW 28)
SAP EHP1 FOR SAP NETWEAVER 7.0 - SPS 11 (SAP BASIS 11, SAP BW 11)
SAP EHP2 FOR SAP NETWEAVER 7.0 - SPS 11 (SAP BASIS 11, SAP BW 11)
SAP EHP3 FOR SAP NETWEAVER 7.0 - SPS 03 (SAP BASIS 03, SAP BW 03)
SAP NETWEAVER 7.1 - SPS 14 (SAP BASIS SP14)
SAP EHP1 FOR SAP NETWEAVER 7.1 EhP1 - SPS 10(SAP BASIS SP10, SAP BW SP10)
SAP NetWeaver 7.2 - no restriction
SAP NETWEAVER 7.3 - SPS 07 (SAP BASIS 07, SAP BW 07)
SAP EHP1 FOR SAP NETWEAVER 7.3 - SPS 03 (SAP BASIS 03, SAP BW 03)
If your system is running on a SPS lower than the one required above, you have to apply the minimum required SPS before upgrading/migrating to SQL Server 2012.
If you install a NetWeaver product on SQL Server 2012, the required SPS for your product must be applied immediately after the installation - see SAP note 1676665, section I for more information.
But performing the Upgrade would be technically possible? I mean not for productive use but technicaly during that time the Database is Upgrade and during SUM Execution.
According to the note it states if you install a Netweaver Product in SQL Server 2012, SPS must be applied immediately, so is kinda ambigous what SAP is saying.
Best
MartinHi Martin,
For a test scenario, there's no harm in trying it (other than spending a lot of time on it, but hopefully that will prove not to be a waste). Generally, I expect you'll be fine upgrading your DBMS even though you aren't on the required minimum SP yet. The main thing you'll be missing out on is the updates to DBACOCKPIT, but once you do your EhP upgrade (with sps update included), you'll be putting that in place.
So, you could try this on your sandbox system and see if there are any problems. I assume the intent is to start the EhP upgrade as soon as the DBMS upgrade is done, right? In other words, you won't be actually using the system without the required SP except to run the EhP upgrade?
Alternatively, you could do a minimal support pack update, perhaps just a Basis SP only, to the minimum SP needed for your current release, then do the DBMS upgrade, then proceed with the EhP upgrade. This would be the safest procedure, but, as I said, I expect you can probably get away without going to this level without much problem. Again, the idea would be minimizing the time between the start and end of the total project on each system (DEV, QAS, PRD, etc).
Regards,
Matt -
SQL Server 2012 installation problem (error server didn't respond in timely fashion ....)
Hi everyone,
I am new to SQL server....I am learning C# programming using visual studio 2013 . And I want to learn SQL database language to create and practice C# database project....My computer meets all the hardware requirement for SQL installation (i.e. My computer
has window 7 OS , 80 GB freen HD and 6 GB RAM. ) Therefore I download Microsoft SQL server express 2012 try to install it in my computer (which already has visual studio).
But during installation of SQL server I have problem ...it says
the server doesn't respond in timely fashion. When I research about it everyone were saying uninstall sql and reinstall again. I uninstall and re install but still having same problem...
The database engine also not installed displaying same error.
I don't know how can i install sql server 2012 to use with visual studio in same computer.
Can somebody please help with SQL installation please ?
It will be great help.
Many thanks in advance
regards
rashHi
my summary file is :
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2146232832
Start time: 2015-04-06 11:34:18
End time: 2015-04-06 19:04:46
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.
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.
Next step for IS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
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 AS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: RASHA-VAIO
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
SQL Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS Database Engine Services 1033
Express Edition 10.1.2531.0 No
SQL Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS SQL Server Replication 1033
Express Edition 10.1.2531.0 No
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: E:\x64\setup\
Installation edition: Enterprise
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_AS
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: TABULAR
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: RASHA-VAIO\RASHA
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: MAIN
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\20150406_112342\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: RASHA-VAIO\RASHA
ENABLERANU: false
ENU: true
ERRORREPORTING: false
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: 0
FILESTREAMSHARENAME: <empty>
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: FilesOnlyMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: RASHA-VAIO\RASHA
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\20150406_112342\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: 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: 0x80004005
Error description: The service did not respond to the start or control request in a timely fashion.
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=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325
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: 0x80004005
Error description: The service did not respond to the start or control request in a timely fashion.
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=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325
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: 0x80004005
Error description: The service did not respond to the start or control request in a timely fashion.
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=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325
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: 0x80004005
Error description: The service did not respond to the start or control request in a timely fashion.
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=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration 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 Integration Services
Component error code: 0x84BB0001
Error description: The service did not respond to the start or control request in a timely fashion.
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=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325
Feature: Data Quality Client
Status: Passed
Feature: Reporting Services - Native
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 Reporting Services
Component error code: 0x84BB0001
Error description: The service did not respond to the start or control request in a timely fashion.
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=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325
Feature: Analysis 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 Analysis Services
Component error code: 0x80131600
Error description: The service could not be started. Reason: The service did not respond to the start or control request in a timely fashion.
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=0x88A466B0%400x857354B0&EvtType=0x88A466B0%400x857354B0
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\20150406_112342\SystemConfigurationCheck_Report.htm
I hope it will help you to figure out ...i dont know how to solve this issue ..i have un install and re install more than 5 times.
thank you -
SQL Server 2012 is prompting wrong message while creating new instance.
Summary:
While performing two task simultaneously 1) deleting existing SQL Server 2008 r2 instance 2) Creating SQL Server 2012 Instance. I received wrong message.
Explanation:
I have SQL Server 2012 setup in my server. By mistake I created SQL Server 2008 r2 instance.
Now simultaneously I was performing two task 1) deleting SQL Server 2008 r2 instance 2) Creating SQL Server 2012 Instance.
While creating SQL Server 2012 instance i received popup message "Another SQL Server 2012 setup is running but the running setup was not SQL Server 2012, it was SQL Server 2008 r2.
Hello,
You should not run two SQL Server setups at the same time. In fact, SQL Server has a rule to verify there is no pending restart because of an installation/uninstallation in progress.
Please cancel the installation of SQL Server and continue uninstalling the SQL Server 2008 R2 instance.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Maybe you are looking for
-
Hi all, I have a Problem with the SLD Configuration in Integration Framework for SMEs. The instance of the SQL Server, that I have to connect includes a backslash and I think, this could be the problem. The JDBC Connection is successfull. Does anyone
-
Using a function as condition for conditional formatting
Hello, I am trying to switch from Excel to Numbers and I'm having trouble figuring out the conditional formatting in Numbers. In Excel, cell(s) can be highlighted, font changed, etc based on a function linked to another cells value. That is, cells A1
-
Favicon background appears black
In Internet Explorer 11 the favicon background appears black. This problem do not exist in older IE versions or in other browsers (like, FF, Safari, Chrome, ...). You can see what I am talking in site www.e-grou.com What could be? Thanks & Regards, R
-
Hy, i use a Garmin GPS for ride and run, and i'm interested to used an app Garmin Connect Mobile. this one is available for IPhone and android, but i can't find it for BB. is it possible to developpe an app for this?? i use Bold 9790. thanks.
-
How can I change the reqion from Thailand to Australia
Thai credit card is not valid in Australia Sotre. How do I change the region kindly suggest me. Thanks