Why is it so complicated to uninstall and reinstall Microsoft SQL Server 2019

Question

Why is it so complicated to uninstall and reinstall Microsoft SQL Server 2019

Anonymous

Why is it so complicated just to uninstall and reinstall Microsoft SQL Server 2019? I have been at this for over an hour now and keep running into errors. I uninstalled every program pertaining to Microsoft SQL Server 2019 and I keep getting "exit code 2069119551" when I try to reinstall it and the instances I have uninstalled 3 times now keep reappearing when I check on them again. This should be streamlined for easier use. I am a student trying to learn and I don't understand every dependency of the program yet and have no knowledge of the locations of every file I need to delete and uninstall to get this to work. I keep trying to fully uninstall and it tells me I need to uninstall dependencies first. When I try to uninstall the dependencies I get more messages saying they are dependent on other files that I need to remove first. I'm trying to follow the directions in the previous comments on this forum but I am having a lot of trouble getting this to work.

I tried contacting customer support but was essentially told to come to this page which has not helped. I need support on this issue as I am a student and I have assignments due that I need SQL server installed for. PLEASE HELP.

Erland Sommarskog 121.9K Reputation points MVP Volunteer Moderator

2023-05-20T17:24:55.9+00:00

What lead you to uninstall in the first place? I mean, once it's installed, why touch it?

Anyway, in C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log, there is one folder for each install and uninstall attempt. The file of most interest in those folder are summary.txt and detail.txt. Can you share these?
Anonymous

2023-05-20T17:47:40.17+00:00

I am in an Associate in applied science program concentrated in cybersecurity and web programming certificate program, last semester my PC was just about full on storage and I had to delete some programs to make space for VMs and other programs. I wasn't using SQL at the time so I deleted it to make space on my PC. I needed to reinstall it for my Database Programming class this semester but realized while reinstalling that not all of the files were deleted the first time. I just deleted those files thinking that they were the issue. I will restore them from my recycle bin and share them in a minute.
Erland Sommarskog 121.9K Reputation points MVP Volunteer Moderator

2023-05-20T17:53:35.55+00:00

OK, that makes sense. I like to believe that once you've uninstalled it, it should be easy to reinstall. But I rarely uninstall SQL Server myself...

A tip, though, don't select "everything". Basically, only select Database Engine without any of the sub-options and also Integration Services. Specifically, don't select Polybase, which can cause trouble in more than one way. (That's the one component I have tried to uninstall, and this failed, and now I'm getting not forth nor back.)

Anonymous

Summary.txt file

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068119551
  Start time:                    2023-05-20 13:53:23
  End time:                      2023-05-20 13:54:30
  Requested action:              Install

Machine Properties:
  Machine name:                  AIDANAHEARN
  Machine processor count:       12
  OS version:                    Microsoft Windows 11 Home (10.0.22621)
  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 2019      SQLEXPRESS           MSSQL15.SQLEXPRESS             Database Engine Services                 1033                 Express Edition      15.0.2000.5     No         Yes       

Package properties:
  Description:                   Microsoft SQL Server 2019 
  ProductName:                   SQL Server 2019
  Type:                          RTM
  Version:                       15
  SPLevel:                       0
  Installation location:         C:\SQL2019\Express_ENU\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:                  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:             C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20230520_135323\ConfigurationFile.ini
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    true
  ENU:                           true
  EXTSVCACCOUNT:                 <empty>
  EXTSVCPASSWORD:                <empty>
  FEATURES:                      SQLENGINE
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTPYTHONLICENSETERMS:     false
  IACCEPTROPENLICENSETERMS:      false
  IACCEPTSQLSERVERLICENSETERMS:  true
  IACKNOWLEDGEENTCALLIMITS:      false
  INDICATEPROGRESS:              true
  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:                    SQLEXPRESS01
  INSTANCENAME:                  SQLEXPRESS01
  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:                         true
  QUIETSIMPLE:                   false
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 DefaultNativeMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
  SQLJAVADIR:                    <empty>
  SQLMAXDOP:                     0
  SQLMAXMEMORY:                  2147483647
  SQLMINMEMORY:                  0
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLEXPRESS01
  SQLSVCINSTANTFILEINIT:         true
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           AIDANAHEARN\arahe
  SQLTELSVCACCT:                 NT Service\SQLTELEMETRY$SQLEXPRESS01
  SQLTELSVCPASSWORD:             <empty>
  SQLTELSVCSTARTUPTYPE:          Automatic
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBFILECOUNT:            1
  SQLTEMPDBFILEGROWTH:           64
  SQLTEMPDBFILESIZE:             8
  SQLTEMPDBLOGDIR:               <empty>
  SQLTEMPDBLOGFILEGROWTH:        64
  SQLTEMPDBLOGFILESIZE:          8
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SUPPRESSPAIDEDITIONNOTICE:     false
  SUPPRESSPRIVACYSTATEMENTNOTICE: false
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 false
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  USESQLRECOMMENDEDMEMORYLIMITS: false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20230520_135323\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Passed

  Feature:                       SQL Browser
  Status:                        Passed

  Feature:                       SQL Writer
  Status:                        Passed

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed

  Feature:                       SQL Client Connectivity
  Status:                        Passed

Rules with failures or warnings:

Global rules:
Warning    IsFirewallEnabled                The Windows Firewall is enabled. Make sure the appropriate ports are open to enable remote access. See the rules documentation at https://go.microsoft.com/fwlink/?linkid=2094702 for information about ports to open for each feature.

Rules report file:               C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log\20230520_135323\SystemConfigurationCheck_Report.htm

Anonymous

2023-05-20T17:57:48.95+00:00

I found the detail.txt file but i think it is way to big to paste in here
Anonymous

2023-05-20T18:18:35.3866667+00:00

I've reinstalled it again and I'm getting the same stop code and when i try to connect to the server in SMSS it gives me this error message -->

TITLE: Connect to Server

Cannot connect to localhost.

ADDITIONAL INFORMATION:

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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

For help, click: https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver--1-database-engine-error

BUTTONS:

OK
Erland Sommarskog 121.9K Reputation points MVP Volunteer Moderator

2023-05-20T18:36:55.1433333+00:00

That error means that SQL Server is not running.

The funny thing is that Summary.txt says on top that it failed, but at the end it says everything Passed.

As for details.txt, no don't paste it. Attach it instead. (The fourth button in the second group.)

Also, if you have a file ERRORLOG in C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS01\MSSQL\LOG, attach this file as well. (You will need to rename it to ERRORLOG.txt to be able to.)
Anonymous

2023-05-20T19:04:23.04+00:00

This is the detail.txt file. I can't seem to locate the ERRORLOG file. I've found 2 separate ones named SQLServer_ERRORLOG_2023-05-20T13.54.19 (other 2 have a .22 and .27 instead of a .19)
Anonymous

2023-05-20T19:04:55.73+00:00

Detail.txt
Anonymous

2023-05-20T19:07:26.19+00:00

Oops realized I was in a different path. When I follow the path you listed to find the ERRORLOG file it won't let me open the MSSQL\LOG file. I see it but when I click on it nothing happens.
Anonymous

2023-05-20T19:08:48.5+00:00

It has 0 bytes so my LOG file is empty

1 answer

Your answer

Erland Sommarskog 121.9K Reputation points MVP Volunteer Moderator

2023-05-20T17:24:55.9+00:00

What lead you to uninstall in the first place? I mean, once it's installed, why touch it?

Anyway, in C:\Program Files\Microsoft SQL Server\150\Setup Bootstrap\Log, there is one folder for each install and uninstall attempt. The file of most interest in those folder are summary.txt and detail.txt. Can you share these?
Anonymous

2023-05-20T17:47:40.17+00:00

I am in an Associate in applied science program concentrated in cybersecurity and web programming certificate program, last semester my PC was just about full on storage and I had to delete some programs to make space for VMs and other programs. I wasn't using SQL at the time so I deleted it to make space on my PC. I needed to reinstall it for my Database Programming class this semester but realized while reinstalling that not all of the files were deleted the first time. I just deleted those files thinking that they were the issue. I will restore them from my recycle bin and share them in a minute.
Erland Sommarskog 121.9K Reputation points MVP Volunteer Moderator

2023-05-20T17:53:35.55+00:00

OK, that makes sense. I like to believe that once you've uninstalled it, it should be easy to reinstall. But I rarely uninstall SQL Server myself...

A tip, though, don't select "everything". Basically, only select Database Engine without any of the sub-options and also Integration Services. Specifically, don't select Polybase, which can cause trouble in more than one way. (That's the one component I have tried to uninstall, and this failed, and now I'm getting not forth nor back.)
Anonymous

2023-05-20T17:57:48.95+00:00

I found the detail.txt file but i think it is way to big to paste in here
Anonymous

2023-05-20T18:18:35.3866667+00:00

I've reinstalled it again and I'm getting the same stop code and when i try to connect to the server in SMSS it gives me this error message -->

TITLE: Connect to Server

Cannot connect to localhost.

ADDITIONAL INFORMATION:

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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

For help, click: https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver--1-database-engine-error

BUTTONS:

OK
Erland Sommarskog 121.9K Reputation points MVP Volunteer Moderator

2023-05-20T18:36:55.1433333+00:00

That error means that SQL Server is not running.

The funny thing is that Summary.txt says on top that it failed, but at the end it says everything Passed.

As for details.txt, no don't paste it. Attach it instead. (The fourth button in the second group.)

Also, if you have a file ERRORLOG in C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS01\MSSQL\LOG, attach this file as well. (You will need to rename it to ERRORLOG.txt to be able to.)
Anonymous

2023-05-20T19:04:23.04+00:00

This is the detail.txt file. I can't seem to locate the ERRORLOG file. I've found 2 separate ones named SQLServer_ERRORLOG_2023-05-20T13.54.19 (other 2 have a .22 and .27 instead of a .19)
Anonymous

2023-05-20T19:07:26.19+00:00

Oops realized I was in a different path. When I follow the path you listed to find the ERRORLOG file it won't let me open the MSSQL\LOG file. I see it but when I click on it nothing happens.
Anonymous

2023-05-20T19:08:48.5+00:00

It has 0 bytes so my LOG file is empty

Answer 1

Erland Sommarskog 121.9K MVP Volunteer Moderator

That should work fine. SQL 2022 has a few more features that will not be available to your class-mates, but no one will notice. Everything that runs on SQL 2019 runs on SQL 2022.

And, also, you can have both installed. More precisely, you can have many instances on a single computer, and they can be running the same or different versions. But possibly you have messed up some folder prohibiting an install of SQL 2019.

Erland Sommarskog 121.9K Reputation points MVP Volunteer Moderator

2023-05-20T19:14:43.66+00:00

I found this in the log:

File 'C:\Program Files (x86)\Microsoft SQL Server\150\Shared\sqlmgmproviderxpsp2up.mof' not found!

Why that file would be missing I don't know, but I have it on my machine. It could be that since you are running a second install that Setup expects it to be there. It could also be that something removed it while running the install. (I don't know, I'm just speculating.) But I'm leaning towards the former.

Maybe an easy way out is to try to install SQL 2022 instead. That install will not look in this folder, but a sister folder with 160 in the path.
Anonymous

2023-05-20T19:17:21.7133333+00:00

Ok, I will talk to my teacher and see if that will suffice for the class I'm taking. The book we are going off is Murach's SQL Server 2019 for Developers so I think I might need the 2019 version. But thank you for the advice I really appreciate you helping me with this.
Anonymous

2023-05-20T19:28:49.8366667+00:00

That makes complete sense. Thank you Erland!
Anonymous

2023-05-20T19:58:44.0133333+00:00

So I installed 2022 without any issues or error messages but when I try to connect to my server in SMSS it keeps saying the same connection error -->

TITLE: Connect to Server

Cannot connect to localhost.

ADDITIONAL INFORMATION:

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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

For help, click: https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver--1-database-engine-error

BUTTONS:

OK
Anonymous

2023-05-20T20:03:23.66+00:00

do I need to download a different SMSS than 19.0.2 since I have SQL Server 2022 installed now or is it compatible with it? From what I can see that is the newest version.
Anonymous

2023-05-20T20:04:36.4266667+00:00

AHH, i got it nevermind! my instance had an 01 at the end that i was missing! Thank you!
Erland Sommarskog 121.9K Reputation points MVP Volunteer Moderator

2023-05-20T21:15:42.9733333+00:00

Glad to hear that everything is working! I converted my comment where suggested you to use SQL 2022 to Answer, so you can accept it if you like.

Also, I like to thank you for being so persistent. These errors about missing mof files and similar comes up every once in a while, but it is difficult to understand what might me the cause. People does not always tell us what they have done to their machines, but you have given me a lead. I will try to install and uninstall to see what happens with the mof file, and then maybe delete it to see if I can repro this.

Share via

Why is it so complicated to uninstall and reinstall Microsoft SQL Server 2019

1 answer

Your answer