When i trying to use my ID im getting the below error msg.
How can i resolve this.
Cannot connect to DSQLM13DATACEN01.
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) (.Net SqlClient Data Provider)
------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
------------------------------ Error Number: 53 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(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) 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.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server) at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
asked Aug 23 '11 at 12:45 PM in Default
Does this SQL instance allow connections from any other users? Is this a new configuration? You may need to enable SQL Server in the firewall. You also need to enable TCP/IP in SQL Server Configuration Manager and allow Remote connections. If using SQL Server 2005 do this in SQL Server Surface Configuration.
answered Aug 23 '11 at 12:49 PM
This blog post has a few things you can work through to see if it might resolve your issue.
Telnet is a good tool to use on testing whether the ports are opened on your server/network for SQL Server connections.
You can check the SQL Server ERRORLOG from the last startup of the services and it should contain the configuration regarding what ports/protocols your instance is listening on. Also, Andy Leondard was kind enough to provide a [quick database connectivity testing] tip.: http://sqlblog.com/blogs/andy_leonard/archive/2011/08/26/quick-database-connectivity-testing.aspx
answered Aug 29 '11 at 11:42 AM
After a quick glance it appears your Client is attempting to connect by Named Pipes... is that protocol enabled on SQL Server?The Client and the Server need a common protocol to communicate over. If the Client is configured to only use Named Pipes and the Server to only use TCP/IP then the two won't be able to talk. Ensure that both have one protocol enabled that the other does as well.
answered Aug 29 '11 at 12:29 PM