Skip to main content

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: 
System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information.
    at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName)

This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

  • TeamCity
  • .NET 4.51
  • EF 6.0.2
  • VS2013

It seems that there is an assembly reference that is not copied to the output. If we are looking closes in the error code we notify that ‘EntityFramework.SqlServer’ is missing.
First step: Check the Unit Test project and rest of the projects to see if that assembly is there – YES
Second step: Check the ‘Copy Local’ attribute of the reference to be true – YES
Third step: Check the configuration file of unit test project to specify the SQL provider – YES
<entityFramework>
<providers>
    <provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer" />
</providers>
</entityFramework>
Forth step: Copy the source code directly from CI machine to local machine and use them to run the tests – YES (all tests are green)
Fifth step: Force that specific assembly to be loaded from code. We need to use a class from EntityFramewok.SqlServer
Type providerService = typeof(System.Data.Entity.SqlServer.SqlProviderServices);

And YES, the build is green, all tests are running. It seems that the reference was not copied in the output folder where unit tests are run.

It seems that this is a known problem for EF 6 without an official solution. I hope that in the next release of EF this problem will be solved.

Comments

  1. I was facing the same issue with Team City, I had to follow the fifth step.
    thanks

    ReplyDelete
  2. In my-case, adding system.data.entity solved the issue.
    thanks for the explanation!.

    ReplyDelete
  3. Only the Fifth step worked for me. Excellent post man! Thank you so much!

    ReplyDelete
  4. Thank you very very very much!!! Fifth step worked!

    ReplyDelete
  5. Thank you - the fifth step was the key - with a simple modification:
    It worked in Debug mode but not in Release. I suspect compiler optimizations to remove the unused variable assignment. To make it work even in Release mode, I've added a function call.
    So, my solution was to add the following line anywhere in the test project:

    var bugFix = typeof(System.Data.Entity.SqlServer.SqlProviderServices).ToString();

    ReplyDelete

Post a Comment

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…