Hi,
I reinstalled Windows XP Pro because I had to. I would like not to have to
do it again.
Before reinstalling SQL Server 2005, I installed EasyPHP 5.3. This software
wouldn't install before because the port 80 (I think) was occupied by SQL
Server.
After, I tried to install SQL Server, but it does not install because of
this port beeing busy. So, I uninstalled EasyPHP, but the problem persists.
SQL Server will not install.
What can I do? How can I free that port (or which ever SQL server needs to
install)?
I use Windows XP Pro and SQL Server 2005 (with VS 2005 Pro).
Thanks
--
Jac Tremblay

Jac Tremblay (jac.tremblay (AT) donotspam (DOT) com) writes:
Who would?

SQL Server only listens on port 80, if you create HTTP endpoints.

So what happens when you try to install?

Which edition of SQL Server are you trying to install?

What components of SQL Server do you try to install?

You find error logs for the install in
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Log

Not that they are eaily understood, but it's at least a start.


--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Hi Erland,
I use Windows XP Pro and SQL Server 2005 (with VS 2005 Pro).
The log file is quite long. I extracted those lines:
--------------------------------------------------------------------------------
Product : Microsoft SQL Server 2005 Backward compatibility
Product : MSXML 6 Service Pack 2 (KB954459)
Product Version : 6.20.1099.0
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0004_SOFICA-JAC_MSXML6_1.log
Error Number : 1603
--------------------------------------------------------------------------------
I checked this log (59k) as well and fund these lines:
*****
Client-side and UI is none or basic: Running entire install on the server.
....
MSI (s) (14:38) [08:32:37:406]: Note: 1: 1729
MSI (s) (14:38) [08:32:37:406]: Product: MSXML 6 Service Pack 2 (KB954459)
-- Configuration failed.
MSI (s) (14:38) [08:32:37:406]: Cleaning up uninstalled install packages, if
any exist
MSI (s) (14:38) [08:32:37:406]: MainEngineThread is returning 1603
MSI (s) (14:64) [08:32:37:406]: Destroying RemoteAPI object.
MSI (s) (14:AC) [08:32:37:406]: Custom Action Manager thread ending.
=== Logging stopped: 2009-12-23 08:32:37 ===
MSI (c) (48:98) [08:32:37:406]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown
will be denied. Counter after decrement: -1
MSI (c) (48:98) [08:32:37:421]: MainEngineThread is returning 1603
=== Verbose logging stopped: 2009-12-23 08:32:37 ===
*****
All I understand from this text is that "MSXML 6.1" won't install and so
won't the rest: Native client, and all the necessary product to run the SQL
Server database tools (I have to run the install again to have the complete
list, and this takes 2 hours). I do not know why and need some help.
Part of my original question was: "How can one free the port 80? Where do I
look for its status?
Thanks for your time.
--
Jac Tremblay


"Erland Sommarskog" wrote:

Jac Tremblay (jac.tremblay (AT) donotspam (DOT) com) writes:
But which edition of SQL Server do you try to install?

The KB article referred is said to be published in November 2008, so
it does not come with the original SQL Server setup. This would indicate
that already have this version on your machine.

Then again, if grabbed a download copy of SQL Server Express, possibly
this has this fix built-in.

The KB article does say that there are known issue with this fix and
installing SQL 2008, but there is nothing about SQL 2005. But I also
recall having seen people having problems with installing SQL 2005 and
MSXML. Maybe XP SP3 was part of the plot as well. (Excuse me for being
vague, but I'm really working from fragmentary memory, offering the
small piece of information that I have.)

There is no denial that these Setup problems are very difficult. The
logs are, as you have noted, grossly verbose, and it is not very easy
to understand what is wrong.

If you have this security fix installed on your machine, I would try
to uninstall it. If you don't have it installed, and you are trying to
install Express. Hm, maybe you should try to apply it separately? Or
should try to find an older version of Express?

What I tried to say in my original answer is that looking at port 80
is not likely to resolve the issue. That'a a blind alley.

--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Hi again Erland,
What do you mean by this?
***
If you have this security fix installed on your machine, I would try
to uninstall it.
***
What security fix do you talk about?
I'm not sure Port 80 is a blind alley. I wil investigate further.
I downloaded SQL Server Express and tried to install it. I Got the same
problem. MSXML SP2 installation fails. Maybe the SP2 install fails because
the program (MSXML6.1) is not installed in the first place?
After the installation, a screen appears that points to the log file and the
Surface Area Configuration Tool. That last link does not work and the tool
does not exist. There are no SQL Server sortcuts in the Windows Start Menu at
all.
What is the problem?
Thanks again.
--
Jac Tremblay


"Erland Sommarskog" wrote:

Jac Tremblay (jac.tremblay (AT) donotspam (DOT) com) writes:
http://support.microsoft.com/default.aspx?scid=954459, this is the KB
article referred to in the log file.

So before you did not try to install SQL Express?

If memory serves, SQL 2005 installs MSXML6. But the RTM version of
SQL 2005 does definitely not install this security fix, because the
fix is far too new for that.

But it could be the other way round. I found this:
http://support.microsoft.com/kb/968749

If the KB Article does not apply, could you please post the full log
file?

Also, which service-pack level of XP do you have? SP2 or SP3?

--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Hi again Erland,
That did it. The second link is the right one for me. The problem
description and error code number (1603) are exactly the ones I had. I
followed the instructions and the reinstallation went fine afterwards.
Thank you very much. You make my day.
Happy new year.
--
Jac Tremblay


"Erland Sommarskog" wrote:

Jac Tremblay (jac.tremblay (AT) donotspam (DOT) com) writes:
Glad to hear that it worked out! It was proabably a bit of luck, because
1603 is a very generic message:

C:\>net helpmsg 1603

Fatal error during installation.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx