Activities of "viswajwalith"

Hi,

Could you share a project that can reproduce the problem? shiwei.liang@volosoft.com I will check it.

It has couple of dependent projects, do u think just sharing the web (UI) project works for you to replicate the issue?

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(IEnumerable1 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, Action1 optionsAction) at Microsoft.Extensions.DependencyInjection.ServiceCollectionApplicationExtensions.AddApplicationAsync[TStartupModule](IServiceCollection services, Action1 optionsAction) at Microsoft.Extensions.DependencyInjection.WebApplicationBuilderExtensions.AddApplicationAsync[TStartupModule](WebApplicationBuilder builder, Action1 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

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?

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 can't fix this. You may consider using a shorter Scope name.

Ok, Thanks for the update

hi

Please share a such URL

We do not add any extra parameters to the URL.

Its not because of any additional parameters, its due to the encryption of Return URL I think (because some times the Length will be around 800 characters and some times more then 3000). we would like to restrict this below 1200 characters all the time(if possible)

https://authserver.xxxxxxxx.com/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3FLOGINUSING%26client_id%3DAppV3_Web%26redirect_uri%3Dhttps%253A%252F%252Fexceego.ehswatch.com%252Fsignin-oidc%26response_type%3Dcode%2520id_token%26scope%3Dopenid%2520profile%2520role%2520email%2520phone%2520AuthServer%2520IdentityService%2520AdministrationService%2520SaasService%2520EmployeeService%2520IncidentService%2520AttachmentService%2520ObservationsService%2520ActionService%2520UserTaskService%2520HSEPlansService%2520NCRService%2520CustomerService%2520InspectionService%2520Forms%2520FileManagement%2520RMService%2520TMService%26response_mode%3Dform_post%26nonce%3D638071896570293599.M2VkZDBkMDctY2U2MS00NmI5LThiMjktNzlmNmYzNWVjOWQ0MzU5NjcyMWMtMjliZC00OTM2LThjYzctMzZhMDBiMjhiYzhh%26state%3DCfDJ8FRhYrLUrBdPg2ipof6Ze15HVIyX7WS4ApP5QoDnN0sbMASqwYqqMGy9rEmEjK6TMFeOm_zu4Eb9w3MveX0N56QEyLnmm5YNKxgGUvl4F3FI2rfnhKM5NJpX8nYQCURZP9QypINWTaqNJqlyx5IpsEKoyffePii8EeTjK8llh99Fy4gqqMxD4DtLt4R1VQ5yFpM5hvBzQHRTLPpRbAhmhgnKgdfw1jgfCC2PjHX1zbm6OTKXCbngXc-FUSadf4m9AeNPjoj-BRvRSDYvQHdg60TE-Io8jbpZTz1N_wt0zqj6J8IX8BI2NU61tmXwGtfEf4ABMGtzFxS8ifUbb77WVd4%26x-client-SKU%3DID_NET6_0%26x-client-ver%3D6.21.0.0

With Tenant ID:

https://authserver.xxxxxxxx.com/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3F__tenant%3D8e3e606e-2370-663b-d891-39ff8fe68689%26LOGINUSING%26client_id%3DAppV3_Web%26redirect_uri%3Dhttps%253A%252F%252Fbarik.ehswatch.com%252Fsignin-oidc%26response_type%3Dcode%2520id_token%26scope%3Dopenid%2520profile%2520role%2520email%2520phone%2520AuthServer%2520IdentityService%2520AdministrationService%2520SaasService%2520EmployeeService%2520IncidentService%2520AttachmentService%2520ObservationsService%2520ActionService%2520UserTaskService%2520HSEPlansService%2520NCRService%2520CustomerService%2520InspectionService%2520Forms%2520FileManagement%2520RMService%2520TMService%26response_mode%3Dform_post%26nonce%3D638071898544026331.ZDQ2YmMzZGEtNmM1Ny00NzU5LTlkOTgtY2M2NTUwMDNiNjk3OTQ1MDc5ZjEtMzliZS00OGYxLWFiNWQtMTdjZGJjOWNjZTY5%26state%3DCfDJ8FRhYrLUrBdPg2ipof6Ze14mEFk5bIQXNQjsIL-lp9gw5t-ix4H0JDqNfa76u7WhP6qsyI5e9taMVSetz5Crd4zSk8hxuws0GCunnqJ5kjJkvYdYkuUO7-vQMrG9PJP66ngYwgXW_2hv1sGNa3NDcK4UlBH36zJe3Gqvzfa4WM-73PcKiOkE1tEcodC8eoWv4-AGfrlnx3YVov5CZ6dm0-d8C376N7R-f9SjQlsK2vif_Waams8HN9V5tElVd5JxJPoHTuj8PIclJ0r8TF5lJKTwPVTCo-7otEd2RrMpmiU-qiPsR12iRM5aT6_KKU5vtRgrIfmLOu_AOsWb4PLQSfI%26x-client-SKU%3DID_NET6_0%26x-client-ver%3D6.21.0.0

builder.WebHost.ConfigureKestrel(x => x.Limits.KeepAliveTimeout = xx);

hummm, Yes. we already tried this but no luck. anyway will try once again with different ways and update you back.