March 11, 2008 at 4:46 am
I've just ugraded from sql 2000 to sql 2005 in my local machine using in-place of type of upgrade, now when accessing the server using Microsoft SQL Server Management Studio it failes with error massege :An error has occured while estableshing a connection to the server.When connecting to SQL Server 2005 ,this failure may be caused by the fact that under default settings SQL Server does not allow remote connections,(provider: TCP Provider, error: 0- No Connection couls be made because the target machine actively refused it.)(Microsoft SQL Server,Error: 10061)
Regard
Soks
March 11, 2008 at 8:00 am
You need to open SQL Server 2005 Surface Area Configuration and set it up to allow remote access. you can reach the SQL Server 2005 Surface Area Configurations by using Start ----> Programs---->Microsoft SQL Server 2005 -------> Configurations Tools ----->SQL Server Surface Area Configurations. Once opened, ensure it is pointing to local host since the DB is on your local machine, if you were trying to do so on a network database, then simply change from local host to the server name/instance fo the database server you are trying to control.
More information on this feature can be found in BOL
Hope this helps
MD
Marvin Dillard
Senior Consultant
Claraview Inc
March 11, 2008 at 8:40 am
Is the SQL Server service even running?
March 12, 2008 at 12:06 pm
Check Remote Connections thru SQL Server 2005 Surface Area Configuration and make sure Local and Remote Connections is checked.
[font="Verdana"]--www.sqlvillage.com[/size][/font]
March 14, 2008 at 8:39 am
Is the SQL Service running?
Gethyn Elliswww.gethynellis.com
March 16, 2008 at 11:19 am
Check the SQL Server Browser service is running too.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
March 17, 2008 at 1:19 am
Hi
In SQL Server configuration Manager\Network protocols
check whether Shared Memory protocol is enabled. This is enabled by default.
"Keep Trying"
March 17, 2008 at 2:15 am
Hi,
The best way to reach the right path is..just use SAC utility and enable the remote/local client check box and try to connect again.
Thankx
Nitin Gupta
March 17, 2008 at 8:09 am
When you connect, for "server name" try using the actual machine name, not "(local)" does that help?
March 17, 2008 at 8:55 am
And check the current error log. Be sure the services are running and then look for what port/name SQL is listening on.
August 24, 2008 at 2:47 am
hello am having the same problem.
i checked every thing u have said, and i couldnt make it happen.
note: my sql server is lsitenning on port 1437, should i pay attention for any thing else.?
..>>..
MobashA
August 25, 2008 at 5:49 am
Try connecting using server's IP address. If that works and server names does not, then you may need to set up a LMHost file relating IP addresses to server names. That is what I had to do to resolve not connecting using server names after all was fine, then suddenly no go.
March 5, 2009 at 12:25 pm
If the above solutions don't work - check whether you are logging on as a Local System Account under -> Control Panel -> Administrative Services -> SQL Server (MSSQLSERVER). If you are, try and change to This Account and input your logon and password details manually.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply