PDA

View Full Version : Problem upgrading to v11.x from v10.x



zbordas
07-25-2008, 04:16 PM
Hi Everyone,

I am trying to upgrade our Flex API to the latest verion from version 10.8.5.0 and I am having problems. It keeps complaining that our vendor keys are incorrect and does not build the utilities. If I simply try to use the jar file from the latest version of the Java API it also complains about the keys which is weird because we have been using these vendor keys in production environment for almost 3 years no (that's when we switched to TRL keys).

Here is the e-mail I sent to support:

Dear Support,

We are currently using FlexLM API v10.8.5.0. Our framework and developer kits are using both the Java and C++ API on both Windows and UNIX platforms. So far we needed license checkout capability on 32-bit libraries only. Due to the Java API our licenses are TRL enabled.

I have recently started to do a pilot task for Windows based 64-bit developer kit libraries. Unfortunately I ran into issues with building and using the FlexLM libraries.

1. First I tried to build the current v10.8.5.0 version of the 64-bit windows toolkit. When the make process gets to the point of generating the lm_new.c using the lmnewgen utility it compains about our vendor key being incorrect:
C:\Development\flexlm\v10\x64_n6>lmnewgen.exe
v8.1+ FLEXlm, using TRL
lc_init failed: Invalid key data supplied.
FLEXnet Licensing error:-44,49
For further information, refer to the FLEXnet Licensing End User Guide,
available at "www.macrovision.com".

I tried to slightly change the makefile and force the build process to use the lm_new.c file generated as part of the i86 build (lm_new.obj and lm_new_md.obj). Our test application builds and links fine using these binaries but when running it and trying to create a Flex job the first time I get a return code of -1 and none of the FlexLM functionality is available.

2. I tried the same process using the new v11.5 and also the v11.6 C++ API. I get the exact same behavior but this time I cannot even build and use the win32 obj and library file.
C:\Program Files\FLEXlm\v11.6\i86_n3>lmnewgen.exe
v8.1+ FLEXnet, using TRL
lc_init failed: Invalid key data supplied.
FLEXnet Licensing error:-44,49
For further information, refer to the FLEXnet Licensing documentation,
available at "www.acresso.com".

C:\Program Files\FLEXlm\v11.6\i86_n3>cd ../..

C:\Program Files\FLEXlm>cd v10.8.5.0\i86_n3

C:\Program Files\FLEXlm\v10.8.5.0\i86_n3>lmnewgen
v8.1+ FLEXlm, using TRL


I have double and triple checked that I am using the exact same lm_code.h file and the vendor name has been properly updated in the makefile each time I tried.

My questions are the following:

1. Is there something wrong with our vendor keys? I am not sure why I can use it on win32 without any problems but when I try to build it in 64-bit mode or try to use a higher version of FlexLM API with the same keys it comes out as incorrect.
2. Is it possible that our keys are locked somehow to this specific platform and FlexLM version?


Here is the full output when trying to build the v11.6 binaries:

C:\Program Files\FLEXlm\v11.6\i86_n3>nmake

Microsoft (R) Program Maintenance Utility Version 8.00.50727.762
Copyright (C) Microsoft Corporation. All rights reserved.

lmrand1 -i ..\machind\lsvendor.c
cl /c /nologo /c /I..\machind /I. /MT -I../h lmcode.c
lmcode.c
LINK /nologo /NODEFAULTLIB /OPT:NOREF /subsystem:CONSOLE lmnewgen.obj l
mcode.obj .\activation\lib\libnoact.lib lmgr.lib libcrvs.lib libsb.lib oldnames
.lib kernel32.lib user32.lib netapi32.lib advapi32.lib gdi32.lib comdlg32.lib
comctl32.lib wsock32.lib libcmt.lib /out:lmnewgen.exe
if exist lm_new.c del lm_new.c
lmnewgen.exe osp -o lm_new.c
v8.1+ FLEXnet, using TRL
lc_init failed: Invalid key data supplied.
FLEXnet Licensing error:-44,49
For further information, refer to the FLEXnet Licensing documentation,
available at "www.acresso.com".
NMAKE : fatal error U1077: '.\lmnewgen.exe' : return code '0x1'
Stop.

C:\Program Files\FLEXlm\v11.6\i86_n3>

And here is the output from the v10.8.5.0:

C:\Program Files\FLEXlm\v10.8.5.0\i86_n3>nmake

Microsoft (R) Program Maintenance Utility Version 8.00.50727.762
Copyright (C) Microsoft Corporation. All rights reserved.

rc /l 0x409 /r /folmwin.res ..\machind\lmwin.rc
lmrand1 -i ..\machind\lsvendor.c
cl /c /nologo /c /I..\machind /I. /MT -I../h lmcode.c
lmcode.c
LINK /nologo /NODEFAULTLIB /OPT:NOREF /subsystem:CONSOLE lmnewgen.obj l
mcode.obj lmgr.lib libcrvs.lib libsb.lib oldnames.lib kernel32.lib user32.lib n
etapi32.lib advapi32.lib gdi32.lib comdlg32.lib comctl32.lib wsock32.lib libc
mt.lib /out:lmnewgen.exe
if exist lm_new.c del lm_new.c
lmnewgen.exe osp -o lm_new.c
v8.1+ FLEXlm, using TRL
cl /nologo /c /I..\machind /I. /MT /Folm_new.obj lm_new.c
lm_new.c
cl /nologo /c /I..\machind /I. /MT /O1 ..\machind\lmsimple.c
lmsimple.c
LINK /nologo /NODEFAULTLIB /OPT:NOREF /out:lmsimple.exe lmsimple.obj lm
_new.obj lmgr.lib libsb.lib libcrvs.lib oldnames.lib kernel32.lib user32.lib net
api32.lib advapi32.lib gdi32.lib comdlg32.lib comctl32.lib wsock32.lib libcmt
.lib
if exist lmsimple.obj del lmsimple.obj
cl /nologo /c /I..\machind /I. /MT /O1 ..\machind\lmflex.c
lmflex.c

… and more.


I hope I provided enough details about the problems we are having. Please let me know if you need any additional information.

Any input is appreciated. It almost looks like our vendor keys have been incorrectly issues or generated by Macrovision.

yossarian
11-11-2008, 06:15 PM
zbordas, did you ever resolve this issue? I'm having the same problem building 10.8.7 for 64-bit RH Linux using an lm_code.h that works for 32-bit Windows and Linux platforms.

zbordas
11-11-2008, 06:37 PM
Yes.

It turned out that 64-bit platforms were not included in our original purhcase. If you look up the original e-mail you got you'll notice that the 64-bit platforms are missing from the list of supported "platforms":

Original e-mail:
Your vendor keys enable the following platforms and are for use only by "xxxx":
java,linux,sun,winnt_intel

The new e-mail says
Your vendor keys enable the following platforms and are for use only by "xxxx":
amd64_re,java,linux,sun,sun64,winnt_intel,x64_win

After purchasing the missing platforms and receiving the proper keys everything worked just fine.

Good luck!

yossarian
11-11-2008, 07:07 PM
Thanks for the reply. However, our license keys did include the platform I'm trying to build:


Your vendor keys enable the following platforms and are for use only by
"<company name removed>": amd64_re,linux,winnt_intel

"linux" and "winnt_intel" have built just fine, but "amd64_re" throws the same error you describe.

zbordas
11-11-2008, 07:19 PM
I would contact Acresso support. I seems like they might have made a mistake when they issued you license keys. In my case after getting the new vendor keys everything worked as expected.

Good luck and keep us informed.