Does that help Are you using Code First/DbContext (your question is filed under entity-framework-4.1)? If so then your connection string should be just a regular connection string - something like this:
wish help you to fix your issue Can you show some details about connection string. I basically want to check the authentication you are using. Demo for setting a typical authentication : http://msdn.microsoft.com/en-us/library/ff649314.aspx Another possibility can be with connection pooling. Try explicitly closing the connection(if there are any open connections)
Entity Framework 4.0 - The underlying provider failed on Open
may help you . The ToList() call will cause the query to run on the database immediately and as this is not filtered in any way will return every employee in your database. This is probably likely to cause you performance issues. However you can't remove this in your case because if you return the IQueryable directly then the context will be disposed by the time you try and fetch results.
Entity Framework The underlying provider failed on Open
hope this fix your issue Seems like a connection issue. You can use the Data link properties to find if the connection is fine. Do the following: Create a blank notepad and rename it to "X.UDL" Double click to open it Under connections tab choose the server name/enter the name use the correct credentials and DB Click OK to save it.
Entity Framework connection failed to postgres: "The underlying provider failed on Open"
this will help I revisited my reproduction of the issue thanks to the surge of helpers recently. I managed to get it working when this stack overflow post made me realize, I had omitted DbConfiguration.SetProviderServices() from the dbconfiguration inheritor. The npgsql documentation is terrible since it failed to mention this was required.
public class NpgSqlConfiguration : DbConfiguration
SetProviderServices("Npgsql", provider: NpgsqlServices.Instance);