i just try reinstalling sql server 2019 and i can't install the database engine

this the summary:

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068052377
  Start time:                    2019-05-07 21:41:32
  End time:                      2019-05-07 21:47:48
  Requested action:              Install

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.


Machine Properties:
  Machine name:                  EVVNNXX
  Machine processor count:       4
  OS version:                    Microsoft Windows 10 Home Single Language (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
  SQL Server 2017                                                          Client Tools Connectivity               1033                                      14.0.1000.169   No         Yes      
  SQL Server 2017                                                          Client Tools Backwards Compatibility    1033                                      14.0.1000.169   No         Yes       
  SQL Server 2017                                                          Client Tools SDK                        1033                                      14.0.1000.169   No        Yes       

Package properties:
  Description:                   Microsoft SQL Server 2017 
  ProductName:                   SQL Server 2017
  Type:                          RTM
  Version:                       14
  SPLevel:                       0
  Installation location:         C:\SQLServer2017Media\ExpressAdv_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:         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
  EXTSVCACCOUNT:                 NT Service\MSSQLLaunchpad$SQLEXPRESS
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE, REPLICATION, ADVANCEDANALYTICS, SQL_INST_MR, SQL_INST_MPY, FULLTEXT
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQLEXPRESS
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTPYTHONLICENSETERMS:     true
  IACCEPTROPENLICENSETERMS:      true
  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:           EVVNNXX\ASUS
  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\20190507_214131\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:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190507_214131\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  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=sql_engine_core_inst.msi%400x162A16FE%400x1639

  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:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190507_214131\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  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=sql_engine_core_inst.msi%400x162A16FE%400x1639

  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:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190507_214131\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  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=sql_engine_core_inst.msi%400x162A16FE%400x1639

  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:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190507_214131\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  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=sql_engine_core_inst.msi%400x162A16FE%400x1639

  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, and then try the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190507_214131\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  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=sql_engine_core_inst.msi%400x162A16FE%400x1639

  Feature:                       SQL Server Replication
  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 Database Engine Services Instance Features
  Component error code:          1639
  Component log file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190507_214131\sql_engine_core_inst_Cpu64_1.log
  Error description:             Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
  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=sql_engine_core_inst.msi%400x162A16FE%400x1639

Rules with failures:

Global rules:

Scenario specific rules:

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

this is the sql server configurationlooks like https://drive.google.com/open?id=19B0nu_Xjuo2n6q1RmBxBdDWT25OlmfJ- , and this is the serviceshttps://drive.google.com/open?id=1SnSC36XnBR_CZjAtBhmUZua8YWzoZU6A

I have a couple of SQL 2008 R2 servers running on Win 2012 that need to be upgraded. One to SQL 2014 and SQL 2016, I want both on Win 2016 for application compatibility.  I don't want to do an in-place upgrade, but the applications that talk to these server are very cumbersome to relocate SQL.  These servers have already been through at least one in-place OS upgrade and maybe one in-place SQL upgrade so I would really like to do this cleanly.  back in the 2005-2008 days, I did a Side/Side upgrade where I built an identically configured SQl server using the same Instance names/folder paths, took the old server offline, copied the DB's over, master and all, renamed the new server to the old server name, started everything up. The last step was to check that the server name was correct in the master DB.  

Will this strategy still work ok in modern SQL?  Is there anything that gets left behind doing this for and SQL construct, ie. jobs, linked servers, etc (understanding I have to deal with any report servers etc)?

Thanks

SSMS got installed successfully on windows 2016 server(which has no internet access) but unable to open in non admin mode.

Facing the below error while trying to open in non admin mode:

"the application was unable to start correctly(0xc00005). click ok to close the application"

Hi all,

We have been using an ISV Runtime version license of SQL 2012 server for quite some time now which was bundled with our Exact Software business software package. The license is an SQL 212 Standard server.

We are planning to implement a second business software package which also has an ISV Runtime license included. 

So we will have purchased two official ISV licenses for SQL Server.

Is it allowed to have both software packages run their own database in the same SQL server installation? I would prefer not to install a complete seperate SQL server just for having the extra database.

Regards,

Alex

Hi all, 

I need to set up a decent home lab as I've been stuck on SQL 2008 for some 8 years now & need to get up to speed with the newer versions. 

I'd like SQL 2008 / 12 / 16 so I can play with migrations.  Inc. AAAG & clustering.  I'm not talking volumes, just me playing around on my laptop.

I'm considering VMWare Fusion, then a MAP subscription.  Is this the best way?  Is there an easier / cheaper way to do this?  

Thank you!

Jess.

Hi !
I encountered an error during the SMSS installation, I have consulted some workarounds on the forum but the results still cannot be installed.
There is a log file given after the installation process failed.
I don't know how to handle it? I need help !

https://1drv.ms/u/s!An1CNjGQWOL5jxu1ZgIuIosLU2Ia

Hi all,

Want to setup and install SQL Server 2017 for a customer, but they do not yet have their VLC licenses purchase come through yet. I want to speed this job up so...

Can I install SQL Server 2017 RTM from the MS Evaluation site, then activate SQL Server 2017 with their license once received before the 180 days expire?

Or must I rather wait until the licensing comes trough and install everything neatly in one go?

Hi, I am downgrading Enterprise to Standard using following link:

https://www.mssqltips.com/sqlservertip/3079/downgrade-from-sql-server-enterprise-edition-to-standard-edition/

Running SELECT * FROM sys.dm_db_persisted_sku_features on all databases, it gives me a table showing some values:

compression = 100

Partitioning = 200

ColumnStoreIndex=600

How to successfully remove these value in order to proceed to further steps.

Thank You

WSBukhari

Hi There,

I am receiving the error "Value cannot be null. Parameter name:userGroupName" when trying to upgrade SQL Server Express 2017 to SQL Server Standard 2017.

The server is running Windows Server 2012R2.

I completely removed the SQL 2017 Standard installation and tried running the upgrade again, but this failed with the same error.

Any help with this would be very much appreciated!

Thanks in advance.

Josh.

Hi All,

Can someone help me if there is a way to specify directories for system ,user and temp db files while installing Sql 2019 on Linux like windows.

Thanks,

Hi,

I'm having an issue when starting my mssql-server.service on Linux.

The following error message is generated:

sqlservr: Unable to read instance id from /var/opt/mssql/.system/instance_id: Success (0)
This program has encountered a fatal error and cannot continue running at Wed May 15 12:24:22 2019
The following diagnostic information is available:

Reason: 0x00000003
Message: Unexpected call to legacy ABI.
Stacktrace: 000055c1f94c6464 000055c1f94c5fdf 000055c1f940a66e
               000055c1f9457977
Process: 23721 - sqlservr
Thread: 23722
Instance Id:
Crash Id:
Build stamp: 70437f6583b8ef39b1ef70539ef84690980315dc7a4436c9c40015f28610e4aa
Distribution: Ubuntu 16.04.6 LTS
Processors: 4
Total Memory: 12598861824 bytes
Timestamp: Wed May 15 12:24:22 2019
Aborted (core dumped)

Does anybody know what is wrong, and why i get this error message?

Any help is appreciated

Hi,

I do have installed the English Version of SQL Server 2016 and SQL Server Management Studio 17.1.  


How can I change the language to English?  As you can see, the DB menu in Object Explorer is in English, but the user interface still is in German.

When I use the link to install other languages. I get a link to http://go.microsoft.com/fwlink/?LinkId=558810&clcid=0x407 

This is completely  wrong, because it redirects me to install a "Microsoft Visual Studio 2015 Sprachpaket" = Language Pack for VS2015.  Why I need to install a Language pack if I installed the English version: "SSMS-Setup-ENU.exe"

I do have Visual Studio 2017 English installed.  

It's very strange.

Regards,

Arash

I have a Windows server, with SQL, SSIS, SSSAS, and SSRS setup, "default" instance(s)

We want to change the Win server's name.

(1)  The process to change the SQL engine is well published.  (Done this before, no issue...)

(2)  The process to change the SSRS is somewhat published (config tool for db location; INI files for other updates)

(3)  However, I am unsure and unable to find steps for what to do with SSIS and/or SSAS services.

Suggestions?  Article Links?

Thanks in advance.

Attempting to install SSDT 15.7 into a version of Visual Studio Team Explorer 15.7.3 Fails with 'Unknown Error 0x80131500'. I have opened up the following issue on the Developer Community site over a month ago and there has not been a hint of feedback.  

What is the deal? Will this ever be fixed?

Dear Team,

I'm very tired to install the SQL SERVER 2014 Management Studio. While Installing the Microsoft SQL Server 2014 it's shows at the end of Process finish "MOF Syntax Error Occurred". I try to Install more then 6 times. Kindly give me the solution.

Dear Sir,

My company want to install main patch without installing Workaround for below patches. But as main patch mentioned below have Known issues in these update

"After installing this update, some customers report that authentication fails for services that require unconstrained delegation after the Kerberos ticket expires (the default is 10 hours). For example, the SQL server service fails."

I want to know is there any risk to my SQL Server 2008/SQL Server 2008R2 with this approach?

https://support.microsoft.com/en-in/help/4489885/windows-7-update-kb4489885
Workaround-KB4493448

https://support.microsoft.com/en-in/help/4493448/windows-7-update-kb4493448
Workaround-KB4499175

https://support.microsoft.com/en-in/help/4496880/windows-7-update-kb4496880
Workaround-KB4499164

https://support.microsoft.com/en-in/help/4489876/windows-server-2008-kb4489876
Workaround-KB4499180

https://support.microsoft.com/en-in/help/4493458/windows-server-2008-update-kb4493458
Workaround-KB4499180

https://support.microsoft.com/en-in/help/4496879/windows-server-2008-update-kb4496879
Workaround-KB4499149

Regards,

Deepak

Lee