December 27, 2008 at 3:20 pm
Are there any files or folders left in the program files\microsoft sql\ server folder?
Is this a named instance?
Does the following exist in the registry?
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\
December 27, 2008 at 3:21 pm
This is really odd. I have found post out there referring to some of the things I found in the install logs, bust most of them are referring back to when 2005 was in CTP. There is not a whole lot since then.
I think I am going to strip the server down to the base OS. That is to say uninstall the .Net framework and IIS and try building it up from there. If that fails, I think I am looking at a complete rebuild.
December 27, 2008 at 3:27 pm
No this is not a named instance, though when 2005 was installed on the server before it was a named instance with SQL 2000 being the default instance.
After I uninstalled SQL 2005 the first time, I went back and deleted all the folders that I was using with both instances after the uninstall.
As for the registry key, it does exist.
I am sorry for the confusion. This is not a CTP install, it is actually enterprise edition.
I will definitely check out the tool.
December 27, 2008 at 3:36 pm
Just be careful with the tool, it can do bad things.
December 27, 2008 at 3:41 pm
Will do!
Thanks for your efforts! They are greatly appreciated!
December 27, 2008 at 3:43 pm
Wish some kind of fix was in he offing.
Please post whatever you do to get a final resolution for the problem.
December 28, 2008 at 11:43 pm
Hi,
If the current one is a default instance. Install another named instance and reboot the server and try to uninstall both using the arpwrapper.exe
Thanks
Chandra Mohan N
[font="Verdana"]Thanks
Chandra Mohan[/font]
January 2, 2009 at 7:17 am
Ok,
After spending way too much time tinkering with this, I finally got SQL 2005 to reinstall properly. Here are the steps that I followed that finally worked:
1. Un-installed the failed installation of SQL 2005 using arpwrapper.exe.
2. Un-installed all remaining SQL support products (SQLXML4, Native Client, Books Online, etc.)
3. Used the Windows installer cleanup utility to ensure that there weren't any references to any SQL products remaining.
4. Un-installed IIS.
5. Un-installed .Net 2.0
6. Rebooted and then opened a command prompt and ran the command line statement "Del /S *.tmp" to delete off all temporary files that were not in use.
7. Reinstalled .Net 2.0.
8. Reinstalled IIS.
9. Successfully reinstalled SQL 2005.
My best guess is that something got fouled up in the .Net framework and that was preventing the successful reinstall of SQL 2005.
Thanks to everyone for their help and support!
January 2, 2009 at 7:29 am
Wow, that's some work, but glad it did.
Thanks for posting back your solution.
January 4, 2009 at 10:28 am
usually a repair of the .NET 2 framework is enough did you try that at all in your previous steps
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 5, 2009 at 7:16 am
Yes. I did try a repair first and was a little disappointed when it didn't work. Removing and re-installing IIS and .Net where my last ditch efforts before rebuilding the entire box.
Viewing 12 posts - 16 through 26 (of 26 total)
You must be logged in to reply to this topic. Login to reply