Hi,
You should make sure all abp packages upgrade to 7.1.1
BTW, ABP 7.1.1 is based on NET 7.0, you need to also upgrade all Microsoft's packages.
You can check the migration guide: https://docs.abp.io/en/commercial/latest/migration-guides/index
When you done, please run
dotnet clean
&dotnet build
command.
Hi As I mentioned earlier I already tried with all packages with 7.1.1 anyhow I did tried again and obviously .net version is 7
still getting the below error
2023-04-11 13:13:57.474 +05:30 [FTL] Exceego.EHSWatch.AppV3.Web terminated unexpectedly!
Volo.Abp.AbpInitializationException: An error occurred during ConfigureServicesAsync phase of the module Volo.Abp.AspNetCore.Mvc.AbpAspNetCoreMvcModule, Volo.Abp.AspNetCore.Mvc, Version=7.1.1.0, Culture=neutral, PublicKeyToken=null. See the inner exception for details.
---> System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types.
Could not load type 'Volo.Abp.EventBus.ILocalEventHandler1' from assembly 'Volo.Abp.EventBus, Version=7.1.1.0, Culture=neutral, PublicKeyToken=null'. at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module) at Microsoft.AspNetCore.Mvc.Controllers.ControllerFeatureProvider.PopulateFeature(IEnumerable
1 parts, ControllerFeature feature)
at Microsoft.AspNetCore.Mvc.ApplicationParts.ApplicationPartManager.PopulateFeature[TFeature](TFeature feature)
at Microsoft.Extensions.DependencyInjection.MvcCoreMvcBuilderExtensions.AddControllersAsServices(IMvcBuilder builder)
at Volo.Abp.AspNetCore.Mvc.AbpAspNetCoreMvcModule.ConfigureServices(ServiceConfigurationContext context)
at Volo.Abp.Modularity.AbpModule.ConfigureServicesAsync(ServiceConfigurationContext context)
at Volo.Abp.AbpApplicationBase.ConfigureServicesAsync()
System.TypeLoadException: Could not load type 'Volo.Abp.EventBus.ILocalEventHandler1' from assembly 'Volo.Abp.EventBus, Version=7.1.1.0, Culture=neutral, PublicKeyToken=null'. --- End of inner exception stack trace --- at Volo.Abp.AbpApplicationBase.ConfigureServicesAsync() at Volo.Abp.AbpApplicationFactory.CreateAsync[TStartupModule](IServiceCollection services, Action
1 optionsAction)
at Microsoft.Extensions.DependencyInjection.ServiceCollectionApplicationExtensions.AddApplicationAsync[TStartupModule](IServiceCollection services, Action1 optionsAction) at Microsoft.Extensions.DependencyInjection.WebApplicationBuilderExtensions.AddApplicationAsync[TStartupModule](WebApplicationBuilder builder, Action
1 optionsAction)
at Exceego.EHSWatch.AppV3.Web.Program.Main(String[] args) in C:\Official\EHSWatchV3\repo\EHSWatch_AppV3\apps\web\src\Exceego.EHSWatch.AppV3.Web\Program.cs:line 29
Let me know if anything is missing
I tried by upgrading all abp versions to 7.1.1 also tried with combinations. but getting the below error in both the cases.
Volo.Abp.AbpInitializationException: An error occurred during ConfigureServicesAsync phase of the module Volo.Abp.AspNetCore.Mvc.AbpAspNetCoreMvcModule, Volo.Abp.AspNetCore.Mvc, Version=7.1.0.0, Culture=neutral, PublicKeyToken=null. See the inner exception for details.
---> System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types.
Could not load type 'Volo.Abp.EventBus.ILocalEventHandler1' from assembly 'Volo.Abp.EventBus, Version=7.1.1.0, Culture=neutral, PublicKeyToken=null'. at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module) at Microsoft.AspNetCore.Mvc.Controllers.ControllerFeatureProvider.PopulateFeature(IEnumerable
1 parts, ControllerFeature feature)
at Microsoft.AspNetCore.Mvc.ApplicationParts.ApplicationPartManager.PopulateFeature[TFeature](TFeature feature)
at Microsoft.Extensions.DependencyInjection.MvcCoreMvcBuilderExtensions.AddControllersAsServices(IMvcBuilder builder)
at Volo.Abp.AspNetCore.Mvc.AbpAspNetCoreMvcModule.ConfigureServices(ServiceConfigurationContext context)
at Volo.Abp.Modularity.AbpModule.ConfigureServicesAsync(ServiceConfigurationContext context)
at Volo.Abp.AbpApplicationBase.ConfigureServicesAsync()
System.TypeLoadException: Could not load type 'Volo.Abp.EventBus.ILocalEventHandler1' from assembly 'Volo.Abp.EventBus, Version=7.1.1.0, Culture=neutral, PublicKeyToken=null'. --- End of inner exception stack trace --- at Volo.Abp.AbpApplicationBase.ConfigureServicesAsync() at Volo.Abp.AbpApplicationFactory.CreateAsync[TStartupModule](IServiceCollection services, Action
1 optionsAction)
at Microsoft.Extensions.DependencyInjection.ServiceCollectionApplicationExtensions.AddApplicationAsync[TStartupModule](IServiceCollection services, Action1 optionsAction) at Microsoft.Extensions.DependencyInjection.WebApplicationBuilderExtensions.AddApplicationAsync[TStartupModule](WebApplicationBuilder builder, Action
1 optionsAction)
at Exceego.EHSWatch.AppV3.Web.Program.Main(String[] args) in C:\Official\EHSWatchV3\repo\EHSWatch_AppV3\apps\web\src\Exceego.EHSWatch.AppV3.Web\Program.cs:line 29
My UI layer Project file looks like below
<ItemGroup>
<PackageReference Include="DocumentFormat.OpenXml" Version="2.19.0" />
<PackageReference Include="Microsoft.AspNetCore.DataProtection.EntityFrameworkCore" Version="6.0.4" />
<PackageReference Include="Microsoft.AspNetCore.DataProtection.StackExchangeRedis" Version="6.0.0" />
<PackageReference Include="Microsoft.Data.SqlClient" Version="5.0.0" />
<PackageReference Include="Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonXLite" Version="2.1.0" />
<PackageReference Include="Volo.Abp.BackgroundJobs" Version="5.1.3" />
<PackageReference Include="Microsoft.AspNetCore.DataProtection.StackExchangeRedis" Version="6.0.0" />
<PackageReference Include="Microsoft.Data.SqlClient" Version="5.0.0" />
<PackageReference Include="OpenAI" Version="1.6.0" />
<PackageReference Include="Volo.Abp.BackgroundJobs" Version="5.1.3" />
</ItemGroup>
<ItemGroup>
<PackageReference Include="Volo.Abp.Caching.StackExchangeRedis" Version="5.1.3" />
<PackageReference Include="Volo.Abp.EventBus.RabbitMQ" Version="7.1.1" />
<PackageReference Include="Volo.Abp.AspNetCore.Mvc.Client" Version="7.1.1" />
<PackageReference Include="Volo.Abp.AspNetCore.Authentication.OpenIdConnect" Version="5.1.3" />
<PackageReference Include="Volo.Abp.Http.Client.Web" Version="5.1.3" />
<PackageReference Include="Volo.Abp.Http.Client.IdentityModel.Web" Version="5.1.3" />
<PackageReference Include="Volo.Abp.AspNetCore.Mvc.UI.Theme.Lepton" Version="5.1.3" />
<PackageReference Include="Volo.Abp.Account.Pro.Public.HttpApi.Client" Version="5.1.3" />
</ItemGroup>
Note I tried with all abp 7.1.1 also, but same issue.
Please advise.
If I create the Micro Service solution once again and then add the service, it worked. but if this is the case we may the issue if we plan to add the micro service after some releases right
We upgraded the ABP to 7.0.2
Did you upgrade your CLI and Suite to 7.0.2?
Please use the same version of CLI or Suite to create a new service.
Yes I am using the same version of CLI and Suite, anyway upgraded to 7.0.2 and added the new micro service. more or less same issues repeated.
hi
This may be a cache problem. Please try to clear Redis.
I tested the microservice project today, and everything works.
Did you tried by adding additional service to Micro service as described in
https://docs.abp.io/en/commercial/latest/startup-templates/microservice/add-microservice
having the below issues:
a. when we do that, still able to see the API.Host project is referring to .net 6.0
b. many projects are still referring(including test) to .net 6.0 ex:- Microsoft.EntityFrameworkCore.Tools is still referring to 6.0.0
c. MigractorChecker file is not right
Are we missing any anything or CLI issue?
We upgraded the ABP to 7.0.2 and created a Micro Service sample solution using ABP Suite. The solution created successfully and we ran the migrator and able to login to application as a admin user without any issues, but surprisingly not able to see the SAAS management and Product Service in the site.
All databases got created successfully, is it any issue with latest ABP Suite?
inequivalent arg 'x-dead-letter-exchange' for queue 'AppV3_AdministrationService' in vhost '/': received none but current is the value 'AppV3_dead_letter' of type 'longstr''
That means that you have a AppV3_AdministrationService queue on the broker already and it is without an 'x-dead-letter-exchange' argument. Probably you have created it before with that state.
You can remove all RabbitMQ queues and try again.
Thanks for the response, yes we found the issue is with queues, after clearing those it worked perfectly. Thanks
logs shared to liming.ma@volosoft.com
We just created a sample micro service solution on ABP 7.1 and when creating a tenants. tenants are getting created and default user also created. but when we are logging in with tenant user not able to see any applications, are we missing anything??
also we observed there is entries in below table , as per us it should not be empty
We would like to Turn Off the Audit Logging for Specific Tenants , we have a feature for Audit Logging but it just hiding the adult log page for that tenant not the entries into Audit Tables "AbpAuditLogs" & "AbpAuditLogActions"
are we missing anything here? Please advise.