Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

every time i try to install sql server 2005 on windows 7 it tells me error during installation error 1603 installing Microsoft sql server setup support file see log file file for more detailed information fatal error during the installation and setup terminates please advise me to fix this problem

share|improve this question

migrated from stackoverflow.com Sep 29 '09 at 20:37

This question came from our site for professional and enthusiast programmers.

    
Why not just use SQL Server 2008? –  John Saunders Sep 28 '09 at 20:46
    
try this question here: serverfault.com they deal more with this type of question than here on stackoverflow –  KM Sep 28 '09 at 20:58
    
What's in the error log? –  CodeByMoonlight Sep 29 '09 at 22:30
1  
I got this version to install just fine on two 64bit boxes. After the install you have to run sp3 and the successive CU in order to use it. It will correct the problems about user privilege, user provisioning tool, if I remember correctly –  RateControl Dec 9 '09 at 21:31

3 Answers 3

There was an issue where, if you already had .NET 2.0 SP1 installed, the 2005 installer would break.

Wow ... This is a dead question. Oh, well.

share|improve this answer

The installer for SQL2005 and for SQL 2008 both warn that there are compatibility issues with the software on windows 7. I have SQL 2008 installed (64-bit) on a windows 7 box and it runs fine for me.

share|improve this answer

If you can either look at or include the output from the setup logs it would help - summary log should be location in the following location (default location, if you chose to install elsewhere it would be located there instead):

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

There will be a single txt file called "summary.txt" that you will want to inspect/include here first (likely the error exception will be close to the bottom). That will likely point to a problem in a sub-component installation that will have a log file located in the "files" subdirectory below the path above. Anything you can include would help us help you...

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.