Open Closed

microservices template not loading administration menu after login #5199

User avatar
0
smansuri created

  • ABP Framework version: v7.2.2

  • UI type: Angular

  • DB provider: EF Core

  • Tiered (MVC) or Identity Server Separated (Angular): yes Identity Server Separated (Angular)

  • Exception message and stack trace:

  • Steps to reproduce the issue:" Download the ABP commercial framework solution with microservices as template from abp suite. After setting up the environment locally login to app. After successful login we are getting the below screen:

instead of this we should get the page with admin menus as below:

Go to accepted answer
33 Answer(s)
  • User Avatar
    0
    liangshiwei created
    Support Team Fullstack Developer

    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" /> to G1.health.AdministrationService.Domain.csproj
    • Add typeof(AbpIdentityProDomainModule), to AdministrationServiceDomainModule
  • User Avatar
    0
    smansuri created

    that worked, thanks.

  • User Avatar
    0
    smansuri created

    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
  • User Avatar
    0
    liangshiwei created
    Support Team Fullstack Developer

    Hi,

    Please create a new question; thanks.

    BTW, you can check this: https://support.abp.io/QA/Questions/5211

  • User Avatar
    0
    smansuri created

    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" /> to G1.health.AdministrationService.Domain.csproj
    • Add typeof(AbpIdentityProDomainModule), to AdministrationServiceDomainModule

    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.

  • User Avatar
    0
    liangshiwei created
    Support Team Fullstack Developer

    I will check it.

  • User Avatar
    0
    smansuri created

    I will check it.

    Could you please provide an update on this? what is expected time for fixing this?

  • User Avatar
    0
    liangshiwei created
    Support Team Fullstack Developer

    Hi,

    I reproduced the problem.

    You can try remove typeof(AbpIdentityProDomainModule) from AdministrationServiceDomainModule

    And add context.Services.AddTransient<AbpIdentityProSettingDefinitionProvider>(); to AdministrationServiceDomainModule.

Assignee
No one
Labels
None yet
Made with ❤️ on ABP v9.1.0-preview. Updated on December 13, 2024, 06:09