Volo.Abp.AbpInitializationException
An error occurred during ConfigureServices phase of the module Volo.Abp.EntityFrameworkCore.AbpEntityFrameworkCoreModule, Volo.Abp.EntityFrameworkCore, Version=9.0.4.0, Culture=neutral, PublicKeyToken=null. See the inner exception for details.
at Volo.Abp.AbpApplicationBase.ConfigureServices()
at Volo.Abp.AbpApplicationBase..ctor(Type startupModuleType, IServiceCollection services, Action1 optionsAction) at Volo.Abp.AbpApplicationWithExternalServiceProvider..ctor(Type startupModuleType, IServiceCollection services, Action1 optionsAction)
at Volo.Abp.AbpApplicationFactory.Create(Type startupModuleType, IServiceCollection services, Action1 optionsAction) at Volo.Abp.AbpApplicationFactory.Create[TStartupModule](IServiceCollection services, Action1 optionsAction)
at Microsoft.Extensions.DependencyInjection.ServiceCollectionApplicationExtensions.AddApplication[TStartupModule](IServiceCollection services, Action1 optionsAction) at Volo.Abp.Testing.AbpIntegratedTest1..ctor()
at Semicrol.Fundraising.FundraisingTestBase`1..ctor()
at Semicrol.Fundraising.EntityFrameworkCore.FundraisingEntityFrameworkCoreTestBase..ctor()
at Semicrol.Fundraising.Repositories.DeductionPercentagesRepository.DeductionPercentagesRepository..ctor() in C:\Users\Josuegd\Desktop\PruebaClone\Fundanet.Fundraising\test\Semicrol.Fundraising.EntityFrameworkCore.Tests\Repositories\DeductionPercentagesRepository\DeductionPercentagesRepository.cs:line 18
at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean wrapExceptions)
System.TypeLoadException Method 'GetWaitingEventsAsync' in type 'Volo.Abp.EntityFrameworkCore.DistributedEvents.DbContextEventOutbox`1' from assembly 'Volo.Abp.EntityFrameworkCore, Version=9.0.4.0, Culture=neutral, PublicKeyToken=null' does not have an implementation. at Volo.Abp.EntityFrameworkCore.AbpEntityFrameworkCoreModule.ConfigureServices(ServiceConfigurationContext context) at Volo.Abp.AbpApplicationBase.ConfigureServices()
*
To troubleshoot, I’ve already tried the following steps:
abp cleanI came across a related GitHub issue: https://github.com/abpframework/abp/issues/22048, but in my case, I’m not using any RC versions. I'm using the following Lepton theme packages:
<PackageVersion Include="Volo.Abp.AspNetCore.Components.WebAssembly.LeptonTheme" Version="9.0.4" />
<PackageVersion Include="Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton" Version="9.0.4" />
Any help would be appreciated. Let me know if you need more information.
Thanks!
Hi,
I noticed something about management of tenants that catched my atention. It's not a problem but i'm just trying to understand how is it working. I proceed to explain myself with some examples:
When I instantiate it by calling the constructor the property TenantId is acquiring the value of my current tenant even before trying to insert it or saving changes with unit of work. I readed your documentation about this (https://abp.io/docs/latest/framework/architecture/multi-tenancy#when-to-set-the-tenantid) and learned you do it on the base Entity class but i would like to know how you do it. Could you let me know how is it done on that class?
Thanks!
EXCEPTION: 2025-07-17 11:30:13.161 +00:00 [ERR] ---------- RemoteServiceErrorInfo ---------- { "code": null, "message": "InternalServerErrorMessage", "details": null, "data": {}, "validationErrors": null }
2025-07-17 11:30:13.162 +00:00 [ERR] A possible object cycle was detected. This can either be due to a cycle or if the object depth is larger than the maximum allowed depth of 64. Consider using ReferenceHandler.Preserve on JsonSerializerOptions to support cycles. Path: $.Principal.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Issuer. System.Text.Json.JsonException: A possible object cycle was detected. This can either be due to a cycle or if the object depth is larger than the maximum allowed depth of 64. Consider using ReferenceHandler.Preserve on JsonSerializerOptions to support cycles. Path: $.Principal.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Subject.Claims.Issuer.
I found this support ticket https://abp.io/support/questions/8143/A-cycle-during-the-cache-serialization but is not clear how to configure it.
Could you attach an example please?