In addition, you may also set an own CleanUpTime at 'CmAccess2()' using the CMCREDENTIAL structure Whether the license is still valid and meanwhile the unit counter has not a value of 0 or the expiration time has reached.Ģ.

Morever, at 'CmCrypt()'/'WupiCheckLicense()' also the license itself is checked, i.e. Using 'CmCrypt()' you may encrypt/decrypt data increasing security. On encryption or on calling 'CmCrypt()'/'WupiCheckLicense()' in the code. In order to avoid the automatic release of handles as described in 2.c), you should:Ī) manually release all handles no longer required after the access using 'CmRelease()'/'WupiFreeLicense()'.ī) regularily use handles responsible for counting licenses or license management as in AxProtector runtime check using 'CmAccess2()’,Ĭ) the handles were not used longer than the specified CleanUpTimeOut value (default 120 minutes).ġ.

The check for the processes is performed for each new license access, e.g. CodeMeter itself automatically release handles, if:Ī) the CmDongle was disconnected to which the handles previously referred to,ī) the process which opened the handles no longer exists. This renders all handles invalid and reusing handles in your software result in error 106.Ģ. You use a protected software or a software applying CodeMeter Code API/Wupi API and while doing so restart the CodeMeter service. This may, for instance, happen in the following cases:ġ. The error 106 refers to an 'invalid handle' and occurs if a handle was used CodeMeter does not know. CodeMeter with a SAP back office solution.SAP Entitlement Management and CodeMeter.

Turn off codemeter runtime server