WCF客户端调用EF6时出现SQL Provider未找到异常求助

Alright, let's tackle this EF6 + WCF issue you're facing. That error message is pointing straight to the root problem, so let's break it down and fix it step by step.

What's Causing the Error? #

The core issue here is that your server's App.config is missing the Entity Framework 6 configuration section that registers the SqlClient provider. Even though direct EF calls work on the server (likely because Visual Studio handles some runtime config behind the scenes when running the project directly), WCF services rely strictly on the explicit config in App.config—and without that provider registration, EF can't find the SqlClient driver when called via WCF.

Looking at the server config you shared, it's missing both the full connection string setup and the critical <entityFramework> section that tells EF how to use SqlServer.

Step-by-Step Fixes #

1. Fix the Server's App.config #

Update your server's configuration to include the connection string and EF provider registration. Here's the complete, corrected config:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <!-- Complete connection string section (yours was truncated) -->
  <connectionStrings>
    <add name="PeddTaxDbContext" 
         connectionString="Data Source=YOUR_SQL_SERVER_NAME;Integrated Security=True;Database=PeddTax;MultipleActiveResultSets=True" 
         providerName="System.Data.SqlClient" />
  </connectionStrings>

  <!-- Add the required EF6 configuration section -->
  <entityFramework>
    <defaultConnectionFactory type="System.Data.Entity.Infrastructure.LocalDbConnectionFactory, EntityFramework">
      <parameters>
        <parameter value="mssqllocaldb" />
      </parameters>
    </defaultConnectionFactory>
    <providers>
      <!-- This line registers the SqlClient provider for EF6 -->
      <provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer" />
    </providers>
  </entityFramework>

  <!-- Your existing server config -->
  <system.web>
    <compilation debug="true" />
  </system.web>
  <system.serviceModel>
    <services>
      <service name="PeddTaxServer.Communication.UserService">
        <endpoint address="http://localhost:6060/wcf/UserService" binding="basicHttpBinding" bindingConfiguration="" name="UserServiceEndpoint" contract="PeddTax.Communication.Interfaces.IUserService" />
      </service>
    </services>
  </system.serviceModel>
</configuration>

Make sure to replace YOUR_SQL_SERVER_NAME with your actual SQL Server instance name (like localhost or .\SQLEXPRESS).

2. Verify Critical DLLs Are Present #

Double-check that your server's bin/Debug folder contains these two EF6 assemblies:

• EntityFramework.dll
• EntityFramework.SqlServer.dll

You mentioned your client and server debug folders are identical, so the client should already have these—but the server needs them to run EF operations, and the config needs to map to the SqlServer DLL.

3. Confirm Your DbContext Uses the Correct Connection String #

Ensure your EF DbContext class references the connection string name you defined in the config:

public class PeddTaxDbContext : DbContext
{
    public PeddTaxDbContext() : base("name=PeddTaxDbContext")
    {
    }

    // Your DbSet definitions here, e.g.:
    public DbSet<User> Users { get; set; }
}

Why This Works #

When you call EF directly from the server, Visual Studio might inject some runtime config for you. But when WCF hosts the service, it only reads the explicit config in App.config. Adding the <entityFramework> section tells EF exactly where to find the SqlClient provider implementation, which resolves the "No Entity Framework provider found" error.

内容的提问来源于stack exchange，提问作者Lyror