July 29, 2009 at 9:04 pm
I've got one heck of a problem and I'm afraid I brought it on my self. Apparently, my system went through an automatic update over night and rebooted. The following morning, I logged in and the McAfee software asked me if I wanted to allow an update on SQLBrowser.exe and also recommended that I don't allow the update... so I didn't. Big mistake. SQL Server 2005 wouldn't work anymore.
Since it wasn't a production system (it's my desktop box at home), I tried to unistall and it took several times but it finally uninstalled.
Now I'm trying to do a reinstall and it installs many of the components but won't install the database engine, reporting services, or most of the other stuff and I have no idea why. It said to check the log but when I double clicked on the entry, nothing came up. There's about a bazillion log files and, frankly, I have no idea what they're telling me.
Now there's no entry in ADD/REMOVE to try to uninstall and try again.
I'm really stuck, folks. I could really use some help on this. I have Windows XP (sp2) running on a 32 bit machine. I'm trying to reinstall SQL Server 2005 Developers Edition. Thanks for whatever help you can offer because I'm jonesing for my SQL Server.
Heh... and no... I'm not feeling much like an MVP right now. 🙁
--Jeff Moden
Change is inevitable... Change for the better is not.
July 29, 2009 at 9:11 pm
Let's take this one step at a time. Looking at my system here at home the logs are in this directory: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files.
Is this where you are looking?
July 29, 2009 at 9:32 pm
Lynn Pettis (7/29/2009)
Let's take this one step at a time. Looking at my system here at home the logs are in this directory: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files.Is this where you are looking?
Yes. There are multiple numbered instances of the files in that directory and I can easily find the latest instance from the last install.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 29, 2009 at 10:00 pm
Hi Jeff
If u believe u have completely uninstall the SQL Server, you can try to delete the following folder completely C:\Program Files\Microsoft SQL Server.
Once u've delete the folder, try to re-install it again. I think I have the same problem last time and this is how I get around it.
Good Luck
IT
July 29, 2009 at 10:09 pm
Check the latest %SQL.log. From looking at the one in my directory, that is the log for installing the dtabase engine.
July 29, 2009 at 10:21 pm
Lynn Pettis (7/29/2009)
Check the latest %SQL.log. From looking at the one in my directory, that is the log for installing the dtabase engine.
Sorry... I don't see any such file... here's what I have...
Directory of C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files
07/29/2009 10:55 PM 262,754 SQLSetup0013_JMODEN2_BackwardsCompat_1.log
07/29/2009 11:00 PM 262,754 SQLSetup0013_JMODEN2_BackwardsCompat_2.log
07/29/2009 11:02 PM 262,754 SQLSetup0013_JMODEN2_BackwardsCompat_3.log
07/29/2009 11:05 PM 262,754 SQLSetup0013_JMODEN2_BackwardsCompat_4.log
07/29/2009 11:15 PM 262,752 SQLSetup0013_JMODEN2_BackwardsCompat_5.log
07/29/2009 11:15 PM 8,902,442 SQLSetup0013_JMODEN2_BOL_1.log
07/29/2009 11:16 PM 21,712 SQLSetup0013_JMODEN2_Core(Patched).log
07/29/2009 11:07 PM 1,439 SQLSetup0013_JMODEN2_Core.log
07/29/2009 11:16 PM 133,016 SQLSetup0013_JMODEN2_Datastore.xml
07/29/2009 10:55 PM 59,210 SQLSetup0013_JMODEN2_MSXML6_1.log
07/29/2009 10:55 PM 239,192 SQLSetup0013_JMODEN2_OWC11_1.log
07/29/2009 11:00 PM 238,802 SQLSetup0013_JMODEN2_OWC11_2.log
07/29/2009 11:02 PM 238,802 SQLSetup0013_JMODEN2_OWC11_3.log
07/29/2009 11:05 PM 238,796 SQLSetup0013_JMODEN2_OWC11_4.log
07/29/2009 11:13 PM 238,802 SQLSetup0013_JMODEN2_OWC11_5.log
07/29/2009 10:49 PM 52,668 SQLSetup0013_JMODEN2_SCC.log
07/29/2009 10:55 PM 8,543,240 SQLSetup0013_JMODEN2_SQLNCLI_1.log
07/29/2009 11:00 PM 8,543,240 SQLSetup0013_JMODEN2_SQLNCLI_2.log
07/29/2009 11:05 PM 8,543,240 SQLSetup0013_JMODEN2_SQLNCLI_3.log
07/29/2009 11:13 PM 8,543,240 SQLSetup0013_JMODEN2_SQLNCLI_4.log
07/29/2009 10:53 PM 8,669,844 SQLSetup0013_JMODEN2_SQLSupport_1.log
07/29/2009 10:58 PM 8,669,844 SQLSetup0013_JMODEN2_SQLSupport_2.log
07/29/2009 11:02 PM 8,669,844 SQLSetup0013_JMODEN2_SQLSupport_3.log
07/29/2009 11:04 PM 8,669,844 SQLSetup0013_JMODEN2_SQLSupport_4.log
07/29/2009 11:11 PM 8,669,840 SQLSetup0013_JMODEN2_SQLSupport_5.log
07/29/2009 11:05 PM 159,466 SQLSetup0013_JMODEN2_SqlWriter_1.log
07/29/2009 11:07 PM 8,566,856 SQLSetup0013_JMODEN2_SQLXML4_1.log
07/29/2009 11:09 PM 8,566,856 SQLSetup0013_JMODEN2_SQLXML4_2.log
07/29/2009 10:48 PM 8,656,046 SQLSetup0013_JMODEN2_Support.log
07/29/2009 10:52 PM 3,706,754 SQLSetup0013_JMODEN2_WI.log
30 File(s) 118,856,803 bytes
0 Dir(s) 61,575,479,296 bytes free
--Jeff Moden
Change is inevitable... Change for the better is not.
July 29, 2009 at 10:24 pm
Irwan Tjanterik (7/29/2009)
Hi JeffIf u believe u have completely uninstall the SQL Server, you can try to delete the following folder completely C:\Program Files\Microsoft SQL Server.
Once u've delete the folder, try to re-install it again. I think I have the same problem last time and this is how I get around it.
Good Luck
IT
Heh... Good luck, indeed. I don't believe SQL Server uninstalled all the way. It looks like the MSXML 6.0 Parser is stuck and it won't delete using Add/Remove nor will it repair. MSXML 6.0 Parser was the first red error that showed up on the reinstall attempts I've made so far and is one of the things that I found that should be deleted in the following article that I just now found on how to do manual uninstalls....
http://support.microsoft.com/default.aspx/kb/909967
--Jeff Moden
Change is inevitable... Change for the better is not.
July 29, 2009 at 10:36 pm
Jeff, Go up one level, is there a Summary.txt file? If so, what is in it?
July 29, 2009 at 11:04 pm
Yeppp that file exists.... I've tried a reinstall again since the #13 try worth of files I just listed...
Machine : JMODEN2
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : JMODEN2
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_OWC11_1.log
--------------------------------------------------------------------------------
Machine : JMODEN2
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.2004
Uninstall : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_BackwardsCompat_1.log
--------------------------------------------------------------------------------
[highlight]Machine : JMODEN2
Product : MSXML 6 Service Pack 2 (KB954459)
Product Version : 6.20.1099.0
Uninstall : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_MSXML6_1.log
Error Number : 1603 [/highlight]--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Wed Jul 29 23:53:41 2009
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_AS.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_SQLSupport_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_OWC11_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_BackwardsCompat_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_MSXML6_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_SCC.log
That MSXML 6 Service Pack 2 (KB954459) thing is the thing that failed on the GUI for the install.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2009 at 12:04 am
Heh... ok... NOW I'm feeling more like an MVP! It took 8 bloody hours but I think I've got this problem licked. I'm in the middle of another reinstall attempt and it made it past the previous failures. Once I'm sure I've got a good install, I'll post what I did here. I'm also going to write an article on it because the fix can fix a lot of things I saw in other peoples' plea for help on the very same subject.
Thanks for the look-see, Lynn. Heh... I somehow knew you'd be the one to answer after midnight. Even the worldwide and very popular MSDN site hasn't responded, yet. 🙂
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2009 at 12:20 am
Is there a more detailed error message in this file: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_MSXML6_1.log?
July 30, 2009 at 12:53 am
Lynn Pettis (7/30/2009)
Is there a more detailed error message in this file: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_MSXML6_1.log?
Yep.... it's quite long so I'll post the only line in monster 421 line file of garbage` (that's French for "garbage") 🙂
MSI (s) (7C:B0) [23:53:36:062]: Product: MSXML 6 Service Pack 2 (KB954459) -- Removal failed.
... and we already knew that.
The fix I found apparently works... I'm almost at the end of a successful reinstall. Like I said, once I'm sure that everything is copacetic, I'll post what I did to fix this nasty problem.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 30, 2009 at 1:05 am
Jeff Moden (7/30/2009)
Lynn Pettis (7/30/2009)
Is there a more detailed error message in this file: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0014_JMODEN2_MSXML6_1.log?Yep.... it's quite long so I'll post the only line in monster 421 line file of garbage` (that's French for "garbage") 🙂
MSI (s) (7C:B0) [23:53:36:062]: Product: MSXML 6 Service Pack 2 (KB954459) -- Removal failed.
... and we already knew that.
The fix I found apparently works... I'm almost at the end of a successful reinstall. Like I said, once I'm sure that everything is copacetic, I'll post what I did to fix this nasty problem.
That's about as detailed as the other message.
Glad to hear you are getting it fixed.
Well, it's late and i need to go to work later this morning. Missed work yesterday due to a family emergency. Mother-in-law had a heart attack. She's doing okay, and will be in the hospital a few days.
July 30, 2009 at 6:49 am
Glad to hear it's fixed. I don't think you did what I was going to suggest, clean out the registry & then try the reinstall. I had to do that after a 2008 beta crashed during installation. Wiped out every instance of SQL Server on my machine.
Can't wait to see the article.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
July 30, 2009 at 9:46 am
Grant Fritchey (7/30/2009)
Glad to hear it's fixed. I don't think you did what I was going to suggest, clean out the registry & then try the reinstall. I had to do that after a 2008 beta crashed during installation. Wiped out every instance of SQL Server on my machine.Can't wait to see the article.
Heh...I even tried that along with the use of RegSvr32 /u and it still didn't work. I'm at work right now and don't have access to the URL's I'm going to post, but it would have made your reinstall a whole lot easier.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply