The underlying provider failed on Open at the time Unity resolve the dependencies

Question

I am using an MVC Application that works with Unity to register all the dependencies of my project. I am also using Entity Framework for the DAL. In my local machine the application is running fine but at the time I deployed on the server I am receiving an error when Unity is trying to resolve the dependencies.

The underlying provider failed on Open. ... At the time of the exception, the container was: Resolving Class mapped from IClass ... Calling constructor of MyDbContext(System.String connectionName)

1- Does this have a relation with the connection string structure?

Bellow is my connection string

<add name="DBConnection" connectionString="Server=MyServer;Database=MyDatabase;Trusted_Connection=True;MultipleActiveResultSets=True;" providerName="System.Data.SqlClient" />

At this moment I don't have the access to the DB to check if the IIS user has the privileges on the server to run any query, but supposing it doesn't, does this has any relation with the error at the time Unity is trying to resolve the connection string?

2- Does Unity try to open a connection to the DB once it tries to resolve the DBContext?

Here is how I am injecting the parameters

var connectionString = System.Configuration.ConfigurationManager.ConnectionStrings["DBConnection"].ConnectionString;

container.RegisterType<IUnitOfWork, MyDbContext>(
                Activator.CreateInstance<T>(),
                new InjectionConstructor(connectionString));

The exception probably contains everything you need to solve this, but you're only looking at the top level message. Catch it, call ToString on it, then save that somewhere. That will capture the full details including the inner exceptions. — , Oct 14 '16 at 13:46
I'd say most importantly - don't open SQL connection in constructor. Any access to db should use lazy loading, setting up DI is part of critical infrastructure (there shouldn't be a IO operation). — Ondrej Svejdar, Oct 14 '16 at 13:50
that is the final exception, I am registering also in my EventViewer on the Server — Heinrich, Oct 14 '16 at 13:50
MyDbContext (any EntityFramework context) is not thread safe - registering it as singleton to DI is not a good idea. — Ondrej Svejdar, Oct 14 '16 at 13:59
thanks for the tip @OndrejSvejdar but even changing that doesn't solve my problem — Heinrich, Oct 14 '16 at 14:05

score 0 · Accepted Answer · edited May 23 '17 at 10:32

Your problem is most probably tied to fact that your application pool identity on production doesn't have access to the db. Unity creates instance of all dependent classes once the need arises. So if your Class needs IUnitOfWork, unity tries to instantiate MyDbContext.

Let me point out that you shouldn't register instance of entity context (MyDbContext) as singleton in first place - entity framework context is not thread-safe (Entity Framework Thread Safety), also DI is part of critical infrastructure (there shouldn't be IO calls - such as opening the db that can go wrong)

Instead use something like

public interface IEntityContextProvider {
   public MyDbContext CreateContext();
}
public class EntityContextProvider : IEntityContextProvider  {
   public MyDbContext CreateContext() {
     return new MyDbContext("ef connection string");
   }
}

Usage:

public class SomeClassUsingEF {
  // DI
  private readonly IEntityContextProvider _entityContextProvider;
  // DI
  public SomeClassUsingEF(IEntityContextProvider entityContextProvider)
  {
     if (entityContextProvider == null)
       throw new ArgumentNullException(nameof(entityContextProvider));
     _entityContextProvider = entityContextProvider;
  }

  public void SomeQueryToDB() {
    using(var context = _entityContextProvider.CreateContext()) {
      // select/insert/updates here
    }
  }
}

Also you connection string looks a lot like "ordinary" connection string - i.e. connection string to db wout entity framework - I'm missing the metadata in it. Code wise its usually something like

 private string GetEFConnectionString()
 {
    string providerName = "System.Data.SqlClient";
    string serverName = @".\SQL2008";
    string databaseName = "my-db";

    // Initialize the connection string builder for the
    // underlying provider.
    var sqlBuilder = new SqlConnectionStringBuilder();

    // Set the properties for the data source.
    sqlBuilder.DataSource = serverName;
    sqlBuilder.InitialCatalog = databaseName;
    sqlBuilder.IntegratedSecurity = true;

    // Build the SqlConnection connection string.
    string providerString = sqlBuilder.ToString();

    // Initialize the EntityConnectionStringBuilder.
    var entityBuilder = new EntityConnectionStringBuilder();

    // Set the provider name.
    entityBuilder.Provider = providerName;

    // Set the provider-specific connection string.
    entityBuilder.ProviderConnectionString = providerString;

    // Set the Metadata location.
    entityBuilder.Metadata = @"res://*/Model.csdl|
      res://*/Model.ssdl|
      res://*/Model.msl";
    return entityBuilder.ToString();
}

after granting the privileges on IIS, it was working, seems like Unity at the time it resolves the DBContext pings the datadabase and the user was not registered there. — Heinrich, Oct 14 '16 at 17:56

The underlying provider failed on Open at the time Unity resolve the dependencies

1 Answers1