Cannot Start SQL Server using TCP/IP

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

SQL Server Administration (2000)

Cannot Start SQL Server using TCP/IP

Author

Topic

colm
Starting Member

5 Posts

Posted - 2004-03-26 : 06:36:24

Hi,

I found a similar thread on this forum, but did not see a resolution to the problem I am encountering.

I've just installed SQL Server 2000, and SQL Server 2000 SP3 on a windows 2003 server. I did a default instance install, with the system account for the Startup service account, and mixed mode authentication.

I've enabled TCP/IP in SQL Server network utility, and the port number is 1433.

But when I start it, it is ignoring TCP/IP completely (see the ErrorLog below).

When I try to connect to it (telnet 127.0.0.1 1433) I am getting

Could not open connection to the host, on port 1433: Connect failed

Running 'netstat -an' shows no SQL Server processes running, or the port number 1433 in use.

I feel I'm at an impasse, because I have enabled TCP/IP, but it is ignoring it complelely.

Thanks for any pointers on this,

Colm.

-----------------------------ErrorLog--------------------------------

2004-03-26 18:07:50.26 server Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )

2004-03-26 18:07:50.26 server Copyright (C) 1988-2000 Microsoft Corporation.
2004-03-26 18:07:50.26 server All rights reserved.
2004-03-26 18:07:50.26 server Server Process ID is 3904.
2004-03-26 18:07:50.26 server Logging SQL Server messages in file 'd:\MSSQL\MSSQL\log\ERRORLOG'.
2004-03-26 18:07:50.28 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2004-03-26 18:07:50.29 server SQL Server configured for thread mode processing.
2004-03-26 18:07:50.29 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2004-03-26 18:07:50.32 server Attempting to initialize Distributed Transaction Coordinator.
2004-03-26 18:07:52.35 spid4 Starting up database 'master'.
2004-03-26 18:07:52.45 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-03-26 18:07:52.45 spid5 Starting up database 'model'.
2004-03-26 18:07:52.46 spid4 Server name is 'DDD'.
2004-03-26 18:07:52.48 spid8 Starting up database 'msdb'.
2004-03-26 18:07:52.48 spid9 Starting up database 'pubs'.
2004-03-26 18:07:52.48 spid10 Starting up database 'Northwind'.
2004-03-26 18:07:52.59 server SQL server listening on Shared Memory, Named Pipes.
2004-03-26 18:07:52.59 server SQL Server is ready for client connections
2004-03-26 18:07:52.73 spid5 Clearing tempdb database.
2004-03-26 18:07:53.21 spid5 Starting up database 'tempdb'.
2004-03-26 18:07:53.28 spid4 Recovery complete.

saglamtimur
Yak Posting Veteran

91 Posts

Posted - 2004-03-26 : 07:13:38

which version of windows 2003 are you using? web/standart/ent. ?

colm
Starting Member

5 Posts

Posted - 2004-03-26 : 19:52:25

quote:
Originally posted by saglamtimur

which version of windows 2003 are you using? web/standart/ent. ?

Windows 2003 Standard Edition.

How does that affect the problem ?

--Colm

Lizard
Starting Member

2 Posts

Posted - 2004-03-27 : 03:22:29

quote:
Originally posted by colm

Hi,

I've enabled TCP/IP in SQL Server network utility, and the port number is 1433.

I thought Windows 2k used port 1434 for TCP/IP. No doubt someone who actually knows what they're talking about will be along shortly.

saglamtimur
Yak Posting Veteran

91 Posts

Posted - 2004-03-27 : 05:03:56

For example sql server does not run on 2003 web edition. I am using 2003 standart + sql server on the same pc and i see ms-sql-m using tcp 1433 and udp 1434. (Try this ustility its free; ActivePorts http://www.protect-me.com/freeware.html)

Are you running any IP Sec rules that might block port access - even locally?

colm
Starting Member

5 Posts

Posted - 2004-03-27 : 23:34:43

quote:
Originally posted by saglamtimur

Are you running any IP Sec rules that might block port access - even locally?

Ok, showing my lack of networking experienc here, but how would I determine what IP Sec rules are running that might be doing this ?

Thanks,
Colm.

colm
Starting Member

5 Posts

Posted - 2004-03-28 : 23:55:24

quote:
Originally posted by saglamtimur

For example sql server does not run on 2003 web edition. I am using 2003 standart + sql server on the same pc and i see ms-sql-m using tcp 1433 and udp 1434. (Try this ustility its free; ActivePorts http://www.protect-me.com/freeware.html)

I installed ActivePorts, but I do not see ms-sql-m. The only sql server related process I see is sqlmangr.exe.

This process is stopping and starting with each refresh of ActivePorts; after a refresh, I will see a green entry for sqlmangr.exe, then it will turn red a few seconds later, and disappear from the list. On the next refresh, sqlmangr.exe will be there on the list in green, shown to be listening on a different port.

Is this normal behavior for sqlmangr.exe ?

Thanks for any help on this,

Colm.

saglamtimur
Yak Posting Veteran

91 Posts

Posted - 2004-03-29 : 04:41:12

"Is this normal behavior for sqlmangr.exe ?"

No, it seems to be unnormal. I see sqlservr.exe listening tcp 1433, and udp 1434.

For IP Security policies on Windows Server 2003 please reffer to below articles. With default settings it permits all traffic.

http://www.windowsecurity.com/articles/Windows_Server_2003_IPSec_Part1.html

(Above article describes how to monitor IPsec using an MMC console, but I recommend to use Ip Security Policy Managemnt snap-in aswell to change any policy)

http://www.windowsecurity.com/articles/Windows_Server_2003_IPSec_Part2.html

I hope this helps.

colm
Starting Member

5 Posts

Posted - 2004-03-31 : 06:36:15

quote:
Originally posted by saglamtimur

For IP Security policies on Windows Server 2003 please reffer to below articles. With default settings it permits all traffic.

I hope this helps.

Thanks for the articles; I investigate the IP Security Monitor on the 2003 server, and there were no Active policies, and no generic or specific filters in Main mode or Quick mode.

netsh ipsec shows three policies defined, Server (Request Security), Client (Respond Only), Secure Server (Require Security). I don't think they apply to this case, I didn't see anything that was obviously connected.

I tried stopping IPsec service, stopping and restarting SQL Server, and the errorlog showed it starting up not listening on TCP/IP. I saw something different in ActivePorts this time, there was a sqlserver.exe process on ports 4356, 4355, 4354 with connection state is ESTABLISHED, using TCP.

I restarted IPsec, stopped and started SQL Server, and this time ActivePorts shows a sqlserver.exe process in the same state, but with different ports (4558, 4559, 4560).

I'm still trying to figure it out and appreciate any suggestions. Does the kind of IPsec set-up I described above have a serious bearing on how SQL Server starts up ?

Thanks,
Colm.

btolly
Starting Member

1 Post

Posted - 2004-08-23 : 22:59:56

A little late, but maybe it will help someone else - I had this problem - it occurred to me to update SQL with service packs, as mine had none - updated to sp3a - this fixed the problem.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources