Any update on this?
In this case how i'm supposed to host my application? if i have to implement custom solution why i would purchase abp framework.
whats the work around and Expected date of release?
I will check it.
Could you please provide an update on this? what is expected time for fixing this?
Hi,
It's a problem, we will fix it.
You can use the following temporary solution:
- Add
<PackageReference Include="Volo.Abp.Identity.Pro.Domain" Version="7.2.2" />
toG1.health.AdministrationService.Domain.csproj
- Add
typeof(AbpIdentityProDomainModule),
toAdministrationServiceDomainModule
This was working but it created another issue. When trying to open permission menu on actions button for any user, it was giving 500 internal server error. after removing the above package references permission was working fine.
Chat module migration is throwing exception. We have followed instructions as per here : https://docs.abp.io/en/commercial/latest/modules/chat installed location: identityService.
Chat module migration is giving below error:
Autofac.Core.DependencyResolutionException: 'An exception was thrown while activating Volo.Chat.EntityFrameworkCore.ChatDbContext -> λ:Microsoft.EntityFrameworkCore.DbContextOptions`1[[Volo.Chat.EntityFrameworkCore.ChatDbContext, Volo.Chat.EntityFrameworkCore, Version=7.2.2.0, Culture=neutral, PublicKeyToken=null]].'
AbpException: No configuration found for Microsoft.EntityFrameworkCore.DbContext, Microsoft.EntityFrameworkCore, Version=7.0.2.0, Culture=neutral, PublicKeyToken=adb9793829ddae60! Use services.Configure
This exception was originally thrown at this call stack:
Volo.Abp.EntityFrameworkCore.DependencyInjection.DbContextOptionsFactory.Configure<TDbContext>(Volo.Abp.EntityFrameworkCore.AbpDbContextOptions, Volo.Abp.EntityFrameworkCore.DependencyInjection.AbpDbContextConfigurationContext<TDbContext>)
Volo.Abp.EntityFrameworkCore.DependencyInjection.DbContextOptionsFactory.Create<TDbContext>(System.IServiceProvider)
Autofac.Extensions.DependencyInjection.AutofacRegistration.Register.AnonymousMethod__0(Autofac.IComponentContext, System.Collections.Generic.IEnumerable<Autofac.Core.Parameter>)
Autofac.Core.Activators.Delegate.DelegateActivator.ActivateInstance(Autofac.IComponentContext, System.Collections.Generic.IEnumerable<Autofac.Core.Parameter>) in DelegateActivator.cs
Autofac.Core.Activators.Delegate.DelegateActivator.ConfigurePipeline.AnonymousMethod__2_0(Autofac.Core.Resolving.Pipeline.ResolveRequestContext, System.Action<Autofac.Core.Resolving.Pipeline.ResolveRequestContext>) in DelegateActivator.cs
Autofac.Core.Resolving.Middleware.DelegateMiddleware.Execute(Autofac.Core.Resolving.Pipeline.ResolveRequestContext, System.Action<Autofac.Core.Resolving.Pipeline.ResolveRequestContext>) in DelegateMiddleware.cs
Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.BuildPipeline.AnonymousMethod__1(Autofac.Core.Resolving.Pipeline.ResolveRequestContext) in ResolvePipelineBuilder.cs
Autofac.Core.Resolving.Middleware.DisposalTrackingMiddleware.Execute(Autofac.Core.Resolving.Pipeline.ResolveRequestContext, System.Action<Autofac.Core.Resolving.Pipeline.ResolveRequestContext>) in DisposalTrackingMiddleware.cs
Autofac.Core.Resolving.Pipeline.ResolvePipelineBuilder.BuildPipeline.AnonymousMethod__1(Autofac.Core.Resolving.Pipeline.ResolveRequestContext) in ResolvePipelineBuilder.cs
Autofac.Core.Resolving.Middleware.ActivatorErrorHandlingMiddleware.Execute(Autofac.Core.Resolving.Pipeline.ResolveRequestContext, System.Action<Autofac.Core.Resolving.Pipeline.ResolveRequestContext>) in ActivatorErrorHandlingMiddleware.cs
that worked, thanks.
We did not install chat and file module. BUt we will need the two factor issue resolved.
After clearing the redis cache we got SaaS menu and Open Id menus.
But still missing other menus Under Administration->Roles->Actions Menu->Permisions We are missing menus for Chat , File management.
Under administration -> users we are missing Two factor menu option from actions. Under SasS menu->Features we are missing twon menus 1) Chat 2) File management
Hi,
You can try to enable the source link to debug the
AbpPermissionManagementDomainModule
andStaticPermissionSaver
classes.abp will save the permission definition to the database when the application is startup. But here some reason causes the save not to complete, you can debug to check
Hi Team, We are unable to debug the abp framework, This is related to abp framework and we expect you to debug and fix the issue at framework level ASAP.