License check failing #10636

5 Answer(s)

• 

  0

  AI-Bot created 4 months ago

  Support Team ABP Agent

  • This error is coming from ABP Commercial licensing. It typically happens in CI/CD, containers, or Azure Functions/App Services when the deployed environment doesn’t have an ABP CLI login/license session available, so runtime license validation fails and it prints “you should login to abp.io”.

  • Do not create a new project to fix it. The fix is to ensure the environment that builds/publishes (or runs, depending on your setup) has a valid ABP commercial license context.

  Solution

  1. Confirm the exact license error code in logs

     • Look for messages like:
       • ABP-LIC-0008 - License check failed for '...' You need to log in using the command abp login <username>.
       • or ABP-LIC-0018 - ... Your trial period has ended!
     • These two have different resolutions (login/session vs trial/production mismatch).

  2. Re-login on the build/deploy machine (or pipeline agent) using ABP CLI

     • On the machine that produces the deployment artifacts, run:

  abp login <your-abp-io-email>
  

  • Then rebuild and redeploy.

  3. If this started after “AI Management”

     • Adding a commercial module can trigger license checks in places that previously didn’t need them (e.g., your Azure Function now references contracts/packages that require license validation). The deployment environment must be properly licensed/logged in.

  4. If the issue is actually “trial ended” but you have a production license

     • This is usually caused by a stale/old trial login/session cached on the machine. Follow the “purchased a license from trial” cleanup steps referenced by ABP support:
     • If you still can’t see the product key/license details in the organization UI, that’s account/license administration (not a code issue).

  5. Account / product key not visible

     • This is license/account administration; please contact ABP directly:
       • https://abp.io/contact

  Sources

  • ABP support thread pointing to ABP-LIC-0008 guidance: https://abp.io/support/questions/5662
  • ABP-LIC-0008 article: https://support.abp.io/QA/Questions/245/ABP-LIC-0008---License-check-failed-for-%27XXXXX%27
  • Related licensing problem thread: https://abp.io/support/questions/6663
  • How to delete current license login session (useful when switching from trial to production): https://support.abp.io/QA/Questions/817/How-to-delete-current-license-login-session
  • Trial ended / production license mismatch discussion and fix reference: https://abp.io/support/questions/10531
  • “Purchased a license from Trial” fix steps: https://abp.io/support/questions/3931/I-purchased-a-license-from-Trial-License---ABP-LIC-0018#answer-c86140f4-9845-c223-2e3e-3a0721603a9a
  • Contact: 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

  matt@fleetsafe.ai created 4 months ago

  we tried this and its still failing. We reverted back to an older version before we added AI management and get this error now.

  We signed in to the CLI on local machine, then did a manual publish to the function.

  2026-05-02T04:27:45 [Information] [04:27:44 INF] FTCloud coalescer ? geofence forwarder subscription installed 2026-05-02T04:28:08 [Information] Response [467494cb-18b2-471d-9ffa-ef09776274a3] 201 Created (00.0s) ETag:"0x8DEA80326CEFA2A" Server:Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0 x-ms-request-id:a4b7b793-c01e-0004-63ec-d9d541000000 x-ms-client-request-id:467494cb-18b2-471d-9ffa-ef09776274a3 x-ms-version:2024-11-04 x-ms-lease-id:582f174f-8a23-7e65-590c-dd68e089bdc9 Date:Sat, 02 May 2026 04:28:07 GMT Content-Length:0 Last-Modified:Sat, 02 May 2026 04:27:42 GMT 2026-05-02T04:28:11 [Information] [04:28:11 ERR] ABP-LIC-ERROR - License check failed for 'Volo.Abp.OpenIddict.Pro.Domain-v10.0.2.0'.

  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 4 months ago

  Support Team Fullstack Developer

  Hi,

  The error ABP-LIC-ERROR - License check failed for 'Volo.Abp.OpenIddict.Pro.Domain-v10.0.2.0' means the running process can't find your license code at startup. It's not related to the AI Management module — any ABP commercial module (OpenIddict.Pro, Identity.Pro, etc.) does the same check. That's also why rolling back to the previous code didn't help: the issue is on the deployment side, not in your code.

  ABP reads the license code from configuration with the key AbpLicenseCode. In a project generated by ABP Studio, this value lives in appsettings.secrets.json next to each host project (e.g. *.Web.Host, *.AuthServer, *.HttpApi.HostWithIds):

  {
    "AbpLicenseCode": "PABMAGkAYwBlAG4Acw...=="
  }
  

  A couple of quick questions to confirm where the gap is:

  1. Open your local solution and check any host project — do you see an appsettings.secrets.json with an AbpLicenseCode value? (If yes, that's the value we need.)
  2. Is the Azure Function project the one being deployed, or one of the standard ABP host projects?

  For Azure Functions, appsettings.secrets.json usually doesn't get picked up automatically (it's not part of the default Function host configuration, and even if you publish the file, the Functions runtime won't load it unless you wire it up explicitly). The cleanest fix is to set AbpLicenseCode as an Application Setting on the Function App itself:

  1. Azure Portal → your Function App → Settings → Environment variables (older portals: Configuration → Application settings)
  2. Add a new setting:
     • Name: AbpLicenseCode
     • Value: paste the long base64 string from appsettings.secrets.json
  3. Save and restart the Function App.

  ASP.NET Core's environment variables provider exposes this to IConfiguration["AbpLicenseCode"], so the license check will pass without depending on whether the secrets file gets published.

  If you can't find AbpLicenseCode anywhere in your local solution, let me know and I'll help you locate / regenerate it.

  Thanks

  Markdown supported.

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

  Save Cancel
• 

  0

  matt@fleetsafe.ai created 4 months ago

  we just found if we set the asp environment to staging it works, when set to development it is doing the license checks. We need some assurance as what we need to do, we tried logging in on the cli of the dev pc and then publishing to dev environment which has the development aspdotnet environment set, for the function and still had the license check error

  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 4 months ago

  Support Team Fullstack Developer

  Hi,

  Glad you spotted the difference — this is actually by design.

  ABP runs an online license check only when ASPNETCORE_ENVIRONMENT=Development (or the debugger is attached). In any other environment (Staging, Production, etc.) only the offline check runs, which just needs the AbpLicenseCode value from configuration.

  The online check expects the abp login token file (%UserProfile%\.abp\cli\access-token.bin on Windows, ~/.abp/cli/access-token.bin on Linux) to be present in the process's user home directory at runtime. That's why logging in on the dev PC and publishing didn't help — that file lives under your dev user profile, it's not part of the project, so dotnet publish doesn't include it. And even if you copied it into the Function, the token is bound to the developer machine identity, so it's not the right thing to ship to Azure anyway.

  Recommendation for the Azure Function:

  1. Set ASPNETCORE_ENVIRONMENT to Staging or Production in the Function App's Environment variables — never Development for a deployed environment.
  2. Make sure AbpLicenseCode is also set there (the long base64 string from your local appsettings.secrets.json).

  With those two settings, only the offline check runs and it will pass without needing any abp login state on the server.

  Treat Development as something only your local dev machine ever uses — it assumes there is an interactive developer with an active abp login session.

  Thanks

  Markdown supported.

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

  Save Cancel