cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Bad message command. / FlexNet Licensing error:-140,10006

Bad message command. / FlexNet Licensing error:-140,10006

Summary

Bad message command. / FlexNet Licensing error:-140,10006

Question

What causes the lmutil Error : Bad message command. / FLEXnet Licensing error:-140,10006?

Answer

There is a BUG in 11.9 and 11.9.1 lmutil where the above error occurs. It does not occur in 11.8 lmutil. Here is an example:
BUG: IOC-000086279
Use older version 11.8 or lower of lmutil.exe

OUTPUT of lmutil using 11.8, 11.8, 11.9.1
=================================
=========================================================================================
C:\Documents and Settings\mwaliullah\Desktop\FNP_11.8_CLEAN\i86_n3>lmutil_11.8.exe lmdiag -c counted.lic
=========================================================================================
lmutil_11.8 - Copyright (c) 1989-2009 Flexera Software, Inc. All Rights Reserved
.
FLEXnet diagnostics on Mon 1/17/2011 09:33
-----------------------------------------------------
License file: counted.lic
-----------------------------------------------------
"f11" v1.0, vendor: MWALI
License server: SC-MOHAMMADW
floating license starts: 1-jan-1990, no expiration date
Requests from the same USER do not consume a new license
This license can be checked out
-----------------------------------------------------
========================================================================================
C:\Documents and Settings\mwaliullah\Desktop\FNP_11.8_CLEAN\i86_n3>lmutil_11.9.exe lmdiag -c counted.lic
========================================================================================
lmutil_11.9 - Copyright (c) 1989-2010 Flexera Software, Inc. All Rights Reserved
.
FLEXnet diagnostics on Mon 1/17/2011 09:34
-----------------------------------------------------
License file: counted.lic
-----------------------------------------------------
"f11" v1.0, vendor: MWALI
License server: SC-MOHAMMADW
floating license starts: 1-jan-1990, no expiration date
Requests from the same USER do not consume a new license
This license cannot be checked out because:
Bad message command.
Feature: f11
License path: counted.lic;
FLEXnet Licensing error:-140,10006
For further information, refer to the FLEXnet Licensing documentation,
available at "www.flexerasoftware.com".
-----------------------------------------------------
==========================================================================================
C:\Documents and Settings\mwaliullah\Desktop\FNP_11.8_CLEAN\i86_n3>lmutil_11.9.1.exe lmdiag -c counted.lic
==========================================================================================
lmutil_11.9.1 - Copyright (c) 1989-2010 Flexera Software, Inc. All Rights Reserv
ed.
FLEXnet diagnostics on Mon 1/17/2011 09:34
-----------------------------------------------------
License file: counted.lic
-----------------------------------------------------
"f11" v1.0, vendor: MWALI
License server: SC-MOHAMMADW
floating license starts: 1-jan-1990, no expiration date
Requests from the same USER do not consume a new license
This license cannot be checked out because:
Bad message command.
Feature: f11
License path: counted.lic;
FLEXnet Licensing error:-140,10006
For further information, refer to the FLEXnet Licensing documentation,
available at "www.flexerasoftware.com".
============================================================================================
==============
Expected Result:
==============
lmutil should not fail with error Bad message command and FLEXnet Licensing error:-140,10006
----------------------------
Workaround (if any)
-----------------------------
Use older version 11.8 or lower of lmutil.exe
Was this article helpful? Yes No
No ratings
Comments

Currently running LMtools 2020.06 ver 11.16.6.0 build 260203186 n3
I am wondering is the software compatible if installed on a new server running windows server 2019. I am current recieveing the 140,148 error.
If it is not what is the version of Flexnet or Lmtools should I run to work with Windows Server 2019 OS

Version history
Revision #:
1 of 1
Last update:
‎Jan 17, 2011 12:11 PM
Updated by: