April 9, 2009 at 10:20 am
Hi -
I am having issues connecting to SQL Server 2005. The error I get is pasted below. The connection was working just fine until April 1st . I have a feeling that the server admin changed something to deal with the April 1st work. Now we are having trouble getting to connect . I am using SQL Server Management Studio 2008 to connect. The Named pipes in client protocols under server configuration is disabled and TCP/IP is enabled and is order 2 . Shared memory is order 1.
Any advise?
Thanks!
Saleha
TITLE: Connect to Server
------------------------------
Cannot connect to ****
------------------------------
ADDITIONAL INFORMATION:
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: TCP Provider, error: 0 - No such host is known.) (Microsoft SQL Server, Error: 11001)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=11001&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
April 11, 2009 at 4:35 pm
Please check ..
1) Firewall (Any changes that would start blocking port 1433)?
2) Remote access still enabled on TCP/IP.
3) MSSQL Server is running.
Any patching?
Mohit.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
April 12, 2009 at 12:24 am
Just to add Mohit's comment also Check SQL Server Browser service has been started.
~ IM
April 12, 2009 at 5:38 am
has the TCP/IP port number been changed under TCP/IP settings?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 12, 2009 at 8:02 am
1.) Verify that SQL Server service is running
2.) Verify the instance name
3.) Verify the log in
4.) Go to Surface Area Configuration manager and Enable Remote Connections
5.) Verify whether TCP/IP communication protocol is enabled
6.) Verify what port is assigned ( by default 1433)
7.) Check whether it is blocked by any Firewall settings
April 13, 2009 at 6:34 am
You can also check if the admin has reset the password or the password has expired for that instance through which you access SQL server.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply