Can't connect to localhost on SQL Server Expre

Question

I just downloaded the latest version of SQL Express 2012 but I cannot connect to localhost. I tried localhost\SQLExpress and Windows authentication but it gives me an error message saying cannot connect. Am I missing something here? I've used SQL Server 2008 before and I've never had issues connecting to localhost. It seems that it can't even find it. Also in the Services I only see a SQL Server VSS Writer. Is this the way it should be? Or am I missing something? Thanks

Answer 1

First try the most popular solution provided by Ravindra Bagale.

If your connection from localhost to the database still fails with error similar to the following:

Can't connect to SQL Server DB. Error: The TCP/IP connection to the host [IP address], port 1433 has failed. Error: "Connection refused: connect. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall."

1. Open the SQL Server Configuration Manager.
2. Expand SQL Server Network Configuration for the server instance in question.
3. Double-click "TCP/IP".
4. Under the "Protocol" section, set "Enabled" to "Yes".
5. Under the "IP Addresses" section, set the TCP port under "IP All" (which is 1433 by default).

6. Under the "IP Addresses" section, find subsections with IP address 127.0.0.1 (for IPv4) and ::1 (for IPv6) and set both "Enabled" and "Active" to "Yes", and TCP port to 1433.

   

7. Go to Start > Control Panel > Administrative Tools > Services, and restart the SQL Server service (SQLEXPRESS).

Answer 2

I had a similar problem - maybe my solution will help. I just installed MSSQL EX 2012 (default install) and tried to connect with VS2012 EX. No joy. I then looked at the services, confirmed that SQL Server (SQLEXPRESS) was, indeed running.

However, I saw another interesting service called SQL Server Browser that was disabled. I enabled it, fired it and was then able to retrieve the server name in a new connection in VS2012 EX and connect.

Odd that they would disable a service required for VS to connect.

Answer 3

The problem for me was that I was not specifying .\. I was only specifying the name of the instance:

• did not work: SQL2016
• worked: .\SQL2016

Answer 4

According to Aaron Bertand:

1. You need to verify that the SQL Server service is running. You can do this by going to Start > Control Panel > Administrative Tools > Services, and checking that the service SQL Server (SQLEXPRESS) is running. If not, start it.

2. While you're in the services applet, also make sure that the service SQL Browser is started. If not, start it.

3. You need to make sure that SQL Server is allowed to use TCP/IP or named pipes. You can turn these on by opening the SQL Server Configuration Manager in Start > Programs > Microsoft SQL Server 2012 > Configuration Tools (or SQL Server Configuration Manager), and make sure that TCP/IP and Named Pipes are enabled.

   

4. Verify your SQL Server connection authentication mode matches your connection string:

   • If you're connecting using a username and password, you need to configure SQL Server to accept "SQL Server Authentication Mode":

     -- YOU MUST RESTART YOUR SQL SERVER AFTER RUNNING THIS!
     USE [master]
     GO
     DECLARE @SqlServerAndWindowsAuthenticationMode INT = 2;
     EXEC xp_instance_regwrite
       N'HKEY_LOCAL_MACHINE',
       N'Software\Microsoft\MSSQLServer\MSSQLServer',
       N'LoginMode',
       REG_DWORD,
       @SqlServerAndWindowsAuthenticationMode;
     GO
     

   • If you're connecting using "Integrated Security=true" (Windows Mode), and this error only comes up when debugging in web applications, then you need to add the ApplicationPoolIdentity as a SQL Server login:

5. otherwise, run Start -> Run -> Services.msc If so, is it running?

If it's not running then

It sounds like you didn't get everything installed. Launch the install file and chose the option "New installation or add features to an existing installation". From there you should be able to make sure the database engine service gets installed.

Answer 5

Try changing from windows authentication to mixed mode

Answer 6

All my services were running as expected, and I still couldn't connect.

I had to update the TCP/IP properties section in the SQL Server Configuration Manager for my SQL Server Express protocols, and set the IPALL port to 1433 in order to connect to the server as expected.