Activities of "ccernat"

Thanks so much, maliming!

You the best!

God damn!

It worked! It should have returned a more normal error message. Is this from the upgrade? Or?

hello

sent the solution's archive.

tks alot.

Found the problem. All the enum values in json related files from the .suite/entities folder in the solution's root were put to null.

Replace the null values with incremental integers for each enum value and it abp suite started working again.

It worked until 7.0.1, so something must have happened while upgrading.

I think is still needs to be checked why this happened.

hi

it doesn't work. the thing is I literally did nothing than just upgrade packages to 7.01. it worked in all previous versions.

same code.

strange.

• ABP Framework version: v7.0.1
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace:
• at Microsoft.EntityFrameworkCore.Internal.EntityFinder1.<LoadAsync>d__11.MoveNext() at Volo.Abp.Domain.Repositories.EntityFrameworkCore.EfCoreRepository2.<EnsureCollectionLoadedAsync>d__351.MoveNext() at Volo.Abp.Domain.Repositories.RepositoryExtensions.<EnsureCollectionLoadedAsync>d__03.MoveNext() at Volo.Abp.Identity.IdentityUserStore.<AddToRoleAsync>d__40.MoveNext() at Microsoft.AspNetCore.Identity.UserManager1.<AddToRoleAsync>d__105.MoveNext() at Castle.DynamicProxy.AsyncInterceptorBase.<ProceedAsynchronous>d__141.MoveNext() at Volo.Abp.Castle.DynamicProxy.CastleAbpMethodInvocationAdapterWithReturnValue1.<ProceedAsync>d__7.MoveNext() at Volo.Abp.Uow.UnitOfWorkInterceptor.<InterceptAsync>d__2.MoveNext() at Volo.Abp.Castle.DynamicProxy.CastleAsyncAbpInterceptorAdapter1.<InterceptAsync>d__31.MoveNext() at MHU.Data.MHUEmployeesDataSeedContributor.<CreateValidationOfficerAsync>d__9.MoveNext() in F:\EHV\MHUPortalWASM\MHU\src\MHU.Domain\Data\MHUEmployeesDataSeedContributor.cs:line 76 at MHU.Data.MHUEmployeesDataSeedContributor.<SeedAsync>d__8.MoveNext() in F:\EHV\MHUPortalWASM\MHU\src\MHU.Domain\Data\MHUEmployeesDataSeedContributor.cs:line 48 at Volo.Abp.Data.DataSeeder.<SeedAsync>d__7.MoveNext() at Castle.DynamicProxy.AsyncInterceptorBase.<ProceedAsynchronous>d__13.MoveNext() at Volo.Abp.Castle.DynamicProxy.CastleAbpMethodInvocationAdapter.<ProceedAsync>d__7.MoveNext() at Volo.Abp.Uow.UnitOfWorkInterceptor.<InterceptAsync>d__2.MoveNext() at Volo.Abp.Castle.DynamicProxy.CastleAsyncAbpInterceptorAdapter1.<InterceptAsync>d__2.MoveNext() at MHU.Data.MHUDbMigrationService.<SeedDataAsync>d__11.MoveNext() in F:\EHV\MHUPortalWASM\MHU\src\MHU.Domain\Data\MHUDbMigrationService.cs:line 103 at MHU.Data.MHUDbMigrationService.<MigrateAsync>d__9.MoveNext() in F:\EHV\MHUPortalWASM\MHU\src\MHU.Domain\Data\MHUDbMigrationService.cs:line 53 at MHU.DbMigrator.DbMigratorHostedService.<StartAsync>d__3.MoveNext() in F:\EHV\MHUPortalWASM\MHU\src\MHU.DbMigrator\DbMigratorHostedService.cs:line 34 at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>d__12.MoveNext() at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.<RunAsync>d__4.MoveNext() at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.<RunAsync>d__4.MoveNext() at MHU.DbMigrator.Program.<Main>d__0.MoveNext() in F:\EHV\MHUPortalWASM\MHU\src\MHU.DbMigrator\Program.cs:line 28
• Steps to reproduce the issue: Upgrade to 7.0.1 and tried to run DBMigrator to seed some users."

Hello!

I upgraded to 7.0.1 and tried to add seed some users and add them to specific roles.

This is what running DbMigrator does:

Tks for providing any hint.

Hi, ABP support team!

You guys managed to reproduce this?

Can I downgrade the ABP suite version, because is impeding my work.

Tks for any hint!

Catalin

Hi,

Can I do smth until then?

If not, is it possible to have a rough estimation when the new version gonna be released, to know when I should expect to deploy in production?

Tks alot, maliming!

Hi!

Indeed, WS were not enabled. I enabled them, but, unfortunately, still the same behavior. :(

• ABP Framework version: v7.0.1
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace:
• Steps to reproduce the issue: Upgrade ABP suite from 6.0.2 to 7.0.1"

Hello!

After I upgraded the solution and also ABP suite to 7.0.1, when I open the Crude Page Generator I encountered the error in the description.