Uninstall a single SQL server Instance through the registry
I'm running SQL Server 2014 and have 50 separate instances running. This is the max limit of number of instances for this version and I obviously need to uninstall some instances and clean up.
However upon research there's a bug which won't allow you to uninstall instances through the Programs and Features installer or command line when you have 50 instances installed. The installer freezes when querying the list. I checked the bootstrap log files and the exported errors state that it can't perform the operation because there are too many instances which is the whole problem in the first place!
I need to uninstall the instance through the registry. I was able to remove the instance from HKLMSOFTWAREMicrosoftWindowsCurrentVersionUninstall using msiexec but when I did that the SQL Browser service crashed, the other sql instances lost connection and the services for the old instance would reappear. I had to restore the registry from the backup I made. Is there a way to remove an instance from the registry properly and re-situate the browser service? Maybe some registry items I'm missing?
windows-registry uninstall sql
asked Dec 31 '18 at 16:57
user979474user979474
11
add a comment |
I'm running SQL Server 2014 and have 50 separate instances running. This is the max limit of number of instances for this version and I obviously need to uninstall some instances and clean up.
However upon research there's a bug which won't allow you to uninstall instances through the Programs and Features installer or command line when you have 50 instances installed. The installer freezes when querying the list. I checked the bootstrap log files and the exported errors state that it can't perform the operation because there are too many instances which is the whole problem in the first place!
I need to uninstall the instance through the registry. I was able to remove the instance from HKLMSOFTWAREMicrosoftWindowsCurrentVersionUninstall using msiexec but when I did that the SQL Browser service crashed, the other sql instances lost connection and the services for the old instance would reappear. I had to restore the registry from the backup I made. Is there a way to remove an instance from the registry properly and re-situate the browser service? Maybe some registry items I'm missing?
windows-registry uninstall sql
asked Dec 31 '18 at 16:57
user979474user979474
11
add a comment |
I'm running SQL Server 2014 and have 50 separate instances running. This is the max limit of number of instances for this version and I obviously need to uninstall some instances and clean up.
However upon research there's a bug which won't allow you to uninstall instances through the Programs and Features installer or command line when you have 50 instances installed. The installer freezes when querying the list. I checked the bootstrap log files and the exported errors state that it can't perform the operation because there are too many instances which is the whole problem in the first place!
I need to uninstall the instance through the registry. I was able to remove the instance from HKLMSOFTWAREMicrosoftWindowsCurrentVersionUninstall using msiexec but when I did that the SQL Browser service crashed, the other sql instances lost connection and the services for the old instance would reappear. I had to restore the registry from the backup I made. Is there a way to remove an instance from the registry properly and re-situate the browser service? Maybe some registry items I'm missing?
windows-registry uninstall sql
asked Dec 31 '18 at 16:57
user979474user979474
11
I'm running SQL Server 2014 and have 50 separate instances running. This is the max limit of number of instances for this version and I obviously need to uninstall some instances and clean up.
However upon research there's a bug which won't allow you to uninstall instances through the Programs and Features installer or command line when you have 50 instances installed. The installer freezes when querying the list. I checked the bootstrap log files and the exported errors state that it can't perform the operation because there are too many instances which is the whole problem in the first place!
I need to uninstall the instance through the registry. I was able to remove the instance from HKLMSOFTWAREMicrosoftWindowsCurrentVersionUninstall using msiexec but when I did that the SQL Browser service crashed, the other sql instances lost connection and the services for the old instance would reappear. I had to restore the registry from the backup I made. Is there a way to remove an instance from the registry properly and re-situate the browser service? Maybe some registry items I'm missing?
windows-registry uninstall sql
windows-registry uninstall sql
asked Dec 31 '18 at 16:57
user979474user979474
11
asked Dec 31 '18 at 16:57
user979474user979474
11
asked Dec 31 '18 at 16:57
user979474user979474
11
asked Dec 31 '18 at 16:57
user979474user979474
11
asked Dec 31 '18 at 16:57
user979474user979474
11
11
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I've figured out the solution for this based on an order of operations. This resolved my issue.
- Stop the SQL Browser service
- SC Delete the SQL Server service for the particular erroneous instance
- Run the uninstall command from the
setup.exeusing the installer diskSetup.exe /Action=Uninstall /FEATURES=SQLEngine /INSTANCENAME=MyInstance /Q
- (The SQL Server Agent service for the erroneous instance will disappear)
- Start the SQL Browser service
- Uninstall subsequent erroneous instances through Programs and Features as this will now complete without hanging.
edited Jan 17 at 2:04
GabrielaGarcia
693415
answered Jan 16 at 22:43
KcdemagKcdemag
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1389330%2funinstall-a-single-sql-server-instance-through-the-registry%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've figured out the solution for this based on an order of operations. This resolved my issue.
- Stop the SQL Browser service
- SC Delete the SQL Server service for the particular erroneous instance
- Run the uninstall command from the
setup.exeusing the installer diskSetup.exe /Action=Uninstall /FEATURES=SQLEngine /INSTANCENAME=MyInstance /Q
- (The SQL Server Agent service for the erroneous instance will disappear)
- Start the SQL Browser service
- Uninstall subsequent erroneous instances through Programs and Features as this will now complete without hanging.
edited Jan 17 at 2:04
GabrielaGarcia
693415
answered Jan 16 at 22:43
KcdemagKcdemag
1
add a comment |
I've figured out the solution for this based on an order of operations. This resolved my issue.
- Stop the SQL Browser service
- SC Delete the SQL Server service for the particular erroneous instance
- Run the uninstall command from the
setup.exeusing the installer diskSetup.exe /Action=Uninstall /FEATURES=SQLEngine /INSTANCENAME=MyInstance /Q
- (The SQL Server Agent service for the erroneous instance will disappear)
- Start the SQL Browser service
- Uninstall subsequent erroneous instances through Programs and Features as this will now complete without hanging.
edited Jan 17 at 2:04
GabrielaGarcia
693415
answered Jan 16 at 22:43
KcdemagKcdemag
1
add a comment |
I've figured out the solution for this based on an order of operations. This resolved my issue.
- Stop the SQL Browser service
- SC Delete the SQL Server service for the particular erroneous instance
- Run the uninstall command from the
setup.exeusing the installer diskSetup.exe /Action=Uninstall /FEATURES=SQLEngine /INSTANCENAME=MyInstance /Q
- (The SQL Server Agent service for the erroneous instance will disappear)
- Start the SQL Browser service
- Uninstall subsequent erroneous instances through Programs and Features as this will now complete without hanging.
edited Jan 17 at 2:04
GabrielaGarcia
693415
answered Jan 16 at 22:43
KcdemagKcdemag
1
I've figured out the solution for this based on an order of operations. This resolved my issue.
- Stop the SQL Browser service
- SC Delete the SQL Server service for the particular erroneous instance
- Run the uninstall command from the
setup.exeusing the installer diskSetup.exe /Action=Uninstall /FEATURES=SQLEngine /INSTANCENAME=MyInstance /Q
- (The SQL Server Agent service for the erroneous instance will disappear)
- Start the SQL Browser service
- Uninstall subsequent erroneous instances through Programs and Features as this will now complete without hanging.
edited Jan 17 at 2:04
GabrielaGarcia
693415
answered Jan 16 at 22:43
KcdemagKcdemag
1
edited Jan 17 at 2:04
GabrielaGarcia
693415
edited Jan 17 at 2:04
GabrielaGarcia
693415
edited Jan 17 at 2:04
GabrielaGarcia
693415
693415
answered Jan 16 at 22:43
KcdemagKcdemag
1
answered Jan 16 at 22:43
KcdemagKcdemag
1
answered Jan 16 at 22:43
KcdemagKcdemag
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1389330%2funinstall-a-single-sql-server-instance-through-the-registry%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
