There is already an object named AspNetRoles in the database. (entity-framework-core)

asp.net-core asp.net-core-mvc asp.net-identity entity-framework-core

Question

I have an asp.net core mvc website using entity framework core.

I don't know how it initially happened, but I can't get past the error: "There is already an object named AspNetRoles in the database"

I ended up deleted the database, deleting all my migration .cs files and starting from scratch.

I've then tried add-migration MyInitialMigration

same error

I then deleted the database again, and tried a direct update-database (without adding a migration)

still the same error

I tried changing the appsettings config string to point to a new, non-existing database.

Still the same error!

Previously on MVC5/EF6 I've encountered this error and have resolved it using the same method as this answer: There is already an object named in the database

-Add-Migration Initial -IgnoreChanges

However -IgnoreChanges is unsupported in EFCore

Or previously on EF6 I've resolved it by adding a migration, then deleting everything in the Up/Down and running an empty migration. This has not worked on EFCore

How can I continue? I've checked the migration table and they're always empty even though it's created the whole database each time. Just doesn't seemed to have logged it in the migrations table

1
3
5/23/2017 11:59:58 AM

Fastest Entity Framework Extensions

Bulk Insert
Bulk Delete
Bulk Update
Bulk Merge

Accepted Answer

Found my issue.

I had followed this tutorial to load appsettings from EntityFramework: https://docs.asp.net/en/latest/fundamentals/configuration.html#example-entity-framework-settings

In the EntityFrameworkConfigurationProvider there is a public override void Load() which has a dbContext.Database.EnsureCreated(); and a CreateAndSaveDefaultValues

Between the two of those it looks like it was initializing the database without tracking the migration.

I commented those out, ran a migration and it worked fine. Hopefully I don't have to comment them out every time I want to run a migration :/

7
9/21/2016 10:00:25 AM

Popular Answer

I've just had the same issue, and seems like Database.EnsureCreated() doesn't use migrations, you can use Database.Migrate() instead which is what I've just tried and seems to work, but time will tell when I try another migration.

RichardB

Related Questions

There is already an object named in the database

Maybe you have changed the namespace in your project!... There is a table in your data base called ...dbo.__MigrationHistory.... The table has a column called ...ContextKey....... The value of this column is based on your ...namespace.... for example is "...DataAccess.Migrations.Configuration..."....When you change the namespace, it causes duplicat...
database ef-code-first ef-migrations entity-framework entity-framework-6
asked by Elnaz

ef core: There is already an object named in the database

The simplest way is create the one DbContext that will include all sets of entities and relations between them. After that you can separate storage logic with repositories. The hard way is create context-specific migrations for each context. And if you need to add set of entities, that exists in another context - you will need to create an empty mi...
asp.net-core database entity-framework entity-framework-core
asked by R. Bukin

There is already an object named 'AspNetRoles' in the database when trying to update with Entity Framework

The fastest solution is: ...delete migration folder ...delete database...enable-migrations...add initial migration...update-database
asp.net-core c# entity-framework-core
asked by szydzik

How to recover from Entity Framework nightmare - database already has tables with the same name

I originally wrote this as a self-answering question as I had struggled with the proble for some time, as had a few colleagues, but unfortunately, my answer was deleted and I can't recover it....Since it's a situation that I suspect can happen several times as people try to "clean up" old migrations, I thought I'd document it with step by step inst...
database-migration ef-migrations entity-framework entity-framework-6
asked by System.Exception

Error while migration - There is already an object named 'AspNetRoles' in the database. (Entity Framework Core)

Briefly looked through and the first thing I noticed is that your should use Generic IdentityDbContext:...public class ApplicationIdentityDbContext : IdentityDbContext<ApplicationUser> ...Full recommended scenario:...define your ApplicationUser class:...2.define context (I am prefer not hard code connection string here):...public class ApplicationI...
asp.net-identity c# entity-framework-core
asked by Алексей Сидоров

Add child entities to database and assign them to parent object in database Entity Framework Core

"First of all I don't see where a foreign key is set for the instance of type "DocumentLine"."...Well, then first of all - check that. In the actual database created by EF. You're most probably gonna find an FK on ...DocumentId... in your ...DocumentLines... table....Your ...Document... and ...DocumentLines... are in a 1toMany relationship - a ...D...
c# entity-framework-core xamarin.forms
asked by V0ldek

.NET Core Entity Framework throws Invalid object name when accessed as entity, but works with SQL

I found the solution. You can't put the schema in the table name....//This Does NOT work [Table("Cdef.CellDefinition")] public partial class CellDefinition{} //But this DOES work [Table("CellDefinition",Schema = "Cdef")] public partial class CellDefinition{}
asp.net-mvc entity-framework entity-framework-core
asked by John P

EF Core There is already an object named 'AspNetRoles' in the database

It looks like we have to drop the database anytime we see this error....However, there is a way to keep the data while recreating the database:...Using SQL Server Management Studio, we can go to Task -> Generate Scripts, then in the "Set Scripting Options" window to back up the data, we should set the type of data to be backed up to "Data Only"...
asp.net-core asp.net-identity c# entity-framework entity-framework-core
asked by Hamid Baghernia

There is already an object named 'xxx' in the database

This error shows up because you probably have migration that includes table, column same like in one of previous migrations. Check every migration if there is no some duplicates. It sometimes happen when you revert your snapshot file. If you want more help with this issue you will need provide more information about your migrations and schema.
ef-migrations entity-framework-core
asked by kyziur

I am unable to store data into database using Entity Framework Core and Ajax

Add ...contentType: "application/json"... to specify the type of data you're sending.If you do not specify it,it would use ...application/x-www-form-urlencoded; charset=UTF-8... by default:... $.ajax({ contentType: "application/json", }); ...And add ...[FromBody]... to your action:...[HttpPost] public async Task<IActionResult> Sa...
asp.net asp.net-core asp.net-core-2.0 asp.net-core-mvc entity-framework-core
asked by Rena

Fastest Entity Framework Extensions

Bulk Insert
Bulk Delete
Bulk Update
Bulk Merge
View more on Stack Overflow

Prime Library

Performance

Expression Evaluator

More Projects...

Related

Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow