unable to connect to localhost and now I realized Sql Server Configuration Manager (SQL Server 2016)

  • My laptop came with SQL Server 2016 and for past 2 months I was able to develop within localhost just fine.  Now, during a 2 week pause (away from SQL Server) I have returned to it, installed recommended updates, and now find I can't connect to localhost ...

    Discovered Aaron Bertrand's advise for connecting to SQL Server Configuration Manager at this link http://stackoverflow.com/questions/12774827/cant-connect-to-localhost-on-sql-server-express-2012-2016   but I can't connect to Config Manager either.

    I perceive that if I can connect to Config Manager then I will be able to activate localhost and be back to work. 

    Will someone please walk me through to connecting Config Manager and ultimately being able to work within localhost again?

    --Quote me

  • You probably want to check Services and make sure it's running. Do you know what edition of SQL Server was installed? Were you using LocalDB from SSDT? Try to view the entire error message or check the windows log for the errors. It will be much easier to figure out the issue you can find the error message.

    Sue

  • Sue_H - Monday, April 24, 2017 10:06 AM

    You probably want to check Services and make sure it's running. Do you know what edition of SQL Server was installed? Were you using LocalDB from SSDT? Try to view the entire error message or check the windows log for the errors. It will be much easier to figure out the issue you can find the error message.

    Sue

    Here's what I get when I check services.  

    Without being able to run Select @@Version I can't tell you what edition, but it is likely Developer.  
    Regarding question if I was using LocalDB from SSDT, I am puzzled.  SSDT is SQL Server Data Tools, which I only use when building SSRS, SSIS pkgs.  So, I think the answer is no.    

    Below is error I am getting. 

    ===================================

    Cannot connect to ..
    ===================================
    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)
    ------------------------------
    Error Number: 2
    Severity: 20
    State: 0
    ------------------------------
    Program Location:
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
       at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
       at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
       at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
       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()
    ===================================
    The system cannot find the file specified

    --Quote me

  • Well, the service is not running.  Right click on it in Services, and pick Start.

    Michael L John
    If you assassinate a DBA, would you pull a trigger?
    To properly post on a forum:
    http://www.sqlservercentral.com/articles/61537/

  • thanks for getting me localhost operational Sue and Michael.

    --Quote me

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply