Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
chedderslam
Posting Yak Master
223 Posts |
 Posted - 2008-01-29 : 12:28:47
|
| I have just recently installed MS SQL Server 2005 Developer edition. I have installed SP2.Today when I try to connect via Management Studio, I get the following error:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (.Net SqlClient Data Provider)I installed it as a default instance.I recently added a login with dbo privileges. I have tried logging in with that sql account and also with windows authentication to no avail.Thank you for any help. |
|
|
chedderslam
Posting Yak Master
223 Posts |
Posted - 2008-01-29 : 15:59:42
|
| I have tried uninstalling and reinstalling SQL server and still can't get in. I tried applying SP2 and tried both windows authentication and the sa account. |
 |
|
|
tprupsis
Yak Posting Veteran
88 Posts |
Posted - 2008-01-29 : 16:42:35
|
| Did you install locally or on a server? I have no idea why you would get this on a local installation of the database. But if you installed on a server and are trying to access using SSMS from a remote PC, logon to the server and open up SQL Server Configuration Manager. Check that the services are running. Then look under the network configuration for your instance. Check that TCP/IP and Named Pipes are enabled.Tom RupsisGranite Peak SystemsPhone: 406-672-8292Email: trupsis@granitepeaksys.comLinkedIn: www.linkedin.com/in/trupsis |
|
|
|
|
|
|
Cannot connect to local instance