Unable to generate an explicit migration in entity framework

Question

I am adding a new migration but this message shows      Unable to generate an explicit migration because the following   explicit migrations are pending   201203170856167 left   Apply the   pending explicit migrations before attempting to generate a new   explicit migration    Can any one help me

User · Answer

It tells you that there is some unprocessed migration in your application and it requires running Update-Database before you can add another migration

User · Answer

When running into this issue  please try adding parameters to your add-migration cmdlet  For example  specifying the start up project as well as the connection string name could help EF find your target database   add-migration Delta Defect 0973 -ConfigurationTypeName your namespace ContextClassName -StartUpProject DeltaProject -ConnectionStringName DeltaSQL   Where   Delta Defect 0973 is the name of your migration  your namespace ContextClassName is the name of your Configuration class in your migration folder  prefixed with the full name space   DeltaProject is the name of your main project with your web config or app config file   DeltaSQL is the name of your connection string defined in your web config or app config file

User · Answer

Scenario   I am working in a branch in which I created a new DB migration  I am ready to update from master  but master has a recent DB migration  too   I delete my branch s db migration to prevent conflicts  I  update from master     Problem  After updating from master  I run  Add-Migration my migration name   but get the following error      Unable to generate an explicit migration because the following   explicit migrations are pending     201607181944091 AddExternalEmailActivity   Apply the pending explicit   migrations before attempting to generate a new explicit migration    So  I run  Update-Database  and get the following error      Unable to update database to match the current model because there are   pending changes and automatic migration is disabled   Solution  At this point re-running  Add-Migration my migration name  solved my problem  My theory is that running  Update-Database  got everything in the state it needed to be in order for  Add-Migration  to work

User · Answer

I had the same problems and was only able to resolve it running Add-Migration  MigrationName  -Force   With -Force being the important part

User · Answer

I had this problem too for a database that I knew was up to date when running Add-Migration  Solved by simply running the Add-Migration command a second time  Suspect a connectivity issue  as suggested by Robin Dorbell above

User · Answer

1  Connection String   Connection Permissions  Check the connection string again     Make sure the user you are connecting with still has permission to read from    MigrationHistory  and has permission to edit the schema   You can also try changing the connection string in the App or Web config file to use Integrated Security  Windows Auth  to run the add-migration command as yourself     For example   connectionString  data source server initial catalog db persist security info True Integrated Security SSPI      This connection string would go in the App config file of the project where the DbContext is located   2  StartUp Project  You can specify the StartUp project on the command line or you can right click the project with the DbContext  Configuration and Migrations folder and select Set as StartUp project   I m serious  this can actually help

User · Answer

Had the same issue and was able to solve with some hints from above answers    In package manager console check the default project  point to the project with the migration configuration Ensure the startup-proj has a web config with a valid connectionstring   or Ensure the project with migrations has an app config   web config with a valid connectionstring Check permissions in DB  for the user configured in you connectionstring    Use  update-database -verbose  in the package manager console to get more specific information where migrations tries to connect to   Helped in my case to find out my startup proj was not set correctly

User · Answer

Historically I always solved this by deleting the pending migrations  or if there was only 1 remaining and it was mostly desirable  by using -f to recreate it   Recently  this has stopped working for me   When this happened the first time  I restarted Visual Studio  and then it let me proceed   The second time  it only worked after I ran a Clean on the project  It was almost as if the pending migrations were retained despite deleting all the files from explorer

User · Answer

In my case  I forgot to add my IP address in firewall rules in Azure  basically as I was unable to connect to the database I was getting this error  So specifically for my case  I added my IP address in database firewall rules in Azure and it all worked well  Apart from this  it could be the issue of proxy internet connection DB username password DB connection string etc  OR obviously  you might have pending migrations for which you need to run Update-Database command

User · Answer

My local database did not have the   MigrationHistory populated  or existing  I manually created the table  and then migrated the data in that table from PROD to my local database  This caused VS to think the migrations had been applied  which they had been

User · Answer

This error can also mean that the migrations are not recognized anymore  This happened to me after having changed the value of the ContextKey in Migrations Configuration  The solution was simply to update the ContextKey in the database table    MigrationHistory   or revert the value in the Configuration class I guess    The ContextKey and the Namespace in your application should match

User · Answer

Just my two cents   My scenario    I restored my local database to a working state  Already had migrations already applied to it  Whenever I tried adding a new migration i got the error about pending migrations as mentioned my the OP    Solution   To get around this i just provided more explicit parameters   Add-Migration -ConnectionString  Server localhost SQLEXPRESS Database YourDataBase Trusted Connection True   -ConnectionProviderName  System Data SqlClient  -verbose   I am lead to believe that you can set a setting in your app config folder to allow you to default this behaviour so you don t have to provide explicit parameters everytime  However I am not sure on how to do this

User · Answer

i solved same problem like this    delete old migration file  update-database -force Add-Migration AddedEntity update-database

User · Answer

In my case  using MS Visual Studio   it was as simple as restarting Visual Studio

User · Answer

I did another way  I droped database entirely and run  update-database  again in vs

User · Answer

For me  i deleted the migration file in your case  201203170856167 left   from Migrations folder  and then ran the below command in Package Manager console  Add-Migration  lt Parameter gt  Update-Database

User · Answer

That was happened when i suddenly renamed class of old migration that already exist in db  I checked VCS history  determined that and renamed back  All worked afterwards

User · Answer

I had a simpler problem  VS erroneously reported this error when I had a VPN connection to a client s site connected on my workstation  The problem was that the DBMS security was set to accept requests only from my real local IP  Simply turning off the VPN resolved the problem

User · Answer

I suffered exactly the same problem just after reverting from a migration to another   In my case I  targetedmigration  from  migration06  to  migration04    I needed to delete the  migration0 6 and then I was able to force creating the  migration05   This basically means that you need to just keep the next migration after the targeted one

User · Answer

There is an ambiguity and so error  Best way is to exclude the current migration file and create new migration add-migration  file and then copy the content of new migration to excluded file and include it again and run update-database command

User · Answer

Old post but might help someone  For me it happened because I renamed Assembly name and Default namespace of the project  So I had to update ContextKey in  MigrationHisotry table to the new value of Assembly name or Default namespace  Honestly I don t know which one should be used  because for me both are same

User · Answer

You either need to run  update-database  from the package manager console to push your changes to the database OR you can delete the pending migration file   201203170856167 left   from your Migrations folder and then re-run  add-migration  to create a brand new migration based off of your edits

User · Answer

Tip  It s always good to use the -Script switch for migration commands if you re not sure  It also really helps understand what Update-Database actually does   I run the following to update the database  then I get a script I can apply manually  or just run it again without the -Script tag    For Update-Database I would run the following    Update-Database -Script -ConfigurationTypeName Configuration ASPNETIdentity -ConnectionStringName SQL AzureLive  Where SQL AzureLive is the named connection string in my config   Then I can verify the SQL looks right  apply it and be done  As many others have said if the connection string is wrong or invalid you ll get this error

User · Answer

If you haven t used Update-Database you can just delete it  If you ve run the update then roll it back using Update-Database -TargetMigration  NameOfPreviousMigration   then delete it   Reference  http   elegantcode com 2012 04 12 entity-framework-migrations-tips   I copied this text directly from here  How do I undo the last Add-Migration command

User · Answer

I also came across this issue  It came when I created new DB and I had pending changes for my code-first DB migration then I tried to run  Update-Database  command  Solution   Run  Add-Migration -MigrationName  command to create new migration for new DB  Then run  Update-Database  command

User · Answer

This isn t going to be the answer for many people  but EF will chuck this error when it can t connect to the DB  If you re working from home like I am  make sure you re still connected to your VPN

User · Answer

This error means there are pending migrations need to be commited before you can execute another explicit migration  You can choose to    Execute those pending migrations using Update-Database command Delete those pending migrations  Safest way is open Migrations folder  right click on  201203170856167 left    Exclude from project   After this one you can start  Add-Migration      again  Hope it helps

User · Answer

I had the same problem  Apparently entity framework generates this error when it s unable to connect to the database  So make sure that you re able to access it before searching for other problems

[entity-framework] Unable to generate an explicit migration in entity framework

Examples related to entity-framework

Examples related to entity-framework-migrations