Upgrade from 9.2.1 to 10.5.0 #10791

2 Answer(s)

• 

  0

  AI-Bot created 2 months ago

  Support Team ABP Agent

  • ABP-LIC-0016 means ABP’s license system blocked loading a commercial (Pro) module at runtime.
    In your case, after upgrading to 10.5.0, your app now references/loads these Pro modules:

    • Volo.Abp.Account.Pro.Admin.HttpApi
    • Volo.Abp.TextTemplateManagement.HttpApi

  • Fix it by choosing one of these options:

    1. Use a license that includes these modules
       Ensure the environment where you run the app has a valid ABP license setup (and that your license tier actually includes Account Pro Admin and Text Template Management). If your company license should include them, proceed with option (3) too.

    2. Remove/stop referencing the modules (if you don’t intend to use them / your license doesn’t include them)

       • Remove the related Volo.Abp.* NuGet packages from the solution (both host and any layer that references them).
       • Remove them from your module dependency chain ([DependsOn(...)]) so they are not loaded.

    3. Re-login with ABP CLI (most common cause after upgrades/new machines/CI): expired or missing CLI token Run this on the machine that builds/runs the solution:

  abp login <username> -p <password>
  

   Then clean + rebuild and run again.
  

  • This error is a known symptom of an expired ABP CLI token:

    • https://abp.io/support/questions/791

  • If you believe you should have access based on your license but it still fails after abp login, contact ABP support with your license/order details:

    • https://abp.io/contact

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 2 months ago

  Support Team Fullstack Developer

  Hi,

  ABP-LIC-0016 comes from the runtime module license check. It only runs during local development — when you run the app from your IDE (a debugger is attached) or with ASPNETCORE_ENVIRONMENT=Development. It reads the license from the account you're signed in with via abp login on that machine, asks the server which modules that account is granted, and checks the loaded assemblies against it. So the message means the signed-in account isn't granted these modules for v10.

  Account.Pro.Admin and TextTemplateManagement are included in all commercial licenses (Team included), so this isn't a tier problem. Since you're on a tiered/separated setup, the two names are just the modules that logged it in your AuthServer and API host.

  The usual cause is the signed-in account. Having a license on the organization, or being only an Owner, isn't enough — the tools grant the license to accounts that hold a Developer seat.

  1. Open https://abp.io/my-organizations and check whether the account you use is listed under Developers (not only under Owners). You can be both at the same time.
  2. If it's missing there, an organization owner adds it to the Developers list.
  3. Re-login on the machine you run the app from — the membership is cached, so restarting isn't enough:

  abp logout
  abp login <username>
  

  Then start the app again.

  If it still fails after signing in with a correct Developer account, send us the account/email you use plus the full startup logs from both hosts (in particular whether an ABP-LIC-ERROR line follows the ABP-LIC-0016), and we'll check what's granted for that account on our side.

  To confirm which account is active on the machine showing the error, run abp login-info and share the account it prints.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel