OCT 12 2006

Errors connecting to SQL Server on TCP 1433

Related Categories: Breeze, ColdFusion, JRun

Some people are having issues connecting to SQL Server on the default TCP port 1433. This is not an issue with Adobe products (Breeze, CF, JRun, etc.). You have to go beyond enabling TCP/IP in the Server Network Utility (2000) or Network Configuration Manager (2005). The first step is to check the SQL Server error log ($sql_root\log\ERRORLOG). It will tell you what protocols SQL Server is listening at startup, and to which IP addresses and ports:

2006-10-12 11:31:18.06 server SQL server listening on 10.7.241.212: 1433.
2006-10-12 11:31:18.06 server SQL server listening on 192.150.23.103: 1433.
2006-10-12 11:31:18.06 server SQL server listening on 127.0.0.1: 1433.
2006-10-12 11:31:19.60 server SQL server listening on TCP, Shared Memory, Named Pipes, Rpc.
2006-10-12 11:31:19.62 server SQL Server is ready for client connections
If your ERRORLOG does not list TCP and you do not see 1433, then its not listening/bound to TCP port 1433.

Now ensure that TCP port 1433 is open. In the rare case that the ERRORLOG reports SQL Server is listening to TCP, there may be something else bound to that port. Use netstat -anop TCP (Windows XP and 2003 only) to verify connectivity on TCP 1433. This will list all of the open TCP ports, their state, and the process id (PID) bound to them. Cross-reference the PID values with task manager, pslist, tasklist, etc.

netstat -anop tcp

This image shows process id 3972 LISTENING on local address 0.0.0.0:1433. Cross-referencing 3972 with task manager shows that this is sqlservr.exe.

Task manager

Search Microsoft's site for more information on why SQL Server is not listening/binding to TCP 1433.

Comments (1) | Print | Send | del.icio.us | Digg It! | Linking Blogs

Related Blog Entries

TweetBacks
There are no TweetBacks for this entry.
Comments (Comment Moderation is enabled. Your comment will not appear until approved.)

[Add Comment] [Subscribe to Comments]

Dan Parker's Gravatar Sarge,

I found your comments over on Charlie's blog. I wanted to stop by and thank you for posting your comment regarding checking the SQL Server port.

I followed Charlie's instructions and learned that the TCP/IP protocol was disabled by default, but I was still having trouble. I read your post, ran "netstat -anop TCP" and learned that sqlserver.exe was listening on port 2720. I changed the CF data source to use 2720 and was pleased to find the message "datasource updated successfully".

I'd still like to know why SQL Server 2005 installed with port 2720, but hey, beggars can't be choosers, I'm just glad it works. I owe ya a cold one if I ever meet up with you somewhere. Thanks a lot!
# Posted By Dan Parker | 7/23/07 8:27 PM
Welcome to Sarge's personal blog A green acorn

Previous Month September 2010 Next Month

Sun Mon Tue Wed Thu Fri Sat
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30    

Subscribe
Enter your email address to subscribe to this blog.