Activities of "EngincanV"

[nacho] said:

[EngincanV] said:

[nacho] said: Thanks, bot! 🙂ABP team, I reported this so you can take a look, as it could become a time-consuming issue if all three developers are experiencing the same problem.I hope the information provided is enough to investigate. If not, I’d be happy to show you the issue live by sharing my screen, just let me know.

Hi, sorry for the bot's response, it sometimes helps :)

Thanks for the detailed information and sharing the appsettings.json file with the error logs, this helps a lot to identify the problem.

[ERR] Error getting value from 'MigrationsMigrationsDbContext' on 'Volo.Abp.Suite.Models.Solution'.

Before you update the appsettings.json file, do you remember the value of the MigrationsMigrationsDbContext field? Also, I will create a tiered solution and try to understand the problem better, but by any chance, can you also share the not-updated (default) values of the appsettings.json file, so I can see the changes and check at the code level? (I'll try to identify at which point ABP Suite is currently unable to determine the related path)

Regards.

No, sorry... we don't have the previous appsettings.json. When we encountered the issue, we removed the solution from ABP Suite and tried to add it again (also without success). What we can share with you (preferably in an online meeting) are the error messages and logs we get when trying to add or open the solution in ABP Suite (after removing the solution from ABP Suite). That might be a quicker way for you to troubleshoot the issue.

Thanks for the update. Actually, I've created a tiered application just before and will try to reproduce it on my side. If i can't do it, I might need your help, I'll let you know.

Thanks again. Regards.

[danielgan] said: FAQ suggests that without the abp key, apps are perpetual and are still supposed to run without the obligation to renew. However, the reply from the bot is that ABP commercial license is time-based.

Hi, sorry for the inconvenience, and please ignore the bot’s response.

As mentioned on our FAQ page, ABP licenses are perpetual, meaning you can continue using them without needing to renew. There are some limitations after your subscription ends, such as losing access to version upgrades and tools like ABP Suite but your existing applications and usage remain fully valid and unaffected.

Please let me know if you have any further questions.

Hi, since you're using a tiered application, by design, the HttpApi.Host and AuthServer projects have direct access to the database and are responsible for exposing the necessary APIs. The UI layer (typically the Web project) consumes these APIs.

Would it be possible for you to implement your logic in the HttpApi.Host project to return the background image as a URL, and then use that URL in your Web project? Or is there a specific reason this approach doesn’t work for your case?

If there’s something I’m missing, could you please clarify and provide a bit more detail so we can better assist you?

Regards.

Hi, we've assigned an Angular developer to assist you with your question. To help her support you more efficiently, could you please share the following information:

• ABP version of your projects
• Your ABP Suite version

Regards.

[nacho] said: Thanks, bot! 🙂 ABP team, I reported this so you can take a look, as it could become a time-consuming issue if all three developers are experiencing the same problem. I hope the information provided is enough to investigate. If not, I’d be happy to show you the issue live by sharing my screen, just let me know.

Hi, sorry for the bot's response, it sometimes helps :)

Thanks for the detailed information and sharing the appsettings.json file with the error logs, this helps a lot to identify the problem.

[ERR] Error getting value from 'MigrationsMigrationsDbContext' on 'Volo.Abp.Suite.Models.Solution'.

Before you update the appsettings.json file, do you remember the value of the MigrationsMigrationsDbContext field? Also, I will create a tiered solution and try to understand the problem better, but by any chance, can you also share the not-updated (default) values of the appsettings.json file, so I can see the changes and check at the code level? (I'll try to identify at which point ABP Suite is currently unable to determine the related path)

Regards.

Hi, could you please send an email to license@abp.io regarding this issue? This platform is focused on technical support, and licensing-related questions are best handled directly by our licensing team.

In your email, please include the following details to help us assist you faster:

• Whether your NuGet.Config file includes the https://nuget.abp.io feed.
• Whether your appsettings.secrets.json contains the AbpLicenseCode (or any related configuration).

Providing this information will help us identify and resolve the issue more efficiently.

Thanks for your understanding. Best regards.

[vkelwan] said: We already Run the Migrations for Both PostGres service and MongoDb Service. Also there is no option to provide permissions for role or user and also not appear in the database.

We also take reference from community post and also check sample code given in repository, but it did not helped me in sorting this out.

So help me.

Hi, by any chance, can you share your solution via email (to support@abp.io with the ticket number), so I can directly check it through your project?

Update: I'm able to reproduce this problem and created an internal issue (#20272).

[cstobler] said: Thanks for looking into this. I deleted all of the migrations, created a new one using the CLI, and the new migration was again empty: I'm not sure what is going on here. I can delete the databases if necessary, like I said, there is no permanent data on there that needs to persist. But I'm not sure how to go about this in a way that will result in a clean slate. I checked your documentation and the book, and they both say to just run DbMigrator to create a new database, which worked for me in the beginning but obviously isn't working now.

Charlie

Sorry, I forgot to mention that. Yes, you should delete your database because otherwise EF Core looks into Migrations History table and thinks that all other migrations are already applied and needs to create a new one. If you delete your database or change the connection string and re-create a new migration, then it should fill up with all the database tables.

[cstobler] said: I zipped up my solution folder and sent it via email with the ticket number.

Additionally, not sure the best way to show this, but here are my tables so you can see that it doesn't have SaasTenants, or the other tables I was expecting:

My database is still being used for testing and can easily be recreated, so if we need to recreate it, that is totally fine.

Charlie

Hi again, thanks for sharing your project. I've downloaded and checked it. It seems the configurations are right, but weirdly, your migration structure was broken. As you indicated in your email, if the migrations are not important for you and if it's okay for you, you can delete all migrations and create a fresh migration, then you should be able to see the related database table in your database:

You can see the screenshot above as an example. I've deleted all migration files, and then created a new initial one. (Probably, since in the free version there are tenant related tables coming from the TenantManagement Module, it might cause some problems. Resetting the migrations fix the problem)

Regards.