Hello,

Have a new server with SQL 2008 and an old server with SQL 2005 sp1.  I need to move my data over to new server but the SQL's are not compatible.  When trying to upgrade my old server to SQL 2008 its unsuccessful.  Cant even upgrade on old server to SQL 2005 sp4

we have a sql server 2016 which is running on windows server and is part of Active directory domain.

I have provided db_owner permission on an active directory group account(Domain\accountname) and user id(Domain\userid) is member of that group. When user tried with id (Domain\userid) using active directory password authentication via SSMS getting below error:

ERROR:18456 -  could not find  a login matching the name provided.

Sql server is running in AD domain, user had AD credentials and is part of active directory group account but getting the error.

Kindly help!

I encountered this error and I cannot fix it.

I tried to give full permissions to everyone,I tried some stackoverflow.com's tips(I'm not allowed to post here links yet)  and I aalso tried to setup my tmp folder as I have seen on some links,but my folder was already  like there. And many others things I don't remember right now...

Also the summary of log file is(if it helps):

Overall summary:

  Final result:                  Failed: see details below

  Exit code (Decimal):           -2068051813
  Start time:                    2019-10-11 13:27:16
  End time:                      2019-10-11 13:29:40
  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, 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 Browser:         Use the following information to resolve the error, and then try the setup process again.
  Next step for Writer:          Use the following information to resolve the error, and then try the setup process again.
  Next step for SNAC:            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.
  Next step for ComponentUpdate: Use the following information to resolve the error, and then try the setup process again.


Machine Properties:
  Machine name:                  DESKTOP-7A3NATV
  Machine processor count:       8
  OS version:                    Microsoft Windows 10 Pro (10.0.17134)
  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

Package properties:
  Description:                   Microsoft SQL Server 2017 
  ProductName:                   SQL Server 2017
  Type:                          RTM
  Version:                       14
  SPLevel:                       0
  Installation location:         C:\SQLServer2017Media\Express_ENU\x64\setup\
  Installation edition:          Express

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      true
  AGTSVCACCOUNT:                 NT AUTHORITY\NETWORK SERVICE
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Disabled
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  TABULAR
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTELSVCACCT:                  <empty>
  ASTELSVCPASSWORD:              <empty>
  ASTELSVCSTARTUPTYPE:           0
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Automatic
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    true
  ENU:                           true
  EXTSVCACCOUNT:                 <empty>
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE, REPLICATION, SNAC_SDK
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTPYTHONLICENSETERMS:     false
  IACCEPTROPENLICENSETERMS:      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:                    SQLEXPRESS
  INSTANCENAME:                  SQLEXPRESS
  ISMASTERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISMASTERSVCPASSWORD:           <empty>
  ISMASTERSVCPORT:               8391
  ISMASTERSVCSSLCERTCN:          <empty>
  ISMASTERSVCSTARTUPTYPE:        Automatic
  ISMASTERSVCTHUMBPRINT:         <empty>
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  ISTELSVCACCT:                  <empty>
  ISTELSVCPASSWORD:              <empty>
  ISTELSVCSTARTUPTYPE:           0
  ISWORKERSVCACCOUNT:            NT AUTHORITY\Network Service
  ISWORKERSVCCERT:               <empty>
  ISWORKERSVCMASTER:             <empty>
  ISWORKERSVCPASSWORD:           <empty>
  ISWORKERSVCSTARTUPTYPE:        Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  MRCACHEDIRECTORY:              
  NPENABLED:                     0
  PBDMSSVCACCOUNT:               <empty>
  PBDMSSVCPASSWORD:              <empty>
  PBDMSSVCSTARTUPTYPE:           0
  PBENGSVCACCOUNT:               <empty>
  PBENGSVCPASSWORD:              <empty>
  PBENGSVCSTARTUPTYPE:           0
  PBPORTRANGE:                   <empty>
  PBSCALEOUT:                    false
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 DefaultNativeMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         *****
  SECURITYMODE:                  SQL
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS
  SQLSVCINSTANTFILEINIT:         false
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           DESKTOP-7A3NATV\Miriam
  SQLTELSVCACCT:                 NT Service\SQLTELEMETRY$SQLEXPRESS
  SQLTELSVCPASSWORD:             <empty>
  SQLTELSVCSTARTUPTYPE:          Automatic
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBFILECOUNT:            1
  SQLTEMPDBFILEGROWTH:           64
  SQLTEMPDBFILESIZE:             8
  SQLTEMPDBLOGDIR:               <empty>
  SQLTEMPDBLOGFILEGROWTH:        64
  SQLTEMPDBLOGFILESIZE:          8
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 true
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

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

Detailed results:
  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:                SQL Server Setup Support Files
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\SqlSupport_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=SqlSupport.msi%40InstallInitialize%402203

  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:                SQL Server Setup Support Files
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\SqlSupport_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=SqlSupport.msi%40InstallInitialize%402203

  Feature:                       SQL Browser
  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:                SQL Server Setup Support Files
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\SqlSupport_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=SqlSupport.msi%40InstallInitialize%402203

  Feature:                       SQL Writer
  Status:                        Failed
  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 Writer Component
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\SqlWriter_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=SqlWriter.msi%40InstallInitialize%402203

  Feature:                       SQL Client Connectivity
  Status:                        Failed
  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 Native Client Access Component
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\sqlncli_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=sqlncli.msi%40InstallInitialize%402203

  Feature:                       SQL Client Connectivity SDK
  Status:                        Failed
  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 Native Client Access Component
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\sqlncli_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=sqlncli.msi%40InstallInitialize%402203

  Feature:                       Setup Support Files
  Status:                        Failed
  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 Setup Support Files
  Component error code:          2203
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20191011_132715\SqlSupport_Cpu64_1.log
  Error description:             The installer has encountered an unexpected error. The error code is 2203. Database: C:\WINDOWS\Installer\inprogressinstallinfo.ipi. Cannot open database file. System error -2147286788.
  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=SqlSupport.msi%40InstallInitialize%402203

Rules with failures:

Global rules:

Scenario specific rules:

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

Thanks in advance!

Hi,

we are going to migrate SQL 2016 Enterprises to SQL 2017 Standard edition.

 what are the things to take care for this?

•   Compatibility?
•   can we upgrade SQL 2016 Ent to SQL 2017 Stand directly ( In-place upgrade)
•   we are using Rebuild with online /Table partition features in Enterprises. (what are the features differentiate with         standard)
•   Is there any difference in  Performance compare with SQL 2016 Ent vs SQL 2017Std.
• we configured Transnational Replication.

windows2012R2服务器上已经安装了sql2014的数据库实例，另外新增安装sql2016实例时报如下错误，且在使用sql2014sp3升级包升级已存在实例时同样报以上错误，不知如何排查了，请教该如何分析呢，谢谢

SQL Server Setup has encountered the following error: Failed to retrieve data for this request.. For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&EvtType=0xE8A0C283%25400xAC7B1A58%25401233%254053 ------------------------------ BUTTONS: OK ------------------------------

I've downloaded SQL Server 2017 to find out what Object Explorer is and how it works.  At the very least I'd like to create a database and create some Tables.  However, I don't seem to have an application loaded that I can run to do this.

I have installed SQL Server 2017 Express using SQLServer2017-SSEI-Expr.exe.  I understand this is free of charge.  The following are now listed as installed programs on my machine:

• Microsoft SQL Server 2017 T-SQL Language Service
• Microsoft SQL Server 2017 Setup (English)
• Microsoft SQL Server 2017 LocalDB
  
• Microsoft SQL Server 2017 (64-bit)
• Microsoft SQL Server 2012 Native Client
  
• Microsoft SQL Server 2008 R2 Native Client

In the list of apps under the heading of Microsoft SQL Server 2017, shown when I click on my Windows 10 Start button, I have the following list of programs that I can run:

• SQL Server 2017 Configuration Manager
• SQL Server 2017 Import and Export Data (32-bit)
• SQL Server 2017 Import and Export Data (64-bit)
• SQL Server 2017 Error and Usage Reporting
  
• SQL Server 2017 Installation Center (64-bit)

However, I get the impression that to use SQL Server 2017 Express I need to use something like SQL Server Management Studio, but that is not free except for a limited period.  However, a possible alternative, Microsoft Management Console, is listed in my Task Manager as being inactive and I don't know how to activate it.  Anyway, from the documentation it seems that I need SQL Server Management Studio to use Object Explorer, anyway.

Is there is free way of using

• Object Explorer
• Creating a database, creating tables and doing queries

please?

Hi,

I have a 6 core sql license. But I have only used 4-cores in one project.

Can I use the other 2-cores in another project in another sql server installation?

Thanks,

Hello All,

I have a quesiton for Data base migrate.

we MIgrage database from low version(11.0) to high version. Now we have to migate the database from the high version to low verion.

I try using Copy, it give one error (exceute SQL Server Agent Job Error) of 5. and package was not able to created.

"Backup and restore" : System give error message: data base could be restored on lower version SQL.

try to "Export  Data-Tier Application" and SQL server gives 3 errors of 7. We get operation fail as a result.

How can we transfer the data from 14.0 to 11.0? 

Please give advice.

brgds

Liu Wei

Hello,

I've been struggling to install sql server 2017 for a few days now. I keep getting message:

Oops... Unable to install SQL Server(setupe.exe). Exit code(Decimal)-2068052377 Error description:Invalid command line argument.Consult the Windows Installer SDK for detailed command line help.

 I've tried to delete all sql folders , registry keys, uninstall everything related to SQL Server, installing as admin, cleaning and fixing the registry, rebooting,... Still cant install. Please help. Thanks in advance. I attached 3 log files inhttps://mega.nz/#F!J4FUCS5Q!S9lRhfgZfDafzM4AG9Py-Q

We are provisioning a server for a customer and have purchased SQL Standard 2017 Core Edition. The customer has just asked us to install 2014 instead, as they cannot upgrade their database version yet.

I think there are downgrade rights to 2014 but will I need to purchase a downgrade kit with a license key or is it a keyless installation?

Hi all,

Relatively basic question but much harder to actually get any solid numbers on.

Currently in the process of upgrading our main servers and trying to weigh up options of current Intel and AMD offerings.

Does anyone have any experience with the new EPYC 7002 series vs 2nd gen Intel Xeon Scalable? If you want specifics, I'm looking for comparison of the Xeon Gold 5222 and EPYC 7262. Currently using Xeon E5-2637 v3 chips and whilst I expect Intel will still offer a performance advantage, AMD does offer a much more compelling platform with PCIe 4.0 and faster memory support.

Any first hand experience would be fantastic, thanks in advance.

Hello,

We are currently preparing for a new SQL Server 2017 Standard for our site (Internal Site).

We are buying a Server + CAL licensing model for the SQL Server to install on our server, but we found that one of our devices is using iPad to access the database through our application.

We are buying 5 devices CAL for the SQL Server, which we are wondering if this can be used/install on an iPad.

Since we are using express edition in the past, we would like to know if the CAL will work on an iPad or other android devices.

Thanks for your help.

Best Regards,

Foc3

I was using SQL Sever 2008 R2 on my notebook but I need to replace hard disk with SSD and have to install fresh copy of windows 10.
On new machine I tried to install SQL Server 2008 R2 but it stuck on almost ending process of SqlEngineDBStartConfigAction_install_configrc_Cpu64 shown in below screenshot. I also checked in Services and found that SQL Server service keeping in "starting" mode.

I tried below link trick but not able to find registery key "AppCompat" on Windows 10 machine. https://www.networkworld.com/article/2228061/tricky-sql-server-install-on-64-bit-machines---use-switchback-.html https://blogs.msdn.microsoft.com/sql_protocols/2010/08/13/windows-7-appcompat-changes-and-sql-server-client-and-setup-hangs/

Can anyone please help me as I could not upgrade to newer version of SQL Server.

Hi,

Does anyone have any experience with running SQL Server 2016 on compatibility mode 2008 in terms of performance/ query plans and also general compatibility with 3rd party applications? It will be reassuring if not much changes on the new database.

We are planning the migration of a high volume, few terabytes of data 2008 based system to 2016. We are hoping that performance stay the same (at least).

We will eventually migrate to 2016 compatibility level but not at this stage. Any other advise you can give?

Thanks very much.

Panos.

Hi everyone,

We are a little company with 10 computer stations connected to one server and use SQL server 2008 - version 10.50.1600.1 not clustered. We want to add one more station and we have been told that we need to upgrade to SQL Standard 2017. They charge us a lot of money for that.

My questions are:

- Do we need to upgrade because of the add of one more station? and do we have to pay for 11 licences ?

- For upgrade is it logical that the price is for a new licence?

I don't understand much in all these problems so I'll be glad to get some advices from experts

Thank you in advance all

Sylvie

Hi all,

I wanted to know if there is a quick way to upgrade our  trial SQL2016 cluster to a licensed SQL 2016 cluster without rebuilding the whole server.

Our consultant forgot to mention that he needed to upgrade the trial to a licensed model. And now we are working in Production with the trial. Rebuilding the SQL cluster looks like the only solution, but we hope there is a better way.

I thought it would be possible to remove the cluster connections so you have a stand alone sql server and then upgrade the both servers and make the Clustering complete again. But is that possible with the cluster modules installed on it?

hope some one can help us quickly

Installing on Domain Server (only server, small network), 2012 R2

I am a volunteer with very limited network experience

SQL Server Express 2012 is already installed

I uninstalled the last attempt at installing SQL Server Express 2017, rebooted and installed using the custom option

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, 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:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026

  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, uninstall this feature, and then run the setup process again.
  Component name:                Machine Learning Services (In-Database)
  Component error code:          0x80131509
  Error description:             Cannot find group with identity S-1-5-21-464858192-4288412492-2497808848-1306.
  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=0x69EA8169%400xE9BC3D64&EvtType=0x69EA8169%400xE9BC3D64

  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, uninstall this feature, and then run the setup process again.
  Component name:                Machine Learning Services (In-Database)
  Component error code:          0x80131509
  Error description:             Cannot find group with identity S-1-5-21-464858192-4288412492-2497808848-1306.
  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=0x69EA8169%400xE9BC3D64&EvtType=0x69EA8169%400xE9BC3D64

  Feature:                       Machine Learning Services (In-Database)
  Status:                        Failed
  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:                Machine Learning Services (In-Database)
  Component error code:          0x80131509
  Error description:             Cannot find group with identity S-1-5-21-464858192-4288412492-2497808848-1306.
  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=0x69EA8169%400xE9BC3D64&EvtType=0x69EA8169%400xE9BC3D64

  Feature:                       Database Engine Services
  Status:                        Failed
  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:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026

  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, 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:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       Client Tools SDK
  Status:                        Passed

  Feature:                       Client Tools Connectivity
  Status:                        Passed

  Feature:                       Client Tools Backwards Compatibility
  Status:                        Passed

  Feature:                       Setup Support Files
  Status:                        Passed

hi,

i am trying to uninstall sql server 2012 64b and get an error like this:

"this sql server setup media does not support the language of the OS,or does not have the sql server English-language version installation files. use the matching language specific sql server media, or install both the language specific MUI and change the format and system locales through the regional setting in the control panel"

how to resolve this error and successfully remove sql server 2012 64b??