[]
DOCS DEMOS BLOGS SUPPORT PRICING EULA
(Showing Draft Content)

Troubleshooting

The ComponentOne licensing process is designed to minimize manual intervention. However, licensing issues can occur due to configuration problems, missing files, or build-time errors.

If you encounter runtime license error messages or license warning dialogs, review the sections below to help identify and resolve the issue.

Troubleshooting Current ComponentOne Licensing

Use this section for current ComponentOne product versions.

1. Verify that the serial key is activated.

Ensure that the serial key is activated on the machine that builds the project.

  • Use the MESCIUS License Manager or the command-line tool to confirm activation.

  • From the command line, you can list activated licenses:

sa3client list

If the license is not activated, activate it using a valid serial key.

See Activating a Serial Key.

2. Verify the licenses.licx file (.NET Framework only).

For WinForms, WPF, and ASP.NET Web Forms projects targeting .NET Framework:

  • Confirm that a licenses.licx file exists in the project’s Properties folder.

  • Verify that the file contains the full names of all referenced ComponentOne components.

  • Remove version-specific information if present.

For more information, see Licensing .NET Framework Applications.

3. Verify the runtime license file (.sa3licx).

Ensure that the runtime license file is generated and included with the application.

  • Check the build output folder (for example, obj/Debug or obj/Release).

    • The file may not appear in the output for some .NET Framework projects.

  • If the file is included in the project:

    • Confirm that its Build Action is set to Embedded Resource.

  • If the file was generated manually (for example, using sa3client license-compile):

    • Verify that the correct target names and paths were specified.

4. Verify licensing for libraries and user controls.

If you are using ComponentOne controls in a library or user control:

  • Ensure the project is licensed for this usage scenario.

  • For WinForms and WPF:

    • Confirm that the licenses.licx file is embedded as a resource when required.

    • Verify that a corresponding .sa3licx file is generated and embedded when applicable.

See Licensing User Controls for details.

5. Review build output.

Check the Output window during build for warnings or errors related to licensing.

These messages often indicate issues with license generation or embedding.

6. Generate a runtime license log (if needed).

If the issue is not resolved, generate a runtime license log to share with the support team.

Generate a Log

On the machine where the issue occurs, enable logging:

sa3client log --on

Rebuild and run the application. One or more log files will be generated in the SA3 log folder.

After collecting the logs, disable logging:

sa3client log --off

Troubleshooting Licensing Using GrapeCity License Manager (GCLM)

Use this section only if your product version requires GCLM.


1. Verify that the serial key is activated.

Ensure the serial key is activated on the machine that builds the project.

  • Run gclm.exe and verify that the product is activated.

  • If it is not activated, activate it using a valid serial key.

See Activating a Serial Key.


2. Verify the licenses.licx file (.NET Framework only).

For WinForms, WPF, and ASP.NET Core Web Forms projects:

  • Confirm that a licenses.licx file exists in the Properties folder.

  • Verify that the file contains the correct full names of referenced components.

  • Remove version-specific information if present.

See Licensing .NET Framework Applications.


3. Verify the runtime license file (.gclicx).

Ensure that the runtime license file is generated and included correctly.

  • Check the build output folder (obj/Debug or obj/Release).

    • The file may not appear in the output for .NET Framework applications.

  • If the file is included in the project:

    • Confirm that its Build Action is set to Embedded Resource.

  • If the file was generated manually:

    • Verify that the correct entry assembly name or public key token was used.

4. Verify licensing for libraries and user controls.

If you are using ComponentOne controls in a library or user control:

  • Ensure the project is licensed for this usage scenario.

  • For WinForms and WPF:

    • Confirm that the licenses.licx file is embedded as a resource when required.

See Licensing User Controls.

5. Review build output.

Check the Output window during build for warnings or errors related to licensing.

6. Generate a runtime license log (GCLM).

If further investigation is required:

  1. Create a folder named Log at:

    C:\\ProgramData\\GrapeCity\\gclm

  2. Rebuild and run the application.

  3. One or more log files will be generated in the folder.

  4. Share the log files with the support team.

  5. Delete the Log folder to disable logging.

Troubleshooting older licensing models

If you are working with older technologies such as .NET 2.0, .NET 4.0, ActiveX, Silverlight, LightSwitch, or ComponentOne versions released prior to 2020 v2, see Troubleshooting Old Licensing.

Contact Support

If you are unable to resolve the issue, get in touch with the MESCIUS support team.