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
  6. Solves my issue at step 1! Thanks for the explanation.

    ReplyDelete
  7. https://stackoverflow.com/a/47410082/774494

    I had encountered exactly the same problem on my CI build server (running Bamboo), which doesn't install any Visual Studio IDE on it.

    Without making any code changing for the build/test process (which I don't think is good solution), the best way is to copy the EntityFramework.SqlServer.dll and paste it to C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE. (where your mstest running)

    Problem solved!

    ReplyDelete

Post a Comment

Popular posts from this blog

Fundamental Books of a Software Engineer (version 2018)

More then six years ago I wrote a blog post about fundamental books that any software engineer (developer) should read. Now it is an excellent time to update this list with new entries.

There are 5 different categories of books, that represent the recommended path. For example, you start with Coding books, after that, you read books about Programming, Design and so on.
There are some books about C++ that I recommend not because you shall know C++, only because the concepts that you can learn from it.

Coding

Writing solid codeCode completeProgramming Pearls, more programming pearls(recommended)[NEW] Introduction to Algorithms

Programming

Refactoring (M. Fowler)Pragmatic ProgrammerClean code[NEW] Software Engineering: A Practitioner's Approach[NEW] The Mythical Man-Month[NEW] The Art of Computer Programming

Design

Applying UML and Patterns (GRASP patterns)C++ coding standards (Sutter, Alexandrescu)The C++ programming language (Stroustrup, Part IV)Object-oriented programming (Peter Coad)P…

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…