Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Uninstalling SQL Server 2005 Standard on Windows Server 2003 Fails With Fatal Error

Posted on 2011-02-11
4
Medium Priority
?
441 Views
Last Modified: 2012-05-11
I've got a Windows Server 2003 that originally had just SQL Server 2005 standard edition on it. Later I installed SQL Server 2008 standard edition on it as well. I am now trying to uninstall SQL Server 2005 and the uninstall is terminating with a fatal error. This server also runs Active Directory. Can't remember if I promoted it after the initial SQL Server 2005 or before. The specific error message: "The setup has encountered an unexpected error while Setting Internal Properties. The error is : Fatal error during installation." I came across this kb article, but my registry does not have the exact keys they specify so I could not do anything with it:
http://support.microsoft.com/kb/919945

Thanks for any help.
0
Comment
Question by:tcianflone
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 5

Assisted Solution

by:robertg34
robertg34 earned 2000 total points
ID: 34872860
You might want to check these registry keys as well:
http://support.microsoft.com/kb/925976
0
 
LVL 1

Author Comment

by:tcianflone
ID: 34982477
Question not abandoned. Haven't had time to get back to this, buy I intend to and then post my results here. Thanks.
0
 
LVL 1

Accepted Solution

by:
tcianflone earned 0 total points
ID: 35039458
Well, this was quite an adventure. Turns out that kb article referenced by robertg34 helped to explain the one I referenced in the question, which ultimately led to the fix. kb919945 references this registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X but it doesn't tell you the 'X' is a placeholder for the version of SQL you're running. That I learned from the kb article posted by robertg34. Once I learned that and started looking at the registry again, I saw that SQL Server 2005 had both an SQL name (MSSQL.1) and an OLAP name (MSSQL.2). Found this in the InstanceNames key of the registry. Under MSSQL.1 I deleted the key data (NOT the keys themselves) suggested in kb919945. This got me to the point that the 2005 database server would uninstall, but the analytical services still failed to uninstall. Under MSSQL.2 I found one more group key not mentioned in kb919945: ASGroup. This also had a security identifier loaded, so I deleted that data, just like I did the in the keys under MSSQL.1, and then that part of the uninstall completed successfully.
0
 
LVL 1

Author Closing Comment

by:tcianflone
ID: 35081083
I'm awarding robertg34 since he's the only one to offer any clarifying material.
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article we will get to know that how can we recover deleted data if it happens accidently. We really can recover deleted rows if we know the time when data is deleted by using the transaction log.
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
We’ve all felt that sense of false security before—locking down external access to a database or component and feeling like we’ve done all we need to do to secure company data. But that feeling is fleeting. Attacks these days can happen in many w…
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question