Did you try the Repair option? If that does not work out, the best may be to start over. This link is nothing I have tried myself, but I learnt it from another poster here who I tried to help: https://www.sql-easy.com/learn/how-to-uninstall-sql-server/ That poster was able to sort out his problems after following things article.
SQL Serv3er (Basic) install failing
Something happened to my MS SQL server and I need to reinstall and restore the db from a .bak file. However, I can't get the install to work. This is the Developer Edition (Basic). the error says :" Cannot find registry key "SOFTWARE\Microsoft\Microsoft SQL Server\160\ConfigurationState' Error description: Invalid command line argument.
CAn someone help me get this backup and running?
SQL Server
-
Erland Sommarskog 109.8K Reputation points • MVP
2024-03-03T18:16:13.0066667+00:00 So what did you actually do? You said that you have a backup file. This suggests that you have had SQL Server running somewhere previously. But now you are trying to install SQL Server? Is this on a different machine than you had originally? Or how did you end up here?
-
Ira Fuchs 0 Reputation points
2024-03-03T18:19:26.0566667+00:00 What did I do? That’s a very good question. I had an SQL server. Running on my windows 10 system but I haven’t used it in a few months. I went back to use it and all of a sudden couldn’t connect. So I investigated further and couldn’t find that there was any SQL server running, nor could I start it. I decided to Try to reinstall it but that’s where I am stuck.
Sign in to comment
1 answer
Sort by: Most helpful
-
Erland Sommarskog 109.8K Reputation points • MVP
2024-03-03T18:23:38.45+00:00 -
Ira Fuchs 0 Reputation points
2024-03-03T18:49:11.5733333+00:00 When I run the installer, the option given is only to install. Where do I find the repair option?
-
Ira Fuchs 0 Reputation points
2024-03-03T19:12:18.4766667+00:00 I went to that loink and I am trying Method 2 (uninstall from CLI as SQL server does not show up in Control Panel. Get get to step #1:
PS C:\Windows\system32> Get-WmiObject -Class win32_product | Where-Object {$_.Name -like "SQL Server"}
IdentifyingNumber : {DA835B20-B5E0-462B-A2BF-544562EF49F6}
Name : SQL Server 2022 Database Engine Services
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Database Engine Services
IdentifyingNumber : {94AEB0A0-365C-449B-B573-D2ECB353EB06}
Name : SQL Server 2022 XEvent
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 XEvent
IdentifyingNumber : {12618131-AA9A-4DAE-9387-CE4417955B9F}
Name : SQL Server 2022 Shared Management Objects
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Shared Management Objects
IdentifyingNumber : {E46B6112-6CA0-41DA-A17F-4026EF597001}
Name : SQL Server 2022 Database Engine Services
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Database Engine Services
IdentifyingNumber : {161B8D12-C41B-4ACF-9BB5-E1FEE6788869}
Name : SQL Server 2022 Database Engine Shared
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Database Engine Shared
IdentifyingNumber : {EAC54B82-7A37-4A9E-8953-474316BD40F6}
Name : SQL Server 2022 Connection Info
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Connection Info
IdentifyingNumber : {770DA7F2-817B-4AA6-9160-08BB658ABDC6}
Name : SQL Server 2022 Connection Info
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Connection Info
IdentifyingNumber : {8A033D83-DF0B-48E9-ACD3-EC33AA2A4639}
Name : SQL Server 2022 Database Engine Services
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Database Engine Services
IdentifyingNumber : {9D6F8754-28E9-4940-B319-3FC8588CF18F}
Name : Microsoft OLE DB Driver for SQL Server
Vendor : Microsoft Corporation
Version : 18.5.0.0
Caption : Microsoft OLE DB Driver for SQL Server
IdentifyingNumber : {8770AF64-BB4B-4404-BDD6-6AF8E4C461FC}
Name : SQL Server 2022 Common Files
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Common Files
IdentifyingNumber : {73F209E4-A55B-43CD-A868-33934D894976}
Name : SQL Server 2022 Database Engine Services
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Database Engine Services
IdentifyingNumber : {35EC6145-E333-42DB-BCB3-380DF6140C11}
Name : SQL Server 2022 Shared Management Objects Extensions
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Shared Management Objects Extensions
IdentifyingNumber : {6621C765-569C-4D46-A8E9-C69A47971357}
Name : SQL Server 2022 Database Engine Services
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Database Engine Services
IdentifyingNumber : {FDB357D5-CC78-480A-8D26-C15D1A877642}
Name : Browser for SQL Server 2022
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : Browser for SQL Server 2022
IdentifyingNumber : {DCA0C2D6-83BF-41AE-B1AB-C4181002DE40}
Name : SQL Server 2022 DMF
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 DMF
IdentifyingNumber : {D6E82158-05B9-4A18-A624-EA135BC77766}
Name : SQL Server 2022 Database Engine Shared
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Database Engine Shared
IdentifyingNumber : {0CEFE958-E71A-4171-9DEF-77E9234A5613}
Name : SQL Server 2022 SQL Diagnostics
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 SQL Diagnostics
IdentifyingNumber : {AB5D8778-81F3-47E2-87A4-35E776CD664B}
Name : Microsoft VSS Writer for SQL Server 2022
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : Microsoft VSS Writer for SQL Server 2022
IdentifyingNumber : {7EFD8B19-A9E6-41CF-A96F-B9B6E30EC345}
Name : SQL Server 2022 Batch Parser
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Batch Parser
IdentifyingNumber : {BD8B7339-7559-4FC3-95E6-264324D45235}
Name : SQL Server 2022 XEvent
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 XEvent
IdentifyingNumber : {629C8FC9-3763-4C58-8264-5288AE34AFEF}
Name : Microsoft SQL Server 2022 RsFx Driver
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : Microsoft SQL Server 2022 RsFx Driver
IdentifyingNumber : {41F638F9-A187-4193-BD4B-489ACE256908}
Name : SQL Server 2022 Database Engine Services
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Database Engine Services
IdentifyingNumber : {6F8242AA-1B25-421C-8E45-FC5978D9AA3A}
Name : SQL Server 2022 Shared Management Objects
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Shared Management Objects
IdentifyingNumber : {A0F7ACBA-075F-4BC7-A85A-5DC301FCEC74}
Name : SQL Server 2022 Shared Management Objects Extensions
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Shared Management Objects Extensions
IdentifyingNumber : {853997DA-6FCB-4FB9-918E-E0FF881FAF65}
Name : Microsoft ODBC Driver 17 for SQL Server
Vendor : Microsoft Corporation
Version : 17.7.2.1
Caption : Microsoft ODBC Driver 17 for SQL Server
IdentifyingNumber : {0029E33B-8F28-4225-9A4D-5CE25ABE529E}
Name : SQL Server 2022 Database Engine Services
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Database Engine Services
IdentifyingNumber : {BF4D8C4B-D931-4D62-A7ED-8A34B2FC0D1B}
Name : Microsoft SQL Server 2022 Setup (English)
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : Microsoft SQL Server 2022 Setup (English)
IdentifyingNumber : {7CC3CAFB-D225-448F-AE8D-9847FAEE1606}
Name : MySQL Server 8.0
Vendor : Oracle Corporation
Version : 8.0.36
Caption : MySQL Server 8.0
IdentifyingNumber : {6A68D32C-4C0D-4847-B70C-58E6B4D76A12}
Name : SQL Server 2022 Common Files
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Common Files
IdentifyingNumber : {C4CF167C-4739-4A3A-8D75-59C9C5F135CA}
Name : SQL Server 2022 Database Engine Services
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 Database Engine Services
IdentifyingNumber : {5AB77D4E-9E5F-4627-B78B-129A5EC2858A}
Name : SQL Server 2022 DMF
Vendor : Microsoft Corporation
Version : 16.0.1000.6
Caption : SQL Server 2022 DMF
step #2 requires that you an instance number. What id #? I just want to get rid of anything that is preventing the install.
-
Erland Sommarskog 109.8K Reputation points • MVP
2024-03-03T19:20:28.54+00:00 When I run the installer, the option given is only to install. Where do I find the repair option?
Select the Download media option and run the install from the ISO. Then you have the Repair option on the Maintentance page:
As for the details on how to follow the article I pointed you to, I'm afraid I have not reason to study the article in detail myself, so I cannot answer about what the id might be.
-
Ira Fuchs 0 Reputation points
2024-03-03T19:24:30.3333333+00:00 I don’t have an iso file. All I did was download the developer edition file from the Microsoft site. After spending a lot of time on this and trying to follow several responses, probably the best thing I can do now is to run SQL server under Linux.
-
Erland Sommarskog 109.8K Reputation points • MVP
2024-03-03T19:32:46.7466667+00:00 I went to https://www.microsoft.com/en-us/sql-server/sql-server-downloads. I selected the option to download SQL Server Developer Edition. When I start the installer I see this:
Select the option to the right to get the ISO.
-
Ira Fuchs 0 Reputation points
2024-03-03T20:28:16.0066667+00:00 OK, I downloaded the .iso and ran repair (successfully). I don't know what that accomplished as there is still no SQL Server running nor is it listed in Services.
-
Ira Fuchs 0 Reputation points
2024-03-03T21:27:14.93+00:00 MS SQL no longer appears in Services or Programs. I tried once more to do the Basic installation and it fails with:
Detailed results: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\160\Setup Bootstrap\Log\20240303_162408\sql_engine_core_inst_Cpu64_1.log
Error description: Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
-
Erland Sommarskog 109.8K Reputation points • MVP
2024-03-03T22:00:12.88+00:00 Did you look into to that log file? Yes, I know it is very verbose. But still you can at least try. There is also a detail.txt in the same folder.
Feel free to upload them here. (As attachments!) We also like to see summary.txt.
-
Ira Fuchs 0 Reputation points
2024-03-03T22:19:25.4233333+00:00 Here is the detail.txt file. If anyone can suggest what I can do to get SQL Server working again, I would be most grateful.Detail.txt
-
Erland Sommarskog 109.8K Reputation points • MVP
2024-03-03T22:43:16.94+00:00 Did you run the install from the ISO? I see this error:
(01) 2024-03-03 16:24:26 Slp: Sco: File 'C:\SQL2022\Developer_ENU\x64\setup\x64\sql_engine_core_inst.msi' does not exist
I would not expect this if you run from the ISO. But I've seen other people running into this, and I suspect this is because they have things in their registry which fools Setup to think the file is there already, so it does not extract it. But that is only speculation on my part.
In any case, I would not expect this error if you run from the ISO.
But since, quite clearly, your machine is apparently messed up, you may fail on the next error. This is why I recommended to follow this article for a total uninstall.
The other alternative is to build a virtual machine and run SQL Server on the VM.
-
Ira Fuchs 0 Reputation points
2024-03-03T22:51:01.2433333+00:00 I just tried doing the install with the .iso and got this error:
TITLE: Microsoft SQL Server 2022 Setup
The following error has occurred:
The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
-
Erland Sommarskog 109.8K Reputation points • MVP
2024-03-03T22:56:24.7933333+00:00 Yes, I've seen that error before. No, I don't know how to deal with it. I think a VM is your best bet.
-
Ira Fuchs 0 Reputation points
2024-03-03T22:59:01.6633333+00:00 Yes, it would appear that perhaps a Linux implementation would be a better way to go as there doesn’t seem to be a way to install SQL server on this machine in it’s current state.
Sign in to comment -