comp.lang.idl-pvwave archive: archive » HASP/ flexLM licensing conflict

Home » Public Forums » archive » HASP/ flexLM licensing conflict

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

HASP/ flexLM licensing conflict [message #27888]

Fri, 09 November 2001 12:07

Rick Towler
Messages: 821
Registered: August 1998

Senior Member

Platform: Windows 2000
IDL Ver: 5.4 soon to be 5.5

We license IDL by setting the LM_LICENSE_FILE environment variable to the
port@machine.name where we have our IDL license server (running the FlexLM
daemon). This is a quick and easy and allows me to only manage license
files on one machine.

We just purchased a software product that is licensed via HASP + dongle
(just like IDL has been up to 5.5). Upon installing the HASP driver, IDL
refuses to connect to the network license manager and only looks for a local
license file. I ran into this issue before when this same machine was
upgraded to 5.4 and simultaneously switched from HASP licensing to use a
network license. The solution (after lots of head scratching) was to remove
the HASP driver.

Does anybody know of a way to get the HASP driver + IDL + network license to
coexist in harmony?

I am assuming that the last resort would be to copy the network license file
to the local machine and configure IDL to use a network license in the pre
5.4 manner but that introduces the headache of having to manage license
files on every machine that has this new software package installed.
Bugger.

Thanks for any sage advice.

-Rick

Report message to a moderator

Re: HASP/ flexLM licensing conflict [message #27950 is a reply to message #27888]

Tue, 13 November 2001 08:37

Pavel A. Romashkin
Messages: 531
Registered: November 2000

Senior Member

I don't know if its relevant in this case, but I saw the same behavior
from a non-dongle license. If I plug in a dongle, IDL will not start up
with the dongleless license. Once the dongle is pulled out, it starts
just fine.

Pavel

Rick Towler wrote:
>
>> Did you set correctly the LM_LICENSE_FILE environment variable.
>> It must be something like
>> export LM_LICENSE_FILE=1700@YOURMACHINE
>
> Yes. Everything works fine until you install the HASP driver. Then IDL
> ignores the environment variable alltogether and only looks locally for a
> license file. If I unistall the HASP driver then IDL works as expected
> (finding the license file at port@host).
>
> Although my knowledge of this is quite limited, I suspect that this problem
> is a limitation in IDL. With older versions of IDL I seem to remember that
> you couldn't just set the LM_LICENSE_FILE variable to port@host to access
> the license file from the licensing server and instead you had to install a
> copy of your license file on every client. It seems that when started, IDL
> looks for the HASP driver and if it is found, it behaves like the older
> versions of IDL. At least that is the working theory.
>
> I guess I just have to put up with it until 5.6 when, at least according to
> rumor, HASP licensing will be dropped altogether.
>
> -Rick

Report message to a moderator

Re: HASP/ flexLM licensing conflict - Follow up [message #27989 is a reply to message #27888]

Wed, 14 November 2001 16:02

Rick Towler
Messages: 821
Registered: August 1998

Senior Member

This is a follow up to my original HASP/flexLM licensing issue. To recap,
licensing client machines by setting the LM_LICENSE_FILE variable to
port@machine (eq 1700@goldfish.com) failed when a HASP driver was installed.
The HASP driver was installed for another product, not for IDL which was
licensed via flexLM.

Whatever the reason, you can not configure a client machine to access the
license file from your flexLM license server as described on page 67 of the
License Management Guide (LMG) if the client machine has a HASP driver
installed. Setting the environment variable LM_LICENSE_FILE to port@server
will not work.

The solution is to license your client machine as described in the section
titled "Installing License File Copies on Client Machines" on page 68 of the
LMG. This unfortunately requires your admin to manage multiple copies of
your IDL license file, just like in the old days....

-Rick

"Rick Towler" <rtowler@u.washington.edu> wrote in message
news:9shd3p$24h2$1@nntp6.u.washington.edu...
> Platform: Windows 2000
> IDL Ver: 5.4 soon to be 5.5
>
> We license IDL by setting the LM_LICENSE_FILE environment variable to the
> port@machine.name where we have our IDL license server (running the FlexLM
> daemon). This is a quick and easy and allows me to only manage license
> files on one machine.
>
> We just purchased a software product that is licensed via HASP + dongle
> (just like IDL has been up to 5.5). Upon installing the HASP driver, IDL
> refuses to connect to the network license manager and only looks for a
local
> license file. I ran into this issue before when this same machine was
> upgraded to 5.4 and simultaneously switched from HASP licensing to use a
> network license. The solution (after lots of head scratching) was to
remove
> the HASP driver.
>
> Does anybody know of a way to get the HASP driver + IDL + network license
to
> coexist in harmony?
>
> I am assuming that the last resort would be to copy the network license
file
> to the local machine and configure IDL to use a network license in the pre
> 5.4 manner but that introduces the headache of having to manage license
> files on every machine that has this new software package installed.
> Bugger.
>
> Thanks for any sage advice.
>
> -Rick
>
>

Report message to a moderator

Re: HASP/ flexLM licensing conflict - Follow up [message #28056 is a reply to message #27989]

Thu, 15 November 2001 12:37

Mark Hadfield
Messages: 783
Registered: May 1995

Senior Member

From: "Rick Towler" <rtowler@u.washington.edu>
> ...This unfortunately requires your admin to manage
> multiple copies of your IDL license file, just like
> in the old days....

It's good for them. Otherwise they'd just be sitting around having "most
clueless user of the week" competitions. Or thinking up spurious reasons why
they can't let James have multiple X configurations.

---
Mark Hadfield
m.hadfield@niwa.cri.nz http://katipo.niwa.cri.nz/~hadfield
National Institute for Water and Atmospheric Research

--
Posted from clam.niwa.cri.nz [202.36.29.1]
via Mailgate.ORG Server - http://www.Mailgate.ORG

Report message to a moderator

Previous Topic:	idl / psutils
Next Topic:	the dimension of array

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Oct 08 16:52:36 PDT 2025

Total time taken to generate the page: 0.00597 seconds