Could not connect to SQL Server localdb instance

Question

I have installed SQL Server 2014 localdb and SQL Server Management Studio. I am trying to connect to the localdb using a WPF application developed in Visual Studio.

Here is the connection string that I am using

<connectionStrings>
    <add name="ReservationContextString" 
         connectionString="Data Source=(localdb)\\MSSQLLocalDB;Initial Catalog=ReservationDB;AttachDbFilename=|DataDirectory|\\ReservationDB.mdf" 
         providerName="System.Data.SqlClient" />
</connectionStrings>

When I run the application I get the following exception

An exception of type 'System.Data.SqlClient.SqlException' occurred in EntityFramework.dll but was not handled in user code

Additional information: 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

I am not sure why the application could not connect to localdb

Note: I am able to use the SQL Server Management Studio to connect to localdb using (localdb)\MSSQLLocalDB as Server Name. So, localdb seems to be installed properly.

I think the problem is that you're **(1)** defining a database to connect to (`Initial Catalog=ReservationDB`) in your LocalDB instance, as well as **(2)** defining a `.mdf` file to attach (`AttachDbFilename=|DataDirectory|\\ReservationDB.mdf`) - you can do **either** of the two, but I'm not sure what happens if you do **both** things at once. Try one **OR** the other - does that work? — marc_s, Mar 30 '15 at 10:06
@marc_s In SQL Server Configuration Manager, no Service is listed under the SQL Server Services node. But, I believe that the localdb instance is not listed there. Not sure that's why letting you know. — Jatin, Mar 30 '15 at 10:45
**For Code Migrations** (`update-database` et al) [see this answer](https://stackoverflow.com/a/31266905/3258851). — Marc.2377, Jul 31 '18 at 21:15

score 1 · Answer 1 · answered Mar 31 '15 at 01:07

Taking inspiration from this troubleshooting guide I was able to resolve the issue. The Entity Framework's defaultConnectionFactory should point to a localdb instance, but in app.config (or web.config), I had it set pointing to SQL Server Instance. It had to be changed to use localdb instance instead.

Old Entry

  <entityFramework>
      <defaultConnectionFactory type="System.Data.Entity.Infrastructure.SqlConnectionFactory, EntityFramework" />
      </defaultConnectionFactory>      
      ....
  </entityFramework>

should be (new code)

  <entityFramework>
    <defaultConnectionFactory type="System.Data.Entity.Infrastructure.LocalDbConnectionFactory, EntityFramework">
        <parameters>
          <parameter value="MSSQLLocalDB" />
        </parameters>
      </defaultConnectionFactory>      
      ..      
  </entityFramework>

Notice the System.Data.Entity.Infrastructure.LocalDbConnectionFactory, instead of System.Data.Entity.Infrastructure.SqlConnectionFactory

score 0 · Answer 2 · edited Jun 20 '20 at 09:12

0

In my case, I had to create the DB first from inside VS

Then everything worked like a charm

edited Jun 20 '20 at 09:12

Community

1
1

answered Sep 18 '16 at 13:20

Korayem

12,108
5
69
56

Could not connect to SQL Server localdb instance

2 Answers2