Activities of "cellero"

On further investigation it seems it may be related to the Syncfusion Blazor Grid and Kanban components we are using. I will log a ticket with Syncfusion to see if it is a known issue for them.

We have reviewed support cases #6280 and #5289 which describe identical issues. We've implemented the recommended workarounds: • Increased DisconnectedCircuitRetentionPeriod to 30 minutes • Increased DisconnectedCircuitMaxRetained to 1000 • Added circuit handler with ObjectDisposedException catching • Increased Hub timeout intervals However, our application is still experiencing fatal crashes (application process termination with IsTerminating: true). The exceptions are occurring on background threads from LeptonX theme component event handlers, NOT in the circuit inbound activity pipeline. Specific question: Are there any updates or patches since cases #6280 and #5289 were closed? Our crash pattern suggests the issue extends beyond what the circuit handler can catch.

Are there any updates or patches since cases #6280 and #5289 were closed? Our crash pattern suggests the issue extends beyond what the circuit handler can catch.

Ok, the database size issue has been sorted.
Can you log in then log out to experience the 403 - Forbidden: Access is denied.

Thanks!

Can you expand on the suggested Ensure Claims/Permissions Are Refreshed: Where should this code go?

I can replicate this each time I choose logout from the top right menu:

Blazor Web App ABP 9.2.2

On a production system, I am able to log in and use the system all ok. But often when logging back in a 403 - Forbidden: Access is denied error is given. Looking at the logs there are a bunch of "PermissionRequirement" messages.

This looks similar to this support case: https://abp.io/support/questions/8904/Returning-user-causes-permissions-to-fail-in-blazor-app

2025-08-09 15:25:11.480 +10:00 [INF] Request starting HTTP/1.1 GET https://cellero.net/Error?httpStatusCode=404 - null null 2025-08-09 15:25:11.482 +10:00 [INF] Executing endpoint 'Volo.Abp.AspNetCore.Mvc.UI.Theme.Shared.Controllers.ErrorController.Index (Volo.Abp.AspNetCore.Mvc.UI.Theme.Shared)' 2025-08-09 15:25:11.482 +10:00 [INF] Route matched with {action = "Index", controller = "Error", area = "", page = ""}. Executing controller action with signature System.Threading.Tasks.Task`1[Microsoft.AspNetCore.Mvc.IActionResult] Index(Int32) on controller Volo.Abp.AspNetCore.Mvc.UI.Theme.Shared.Controllers.ErrorController (Volo.Abp.AspNetCore.Mvc.UI.Theme.Shared). 2025-08-09 15:25:11.482 +10:00 [INF] Executing ViewResult, running view ~/Views/Error/404.cshtml. 2025-08-09 15:25:11.484 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: SettingManagement.Emailing 2025-08-09 15:25:11.484 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpAccount.SettingManagement 2025-08-09 15:25:11.484 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpIdentity.SettingManagement 2025-08-09 15:25:11.485 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AuditLogging.AuditLogs.SettingManagement 2025-08-09 15:25:11.485 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: FeatureManagement.ManageHostFeatures 2025-08-09 15:25:11.485 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: Saas.SettingManagement 2025-08-09 15:25:11.486 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: SettingManagement.Emailing 2025-08-09 15:25:11.486 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpAccount.SettingManagement 2025-08-09 15:25:11.486 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpIdentity.SettingManagement 2025-08-09 15:25:11.486 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AuditLogging.AuditLogs.SettingManagement 2025-08-09 15:25:11.487 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: FeatureManagement.ManageHostFeatures 2025-08-09 15:25:11.487 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: Saas.SettingManagement 2025-08-09 15:25:11.488 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: SettingManagement.Emailing 2025-08-09 15:25:11.488 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpAccount.SettingManagement 2025-08-09 15:25:11.488 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpIdentity.SettingManagement 2025-08-09 15:25:11.488 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AuditLogging.AuditLogs.SettingManagement 2025-08-09 15:25:11.488 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: FeatureManagement.ManageHostFeatures 2025-08-09 15:25:11.488 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: Saas.SettingManagement 2025-08-09 15:25:11.489 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: SettingManagement.Emailing 2025-08-09 15:25:11.489 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpAccount.SettingManagement 2025-08-09 15:25:11.490 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AbpIdentity.SettingManagement 2025-08-09 15:25:11.490 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: AuditLogging.AuditLogs.SettingManagement 2025-08-09 15:25:11.490 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: FeatureManagement.ManageHostFeatures 2025-08-09 15:25:11.490 +10:00 [INF] Authorization failed. These requirements were not met: PermissionRequirement: Saas.SettingManagement

Hi everyone,

We sincerely apologize for the issue caused by the recent release with a 3rd party component. The affected versions are 9.0.7 and 9.1.0, other versions don't have any issue. We understand how frustrating it is, especially when it affects live systems. The ABP project, like other software solutions, includes many 3rd party components, and sometimes there may be problems with them. We contacted our 3rd party vendor and completely fixed the case.

The issue is now resolved, and here's the quick fix:

1. Run this command on your development computer to clear your local NuGet cache:
   dotnet nuget locals all --clear

2. Uninstall and install ABP Suite again:
   abp suite remove
abp suite install

3. Rebuild your ABP solution and publish it again to your live environment

Thank you for your patience, and we truly appreciate the feedback. We're taking extra measures to prevent this in future releases.

– ABP Team

I'm sorry, that is not an explanation of what went wrong, and gives us no reassurance that it won't happen again.

We have customers that cannot tolerate an outage like this, and saying "someone else will fix it in the next day" is NOT an acceptable answer. Being may time zones away that means we are effectively shutting down their business for at least a day.

We put a LOT of effort into creating an offline build so that we are not affected by a temporary outage of any NuGet servers, but this problem stopped logins in code that was already functional and deployed. That means that 1 of 2 things happened, both of which are unacceptable:

1. A component in our compiled code is reaching out to a server live to determine if it is allowed to run
2. A license code embedded in our dependencies has an expiration date that we do not know about

We need to answer our organizations with a specific cause for this outage, or we will be forced to abandon ABP entirely (which we do not want to do).

Well said. I 100% agree. I am watching this space for ABP to acknowledge this is an architectural flaw and needs to be rectified.

When using the ABP Docs module in a Blazor WebApp the left side bar menu does not render. There is empty space where the menu and branding should be:

Menu:

context.Menu.AddItem( new ApplicationMenuItem( ConcreteMenus.UserDocs, l["Menu:Docs"], url: "/Documents", icon: "fa fa-question-circle", order: 600 ) );

Please advise how to render the side bar menu correctly.

Thanks.

ABP Version: 9.1.0 UI: Blazor WebApp DB: EF

How did it suddenly stop working? We had a functional 9.1.0 build that was working without errors.

This is a serious / important question. I had a fully deployed system that stopped working due to this issue.
The system has a requirement to have high availability.

My customer will not accept this type of architecture whereby the site availability is dependent on a third party.

@ABP - Do you agree? Do you think a chance is required here?

hi karl.ettinger

Can you rebuild and publish the website?

Sorry for your production website. Please get in touch with us(info@abp.io). We will do something.

Hi Maliming, I would like to understand this as well. I also had a site go down.
I am concern that a fully deployed system has dependencies on ABP.

Can you please advise what is being done to prevent this.

Thank you.