Hello support team,
we follow the steps to create a blazor ui based project from commerical abp. while setting up everything and reach to run and see the screen of app, we are seeing this error "Error: Volo.Abp.AbpException: Undefined permission: AbpId"
Can you please help us out to resolve this issue. Thank you
- ABP Framework version: latest
- UI type: Blazor
- DB provider: EF Core
- **Tiered (MVC) **: no
15 Answer(s)
-
0
Sadly, ABP Suite is completely broken currently for Blazor as reported in several other threads here like this one and in the sticky for 4.4.4
https://support.abp.io/QA/Questions/2124/ABP-Suite-broken-with-Blazor-Server-and-client
https://support.abp.io/QA/Questions/2109/VoloAbpAbpException-Undefined-permission
https://support.abp.io/QA/Questions/1543/Bugs--Issues-v44X#answer-23dbf383-327f-fea0-4c51-3a001cefbe40
The complete silence from the support team about this is worrying...
-
0
Hi,
ABP Framework version: latest
Are you using version 4.4.4 or 5.0.0.beta3?
-
0
Hi,
ABP Framework version: latest
Are you using version 4.4.4 or 5.0.0.beta3?
Hi,
As there are several customers who have reported the same problem, the information is currently a bit spread out unfortunately. We initially wrote in the 4.4.4 bug thread but when we got no reply there, we created a new thread. Maybe you should try to collect all related posts in just one thread or something like that.
We tried creating new blazor projects with ABP Suite and CLI 4.4.4 installed, both with stable and preview. The problems we got where kind of the same, maybe that the one based on the 4.4.4 never worked, but the one based on beta 3 worked sometimes (as strange as that might seem) which had us wondering if it could be VS2022/.net initially, but all problems when away when we downgraded to ABP 4.4.3). Also please note that the project wouldn't even build in VS2019 (latest version) as mentioned in the 4.4.4 bug thread. Something strange is going on here, but as it seem to affect other customers as well, it probably isn't my local configuration etc.
Having downgraded to 4.4.3 and made sure new project were created with 4.4.3 packages (using CLI), everything seem to be working again.
-
0
Hi @improwise,
I tried it again, but there is no problem, as you know I can't solve this problem if I can't reproduce. If you can provide a project I believe I can help you solve this problem quickly
-
0
Hi,
Was able to recreate the same problem with ABP Suite and CLI 4.4.3 as ABP Suite seem to go for the latest packages regardless of version. Will email it to you know with "instructions".
-
0
Hello Guys, that's correct. One some computers it is creating problem with 4.4.4 and also with 4.4.3 where as on some it is working ok with 4.4.3 and even 4.4.4.
but issue is its not working on our systems.
-
0
Hello Guys, that's correct. One some computers it is creating problem with 4.4.4 and also with 4.4.3 where as on some it is working ok with 4.4.3 and even 4.4.4.
but issue is its not working on our systems.
If you create a new project in ABP Suite, and first just build it in VS2019 and then rebuild it, is it a difference? We have noticed that sometimes it works when you build it first time, but when you rebuild it, it will not even compile in VS2019. In VS2022 it will still compile with rebuild all, but instead fail runtime.
This with ABP 4.4.4 packages (which ABP Suite will use regardless of version, or at least use the latest version of packages).
-
0
Hello Guys, that's correct. One some computers it is creating problem with 4.4.4 and also with 4.4.3 where as on some it is working ok with 4.4.3 and even 4.4.4.
but issue is its not working on our systems.
If you create a new project in ABP Suite, and first just build it in VS2019 and then rebuild it, is it a difference? We have noticed that sometimes it works when you build it first time, but when you rebuild it, it will not even compile in VS2019. In VS2022 it will still compile with rebuild all, but instead fail runtime.
This with ABP 4.4.4 packages (which ABP Suite will use regardless of version, or at least use the latest version of packages).
it builds successfully, but when you see the first page. you are seeing exception in inspect window with the error above mentioned.
-
0
Hello Guys, that's correct. One some computers it is creating problem with 4.4.4 and also with 4.4.3 where as on some it is working ok with 4.4.3 and even 4.4.4.
but issue is its not working on our systems.
If you create a new project in ABP Suite, and first just build it in VS2019 and then rebuild it, is it a difference? We have noticed that sometimes it works when you build it first time, but when you rebuild it, it will not even compile in VS2019. In VS2022 it will still compile with rebuild all, but instead fail runtime.
This with ABP 4.4.4 packages (which ABP Suite will use regardless of version, or at least use the latest version of packages).
it builds successfully, but when you see the first page.
you are seeing exception in inspect window with the error above mentioned.Yes, that is what we get in VS2022, where it still builds. In VS2019 however, it will not build at all after we do a rebuild (rebuild all), but instead complain about:
Severity Code Description Project File Line Suppression State Error CS1576 The line number specified for #line directive is missing or invalid BlazorTest1.Blazor M:*************\BlazorTest1\aspnet-core\src\BlazorTest1.Blazor\obj\Debug\net5.0\Razor\Components\Layout\MainFooterComponent.razor.g.cs 111 Active
-
1
I have the same issue, with all combination of CLI & nuget 4.4.4 / 5.0.0-beta3 on Blazor Server with EfCore. 1st run all is ok 2nd run error and log truncated: Unhandled exception in circuit '1p-8ASDVzLQleQfw2SNY1-9IQo226k0XJ5M-bbKlSC4'. Volo.Abp.AbpException: Undefined permission: AuditL
Undefined permission can be different on each run, and this appen only if there is an instance of browser left open
-
0
I have the same issue, with all combination of CLI & nuget 4.4.4 / 5.0.0-beta3 on Blazor Server with EfCore. 1st run all is ok
2nd run error and log truncated: Unhandled exception in circuit '1p-8ASDVzLQleQfw2SNY1-9IQo226k0XJ5M-bbKlSC4'. Volo.Abp.AbpException: Undefined permission: AuditLUndefined permission can be different on each run, and this appen only if there is an instance of browser left open
Just to clarify, this is what we are seing also. That if you manage to compile it, it seem to work first time but then not again. I think that when we messed around with it a bit, we got some idea that it could be related to if you were authenticated or not and that clearing cookies could sometimes have an effect. But if that was some random thing or not we never managed to figure out before we gave up and downgraded to 4.4.3.
I do believe that we can say that enough users are affected by this in some way or another so that we can conclude that it is an actual real problem with ABP 4.4.4 / and beta 5 and not just something related to bad configuration on a single development machine etc. And since everything seem to work fine when you downgrade to 4.4.3 (at least it seems to do for us), I guess it is unlikely that it is due to problems with VS2022 or .net 5/6 even though you can of course never be sure.
-
0
Hi,
I reproduced this problem using VS 2022, but it is a random occurrence. I have no idea yet, but I will continue to investigate
This problem does not occur with
dotnet runcommand orRider.Can you try use
dotnet runto test it? -
0
VS 2022 using dotnet run with 5.0.0-beta3 same random error with log truncated: Volo.Abp.AbpException: Undefined permission: IdentityServer.IdentityResourc
This is new for me: [12:14:55 WRN] Unhandled exception rendering component: Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at Volo.Abp.AspNetCore.Components.Web.LeptonTheme.Components.ApplicationLayout.MainHeader.MainHeader.Dispose() at Microsoft.AspNetCore.Components.Rendering.ComponentState.Dispose() at Microsoft.AspNetCore.Components.RenderTree.Renderer.Dispose(Boolean disposing) [12:14:55 WRN] Unhandled exception rendering component: Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at Volo.Abp.AspNetCore.Components.Web.LeptonTheme.Components.ApplicationLayout.Navigation.MainSiderbar.Dispose() at Microsoft.AspNetCore.Components.Rendering.ComponentState.Dispose() at Microsoft.AspNetCore.Components.RenderTree.Renderer.Dispose(Boolean disposing) [12:14:55 ERR] Unhandled exception in circuit 'n4jrJsB74BSqQoAm48gqZ7JuicaORcTXqEymb55ZBek'. System.AggregateException: Exceptions were encountered while disposing components. (Object reference not set to an instance of an object.) (Object reference not set to an instance of an object.) ---> System.NullReferenceException: Object reference not set to an instance of an object. at Volo.Abp.AspNetCore.Components.Web.LeptonTheme.Components.ApplicationLayout.MainHeader.MainHeader.Dispose() at Microsoft.AspNetCore.Components.Rendering.ComponentState.Dispose() at Microsoft.AspNetCore.Components.RenderTree.Renderer.Dispose(Boolean disposing) --- End of inner exception stack trace --- ---> (Inner Exception #1) System.NullReferenceException: Object reference not set to an instance of an object. at Volo.Abp.AspNetCore.Components.Web.LeptonTheme.Components.ApplicationLayout.Navigation.MainSiderbar.Dispose() at Microsoft.AspNetCore.Components.Rendering.ComponentState.Dispose() at Microsoft.AspNetCore.Components.RenderTree.Renderer.Dispose(Boolean disposing)<---
-
0
On VS2022 with 5.0.0-rc1 seem to be working.
-
0
I have the same problem also !!!!
Is there already a solution for this problem ? this getting really annoying and time consuming.
I always start from a new solution created from abp suite. I tried already several versions 4.4.3 , 4.4.4 , aswel visual studio 2019 and 2022
Today i also tried version 5.0.0-RC1 (visual studio 2022) - complete new solution
I run the blazor projects as well in chrome, safari, microsoft edge...
Tried it on 3 different laptops. On 2 laptops i have local admin rights (but the pc is moderated by my customer/company), On my personal laptop , i have all rights. But doesn't seem to make any difference.
I can always build / run complete solution. Also the initial database migration works with DBMigration
And I always get the same error
Important info : the same solution/project runs without any problem for my fellow developer (located in Pakistan, i'm lcoated in europe)
I'm really stuck and i lost already a week finding a solution ....
We moved from the asp.net zero framework to abp.commercial for the blazor support, but I'm getting the feeling that this what not a good move !!!!
Please help
