Hi Tamas,

Can you post the log file with the error ?

From the screenshots you've sent me by email it seems that licensing server is either returning a not authorized status or non-professional license type. To be more accurate I would need some actual log files. Also you can ask them to go to the Product Activation window and hit CTRL+F10 and run the licensing diagnostics. This might also provide some details about their current setup.

PS: You can insert images if you use rich formatting when replying.

What kind of log files do you think about?

Studio logs or if there is some kind of logging on the plugin.

Hi,

this is what the diagnostics tool returns:

Does this contain anything useful?

Running Licensing Diagnostics - 01.12.2014 16:45:52

Current licensing provider: SafeNetRMS

Using license server: True

Licensing server name: XXXXX

License status: NotAuthorized

License mode: Lease

License mode details: UnlimitedUsage

An exception occurred while running the diagnosis - Sdl.Common.Licensing.Provider.SafeNetRMS.SafeNetRMSLicensingProviderException: Could not get feature AllowDomainExecution activation ID.

  at Sdl.Common.Licensing.Provider.SafeNetRMS.LicenseFeature.GetActivationID()

  at Sdl.Common.Licensing.Provider.SafeNetRMS.LicensingProvider.GetDiagnosticInfo()

End ----------------------------------------

Thanks,

Tamas

This seems to be a configuration issue with SafeNet network licensing and is not related to Studio API. This can have multiple reason so my suggestion would be to ask them to contact SDL support.

Are they using the SafeNet licensing provider introduced in SP2 or are they still using the Nalpeiron License provider?  

If they are still using Nalpeiron then ask them to change the following value in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SDL\Studio2License

CurrentLPID - should be set to: Nalpeiron

If they are using SafeNet then there is another issue related to the app not working with the safenet license.

Thanks for the tip, in the meantime, the client already resolved the problem. It turned out that this issue was specific to one single PC. They created another test environment, and there it works correctly. Thank you for your help!

Tamas

Thanks for the tip, in the meantime, the client already resolved the problem. It turned out that this issue was specific to one single PC. They created another test environment, and there it works correctly. Thank you for your help!

Tamas