Licensing Error with new version 1.0.2.075

Home Forums Forums SW1 Support Forum Licensing Error with new version 1.0.2.075

This topic contains 2 replies, has 2 voices, and was last updated by  ludopatico 9 years, 2 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #1340

    ludopatico
    Participant

    Hello,
    when I open SitNGo Wizard a popup form appear:

    Licensing Error

    when I push the button “Fix it” SGW open and I see correctly the word “registered” in the title bar.
    But if I close and reopen SGW the popup form appear again.
    I attach the code of the error:

    Syncfusion Licensing System – Detailed diagnostics.

    ErrorKind = RuntimeLicensedComponentEntryMissing

    UsageMode = Runtime

    IsAspDotNet = False

    RuntimeLicenseKey = No runtime license key found in licx.

    ExecutingVersionInfo = Syncfusion.Core, Version=7.2.0.21, Culture=neutral, PublicKeyToken=632609b4d040f6b4

    ExecutingVersionInfoFromAssembly = Syncfusion.Core.Licensing.FusionLicenseProvider, Syncfusion.Core, Version=7.403.0.0, Culture=neutral, PublicKeyToken=632609b4d040f6b4

    ErrorMessage = Unable to grant a runtime license. Please ensure that the project was compiled with an appropriate licenses.licx file as an embedded resource.

    Clicking the button below will launch a utility that will adjust your project settings appropriately.

    Assemblies with licenses.licx resource:

    SitNGoWizard.UI.2.0, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null

    Syncfusion.Core entries found in licenses.licx files:

    Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core, Version=12.4350.0.0, Culture=neutral, PublicKeyToken=632609b4d040f6b4

    Thank you
    Andrea Lanza

    #1343

    SitNGo Wizard
    Keymaster

    Please download the release again. The problem should be fixed.

    #1344

    ludopatico
    Participant

    Thank you,
    the problem is fixed now.

    Regards
    Andrea Lanza

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.