December 15, 2005 at 11:40 am
Earlier this year I installed the SQL Server 2005 Beta as an upgrade to SQL Server 2000 on my test machine (Windows XP SP2). I wasn't able to do much with it, unfortunately, and the beta period has expired.
Anyway, now when I try to uninstall it I get the following: "The Microsoft.Net Framework 2.0 is not installed. Please install before running setup." I click past the error and get the message about sending an error report to Microsoft.
Of course I've got the Framework 2.0 installed, but I thought I'd run the 'Repair' option on the Framework setup just in case. The above error appeared again when I went to uninstall SQL 2005 beta.
I've checked the .NET Framework folder on my PC and I see that there are five versions: v1.0.3705, v1.1.4322, v2.0.40607, v2.0.50215, and v2.0.50727. So I think I've got the Framework installed!
Any idea what's happening to me? Thank you!
thetowncrank.blogspot.com
Steven W. Erbach
Neenah, WI
http://thetowncrank.blogspot.com
December 15, 2005 at 12:30 pm
Actually, to confuse matters you have 3 different versions of the .NET framework installed, but 3 different versions of 2.0.
.NET Framework 1.0
.NET Framework 1.1
.NET Framework 2.0
.NET Framework 1.0 and 1.1 generally play nice with each other. .NET Framework 2.0 is supposed to play separately from 1.0 and 1.1.
Did you upgrade .NET Framework 2.0 or install the production version?
K. Brian Kelley
@kbriankelley
December 15, 2005 at 1:20 pm
Brian,
» Did you upgrade .NET Framework 2.0 or install the production version? «
Excellent question. I'm pretty sure that I either installed it from an MSDN Universal install disk on its own or as part of the install for Visual Studio 2003...but I'm not positive.
During this process of trying to uninstall the SQL 2005 Beta I uninstalled the .NET Framework 1.1...at least it doesn't show up anymore on the list of installed programs.
Belarc Advisor shows that I've got Visual Studio .NET ver. 7.10.3077.0 and Visual Studio 2005 ver. 8.0.40607.42 installed, for what it's worth. The installed programs list only shows VS .NET 2003 Enterprise Architect.
I'm thinking that this is totally balls-up. I've been waiting for my MSDN Universal subscription to send me the new SQL Server 2005 DVDs, but they haven't arrived yet. I don't suppose there's any future in simply deleting the SQL Server 2005 folder and running a registry clean-up tool, is there?
thetowncrank.blogspot.com
Steven W. Erbach
Neenah, WI
http://thetowncrank.blogspot.com
December 15, 2005 at 1:28 pm
It's worth a shot. Of course, the usual provisos apply: make copies of your important stuff before you do. .NET Framework 2.0 would have come with VS2k5, though. Also, if you have MSDN universal, you can DL the ISOs.
K. Brian Kelley
@kbriankelley
December 15, 2005 at 1:36 pm
Brian,
Thanks for the encouragement. I'll Ghost the drive and polish off the SQL 2005 beta folder.
Any registry irregularity repair tool you recommend? I use Registry Mechanic and the one that comes with Norton Utilities.
Thanks again,
http://thetowncrank.blogspot.com
Steven W. Erbach
Neenah, WI
http://thetowncrank.blogspot.com
December 15, 2005 at 1:52 pm
Actually, no, don't have much comment on that part. In the past when I've had to manually uninstall a SQL Server (granted it was SQL Server 2000), I went at the registry manually.
K. Brian Kelley
@kbriankelley
December 15, 2005 at 3:28 pm
Brian,
Yeah, I've done the same in the past, too. Just keeping an eye open for a more convenient way to do it. Thank you.
Steven W. Erbach
Neenah, WI
http://thetowncrank.blogspot.com
December 15, 2005 at 8:42 pm
The uninstall utilities for each of the different CTP (beta) versions were different... and none of them were 100%. We went through April, June and September and after that there was a tool that supposedly uninstalled any of them. There was a very particular sequence for uninstalling, as well. It was sort of logical; but not totally intuitive, if you know what I mean. I would NOT blow away the directory structure and expect it to work. You seem to be doing the right thing - making a Ghost copy first; but I am quite sure you will find that it will never be quite right. You could probably spend a month trying to clean things up and still not get it - and end up doing a fresh OS installtion anyway. THAT would be my recommendation from the get-go based on where you stand. The two tools you mentioned for cleaning the registry are pretty good; but again, you will never get it perfect once you start heading down-hill, it just isn't going to ever be the same. My first step, given your situation, would be to try to find the uninstall utility from MS that was released in the middle of October. The next step would be to uninstall from the CTP that you installed. Third step might be to use the other two uninstall utilities... (for instance, if you had April installed, to use the June and September utilities)... of course, this is considering that the October tool did not do the job. If you can't find it send me a private message and I will locate it for you. I know we have it on a server - just not sure were it came from exactly, and I never had to use it because by then I was freshly Ghosted.
You can make it painful on yourself; but the least pain will come from a fresh installation... This doesn't have to be the case; but your problems look familar.
December 16, 2005 at 6:56 am
David,
Thank you for that very thoughtful and detailed reply! I will, indeed, look for the MS uninstall utility you mentioned. I haven't dived into the drastic surgery method just yet...thought I'd wait for a lull during the holidays. But your suggestion is something to try sooner. Thanks, again.
Regards,
Steven W. Erbach
Neenah, WI
http://thetowncrank.blogspot.com
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply