Hello

I am trying to do backups with Backup Exec on an SQL 2014 server. I am getting an error that looks like this:

WARNING: The DBCC NEWALLOC command requires SA rights.  The consistency check cannot be completed.User 'guest' does not have permission to run DBCC checkdb for database 'master'
There was a problem running the DBCC.The server principal "domain\backup account" is not able to access the database "tew_app_macro" under the current security context.
My two questions are, 1) how do I remove the 'guest' account from the permissions tab in each database; and 2) hos do I give the domain\user account
the ability\access  to run the DBCC?
Thanks

Stephen Keating

I am attempting to upgrade an existing SQL Server 2012 Express database instance. I'm running the upgrade from the command line with the following command.

SQLEXPR_x64_ENU.exe /Action=Upgrade /UPDATEENABLED=False /IACCEPTSQLSERVERLICENSETERMS=True /INSTANCENAME=MyServer /ENU=True /ISSVCACCOUNT="NT AUTHORITY\\NetworkService"

It passes all the rule checks, but then while installing it gives a not too informative error- The Database Engine error log location is missing from the Parameters key.

From the log file -

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, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A004A
  Error description:             The Database Engine error log location is missing from the Parameters key.

I've reviewed the following posts and none of them have resolved the issue:

https://sqlcan.com/2014/10/20/the-database-engine-system-data-directory-in-the-registry-is-not-valid/ - The SQLDataRoot value is correctly set

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/116cb02f-81f0-456b-ab7b-2c2dc157e99e/sql-2000-to-2008-upgrade-failed-message-wait-on-the-database-engine-recovery-handle-failed-check?forum=sqlsetupandupgrade 
and
https://blogs.msdn.microsoft.com/varund/2009/03/21/how-to-verify-path-for-sql-server-error-log-files/ - the Parameters key has all the correct values assigned

https://answers.microsoft.com/en-us/windows/forum/windows8_1-update/windows-update-fail-sql-server-update/8d2be866-8a3c-4c8e-8071-df26c057a4a3 - the database owner is 'sa'

The current database version is the RTM release. I've tried SP1, SP2, and SP3 installers with the same result. I've tested this on (x64) versions of Windows 7, Windows 8 and Windows 10 Virtual Machines with the same result.

Any additional support would be appreciated.

Right click  - Database 

select  - Import Data tier application

After finish select file and click next it show error like this.

(Ps. i try to restart pc and do it again not connect to anything it still show)

---

 SQL Server Management Studio15.0.18068.0
Microsoft Analysis Services Client Tools15.0.900.163
Microsoft Data Access Components (MDAC)10.0.17134.1
Microsoft MSXML3.0 6.0 
Microsoft Internet Explorer9.11.17134.0
Microsoft .NET Framework4.0.30319.42000
Operating System6.3.17134

ERROR BELOW===================================

There is already an open DataReader associated with this Command which must be closed first. (System.Data)


===================================

Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)

------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476

------------------------------
Program Location:

   at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
   at Microsoft.SqlServer.Management.Smo.ExecutionManager.GetEnumeratorData(Request req)
   at Microsoft.SqlServer.Management.Smo.SqlSmoObject.GetCollationRelatedProperties(String dbName, ContainmentType& containmentType, CatalogCollationType& catalogCollation)
   at Microsoft.SqlServer.Management.Smo.SqlSmoObject.GetDbComparer(Boolean inServer)
   at Microsoft.SqlServer.Management.Smo.SqlSmoObject.InitializeStringComparer()
   at Microsoft.SqlServer.Management.Smo.SqlSmoObject.get_StringComparer()
   at Microsoft.SqlServer.Management.Smo.AbstractCollectionBase.get_StringComparer()
   at Microsoft.SqlServer.Management.Smo.SimpleObjectCollectionBase.InitInnerCollection()
   at Microsoft.SqlServer.Management.Smo.SmoCollectionBase.get_NoFaultCount()
   at Microsoft.SqlServer.Management.Smo.SqlSmoObject.InitObjectsFromEnumResultsRec(SqlSmoObject currentSmoObject, XPathExpression levelFilter, Int32 filterIdx, IDataReader reader, Int32 columnIdx, Object[] parentRow, Boolean forScripting, List`1 urnList, Int32 startLeafIdx)
   at Microsoft.SqlServer.Management.Smo.SqlSmoObject.InitObjectsFromEnumResults(Urn levelFilter, IDataReader reader, Boolean forScripting, List`1 urnList, Int32 startLeafIdx, Boolean skipServer)
   at Microsoft.SqlServer.Management.Smo.SqlSmoObject.InitChildLevel(Urn levelFilter, ScriptingPreferences sp, Boolean forScripting, IEnumerable`1 extraFields)
   at Microsoft.SqlServer.Management.Dac.DacWizard.ImportSettingPageController.CommitChanges()
   at Microsoft.SqlServer.Management.TaskForms.SqlWizardPageController.Microsoft.SqlServer.Management.TaskForms.ISqlWizardPageController.CommitChanges()
   at Microsoft.SqlServer.Management.TaskForms.ControllerPage.OnSave()
   at Microsoft.SqlServer.Management.TaskForms.ControllerPage.OnWizardNext()
   at Microsoft.SqlServer.Management.SqlWizardFramework.WizardFramework.GoToPage(Page page)
   at Microsoft.SqlServer.Management.SqlWizardFramework.WizardFramework.OnNext()
   at Microsoft.SqlServer.Management.SqlWizardFramework.WizardButtonsPanel.OnNext(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at Microsoft.SqlServer.Management.ActionHandlers.DialogBasedActionHandler.RunTaskFormThread(Object contextObject)

===================================

There is already an open DataReader associated with this Command which must be closed first. (System.Data)

------------------------------
Program Location:

   at System.Data.SqlClient.SqlInternalConnectionTds.ValidateConnectionForExecute(SqlCommand command)
   at System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String method, SqlCommand command)
   at System.Data.SqlClient.SqlCommand.ValidateCommand(String method, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader()
   at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
   at Microsoft.SqlServer.Management.Common.ServerConnection.GetExecuteReader(SqlCommand command)
   at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteReader(String sqlCommand, SqlCommand& command)
   at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataReader(String query, SqlCommand& command)
   at Microsoft.SqlServer.Management.Smo.DataProvider.SetConnectionAndQuery(ExecuteSql execSql, String query)
   at Microsoft.SqlServer.Management.Smo.ExecuteSql.GetDataProvider(StringCollection query, Object con, StatementBuilder sb, RetriveMode rm)
   at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillData(ResultType resultType, StringCollection sql, Object connectionInfo, StatementBuilder sb)
   at Microsoft.SqlServer.Management.Smo.SqlObjectBase.FillDataWithUseFailure(SqlEnumResult sqlresult, ResultType resultType)
   at Microsoft.SqlServer.Management.Smo.SqlObjectBase.BuildResult(EnumResult result)
   at Microsoft.SqlServer.Management.Smo.DatabaseLevel.GetData(EnumResult res)
   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)

This appears to be the same problem as in https://social.msdn.microsoft.com/Forums/sqlserver/en-US/5006a537-f588-4062-8dec-922ae85cf698/sql-server-2012-error-0x851a004a-during-upgrade?forum=sqlexpress but that has no answer.

On a clean test VM, I can run the SQL Express 2012 RTM installer successfully.

On a clean test VM, I can also run the 2012 SP4 installer successfully.

However, trying to run the 2012 SP4 installer to perform an upgrade on an existing RTM instance fails:

(This is repeatable on several different Windows versions and systems.)

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2061893558
  Start time:                    2019-03-27 19:12:48
  End time:                      2019-03-27 19:14:56
  Requested action:              Upgrade

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
  Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.


Machine Properties:
  Machine name:                  WIN8-VMGL
  Machine processor count:       2
  OS version:                    Future Windows Version
  OS service pack:               
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                  Language             Edition              Version         Clustered  Configured
  SQL Server 2012      COMPAC               MSSQL11.COMPAC                 Database Engine Services                 1033                 Express Edition      11.0.2100.60    No         Yes       
  SQL Server 2012      COMPAC               MSSQL11.COMPAC                 SQL Server Replication                   1033                 Express Edition      11.0.2100.60    No         Yes       
  SQL Server 2012                                                          Management Tools - Basic                 1033                 Express Edition      11.0.2100.60    No         Yes       

Package properties:
  Description:                   Microsoft SQL Server 2012 
  ProductName:                   SQL Server 2012
  Type:                          RTM
  Version:                       11
  Installation location:         C:\CDBSQL2012\x64\setup\
  Installation edition:          Express

  Slipstream:                    True
  SP Level                       4

Product Update Status:
  User selected not to include product updates.

User Input Settings:
  ACTION:                        Upgrade
  AGTDOMAINGROUP:   <empty>
  ALLOWUPGRADEFORSSRSSHAREPOINTMODE: false
  CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20190327_191130\ConfigurationFile.ini
  ENU:                           true
  ERRORREPORTING:                false
  FAILOVERCLUSTERROLLOWNERSHIP:  2
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  FTUPGRADEOPTION:               Import
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  false
  INDICATEPROGRESS:              false
  INSTANCEID:                    COMPAC7001
  INSTANCENAME:                  COMPAC
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   true
  RSCATALOGSERVERINSTANCENAME:   Unknown
  RSUPGRADEDATABASEACCOUNT:      <empty>
  RSUPGRADEPASSWORD:             <empty>
  SQMREPORTING:                  false
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 false
  UpdateSource:                  Slipstream
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20190327_191130\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, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A004A
  Error description:             The Database Engine error log location is missing from the Parameters key.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.7001.0&EvtType=0x93C54E3E%400x97A656BB%401306%4074&EvtType=0x93C54E3E%400x97A656BB%401306%4074

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A004A
  Error description:             The Database Engine error log location is missing from the Parameters key.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.7001.0&EvtType=0x93C54E3E%400x97A656BB%401306%4074&EvtType=0x93C54E3E%400x97A656BB%401306%4074

  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\20190327_191130\SystemConfigurationCheck_Report.htm

The relevant section from the detail log appears to be:

(01) 2019-03-27 19:13:28 Slp: ----------------------------------------------------------------------
(01) 2019-03-27 19:13:28 Slp: Running Action: SqlEngineConfigAction_patch_validation_Cpu64
(01) 2019-03-27 19:13:28 Slp: Action Data:
(01) 2019-03-27 19:13:28 Slp:   Feature = SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64
(01) 2019-03-27 19:13:28 Slp:   Scenario = patch
(01) 2019-03-27 19:13:28 Slp:   Timing = Validation
(01) 2019-03-27 19:13:28 Slp:   ConfigObjectType = Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate
(01) 2019-03-27 19:13:28 Slp:   FeatureName = SQL_Engine_Core_Inst
(01) 2019-03-27 19:13:28 Slp:   FeatureCpuType = Cpu64
(01) 2019-03-27 19:13:28 Slp:   FeaturePackageId = sql_engine_core_inst
(01) 2019-03-27 19:13:28 Slp:   SlipstreamInstall = 1
(01) 2019-03-27 19:13:28 Slp:   InstallId = Machine[@ID='WIN8-VMGL']/Product[@ID='SQL2011']/Instance[@ID='COMPAC']/Feature[@ID='SQLEngine' and @RegistryPath='SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.COMPAC\Setup\SQL_Engine_Core_Inst' and @RootPath='SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.COMPAC']/Install[@ProductCode='18B2A97C-92C3-4AC7-BE72-F823E0BC895B']
(01) 2019-03-27 19:13:28 SQLEngine: : Action Scenario: Upgrade, Feature Scenario: Patch, Resolved Scenario Upgrade 
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: container.ActiveNode = 
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: container.IsActiveNodeUpgraded = False
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: container.Version = 
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: container.IsDefaultInstance = False
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: container.InstanceId = MSSQL11.COMPAC7001
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: container.ReferenceInstanceId = MSSQL11.COMPAC7001
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: container.InstanceName = COMPAC
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: container.SqlServerServiceName = MSSQL$COMPAC
(01) 2019-03-27 19:13:28 SQLEngine: --GroupProperties: Loading group properties from local machine.
(01) 2019-03-27 19:13:28 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine 
(01) 2019-03-27 19:13:28 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.COMPAC7001\Setup
(01) 2019-03-27 19:13:28 SQLEngine: --EffectiveProperties: Dumping Effective Properties for new instance.
(01) 2019-03-27 19:13:28 SQLEngine: --EffectiveProperties: 	InstanceId = MSSQL11.COMPAC7001
(01) 2019-03-27 19:13:28 SQLEngine: --EffectiveProperties: 	InstanceName = COMPAC
(01) 2019-03-27 19:13:28 SQLEngine: --EffectiveProperties: 	IsDefaultInstance = False
(01) 2019-03-27 19:13:28 SQLEngine: --EffectiveProperties: 	SqlServerServiceName = MSSQL$COMPAC
(01) 2019-03-27 19:13:28 SQLEngine: --EffectiveProperties: 	IsExpressSku = True
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: Dumping Registry Properties
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: SqlServiceRelativeRegPath = System\CurrentControlSet\Services\MSSQL$COMPAC
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: CompleteInstanceRegPathByName = SOFTWARE\Microsoft\Microsoft SQL Server\COMPAC
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: CompleteInstanceRegPathById = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.COMPAC7001
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: ReferenceInstanceRegPathById = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.COMPAC7001
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: MSSQLServerInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.COMPAC7001\MSSQLServer
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: ReferenceMSSQLServerInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.COMPAC7001\MSSQLServer
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: SetupInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.COMPAC7001\Setup
(01) 2019-03-27 19:13:28 SQLEngine: --RegistryProperties: ReferenceSetupInstanceRegPath = SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.COMPAC7001\Setup
(01) 2019-03-27 19:13:28 SQLEngine: --GroupProperties: Dumping Group Properties
(01) 2019-03-27 19:13:28 SQLEngine: --GroupProperties: SqlEngineGroupSid = 
(01) 2019-03-27 19:13:28 SQLEngine: --GroupProperties: SqlEngineGroupNameFromSid = 
(01) 2019-03-27 19:13:28 SQLEngine: --GroupProperties: SqlEngineGroupNameFromSidNoDomain = 
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: Dumping Directory Propreties
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: DataRootDirectory = [DataRootDirectory]
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: SystemDataDirectory = [DataRootDirectory]\DATA
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: InstallSqlInstanceDir = C:\Program Files\Microsoft SQL Server\MSSQL11.COMPAC7001\MSSQL
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: DefaultDataDirectory = [DataRootDirectory]\DATA
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: DefaultLogDirectory = [DataRootDirectory]\DATA
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: BackupDirectory = [DataRootDirectory]\Backup
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: TempDbDirectory = [DataRootDirectory]\DATA
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: TempDbLogDirectory = [DataRootDirectory]\DATA
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: ErrorLogDirectory = 
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: TemplateDataDirectory = [DataRootDirectory]\Template Data
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: SqlInstanceBinnDir = C:\Program Files\Microsoft SQL Server\MSSQL11.COMPAC7001\MSSQL\Binn
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: SqlInstanceTemplatesDir = C:\Program Files\Microsoft SQL Server\MSSQL11.COMPAC7001\MSSQL\Binn\Templates
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: MasterDbPath = 
(01) 2019-03-27 19:13:28 SQLEngine: --MergedDirectoryProperties: MasterLogPath = 
(01) 2019-03-27 19:13:28 SQLEngine: --SqlEngineSetupPrivate: Performing Patch Validation.
(01) 2019-03-27 19:13:28 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing Validation and scenario Validation.
(01) 2019-03-27 19:13:28 Slp: The Database Engine error log location is missing from the Parameters key.
(01) 2019-03-27 19:13:28 Slp: The configuration failure category of current exception is ConfigurationValidationFailure
(01) 2019-03-27 19:13:28 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing Validation and scenario Validation.
(01) 2019-03-27 19:13:28 Slp: Microsoft.SqlServer.Configuration.SqlEngine.ValidationException: The Database Engine error log location is missing from the Parameters key.
(01) 2019-03-27 19:13:28 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.ValidateDataRegistryKeys(EffectiveProperties properties)
(01) 2019-03-27 19:13:28 Slp:    at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Patch(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2019-03-27 19:13:28 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2019-03-27 19:13:28 Slp:    at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2019-03-27 19:13:28 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2019-03-27 19:13:28 Slp: Inner exceptions are being indented
(01) 2019-03-27 19:13:28 Slp: 
(01) 2019-03-27 19:13:28 Slp: Exception type: Microsoft.SqlServer.Configuration.SqlEngine.ValidationException
(01) 2019-03-27 19:13:28 Slp:     Message: 
(01) 2019-03-27 19:13:28 Slp:         The Database Engine error log location is missing from the Parameters key.
(01) 2019-03-27 19:13:28 Slp:     HResult : 0x851a004a
(01) 2019-03-27 19:13:28 Slp:         FacilityCode : 1306 (51a)
(01) 2019-03-27 19:13:28 Slp:         ErrorCode : 74 (004a)
(01) 2019-03-27 19:13:28 Slp:     Data: 
(01) 2019-03-27 19:13:28 Slp:       SQL.Setup.FailureCategory = ConfigurationValidationFailure
(01) 2019-03-27 19:13:28 Slp:       WatsonConfigActionData = PATCH@VALIDATION@SQL_ENGINE_CORE_INST
(01) 2019-03-27 19:13:28 Slp:       WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2019-03-27 19:13:28 Slp:     Stack: 
(01) 2019-03-27 19:13:28 Slp:         at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.ValidateDataRegistryKeys(EffectiveProperties properties)
(01) 2019-03-27 19:13:28 Slp:         at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Patch(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
(01) 2019-03-27 19:13:28 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2019-03-27 19:13:28 Slp:         at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2019-03-27 19:13:28 Slp: Watson Bucket 1 
 Original Parameter Values 

(01) 2019-03-27 19:13:28 Slp: Parameter 0 : SQL Server 2012@RTM@ 

(01) 2019-03-27 19:13:28 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.ValidateDataRegistryKeys 

(01) 2019-03-27 19:13:28 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.ValidateDataRegistryKeys 

(01) 2019-03-27 19:13:28 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.SqlEngine.ValidationException@1306@74 

(01) 2019-03-27 19:13:28 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.SqlEngine.ValidationException@1306@74 

(01) 2019-03-27 19:13:28 Slp: Parameter 5 : SqlEngineConfigAction_patch_validation 

(01) 2019-03-27 19:13:28 Slp: Parameter 6 : PATCH@VALIDATION@SQL_ENGINE_CORE_INST 

(01) 2019-03-27 19:13:28 Slp: 
 Final Parameter Values 

(01) 2019-03-27 19:13:28 Slp: Parameter 0 : SQL Server 2012@RTM@ 

(01) 2019-03-27 19:13:28 Slp: Parameter 1 : 0x93C54E3E 

(01) 2019-03-27 19:13:28 Slp: Parameter 2 : 0x93C54E3E 

(01) 2019-03-27 19:13:28 Slp: Parameter 3 : 0x97A656BB@1306@74 

(01) 2019-03-27 19:13:28 Slp: Parameter 4 : 0x97A656BB@1306@74 

(01) 2019-03-27 19:13:28 Slp: Parameter 5 : SqlEngineConfigAction_patch_validation 

(01) 2019-03-27 19:13:28 Slp: Parameter 6 : 0x37BF4F3D 

(01) 2019-03-27 19:13:29 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20190327_191130\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
(01) 2019-03-27 19:13:29 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20190327_191130\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2019-03-27 19:13:29 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20190327_191130\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
(01) 2019-03-27 19:13:29 Slp: Sco: Attempting to write hklm registry key Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20190327_191130\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
(01) 2019-03-27 19:13:29 Slp: Sco: Attempting to write hklm registry key Uninstall to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20190327_191130\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
(01) 2019-03-27 19:13:29 Slp: Sco: Attempting to write hklm registry key MSSQLServer to file C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20190327_191130\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
(01) 2019-03-27 19:13:31 Slp: The Database Engine error log location is missing from the Parameters key.
(01) 2019-03-27 19:13:31 Slp: Watson bucket for exception based failure has been created
(01) 2019-03-27 19:13:31 Slp: Error: Action "SqlEngineConfigAction_patch_validation_Cpu64" failed during execution.
(01) 2019-03-27 19:13:31 Slp: Completed Action: SqlEngineConfigAction_patch_validation_Cpu64, returned False
(01) 2019-03-27 19:13:31 Slp: Completed Action: ValidationTimingConfigAction, returned True
(01) 2019-03-27 19:13:31 Slp: ----------------------------------------------------------------------

(Possibly of note is that in the prior action it logged a lot of "path not found" errors for registry keys with a "7001" suffix -- the keys do exist without that suffix; I assume this is some side-by-side install thing so that it can rollback cleanly, although then I don't know why it's complaining about it.)

In any case, the final error seems incorrect because the error log location is indeed specified in the Parameters, as it logged only a few lines prior -- but it appears to have been lost when it logged the MergedDirectoryProperties.

Any ideas how to resolve this and let upgrades succeed?

The installation keeps failing no matter how many times I uninstall and try to re-install it. I've tried looking all over for a solution with no luck. Has anyone had this problem?

Here are the summary results:

Express 2016 LocalDB, VS2017 Community and SSMS 2017

will these three work together?

when running the SSMS2017 install, i get 5 or 6 errors that some file could not be parsed, but at the end it says it installed.

however, when i run SSMS, it says one or more components were not installed... i tried doing a 'repair' and got the same 5 or 6 errors and still won't run.

so if these are supposed to be compatible, i'll uninstall Express, Datatools and SSMS and try again.

thanks... eric

Hello.

I have a Visual Studio Subscription. I'd like to know how many times I can download the SQL Server.

Thanks.

Dear Team,

I have try to configured log shipping but getting error message, please help.

TITLE: Microsoft SQL Server Management Studio
------------------------------

SQL Server Management Studio restore database 'Trainee'

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (SqlManagerUI)

------------------------------

Cannot open backup device '\\abc-db-01\LOGSHIPDEVDB\Trainee.bak'. Operating system error 5(Access is denied.).
RESTORE FILELIST is terminating abnormally. (Microsoft SQL Server, Error: 3201)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.00.6000&EvtSrc=MSSQLServer&EvtID=3201&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

With Regards 

[Error Message] The specified directory, "C:\Program Files\Microsoft SQL Server\", for the INSTALLSHAREDDIR parameter is not valid because this directory is compressed or is in a compressed directory. Specify a directory that is not compressed. [Details] Microsoft.SqlServer.Configuration.SetupExtension.CompressedDirException: The specified directory, "C:\Program Files\Microsoft SQL Server\", for the INSTALLSHAREDDIR parameter is not valid because this directory is compressed or is in a compressed directory. Specify a directory that is not compressed.

how to solve it

I want to deploy a sql server database file (.mdf) to a standalone PC. What SQL Server software do I need to deploy or install on that standalone pc as a minimum to access that database file?

Hi,

I've got a VirtualBox with 8GB RAM set up with Windows 10 (I've tried Home and Pro, and face the same issues with both).

I first tried the basic setup (where all the configuration options are handled by the setup), and got the following error:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. 
The server was not found or was not accessible. 
Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Since then, I've tried different permutations of options, but always wind up with this error.

I checked the service status, and found that the only thing related to SQL Server that was running was "SQL Full-text filter...", so attempted to start the server (during the setup - which I hadn't quit yet). The startup appeared to succeed, so I clicked on "Retry" and a few minutes later got the same error. I checked the logs and found a an error :

Unable to open the physical file "d:\dbs\sh\sprel\0822_164025\cmd\33\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\MSDBData.mdf".

I'd started the installation through a download, and hadn't told the setup to look for anything on my virtual optical drive at all. Here's the log from my last attempt (custom installation which I'd earlier tried with all the default options, but this timw ar with the only deviation from defaults being to select "Mixed Mode" with a reasonably complex password) :

2019-04-08 11:17:09.35 Server      Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64) 
	Aug 22 2017 17:04:49 
	Copyright (C) 2017 Microsoft Corporation
	Express Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 17763: ) (Hypervisor)

2019-04-08 11:17:09.41 Server      UTC adjustment: 5:30
2019-04-08 11:17:09.41 Server      (c) Microsoft Corporation.
2019-04-08 11:17:09.41 Server      All rights reserved.
2019-04-08 11:17:09.41 Server      Server process ID is 3024.
2019-04-08 11:17:09.41 Server      System Manufacturer: 'innotek GmbH', System Model: 'VirtualBox'.
2019-04-08 11:17:09.41 Server      Authentication mode is MIXED.
2019-04-08 11:17:09.41 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2019-04-08 11:17:09.42 Server      The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
2019-04-08 11:17:09.42 Server      Registry startup parameters: 
	 -d C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\DATA\master.mdf
	 -e C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Log\ERRORLOG
	 -l C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2019-04-08 11:17:09.42 Server      Command Line Startup Parameters:
	 -s "SQLEXPRESS"
2019-04-08 11:17:09.44 Server      SQL Server detected 1 sockets with 1 cores per socket and 1 logical processors per socket, 1 total logical processors; using 1 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2019-04-08 11:17:09.44 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-04-08 11:17:09.44 Server      Detected 8191 MB of RAM. This is an informational message; no user action is required.
2019-04-08 11:17:09.44 Server      Using conventional memory in the memory manager.
2019-04-08 11:17:09.54 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2019-04-08 11:17:09.71 Server      Buffer pool extension is already disabled. No action is necessary. 
2019-04-08 11:17:09.91 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2019-04-08 11:17:09.91 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
2019-04-08 11:17:09.96 Server      The maximum number of dedicated administrator connections for this instance is '1'
2019-04-08 11:17:09.96 Server      This instance of SQL Server last reported using a process ID of 1712 at 08-04-2019 11:16:54 (local) 08-04-2019 05:46:54 (UTC). This is an informational message only; no user action is required.
2019-04-08 11:17:09.96 Server      Node configuration: node 0: CPU mask: 0x0000000000000001:0 Active CPU mask: 0x0000000000000001:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2019-04-08 11:17:09.99 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2019-04-08 11:17:10.01 Server      In-Memory OLTP initialized on lowend machine.
2019-04-08 11:17:10.07 Server      Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2019-04-08 11:17:10.13 Server      CLR version v4.0.30319 loaded.
2019-04-08 11:17:10.14 Server      Query Store settings initialized with enabled = 1, 
2019-04-08 11:17:10.18 Server      Software Usage Metrics is disabled.
2019-04-08 11:17:10.85 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2019-04-08 11:17:12.79 spid6s      Starting up database 'master'.
2019-04-08 11:17:13.37 spid6s      2 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2019-04-08 11:17:13.37 spid6s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2019-04-08 11:17:13.59 spid6s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-04-08 11:17:13.59 spid6s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-04-08 11:17:13.66 spid6s      SQL Trace ID 1 was started by login "sa".
2019-04-08 11:17:13.68 spid6s      Server name is 'DEMACVM\SQLEXPRESS'. This is an informational message only. No user action is required.
2019-04-08 11:17:14.58 spid16s     A self-generated certificate was successfully loaded for encryption.
2019-04-08 11:17:14.60 spid16s     Server is listening on [ 'any' <ipv6> 50217].
2019-04-08 11:17:14.69 spid16s     Server is listening on [ 'any' <ipv4> 50217].
2019-04-08 11:17:14.81 spid16s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2019-04-08 11:17:14.82 spid16s     Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2019-04-08 11:17:15.15 spid16s     Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2019-04-08 11:17:15.18 spid16s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-04-08 11:17:15.19 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2019-04-08 11:17:15.22 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/DEMACVM:SQLEXPRESS ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2019-04-08 11:17:15.22 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/DEMACVM:50217 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2019-04-08 11:17:15.44 spid17s     A new instance of the full-text filter daemon host process has been successfully started.
2019-04-08 11:17:15.67 spid6s      Starting up database 'msdb'.
2019-04-08 11:17:15.68 spid13s     Starting up database 'mssqlsystemresource'.
2019-04-08 11:17:15.72 spid13s     The resource database build version is 14.00.1000. This is an informational message only. No user action is required.
2019-04-08 11:17:15.98 spid13s     Starting up database 'model'.
2019-04-08 11:17:16.55 spid6s      Error: 17204, Severity: 16, State: 1.
2019-04-08 11:17:16.55 spid6s      FCB::Open failed: Could not open file d:\dbs\sh\sprel\0822_164025\cmd\33\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\MSDBData.mdf for file number 1.  OS error: 21(The device is not ready.).
2019-04-08 11:17:16.55 spid6s      Error: 5120, Severity: 16, State: 101.
2019-04-08 11:17:16.55 spid6s      Unable to open the physical file "d:\dbs\sh\sprel\0822_164025\cmd\33\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\MSDBData.mdf". Operating system error 21: "21(The device is not ready.)".
2019-04-08 11:17:17.41 spid13s     Error: 17204, Severity: 16, State: 1.
2019-04-08 11:17:17.41 spid13s     FCB::Open failed: Could not open file d:\dbs\sh\sprel\0822_164025\cmd\33\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\model.mdf for file number 1.  OS error: 21(The device is not ready.).
2019-04-08 11:17:17.42 spid13s     Error: 5120, Severity: 16, State: 101.
2019-04-08 11:17:17.42 spid13s     Unable to open the physical file "d:\dbs\sh\sprel\0822_164025\cmd\33\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\model.mdf". Operating system error 21: "21(The device is not ready.)".
2019-04-08 11:17:19.26 spid6s      Error: 17207, Severity: 16, State: 1.
2019-04-08 11:17:19.26 spid6s      FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'd:\dbs\sh\sprel\0822_164025\cmd\33\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2019-04-08 11:17:19.26 spid6s      File activation failure. The physical file name "d:\dbs\sh\sprel\0822_164025\cmd\33\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\MSDBLog.ldf" may be incorrect.
2019-04-08 11:17:19.42 spid13s     Error: 17207, Severity: 16, State: 1.
2019-04-08 11:17:19.42 spid13s     FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'd:\dbs\sh\sprel\0822_164025\cmd\33\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2019-04-08 11:17:19.42 spid13s     File activation failure. The physical file name "d:\dbs\sh\sprel\0822_164025\cmd\33\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\modellog.ldf" may be incorrect.
2019-04-08 11:17:19.42 spid13s     Error: 945, Severity: 14, State: 2.
2019-04-08 11:17:19.42 spid13s     Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
2019-04-08 11:17:19.42 spid13s     SQL Server shutdown has been initiated
2019-04-08 11:17:19.42 spid13s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

 Hi
I'm trying to install sql server 2017 and I'm keep getting errors:

I have a brand new win 10 pro

here is the log file.
I already installed successfully in managment studio.

i don't know where to start.

Setup completed with required actions for features.

Troubleshooting information for those features:

  Next step for FullText:        Use the following information to resolve the error, and then try the setup process again.

  Next step for sql_inst_mpy:    Use the following information to resolve the error, and then try the setup process again.

  Next step for sql_inst_mr:     Use the following information to resolve the error, and then try the setup process again.

  Next step for AdvancedAnalytics: Use the following information to resolve the error, and then try the setup process again.

  Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.

  Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.

  Configuration file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20171021_022911\ConfigurationFile.ini

Detailed results:

  Feature:                       Full-Text and Semantic Extractions for Search

  Status:                        Failed

  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 C++ 2015 Redistributable

  Component error code:          1638

  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20171021_022911\VCRuntime140_x64_Cpu64_1.log

  Error description:             VS Shell installation has failed with exit code 1638.

  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=VCRuntime140_x64%40Install%400x1638

  Feature:                       Python

  Status:                        Failed

  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 C++ 2015 Redistributable

  Component error code:          1638

  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20171021_022911\VCRuntime140_x64_Cpu64_1.log

  Error description:             VS Shell installation has failed with exit code 1638.

  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=VCRuntime140_x64%40Install%400x1638

  Feature:                       R

  Status:                        Failed

  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 C++ 2015 Redistributable

  Component error code:          1638

  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20171021_022911\VCRuntime140_x64_Cpu64_1.log

  Error description:             VS Shell installation has failed with exit code 1638.

  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=VCRuntime140_x64%40Install%400x1638

  Feature:                       Machine Learning Services (In-Database)

  Status:                        Failed

  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 C++ 2015 Redistributable

  Component error code:          1638

  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20171021_022911\VCRuntime140_x64_Cpu64_1.log

  Error description:             VS Shell installation has failed with exit code 1638.

  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=VCRuntime140_x64%40Install%400x1638

  Feature:                       Database Engine Services

  Status:                        Failed

  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 C++ 2015 Redistributable

  Component error code:          1638

  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20171021_022911\VCRuntime140_x64_Cpu64_1.log

  Error description:             VS Shell installation has failed with exit code 1638.

  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=VCRuntime140_x64%40Install%400x1638

  Feature:                       SQL Server Replication

  Status:                        Failed

  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 C++ 2015 Redistributable

  Component error code:          1638

  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20171021_022911\VCRuntime140_x64_Cpu64_1.log

  Error description:             VS Shell installation has failed with exit code 1638.

  Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=VCRuntime140_x64%40Install%400x1638

  Feature:                       Client Tools SDK

  Status:                        Passed

  Feature:                       Client Tools Connectivity

  Status:                        Passed

  Feature:                       Client Tools Backwards Compatibility

  Status:                        Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20171021_022911\SystemConfigurationCheck_Report.htm

Avi

I am a Mac user and I wanted to have SQL server 2012 express on my laptop, but this only support windows, how Can I access to this software then?

Thanks

In trying to install SQL Server Express, I'm getting the following error:

I've had issues with getting through our proxy, but if that's what this is, I'm not seeing any way to tell the installer to use it.

Any ideas?  Thanks,

Dave

One of our SQL Express DBs have hit the 10GB size limit. I don't have sysadmin access to the SQL instance to even view the DB.

Is there anything we can do to reduce the size or is my only option to upgrade the SQL Server to standard? Can I even do that without knowing the SA password?

Hello

I have installed MS Server 2008 Express R2 on my pc and now trying to install SQL Server 2008 Management Studio. I keep getting a validation error shown below. I am getting this error after selecting 'Perform a new installation of SQL Server 2008'. The same error is being replicated when I select 'Add features to an existing instance of SQL Server 2008'. I am stuck now after crawling the web for a couple of days now without much joy.

PC Spec: Win 7, x86

Can somebody please help me, I am new to this setup.

Many thanks

i am trying to install ms sql server 2012 database and i have windows 8.1 but i am facing issues please help 

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2147467259
  Start time:                    2019-04-13 08:00:44
  End time:                      2019-04-13 08:12:14
  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 Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.


Machine Properties:
  Machine name:                  SHUMAILA
  Machine processor count:       4
  OS version:                    Future Windows Version
  OS service pack:               
  OS region:                     United States
  OS language:                   English (United States)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                 Language             Edition              Version         Clustered 

Package properties:
  Description:                   Microsoft SQL Server 2012 Service Pack 1
  ProductName:                   SQL Server 2012
  Type:                          RTM
  Version:                       11
  SPLevel:                       0
  Installation location:         d:\9ef5e657df16fd311435191ccab602\x64\setup\
  Installation edition:          Express

Product Update Status:
  User selected not to include product updates.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      true
  AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Disabled
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    true
  ENU:                           true
  ERRORREPORTING:                false
  FEATURES:                      SQLENGINE, REPLICATION, 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\Microsoft SQL Server\
  INSTANCEID:                    MSSQLSERVER
  INSTANCENAME:                  SHUM
  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:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SHUM
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           SHUMAILA\Cantt Computer
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  false
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 false
  UpdateSource:                  MU
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20190413_075413\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:          0x80004005
  Error description:             The system cannot find the file specified.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.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 system cannot find the file specified.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xDC112D1C%400xDC80C325&EvtType=0xDC112D1C%400xDC80C325

  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\20190413_075413\SystemConfigurationCheck_Report.htm

i installed ms sql server 2012 i have windows 8.1 

but when i try to connect this shows an error