Activities of "Repunjay"

I remember that your project is very complicated. You can try to reproduce the problem in the template first. Thanks

is there any changes related to tenant admin databases after upgrading to abp 6.0.2 & openIddict?

I have removed all the Migrations, dbs and pointed to new db connections, after this host database migrations and seed of host database is done but as "SaasTenantConnectionStrings " is not present (as its a new db), it is not migrating & seeding of tenant database.

after updating the "SaasTenantConnectionStrings" table, I ran the dbmigrator then its displaying errors like tables are presented in host database without going to tenant db.

what is the solution for this?

Please refer sample template for openiddict, which will runs on 6.0.2 version, not "rc" versions please

hi

You don't need to use ForwardIdentityAuthenticationForBearer in the HttpApiHost project.

https://docs.abp.io/search/en/commercial/7.0/?keyword=ForwardIdentityAuthenticationForBearer https://docs.abp.io/en/abp/7.0/Migration-Guides/IdentityServer_To_OpenIddict

If you're creating a bug/problem report, please include followings:

1. ABP Framework version: vX.X.X
2. UI type: Angular / MVC / Blazor
3. DB provider: EF Core / MongoDB
4. Tiered (MVC) or Identity Server Separated (Angular): yes / no
5. Exception message and stack trace:
6. Steps to reproduce the issue:"

hi

You should remove all Identity Server codes.

See https://docs.abp.io/en/commercial/latest/migration-guides/openIddict-step-by-step

the current error one belongs to IdentityServerDataSeeder.cs class, In migration guide they didn't mentioned about this class, they only mentioned about "IdentityServerDataSeedContributor.cs" class only.

hi

MyProjectNameEntityFrameworkCoreModule and MyProjectNameDbContextFactory

is this change only related to Identity or other dbcontexts also need change? Please confirm on this.

1. Removed all migrations and tried, same error.
2. Removed all migrations except initial migration and tried, same error.
3. Removed the table "AppCountryCodes" and created & ran the migrations, same error.
4. Removed the table AppHolidayCalendarDetail and created & ran the migrations, same error.
5. Removed the both tables AppHolidayCalendarDetail & AppCountryCodes then created & ran the new Migration, same error.
6. Removed the Migrations step by step and tried, but same error.

I have tried all the above things by restoring the "Litmus_Admin_6_0" database using back file also, but the same error its giving.

Reproducing of the error in sample project, I too don't know, will check and let you know.

is there any possibility of having a working session tomorrow?

You can have a try. after deleting all migration files including initial also I am getting above identity related db table AppHolidayCalendarDetail issue.

after adding "IsActive" property to abpusers and ran the dbmigrator project, getting the attached error.

Did you add new migrations? Will the error still occur if change the connection string to a new database?

You can also try to delete all migrations and create a new one to test.

---

If it still doesn't solve the problem, how to reproduce it with a new project?

do you want me to delete initial Migration also?

hi

// https://www.npgsql.org/efcore/release-notes/6.0.html#opting-out-of-the-new-timestamp-mapping-logic 
AppContext.SetSwitch("Npgsql.EnableLegacyTimestampBehavior", true); 

do I need to add this line in all dbcontext files or how?

by running this command at root directory of the application is solved the issue. abp install-libs

after adding "IsActive" property to abpusers and ran the dbmigrator project, getting the attached error.

Did you add new migrations? Will the error still occur if change the connection string to a new database?

You can also try to delete all migrations and create a new one to test.

---

If it still doesn't solve the problem, how to reproduce it with a new project?

New Migration Added. Connection string modified to new database. tried by deleting earlier migration but not working, please see the screen shot for the migration files.