Stores the location of the floating license database on the end user system and returns an error message in case of failure. To read the location, use the ReadFloatingLicenseLocation API. To clear the stored information, use the DeleteKeys API.
C#: StoreFloatingLicenseLocation(string floatingLicenseDbPath, out bool userLevelResult, out bool machineLevelResult, out string errorMessage)
StoreFloatingLicenseLocation returns true if either the user level or the machine level operation is successful.
- floatingLicenseDbPath- full path (in UNC format) to the floating license database.
- userLevelResult- returned boolean value indicating whether the operation was successful at the user level.
- machineLevelResult- returned boolean value indicating whether the operation was successful at the machine level.
- errorMessage- returned error message containing details about the failure, if any.
QLM stores its data in two locations: one location at the user level and another location at the machine level. The StoreKeysOptions property controls where data is stored.
Additionally, the StoreKeysLocation property controls whether data is stored on the file system or in the registry.
Data on the file system
If you are running XP, the folders are:
C:\Documents and Settings\<your account name>\Application Data\IsolatedStorage\*
C:\Documents and Settings\All Users\Application Data\IsolatedStorage
On Windows 7 or higher, the folders are:
Example on Windows 7 or higher:
Under these folders, a file whose name is the GUID associated to your product (GUID in Define Products page) is created and contains the license keys.
Data in the registry
When QlmLicense.StoreKeysLocation is set to EStoreKeysTo.ERegistry, QLM tries to stores the keys in 2 registry hives, one hive at the user level and one hive at the machine level.
On a 32 bit OS, QLM will write license information to:
On a 64 bit OS, QLM will write license information to: