Summary

Help to alleviate some issues with Trusted Storage breaking on a client machine.

Symptoms

This article should help to alleviate some issues with Trusted Storage breaking on a client machine.

Cause

Trusted Storage can break if any of the Bindings that determine if a license has been moved and has been changed within certain tolerances. Also if the anchoring for a particular fulfilment becomes corrupted or changed, this will also lead to a break.

Another cause for breakage in trusted storage has been found to be caused by the number of anchors that have been used for the fulfilment record. In operations 11.5 and earlier it has been found that track zero anchoring was disabled by default. This could lead to problems if the registry anchor was deleted or corrupted; there was nothing to fall back on. If track zero anchoring was enabled it would also fix the registry anchor and vice versa.

Resolution

To help alleviate any issues that a customer may be facing, you should ensure that as many trusted storage bindings are being used as possible. This may seem counter intuitive, but each binding has a certain weight that determines the overall health of the fulfilment. The more bindings you have the more stable the fulfilment will be.

Another way to help keep the trusted storage fulfilment safe is to upgrade the licensing service to the latest version of FlexNet Publisher. In FlexNet Publisher 11.6.1 there was a trusted storage backup function included in the licensing service; this would overwrite any corrupted trusted storage file with an older copy that worked. This would help to ensure that the change of breakages wou ld be reduced.

Also ensure that track zero anchoring is enabled in the transaction key settings for the licenses that you are attempting to create.