Why does setting LM_A_VENDOR_ID_DECLARE after a checkout fail with a -5 error?

Title

Summary

Why does setting LM_A_VENDOR_ID_DECLARE after a checkout fail with a -5 error?

Question

Why does setting LM_A_VENDOR_ID_DECLARE after a checkout fail with a -5 error?

Answer

The job license refresh is part of LM_A_VENDOR_ID_DECLARE and a few other attribute (e.g. LM_A_DISABLE_ENV).

If test checkout is moved after LM_A_VENDOR_ID_DECLARE attribute setting both checkouts are successful
(LM_A_VENDOR_ID_DECLARE is being set. test checkout out of f1 ... SUCCESS. f1 checked out...)

The failure is not limited to test checkout alone and it holds good with any checkout
(f1 checked out...LM_A_VENDOR_ID_DECLARE is being set., (-5, 414) error).

To avoid this, set LM_A_VENDOR_ID_DECLARE before doing any checkouts.

Additional Information

For example:

lmflex (LM_A_VENDOR_ID_DECLARE is not set)
1.Test_checkout (f1)
<<<=== connection is made here, job has a valid socket, job->daemon->server is populated in connection)
2.// lc_set_attr(LM_A_VENDOR_ID_DECLARE)
<<<==== this attribute is not set
3.Regular checkout (f1)
<<<=== Uses the same connection from first checkout because server conf->server and job->daemon->server (populated in connection) are same.
4.So, subsequent checkouts are successful.

Lmflex 1 ==> (LM_A_VENDOR_ID_DECLARE is SET)
1.Test_checkout (f1)
<<<=== connection is made here, job has a valid socket, job->daemon->server is populated in connection)
2.lc_set_attr(LM_A_VENDOR_ID_DECLARE)
<<<=== this attribute is set
<<<=== the attribute makes the job license to be refreshed so job->daemon->socket is released as part of this
<<<=== the job->socket is still retained
3.Regular checkout ()
<<<=== Since conf->server and job->daemon->server (is null now) are not same, try to attempt a new connection but this job already has a valid connection the connection routine fails with -5.

Was this helpful?

Support Hub

Product

FlexNet Publisher

Visibility

Guest

URL Name

why-does-setting-lm-a-vendor-id-declare-after-a-checkout-fail-with-a-5-error

Are you sure you want to cancel the case creation?

Case closed successfully

Action performed successfully

Upload Attachment

Maximum file size allowed is 3 MB.

File type not supported.

Supported file types:

Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Are you sure you want to close this case

Get Hotline support

Products	Region	Phone Numbers
FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield	North America *	+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America)
	Europe *	+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe)
	Japan *	+81 3-4540-5335 (select option 2)
	Australia *	+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia)
Usage Intelligence (formerly Revulytics) Compliance Intelligence	Please use the Case Portal to submit your support ticket or reach out to your Revenera contact.

Revenera Assistant

Summary

Question

Answer

Additional Information

Related Articles

Please wait...

Case id: 00001065