OCT
12
2006
Troubleshooting SQL Server connection
Related Categories: Breeze, ColdFusion, JRun
Here's a checklist for checking connectivity to SQL Server. Replace 1433 in the following steps with the TCP port bound by your SQL Server:
- Verify SQL Server configuration:
- Ensure SQL Server has started. Sounds simple but this is often overlooked.
- Ensure the TCP protocol is installed on the SQL Server and verify TCP/IP connectivity to it remotely.
- Ensure firewalls and proxies allow connections on port 1433.
- Ensure TCP protocol is enabled for SQL Server and verify the listening port(s).
- Verify the SQL Server instance name(s).
- Check the SQL Server ERRORLOG to verify the protocols, addresses, and ports to which SQL Server is listening:
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. - Ensure installed Service Packs do not break connectivity:
- Use networking tools to verify the SQL Server process has an established connection on the addresses and/or ports listed in the SQL Server ERRORLOG:
C:\>netstat -anop tcp | find "1433"If TCP port 1433 is bound by another process, try:
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING 3972- Stopping any processes bound to port 1433 and restarting SQL Server.
- Adding another or changing SQL Server's listening port.
- Verify the data source configuration:
- Verify the SQL Server ip address and port
- Verify the username and address
- If using JDBC drivers, verify the JDBC URL -- see your vendor's documentation.
- If using named instances, ensure you configure the DSN to point to the unique port for each instance. See Technote tn_18294 for more details.
TweetBacks
There are no TweetBacks for this entry.



There are no comments for this entry.
[Add Comment] [Subscribe to Comments]