SQL not listening on TCP port

[wbodger]

I have Named Pipes, TCP/IP and multiprotocol selected, but when I check it is not listening on any TCP ports that I can find and in the error log it only mentions Shared Memory and Named Pipes on startup...

I have checked that TCP/IP is selected. I have disabled and re-enabled it, I have stopped and restarted SQL Server and the SQL Server Agent and still TCP does not show as being active. Any thoughts, something I've missed?

WB

 

[ptheriault]

Is the TCP protocol installed on the server?

Select the properties of your network adapter and check the installed protocols.

- Paul

- If at first you don't succeed, find out if the loser gets anything.

 

[wbodger]

Yup, TCP/IP is enabled and running properly on the server, just not for SQL Server 2000 Enterprise Edition, sp4.

WB

 

[ptheriault]

from a cmd prompt run "netstat -an" Is anything using TCP?

- Paul

- If at first you don't succeed, find out if the loser gets anything.

 

[wbodger]

Yes, there are many items in that list with states of Listening, Established and Time_Wait all using TCP (plus a few using UDP).

WB

 

[ptheriault]

check to see if the value for TcpPort in the following registry key is incorrectly set to blank or empty:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\ [Instance Name]\MSSQLServer\SuperSocketNetLib\Tcp\REG_SZ TcpPort=

- Paul

- If at first you don't succeed, find out if the loser gets anything.

 

[ptheriault]

By the way, what version of SQL is this?

- Paul

- If at first you don't succeed, find out if the loser gets anything.

 

[wbodger]

That key is set to 1433. Hmm....

 

[ptheriault]

That is correct.

- Paul

- If at first you don't succeed, find out if the loser gets anything.

 

[wbodger]

2000 Ent Ed, sp4

 

[ptheriault]

Check out the bug.

http://support.microsoft.com/kb/306865

Or this link may help too.

http://support.microsoft.com/kb/328306

- Paul

- If at first you don't succeed, find out if the loser gets anything.

 

[wbodger]

Neither of those really address the issue. TCP/IP is not the only protocol enabled and port 1433 is not in use by any other process or application that I can find. When I ran netstat -an there was nothing using port 1433, but when I restarted SQL Server it appears that it could not bind to port 1433 (or it didn't try).

WB

 

[wbodger]

Also, this is an MSDN version of SQL Server as it is not production and I am trying to learn some things. It is SQL 2000 Ent Ed and I have installed sp4, but it still reports itself as RTM. Might this be an issue?

WB

 

[ptheriault]

Yes I would think that is an issue. Re-install SP4.

- Paul

- If at first you don't succeed, find out if the loser gets anything.

 

[wbodger]

I just re-installed SP4 (before I posted) and it is still reporting the same:

8.00.194 RTM Enterprise Edition

as opposed to my production server:

8.00.2039 SP4 Enterprise Edition

and when I ran it on my dev server it ran very quickly. Is there some code on the MSDN version that prevents it from updating?

WB

 

[ptheriault]

How long have you had this version installed. Is your trial time up?

- Paul

- If at first you don't succeed, find out if the loser gets anything.

 

[wbodger]

I wasn't aware of a trial time on the MSDN versions of SQL Server. It's not a 120 day trial of SQL 2000, it is a 10 install version of SQL Server not to be used on production servers as far as I understood it. Though if I have missed it, it wouldn't be a real big stretch. I installed this about 3 months ago.

WB

 

[wbodger]

And the 3rd time is the charm and now tcp shows up...