Ok i solved this with adding below line in DBMigrator Service configuration steps:
context.Services.AddTransient<MyPermissionDataSeedContributor>();
Is this the right approach?
Creating a new tenant does not creates an admin user for that tenant. chris.tune@gmail.com is right.
ABP Framework version: v4.3.0 (new template) UI type: Angular DB provider: EF Core Identity Server Separated: yes Exception message and stack trace: No error.
Steps: Create a tenant, you will see it won't add an admin user for that tenant.
I can confirm that the problem still exists and changing the database option "Is Read Committed Snapshot On" does not solve the problem.
There was no such problem before versions 4.3.* of ABP. What could be the change?
WE STILL NEED HELP!
I see this now :) applying the stuff in below article solves the problem. https://support.abp.io/QA/Questions/1360/Cannot-create-a-new-tenant-after-migrating-to-430
Expected Result: There shouldn't be a button that is linked to a unit (clickable) after the unit is deleted Actual Result: Since the unit no more exists, when we clicked the tab linked to it an error window pops up.