Skip to main content

ASP.NET StoreKeys not writing to registry

Jonathan A. Brown

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

Comments

3 comments

Date Votes
  • Official comment
    Soraco Technologies

    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

  • Jonathan A. Brown

    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
  • Soraco Technologies

    Excellent.

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

     

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post
Powered by Artica