ASP.NET StoreKeys not writing to registry

Follow

Jonathan A. Brown

August 21, 2017 12:43

On my Windows 10 development computer, I can call StoreKeys and it works correctly. I can go into the Registry and find the matching GUID that indicates the license was stored.

However, when I deploy my ASP web app to a Windows Server 2012 R2 server, it does not Store the Key in the registry, as when I go to search for it, it isn't there. I have run and installed the software, as well as input the activation key, from  an administrator account.

I have QLM Pro. 

0

• Official comment

  

  Soraco Technologies August 21, 2017 13:43

  Hi Jonathan

   

  Writing to the registry requires specific privileges. Typically, an ASP.NET application runs in the context of an Application Pool and an Application Pool runs as a specific user. 

  Please confirm the following:

  1. You are activating the license in the context of your ASP.NET app and not from an external tool like the QLM License Wizard (exe).

  2. Your ASP.NET app has its own Application Pool

  3. You have set the QlmLicense.StoreKeysOptions property to EStoreKeysOptions.EStoreKeysPerUser or 

  EStoreKeysOptions.EStoreKeysPerUserAndMachine

  4. If you are running the latest version of QLM v10, please try the sample that we provide in this folder and verify if it works as expected for you:

  C:\Users\Public\Documents\Quick License Manager\Samples\qlmpro\Windows\DotNet\C#\QlmAspDotNetSample

   

  Regards

  John

  Comment actions Permalink
• 

  Jonathan A. Brown August 21, 2017 19:32

  It was the Application Pool. I had it set to DefaultApplicationPool, which uses AplicationPoolIdentity instead of Local System. Changing to Local System allowed it to store the keys in the registry.

   

  Thank you very much.

  0

  Comment actions Permalink
• 

  Soraco Technologies August 21, 2017 20:46

  Excellent.

  If you are satisfied with our support or product, we would very much appreciate some feedback:

  • Leave Feedback on Google (recommended)
  • Leave Feedback and follow us on our Facebook page
  • Follow us on our LinkedIn page

   

  0

  Comment actions Permalink

Please sign in to leave a comment.