"the Provider Did Not Return A Providermanifesttoken String"
Solution 1:
If you are using SQL Azure, this error can be caused if the Azure Database Firewall is not set up to allow your IP Address. Make sure check to make sure you are authorizing the IP Address. This error doesn't necessarily point you in that direction.
Solution 2:
I had same problem and solved it by following method. Just Check the db instance's Object name, it might be like:
privateModel_db=newModel_();
If so, then replace it with MovieDBContext like:
privateMovieDBContextdb=newMovieDBContext();
(or what you set the Class name in Model/Movies.cs like
publicclassMovieDBContext : DbContext
{
public DbSet < Movie> Movies { get; set; }
)
Solution 3:
I had the same problem until I came across this answer
DB Connection string in Web.config to use attached .mdf database won't work
"If you have the *.mdf placed in App_Data folder, using this format works:"
<connectionStrings><addname="ConnectionName"connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|DatabaseName.mdf;Integrated Security=True;User Instance=True"providerName="System.Data.SqlClient" /></connectionStrings>I also used the tutorial, but I had database file *.mdf otherwise than in the tutorial *.sdf.
Maybe this solution will be helpful.
Solution 4:
I figured it out: turns out that "\MSSQLSERVER" isn't needed in my case. I'm not sure if it's because I'm connecting by IP or if it's specific to my server setup, but removing it solved the problem.
Solution 5:
I found my answer here:
"There are two web.config files in ASP.NET MVC3 applications. One is in the root where connection strings should be placed and the other is under Views folder, where connections should not be placed. Guess where I had my connection!"
Post a Comment for ""the Provider Did Not Return A Providermanifesttoken String""