Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

MSSQLFUN

I, Rohit Garg, am working as Consultant in IT Company. I am having an around 5 years of experience in MSSQL server & other Microsoft technologies. I am working as DBA in Microsoft SQL Server from last 5 years in e-Commerce, Telecom, Finance domain. In this tenure, I got a chance of working as Database administrator, Developer and trainer on SQL server 2000 to SQL Server 2012. I am holding Master’s degree in Computer Science along with certification in SQL Server & .Net. I like to learn new things by hand-on experience on regular basis. This journey is so far is delightful & valuable with the addition of wonderful friends.

Check List for SQL Server Connectivity Issue !

SQL Server connectivity is the most common issue & below mention errors is also common at time of connectivity issue.

Error :

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

Resolution : Although, There are many reasons of SQL server connectivity issue. But I have setup an small checklist that helps me most of the time to find out the real cause of connectivity issue.

1. Check SQL services are running

2. Check SQL Browser service is running

3. Check remote connections are enabled

4. Network connectivity between database & application servers by TRACERT command

5. Check TCP/IP protocol enabled at SQL server

6. Check talent connectivity – telnet <IP address> <port no on SQL server running>

7. Check UDP port 1434 is open or not on SQL Server

8. Check firewall is running or not Check

9. If firewall running, SQL Server & UDP port must be added in exception in firewall


Comments

Leave a comment on the original post [mssqlfun.com, opens in a new window]

Loading comments...