Hi,

I'm a bit annoyed that SDL support have redirected me here but I'm hoping that someone will be kind enough to point me in the right direction or confirm that support are responsible for this matter. We use Quahill (www.quahill.com) for project management which uses the project automation API. When I try to create a project from Quahill via the API, I get a license check error from Safenet.

A similar problem with an open exchange app is mentioned here https://community.sdl.com/developers/language-developers/f/57/t/3203#pi239031345filter=all&pi239031345scroll=false. It seems like the safe net network license is not configured correctly and when I check licence diagnostics under product activation with CTRL + F10 it seems that there is a problem:

FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
at System.IO.StreamReader..ctor(String path, Encoding encoding)
at System.IO.File.InternalReadAllLines(String path, Encoding encoding)
at System.IO.File.ReadAllLines(String path)
at Sdl.Common.Licensing.Provider.SafeNetRMS.LicenseFeature.GetActivationID()
at Sdl.Common.Licensing.Provider.SafeNetRMS.LicensingProvider.GetDiagnosticInfo()
End ----------------------------------------

As you can see the professional license is active. 

Please note I am using SDL Studio 2014 SP2 with safenet network licensing and that the Quahill software works properly if a trial professional license is installed on the client but it does not work on any PC in our office using a network license.

As this is not the first time I have had to wrangle with support about configuring the safenet license properly, I'd really welcome a definitive answer. Generally, I've received good support from SDL but recently this seems to sadly have slipped recently. Logging a support incident also costs us a lot of time as it only seems to work properly in Chrome. I guess it's probably time that we raise these issues with our SDL representative...

Regards,

Daniel