We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

Licensing Error

Thread ID:

Created:

Updated:

Platform:

Replies:

37541 Nov 24,2005 03:50 AM Dec 22,2005 08:54 PM General Discussion 24
loading
Tags: General Discussion
Denny Huang
Asked On November 24, 2005 03:50 AM

I am using VC++ as the development language. Every time when I run the built result, a Licensing Error dialog box pop up, and ask me to fix the Licensing Error. Even though I pressed the ''Fix'' button, that dialog box pop up again the next time when I ran the rebuilt result. It seems that the license enabler can fix C# project, but fail to fix VC++ project. you can see the attachment for message in the Licensing Error dialog box Please help. Denny

attachment.zip

Daniel Jebaraj [Syncfusion]
Replied On November 25, 2005 08:39 AM

Hi Denny. Please follow the steps detailed in this KB article. Thank you for using Syncfusion products. Best regards, Daniel >I am using VC++ as the development language. Every time when I run the built result, a Licensing Error dialog box pop up, and ask me to fix the Licensing Error. > >Even though I pressed the ''Fix'' button, that dialog box pop up again the next time when I ran the rebuilt result. > >It seems that the license enabler can fix C# project, but fail to fix VC++ project. > >you can see the attachment for message in the Licensing Error dialog box > >Please help. > >Denny

attachment.zip

Daniel Jebaraj [Syncfusion]
Replied On November 25, 2005 08:40 AM

Sorry, the link was incorrect. Correct link is given below. http://www.syncfusion.com/support/kb/studio/Default.aspx?ToDo=view&questId=17 Best regards, Daniel >Hi Denny. > >Please follow the steps detailed in this KB article. > >Thank you for using Syncfusion products. > >Best regards, >Daniel > >>I am using VC++ as the development language. Every time when I run the built result, a Licensing Error dialog box pop up, and ask me to fix the Licensing Error. >> >>Even though I pressed the ''Fix'' button, that dialog box pop up again the next time when I ran the rebuilt result. >> >>It seems that the license enabler can fix C# project, but fail to fix VC++ project. >> >>you can see the attachment for message in the Licensing Error dialog box >> >>Please help. >> >>Denny

attachment.zip

Denny Huang
Replied On November 28, 2005 04:07 AM

Hello Daniel, Thanks for your reply. I did the LC.exe thing and still get some trouble. When I run the commamd following your instruction, I got the following error: (1) : error LC0003 : Unabled to resolve type ''Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core'' Creating Licenses file d:\emc\myprojects\src\eslez\debug\eslez.exe.licenses...

Daniel Jebaraj [Syncfusion]
Replied On November 28, 2005 09:21 AM

Hi Denny, Do you have Syncfusion.core.dll in the GAC? Best regards, Daniel >Hello Daniel, >Thanks for your reply. I did the LC.exe thing and still get some trouble. >When I run the commamd following your instruction, I got the following error: > >(1) : error LC0003 : Unabled to resolve type ''Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core'' >Creating Licenses file d:\emc\myprojects\src\eslez\debug\eslez.exe.licenses...

Denny Huang
Replied On November 29, 2005 12:39 AM

In "C:\WINNT\assembly", there are two items of Syncfusion.core. One is 3.301.0.0 and the other is 3.300.0.0. >Hi Denny, > >Do you have Syncfusion.core.dll in the GAC? > >Best regards, >Daniel > >>Hello Daniel, >>Thanks for your reply. I did the LC.exe thing and still get some trouble. >>When I run the commamd following your instruction, I got the following error: >> >>(1) : error LC0003 : Unabled to resolve type ''Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core'' >>Creating Licenses file d:\emc\myprojects\src\eslez\debug\eslez.exe.licenses...

Daniel Jebaraj [Syncfusion]
Replied On November 30, 2005 02:57 AM

Hi Denny, The presence of multiple versions in the GAC should be fine. Did you install Essential Studio on this system or is it a build system to which assemblies are copied as part of the build? Can you run Utilities\License Manager and check the keys that are present on the system. This error typically occurs if the keys are invalid or inaccessible. Please let me know what you see. Thanks, Daniel >In "C:\WINNT\assembly", there are two items of Syncfusion.core. One is 3.301.0.0 and the other is 3.300.0.0. > >>Hi Denny, >> >>Do you have Syncfusion.core.dll in the GAC? >> >>Best regards, >>Daniel >> >>>Hello Daniel, >>>Thanks for your reply. I did the LC.exe thing and still get some trouble. >>>When I run the commamd following your instruction, I got the following error: >>> >>>(1) : error LC0003 : Unabled to resolve type ''Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core'' >>>Creating Licenses file d:\emc\myprojects\src\eslez\debug\eslez.exe.licenses...

Denny Huang
Replied On November 30, 2005 04:59 AM

Hi Daniel, I installed Essential Studio on this system on my system. After run License Manager and re-run Assembly Manager, I got the same Error. Please help. >Hi Denny, > >The presence of multiple versions in the GAC should be fine. Did you install Essential Studio on this system or is it a build system to which assemblies are copied as part of the build? > >Can you run Utilities\License Manager and check the keys that are present on the system. This error typically occurs if the keys are invalid or inaccessible. > >Please let me know what you see. > >Thanks, >Daniel > >>In "C:\WINNT\assembly", there are two items of Syncfusion.core. One is 3.301.0.0 and the other is 3.300.0.0. >> >>>Hi Denny, >>> >>>Do you have Syncfusion.core.dll in the GAC? >>> >>>Best regards, >>>Daniel >>> >>>>Hello Daniel, >>>>Thanks for your reply. I did the LC.exe thing and still get some trouble. >>>>When I run the commamd following your instruction, I got the following error: >>>> >>>>(1) : error LC0003 : Unabled to resolve type ''Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core'' >>>>Creating Licenses file d:\emc\myprojects\src\eslez\debug\eslez.exe.licenses...

Daniel Jebaraj [Syncfusion]
Replied On December 3, 2005 09:56 AM

Hi Denny, Sorry for the delay in getting back on this. I will have an update for you by Monday. Best regards, Daniel >Hi Daniel, >I installed Essential Studio on this system on my system. After run License Manager and re-run Assembly Manager, I got the same Error. Please help. > >>Hi Denny, >> >>The presence of multiple versions in the GAC should be fine. Did you install Essential Studio on this system or is it a build system to which assemblies are copied as part of the build? >> >>Can you run Utilities\License Manager and check the keys that are present on the system. This error typically occurs if the keys are invalid or inaccessible. >> >>Please let me know what you see. >> >>Thanks, >>Daniel >> >>>In "C:\WINNT\assembly", there are two items of Syncfusion.core. One is 3.301.0.0 and the other is 3.300.0.0. >>> >>>>Hi Denny, >>>> >>>>Do you have Syncfusion.core.dll in the GAC? >>>> >>>>Best regards, >>>>Daniel >>>> >>>>>Hello Daniel, >>>>>Thanks for your reply. I did the LC.exe thing and still get some trouble. >>>>>When I run the commamd following your instruction, I got the following error: >>>>> >>>>>(1) : error LC0003 : Unabled to resolve type ''Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core'' >>>>>Creating Licenses file d:\emc\myprojects\src\eslez\debug\eslez.exe.licenses...

Daniel Jebaraj [Syncfusion]
Replied On December 5, 2005 08:04 AM

Hi Denny, The problem is that lc.exe requires full version information. Please change your licx file entry for Syncfusion to be. Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core, Version=3.301.0.0, Culture=neutral, PublicKeyToken=632609b4d040f6b4 This should fix the problem. Sorry for the delay in getting back to you. Best regards, Daniel >Hi Denny, > >Sorry for the delay in getting back on this. I will have an update for you by Monday. > >Best regards, >Daniel > >>Hi Daniel, >>I installed Essential Studio on this system on my system. After run License Manager and re-run Assembly Manager, I got the same Error. Please help. >> >>>Hi Denny, >>> >>>The presence of multiple versions in the GAC should be fine. Did you install Essential Studio on this system or is it a build system to which assemblies are copied as part of the build? >>> >>>Can you run Utilities\License Manager and check the keys that are present on the system. This error typically occurs if the keys are invalid or inaccessible. >>> >>>Please let me know what you see. >>> >>>Thanks, >>>Daniel >>> >>>>In "C:\WINNT\assembly", there are two items of Syncfusion.core. One is 3.301.0.0 and the other is 3.300.0.0. >>>> >>>>>Hi Denny, >>>>> >>>>>Do you have Syncfusion.core.dll in the GAC? >>>>> >>>>>Best regards, >>>>>Daniel >>>>> >>>>>>Hello Daniel, >>>>>>Thanks for your reply. I did the LC.exe thing and still get some trouble. >>>>>>When I run the commamd following your instruction, I got the following error: >>>>>> >>>>>>(1) : error LC0003 : Unabled to resolve type ''Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core'' >>>>>>Creating Licenses file d:\emc\myprojects\src\eslez\debug\eslez.exe.licenses...

Denny Huang
Replied On December 5, 2005 09:58 PM

Thanks Daniel. The license file can be generated now, but we met the same problem posted by Konstantin in "Licencing problem" Please help ////////////////////// Syncfusion Licensing System - Detailed diagnostics. UsageMode = Runtime IsAspDotNet = False RuntimeLicenseKey = No runtime license key found in licx. ExecutingVersionInfo = Syncfusion.Core.Licensing.FusionLicenseProvider, Syncfusion.Core, Version=3.3.0.0, Culture=neutral, PublicKeyToken=632609b4d040f6b4 ErrorMessage = Assemblies with licenses.licx resource: eSLEz, Version=1.0.2166.19422, Culture=neutral, PublicKeyToken=null No Syncfusion.Core entries found in licenses.licx files. ///////////////////////////

Bryant Cobarrubias
Replied On December 8, 2005 07:02 PM

I hope this helps... I just had a problem that gave the same error message. I had to open the licx file in notepad and delete all references to Syncfusion. Then I saved the file and rebuilt my solution.

Denny Huang
Replied On December 8, 2005 10:44 PM

Hi Bryant, Thanks for your information. Do you mean that I can fix the problem by modifying the binary licx file generated by LC.exe? coz. the licenses.licx (text format)only has one line. Thanks, Denny >I hope this helps... > >I just had a problem that gave the same error message. I had to open the licx file in notepad and delete all references to Syncfusion. Then I saved the file and rebuilt my solution.

Denny Huang
Replied On December 14, 2005 03:55 AM

Still anybody taking care of this issue?

Administrator [Syncfusion]
Replied On December 14, 2005 01:14 PM

Hi Denny, Could you try adding the following line to your licenses.licx file? Syncfusion.Core.Licensing.FusionLicenseProvider, Syncfusion.Core, Version=3.3.0.0, Culture=neutral, PublicKeyToken=632609b4d040f6b4 After compiling the .licx file with that entry once with LC.exe, your system should remember how to resolve our licenses in the future. Please let me know if this doesn''t work. Regards, Gregory Austin Syncfusion Inc.

Administrator [Syncfusion]
Replied On December 15, 2005 01:08 AM

Hi Gregory, I am using VC++ .NET and already upgraded to Essential Studio v4.1. I modified my licenses.licx as your direction. It still doesn''t work. Thanks, Denny >Hi Denny, > > Could you try adding the following line to your licenses.licx file? > >Syncfusion.Core.Licensing.FusionLicenseProvider, Syncfusion.Core, Version=3.3.0.0, Culture=neutral, PublicKeyToken=632609b4d040f6b4 > > After compiling the .licx file with that entry once with LC.exe, your system should remember how to resolve our licenses in the future. > > Please let me know if this doesn''t work. > >Regards, >Gregory Austin >Syncfusion Inc.

Denny Huang
Replied On December 15, 2005 01:20 AM

Here is the Error MSG ///////////////// Syncfusion Licensing System - Detailed diagnostics. UsageMode = Runtime IsAspDotNet = False RuntimeLicenseKey = No runtime license key found in licx. ExecutingVersionInfo = Syncfusion.Core.Licensing.FusionLicenseProvider, Syncfusion.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=632609b4d040f6b4 ErrorMessage = Assemblies with licenses.licx resource: eSLEz, Version=1.0.2175.25655, Culture=neutral, PublicKeyToken=null No Syncfusion.Core entries found in licenses.licx files. ///////////////// >Hi Gregory, >I am using VC++ .NET and already upgraded to Essential Studio v4.1. >I modified my licenses.licx as your direction. It still doesn''t work. >Thanks, > >Denny > >>Hi Denny, >> >> Could you try adding the following line to your licenses.licx file? >> >>Syncfusion.Core.Licensing.FusionLicenseProvider, Syncfusion.Core, Version=3.3.0.0, Culture=neutral, PublicKeyToken=632609b4d040f6b4 >> >> After compiling the .licx file with that entry once with LC.exe, your system should remember how to resolve our licenses in the future. >> >> Please let me know if this doesn''t work. >> >>Regards, >>Gregory Austin >>Syncfusion Inc.

Administrator [Syncfusion]
Replied On December 16, 2005 01:45 AM

Hi Denny, when you go to "Properties" for licenses.licx in your project, is the Build Action set to "Embedded Resource"? If not that would explain why it does not show up in the diagnostics under >Assemblies with licenses.licx resource: Stefan

Denny Huang
Replied On December 16, 2005 03:12 AM

Hi Stefan, refering to articles in forums, I compile licenses.licx with LC.exe manually first, then link the output as "Embedded Managed Resource". All is because I am using VC++. >Hi Denny, > >when you go to "Properties" for licenses.licx in your project, is the Build Action set to "Embedded Resource"? > >If not that would explain why it does not show up in the diagnostics under > >>Assemblies with licenses.licx resource: > >Stefan >

Administrator [Syncfusion]
Replied On December 16, 2005 03:12 PM

Hi Denny, When you added the entry, did you use your new version (4.1.0.4) instead of 3.3.0.0? Regards, Gregory Austin Syncfusion Inc.

Denny Huang
Replied On December 18, 2005 04:31 AM

Hi Gregory, here is the content of my licenses.licx file: Syncfusion.Core.Licensing.FusionLicenseProvider, Syncfusion.Core, Version=4.101.0.4, Culture=neutral, PublicKeyToken=632609b4d040f6b4 Please tell me if any thing wrong. Thanks, Denny >Hi Denny, > > When you added the entry, did you use your new version (4.1.0.4) instead of 3.3.0.0? > >Regards, >Gregory Austin >Syncfusion Inc.

Administrator [Syncfusion]
Replied On December 20, 2005 02:26 PM

Hi Denny, What worked for me was including both your current entry and Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core, Version=4.101.0.4, Culture=neutral, PublicKeyToken=632609b4d040f6b4 in the licenses.licx file. Regards, Gregory Austin Syncfusion Inc.

Denny Huang
Replied On December 20, 2005 09:25 PM

Hi Gregory, I let the licenses.licx fle has both lines, and it still pops up the Error MSG box. the following is how I gave the lc.exe command. please check. Thanks, Denny ///////////////////////////// lc /target:D:\EMC\MyProjects\Src\eSLEz\debug\eSLEz.exe /complist:D:\EMC\MyProjects\Src\eSLEz\eSLEz\licenses.licx /i:C:\Program Files\Syncfusion\Essential Studio\Assemblies\1.1\Syncfusion.Core.DLL //////////////////////////// >Hi Denny, > > What worked for me was including both your current entry and > >Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core, Version=4.101.0.4, Culture=neutral, PublicKeyToken=632609b4d040f6b4 > >in the licenses.licx file. > >Regards, >Gregory Austin >Syncfusion Inc. > >

Administrator [Syncfusion]
Replied On December 21, 2005 01:50 PM

Hi Denny, From my experience, putting only the final name of the executable on the command line, instead of the full path works much better. Could you try this command line? lc /target:eSLEz.exe /complist:D:\EMC\MyProjects\Src\eSLEz\eSLEz\licenses.licx /i:C:\Program Files\Syncfusion\Essential Studio\Assemblies\1.1\Syncfusion.Core.DLL Regards, Gregory Austin Syncfusion Inc.

Denny Huang
Replied On December 22, 2005 08:54 PM

Hi Gregory, It works! Thanks a lot. Denny >Hi Denny, > > From my experience, putting only the final name of the executable on the command line, instead of the full path works much better. Could you try this command line? > >lc /target:eSLEz.exe /complist:D:\EMC\MyProjects\Src\eSLEz\eSLEz\licenses.licx /i:C:\Program Files\Syncfusion\Essential Studio\Assemblies\1.1\Syncfusion.Core.DLL > >Regards, >Gregory Austin >Syncfusion Inc.

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;