I have been successfully using SQL Server 2005 developer
edition for a couple of months now.However,
when I started Microsoft SQL Server Management Studio this morning I could not
connect to the “Database Engine” (I’m using Windows Authentication). I can still connect with the “Integration
Services” and “Analysis Services” on the same server. The server running on my local machine, so
there shouldn’t be any problems with the network.I am also able to connect with it through
ODBC, it just seems to be the Server Management Studio which can’t connect, and it only has
problems with the “Database Engine.” Any
help would be appreciated.
David
The detailed error message says:
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 -
No connection could be made because the target machine actively refused it.)
(.Net SqlClient Data Provider)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10061&LinkId=20476
Error Number: 10061
Severity: 20
State: 0
Program Location:
at
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception,
Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj)
at
System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner,
Boolean& failoverDemandDone, String host, String failoverPartner, String
protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean
encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection
owningObject, Boolean aliasLookup)
at
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection
owningObject, SqlConnectionString connectionOptions, String newPassword,
Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity
identity, SqlConnectionString connectionOptions, Object providerInfo, String
newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions
options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection
owningConnection, DbConnectionPoolGroup poolGroup)
at
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection
owningConnection)
at
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection
outerConnection, DbConnectionFactory connectionFactory)
at
System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo
ci, IServerType server)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
I'm not sure exactly which setting fixed it, however after reinstalling and adjusting some settings it now is working again.|||I had the same problem. What I did is open the SQL Server Management Studio and view registered servers. Then I right clicked on my server and went to SQL Server Configuration Manager. I then checked the protocols on my server and they were all disabled!! I reenabled them then restarted the SQL Server service. Now I am all good.|||I, too, have this problem. Unfortunately, after enabling the protocols I am still not able to connect! Does anyone have any other ideas?|||
I am having the same problem. I installed SQL Server last week and used it fine until yesterday. Yesterday, I changed the properties on my ASPNET user and tried to restart SQL. The restart failed and I was unable to ever make a connection again. I rebooted my machine a couple of times, I changed the Protocols to "Enabled", etc. yet nothing worked.
I had to uninstall SQL and then re-install it to get it working. That is until this morning. I tried to login this morning and I received the error again. Is this a daily routine now, uninstall and re-install SQL to start my day off?
Does anyone know what is causing this and even better what it takes to fix it?
Thanks,
DP
|||
This happened to me after updating common language runtime and/or installing SQL Server 2005 SP1 and/or configuring some ODBC connections. Here's how I corrected:
Navigate to Start-->Admin Tools-->Computer Mgt-->Sevices&Apps-->SQL Server Config Mgr-->SQL Server 2005 Network Config
Expand & select Protocols for MSSQL Server and verify the following settings:
Shared Memory Enabled (found Enabled)
Named Pipes Enabled (found Disabled)
TCP/IP Enabled (found Disabled)
VIA Disabled (doesn't seem to matter)
To change settings, double-click or right-click each of the above. Then use SQL Server Manager (the server PC icon in your system tray with either the green arrow or red dot) to Stop (if Started) and/or to then Start (if Stopped) the SQL Sever for the changed settings to take effect.
Has anyone else had similar experiences?