none
Installing SQL Server 2017 on VM fails

    Question

  • I am trying to install SQL Server Express 2017 on a VM, and it fails at the end.

    VM: Windows Pro 10 Size Standard D2 v2

    Happens everytime, easy to repeat!

    Summary file below:

    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2068119551
      Start time:                    2019-04-04 16:28:43
      End time:                      2019-04-04 16:42:08
      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, uninstall this feature, and then run the setup process again.
      Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.


    Machine Properties:
      Machine name:                  rsopt-test-vm2
      Machine processor count:       2
      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\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:                 <empty>
      EXTSVCPASSWORD:                <empty>
      FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, CONN, BC, SDK, SNAC_SDK
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SQLEXPRESS
      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:           rsopt-test-vm2\rs-admin
      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:            true
      X86:                           false

      Configuration file:            C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190404_162830\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, uninstall this feature, and then run the setup process again.
      Component name:                SQL Server Database Engine Services Instance Features
      Component error code:          0x84BB0001
      Error description:             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)
      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=0x6BB41ECB%400xDC80C325&EvtType=0x6BB41ECB%400xDC80C325

      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:          0x84BB0001
      Error description:             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)
      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=0x6BB41ECB%400xDC80C325&EvtType=0x6BB41ECB%400xDC80C325

      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:          0x84BB0001
      Error description:             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)
      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=0x6BB41ECB%400xDC80C325&EvtType=0x6BB41ECB%400xDC80C325

      Feature:                       SQL Browser
      Status:                        Passed

      Feature:                       SQL Writer
      Status:                        Passed

      Feature:                       Client Tools SDK
      Status:                        Passed

      Feature:                       Client Tools Connectivity
      Status:                        Passed

      Feature:                       Client Tools Backwards Compatibility
      Status:                        Passed

      Feature:                       SQL Client Connectivity
      Status:                        Passed

      Feature:                       SQL Client Connectivity SDK
      Status:                        Passed

      Feature:                       Setup Support Files
      Status:                        Passed

    Rules with failures:

    Global rules:

    Scenario specific rules:

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

    --

    Thanks.

    Magnus


    A former Javaman

    Friday, April 5, 2019 6:54 AM

Answers

  • Hi, 

    If you choose to download the iso file and not just run it it will exist in your downloads folder. 


    Please, If you think your question has been answered click "Mark as Answer" if just helped click "Vote as helpful". This can be beneficial to other community members reading this forum thread.

    • Marked as answer by magja Tuesday, April 16, 2019 1:48 PM
    Monday, April 15, 2019 6:22 AM

All replies

  • Hi Magnus, 

    I made the same test and the installation was successful. Can you give me more technical details? From the error log you post it seems that are some connectivity issues with sql server service.

    "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)"

    At the image below you can see the results from my installation in a clean Azure VM


    Please, If you think your question has been answered click "Mark as Answer" if just helped click "Vote as helpful". This can be beneficial to other community members reading this forum thread.



    Friday, April 5, 2019 9:19 AM
  • Hi George,

    Thanks for your response. What technical details would you like to see?

    Image below shows where I end up.


    And I found two of these in the Event Viewer:


    A former Javaman


    • Edited by magja Friday, April 5, 2019 2:04 PM
    Friday, April 5, 2019 1:55 PM
  • We also have preconfigured SQL images you can deploy in Azure. This will include all the setup to run SQL in Azure. In fact, that is the suggested route to deploy a SQL image in Azure. 

    Why are you looking to install it manually? 

    Friday, April 5, 2019 4:05 PM
    Moderator
  • I need a Windows 10 VM, and there are no such SQL images preconfigured.

    A former Javaman

    Saturday, April 6, 2019 5:37 AM
  • Hi Magnus, 

    It's weird because I make a demo (West Europe DC) with the same VM name and it was successfully installed.

    Check the following:

    • If any Windows update is available for download
    • Try to deploy a new VM to another Data Center
    • If you install antivirus software, check if use any of the SQL files/services


    Please, If you think your question has been answered click "Mark as Answer" if just helped click "Vote as helpful". This can be beneficial to other community members reading this forum thread.

    Saturday, April 6, 2019 9:01 AM
  • Hi George,

    Yes, it's really weird. I have tried to deploy with both Windows 10 versions 1803 and 1809 VMs in DCs of both Western and Northern Europe. My location is Sweden.

    I don't install anything before I try to install SQL Server 2017 Express (btw, I have tried to install Developer version as well, same result).

    I have also tried installing it with firewall turned off, same result.

    I have also tried both my private and my job Azure account (Pay per usage vs Visual Studio subscription). Same result.

    Deploying a preconfigured SQL VM image works fine, but this is not what we need.


    A former Javaman


    • Edited by magja Sunday, April 7, 2019 6:18 AM
    Sunday, April 7, 2019 6:18 AM
  • I see, can you post the summary.txt from the path C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log

    Please, If you think your question has been answered click "Mark as Answer" if just helped click "Vote as helpful". This can be beneficial to other community members reading this forum thread.

    Sunday, April 7, 2019 10:46 AM
  • Yeah, that's what I did in my initial post!

    A former Javaman

    Sunday, April 7, 2019 4:31 PM
  • You are right, I'm sorry about that. Did you try to download again the iso file maybe something is corrupted.

    Also, can you download Microsoft File Checksum Integrity Verifier to check the downloaded file? And download the full iso file.


    Please, If you think your question has been answered click "Mark as Answer" if just helped click "Vote as helpful". This can be beneficial to other community members reading this forum thread.

    Sunday, April 7, 2019 5:50 PM
  • Hi again,

    I can't find any ISO files available for download. Do they exist?


    A former Javaman

    Sunday, April 14, 2019 6:27 AM
  • Hi, 

    If you choose to download the iso file and not just run it it will exist in your downloads folder. 


    Please, If you think your question has been answered click "Mark as Answer" if just helped click "Vote as helpful". This can be beneficial to other community members reading this forum thread.

    • Marked as answer by magja Tuesday, April 16, 2019 1:48 PM
    Monday, April 15, 2019 6:22 AM
  • Well, I tried some of these preconfigured images. But they add a 1TB data disk that seems mandatory for it to actually work. Why? This makes it very expensive!

    A former Javaman

    Monday, April 15, 2019 4:03 PM
  • When you deploy a SQL Server Azure VM the default storage for the SQL data is 1 TB disk.

    Check this link to decrease the size of the disk.


    Please, If you think your question has been answered click "Mark as Answer" if just helped click "Vote as helpful". This can be beneficial to other community members reading this forum thread.

    Monday, April 15, 2019 5:45 PM
  • Yes, selecting Download Media and run installation from there solved this problem.

    Many thanks for your help, George.

    Best from Magnus


    A former Javaman

    Tuesday, April 16, 2019 1:48 PM