- Exception message and full stack trace:
- Steps to reproduce the issue: It is currently unclear how to reproduce this.
We saw some other support tickets that also had the same issue, where they couldn't identify where the problem came from, but they were able to solve the issue without communicating the solution.
It seems that for whatever reason, we are having the issue from the above screenshot in only one of our databases (DEV database) and all other databases, including local developer databases are working perfectly fine.
If I connect my Host project to that database, I get the same issue. I couldn't find anything strange in the tables. I've tried truncating all the Features relates tables (Features, FeatureGroups and FeatureValues) to no avail.
It seems that this issue only comes from accessing the application-configuration endpoint. And since blazor always goes through that endpoint first, we can't even properly run our blazor app with this issue.
Have you had this issue in the past? Were you able to fix it for others too?
We also tried to import the Features module to add breakpoints to some suspected code, but we could only import the FeatureManagement module. Is there a way to import the Features module via ABP-CLI or ABP-Suite? We can't find that module using abp list-modules command.
5 Answer(s)
-
0
Hi,
AuditLogging.SettingManagementfeature is defined inVolo.Abp.AuditLogging.Application.Contractspackage. Does your application have reference to that package and also[DependsOf(typeof(AbpAuditLoggingApplicationContractsModule))]attribute over the module class?If your architecture tiered, some dependnecies might be missing, you can check and add this package and attribute if not exist
-
0
Yeah we seem to have that (screenshot below). We never had a problem with it until something random happened. And now this issue only comes up when we connect to that very specific database. When connecting to other databases it works fine. Db Migrations don't help and clearing all the features tables doesn't help either.
-
0
Is your solution is micro-service template?
You got this log on which database you trying to connect? Which service/application shows this log?
-
0
Our solution is monolith-tiered. All of our services connect to the same database. We just have different environments like DEV/QA/PROD and each have their own databases. The DEV database is suddenly showing this error.
This includes not only the Host.Api project in our deployed azure environment that connects to the DEV database, but also when I remotely connect my local running Host.Api project on my computer to the DEV database.
The errors are coming from the Host.Api project.
-
0
The exception is thrown from there: https://github.com/abpframework/abp/blob/e23e92e8e181a093746d4d5d41e7ef2773a76ea5/framework/src/Volo.Abp.Features/Volo/Abp/Features/FeatureDefinitionManager.cs#L27
It should be get from StaticStore, but it seems there is a missing configuration and it's not defined. Can you make sure your HttpApi.Host project has direct or indirect reference to
Volo.Abp.AuditLogging.Application.Contractpackage? Normally it should.
