ComponentOne 2026v1.413 - No runtime license is available

ComponentOne 2026v1.413 - No runtime license is available

Posted by: enrique.pv-ext on 30 September 2026, 5:43 am EST

• 

  enrique.pv-ext

  • Post Options:
  • Link
    Copy

  Posted 30 September 2026, 5:43 am EST - Updated 30 September 2026, 5:48 am EST

  I update - Versión:

  4.8.20252.399

  →

  4.8.20261.413

  • C1.Web.Wijmo.Controls.48

    :

  • HintPath

    :
    
    

    ..\..\..\libs\ComponentOne\2025v2.399\bin\v4.8\C1.Web.Wijmo.Controls.48.dll

    →

    ..\..\..\libs\ComponentOne\2026v1.413\bin\C1.Web.Wijmo.Controls.48.dll

    • Versión:

      4.8.20252.399

      →

      4.8.20261.413

  Now, I get the error:

  No runtime license is available. The application cannot run without a valid license. Please install a valid license key.
  Descripción: Excepción no controlada al ejecutar la solicitud Web actual. Revise el seguimiento de la pila para obtener más información acerca del error y dónde se originó en el código.
  
  Detalles de la excepción: C1.Util.Licensing.LicenseException: No runtime license is available. The application cannot run without a valid license. Please install a valid license key.
  
  
  
  [LicenseException: No runtime license is available. The application cannot run without a valid license. Please install a valid license key.]
     C1.Util.Licensing.SA3ProviderInfo.Validate(Type type, Object instance, Boolean allowExceptions, Boolean isDesignTime) +596
     C1.Web.Wijmo.Controls.C1Menu.C1Menu.VerifyLicense() +37
     C1.Web.Wijmo.Controls.C1Menu.C1Menu..ctor() +198
  

  Error
  
  

  

  1391×735 60 KB

  License Manager
  
  

  

  798×348 44.3 KB

  Control Panel
  
  

  please, any solution about it ??
  
  

  

  1552×813 86.4 KB

• 

  enrique.pv-ext

  • Post Options:
  • Link
    Copy

  Posted 30 September 2026, 5:53 am EST - Updated 30 September 2026, 8:52 am EST

  files

  licenses.licx ??

  WebApp.gclicx ? vs WebApp.sa3licx ??

  Do I need this ??

  . To resolve this issue, please generate and embed a runtime license in your project using the steps below:

  Open Command Prompt or PowerShell and navigate to your project directory (where the *.csproj file is located).

  Run the following command to generate the runtime license:

  C:\ProgramData\GrapeCity\gclm\gclm.exe “66129dc3-6206-4481-af49-00d38c22db2d” -lc “.gclicx” “”

  Please replace with your actual project name.

  In Visual Studio, select your project and enable the “Show All Files” option in Solution Explorer.

  Right-click the generated *.gclicx file and select “Include In Project”.

  Right-click the *.gclicx file again and open its Properties.

  Set the Build Action property to “Embedded Resource”.

  https://developer.mescius.com/forums/webforms-edition/runtime-license-file-clarifications

  Hi,

  All queries related to pricing, purchases, and subscriptions are handled by the sales team, not the support team. We kindly request that you contact them directly for such inquiries.

  The pipeline-related questions you raised are covered in our documentation on Pipeline Licensing - https://developer.mescius.com/componentone/docs/license/online-license/common-licensing-scenarios/licensing-apps-on-docker-with-pipeline

  To license your projects, you can embed either a licenses.licx file or a .gclicx file in your project. During the build process (on the pipeline machine), the pipeline license should be activated on that machine, allowing the build to succeed without any issues. So, it is not necessary to generate a runtime license (.gclicx file) on the pipeline machine itself.

  To license an application, you must first activate the license on the machine using the GCLM tool.

  After that, your project must include a valid embedded license file in order to run without any licensing errors. Since your project is an ASP.NET WebForms application based on .NET Framework, it can be licensed using either a licenses.licx file (design-time license) or a .gclicx file (runtime license).

  The licenses.licx file is generated automatically when you open the ASPX designer and drag-drop or modify a C1 control. Similarly, the .gclicx file is also generated automatically when you drag -drop a C1 control (due to the Visual Studio extension installed by the C1 installer)

  In summary, your project must include either a valid licenses.licx file or a .gclicx file to be licensed correctly.

  gclicx problem ?

  C:\ProgramData\GrapeCity\gclm\

  cd “C:\ProgramData\GrapeCity\gclm”

  gclm.exe “” -lc xxxx.WebApp.gclicx “xxxxx.WebApp”

  xxxxx.WebApp.gclicx
  
  Build Action = Embedded Resource
  
  Copy to Output Directory = Do not copy ??

  and C:\ProgramData\SA3 ?? sa3client-ui.exe ??

• 

  enrique.pv-ext

  • Post Options:
  • Link
    Copy

  Posted 30 September 2026, 10:11 am EST - Updated 30 September 2026, 10:14 am EST

  Verified Status
  
  │ File │ Status │ Details

  Properties\licenses.licx │ │ All 15 entries are already using Version=4.8.20261.413.

  xxxxx.WebApp.sa3licx │ │ Visual Studio automatically added
  
  Generated │ and to the end of the .csproj file (line 3506, in its own ItemGroup). No manual action is
  
  embedded required on your part.

  xxxxx.WebApp.gclicx │ No │ The content is byte-for-byte identical to the previous version │ │ changes │ (it still contains v2024.2 in the decoded payload).

  Important explanation

  The .sa3licx file is the new runtime licensing mechanism from Mescius/GrapeCity (based on SA3 = Software Activation 3), which replaces the older .gclicx mechanism (GCLM) in more recent product versions.

  Therefore:

  The .sa3licx file references C1S43693510…033, which matches exactly the activated license we already found in:

  C:\ProgramData\SA3\products\C1S\C1S4369351000000000033.license

  The .gclicx file did not change because it is likely no longer the active licensing mechanism for this product version. Since 2026v1.413 uses SA3, Visual Studio simply left the file as-is and did not regenerate it because it is no longer what the product uses.

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 1 October 2026, 12:38 am EST

  Hello Enrique,

  You’re right, the *.gclicx file is no longer needed. Starting with 2025v2.1, C1 licenses controls through a *.sa3licx file, so you can remove the *.gclicx file from your project.

  Visual Studio has already generated the *.sa3licx file, and its ‘Build Action’ is set to ‘Embedded Resource’, so this error shouldn’t appear. Please clean and rebuild the project, then share the Visual Studio build output so we can investigate.

  If the error still appears after the rebuild, generate a new *.sa3licx file with the command below, add it to your project, and set its ‘Build Action’ to ‘Embedded Resource’. Assuming your application name is ‘xxxxx.WebApp’, the command is:

  sa3client lc -p "C1S,C1P(2024.2.0.0-)" -t "xxxxx.WebApp" -o "xxxxx.WebApp.sa3licx"
  

  Note: Run the command from the project folder (the one that contains the .csproj file). Then enable “Show All Files” in Solution Explorer and use “Include In Project” on the generated file before setting its Build Action. These are the same steps you followed earlier for the *.gclicx file, so please repeat them for the *.sa3licx file.

  For more details, see the documentation: https://developer.mescius.com/componentone/docs/license/online-license/common-licensing-scenarios/create-runtime-license

  Regards,
  
  Uttkarsh