We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome,
Internet Explorer 11,
Safari. Thank you!
AR# 64439: Licensing - Borrow fails: (xilinxd) Activation error (-161,62002:0) No fulfillment exists in trusted storage which matches the request
Licensing - Borrow fails: (xilinxd) Activation error (-161,62002:0) No fulfillment exists in trusted storage which matches the request
I am unable to borrow an activation license that appears to be borrowable.
The Vivado License Manager (VLM) shows the following message:
License was unable to be borrowed, but the exact reason cannot be determined. Common reasons for borrow failure are: An incorrect borrow end-date was specified or the floating license server targeted for the borrow is down
The lmgrd log file from the server shows the following:
(xilinxd) Activation error (-161,62002:0) No fulfillment exists in trusted storage which matches the request
Note: The Activation licensing flow has been deprecated and has been completely removed in Vivado 2017.3 and newer Vivado releases. Any existing activation licenses have been replaced with certificate based licenses and added into the licensing account.
This error will occur if the requested number of days to borrow an activation license is greater than the ACTIVATION_EXPIRY_DAYS value specified in the options file on the server.
To work around this, do one of the following:
Request fewer days
Work with the license administrator to increase the number of days a license can be checked out
Use the ACTIVATION_EXPIRY_DAYS option in the options file to avoid the warning
Below is an extract from the Flexera License Administration Guide for ACTIVATION_EXPIRY_DAYS
ACTIVATION_ EXPIRY_DAYS This option is to control the activation request based on the expiration dates mentioned in the options file while activation. Publisher controls the activations based on the number of expiration days. If the expiration date is greater than the date set in the options file then the functionality is not successful.
ACTIVATION_EXPIRY_DAYS entitlement ID days ACTIVATION_EXPIRY_DAYS entitlementID:FID=fulfillmentID days
For example, if there are more than one entry in the options file, the functionality works fine with respect to first line given in the options file. ACTIVATION_EXPIRY_DAYS ENTL-EZCALC 3
As per the example, if the current date is 11-December-2013 then the client can activate the license until 13-dec-2013. In case of normal activation without option file, client can borrow license beyond 13-dec-2013.
Note If more than one ACTIVATION_EXPIRY_DAYS option for the same EntitlementID and FulfillmentID with different count of days mentioned in the options file, then the functionality always considers first line and ignores subsequent lines