In This Topic
We try to make the licensing process as unobtrusive as possible, but problems may occur for a number of reasons. If you experience any runtime license error messages or nag screens, review this checklist to help resolve the problem.
- Make sure your serial key has been activated on the machine which builds the project.
- Run the MESCIUS License Manager (gclm.exe) and check the product is activated. If not, activate with a valid serial key. See Activating a Serial Key.
- For WinForms, WPF and ASP.NET Web Forms projects make sure the licenses.licx file is correct.
- Check that the licenses.licx file has been generated in the "Properties" folder within the project.
- Check that the licenses.licx file contains all of the referenced components full names correctly.
- Update the license.licx file to remove version specific information. See Licensing .NET Framework Applications.
- Make sure the runtime license file (.gclicx) is being generated and included in the application output.
- Check the license file is found in the build output (obj/Debug or obj/Release). It will not exist here for .NET Framework applications.
- Check the license file is included with the project and its Build Action is set to Embedded resource.
- If you manually generated the license file, check it's generated with correct Entry Assembly Name or Public Key Token.
- If using the ComponentOne controls in a library (such as a UserControl), check that you licensed it properly for this use case. See Licensing User Controls.
- For WinForms and WPF user controls, check that the build action of the licenses.licx file is set to Embedded resource.
- Check that there are any errors or warnings in the output window during build. They may indicate the license issues.
- If everything above appears OK, you can generate a log for the runtime license to share with our support team.
- If working with older versions (.NET 2.0, .NET 4.0, ActiveX, Silverlight, LightSwitch, or any ComponentOne version prior to 2020 v2), see Troubleshooting Old Licensing.
Generate a Runtime License Log
- Create a "Log" folder at "C:\ProgramData\GrapeCity\gclm" on the machine.
- Rebuild and run the problematic application on your machine, and one or more log files will be generated in the folder.
- Share the log file with us.
- Remember to delete the "Log" folder to disable the logging.
Contact Our Support Team
Get in touch with our support team and we will help resolve your licensing issue.