Page 1 of 1

Fusion Flexlm Question and problem

PostPosted: Wed Nov 12, 2014 5:21 pm
by KenOuellette
I am finally getting to install two full floating licenses of Fusion. they were purchased before the acquisition.

I'm having trouble getting the server/dongle connection working.

Can I use the Foundry's flexLM server install with fusion?
I can't find a download link that works for EYEON's Flexlm version.

Is there something special in the lmgrd setup ?

Dongle is on the server,
Server is running
I can ping the machine

My local DFusion.dat (i tried the DFusion.lic as well) is in the correct place next to the install.
I've also tried the system variable for it (and included the ; at the end.

Still not able to connect

the message says
Cannot connect to license server system.
The license server manager (lmgrd) has not been started yet,
the wrong port@host or license file is being used, or the
port or hostname in the license file has been changed
<blah blah>
FLEXnet Licensing error:-15,570
For further information, refer to the FLEXnet Licensing End User Guide

would be great to be able to use what we paid for.
thx
-k

Re: Fusion Flexlm Question and problem

PostPosted: Wed Nov 12, 2014 10:33 pm
by Chris Tomberlin
I'm having the same problem. Bought 7.0 right before 7.5 came out, have a dongle and a license file but can't make it work and can't find any info since the Eyeon site has been taken down.

Re: Fusion Flexlm Question and problem

PostPosted: Wed Nov 12, 2014 11:34 pm
by Stu Friedberg
It's been some time since I set up my FlexLM system for Fusion, but I did overlook something when I got my most recent .dat file, which might be relevant. You have to edit the configuration so it names your FlexLM server machine (which might be localhost, or something more elaborate) rather than the placeholder server in the file as you received it.

Re: Fusion Flexlm Question and problem

PostPosted: Thu Nov 13, 2014 1:21 am
by KenOuellette
Thanks for that Stu.

I did do the rename in the .dat file
and tried the system variable with the ; at the end.

Still not working.

:(

Re: Fusion Flexlm Question and problem

PostPosted: Thu Nov 13, 2014 6:51 pm
by Stu Friedberg
See if you have (or can download) a copy of the LMTOOLS utility from Macrovision (or whoever they are doing business as today). This utility has setup and configuration tools, and also a couple of diagnostic tabs that may help sort out what's going on with your installation. I'm running version 11.4.100 from 2007, and have no idea what the current release is.

I last set up FlexLM from scratch about 5 or 6 years ago, so can't give you the play-by-play. My installation is configured using Services rather than License File, so my render nodes can access their render licenses. If you're set up this way, you should be running a service named "FlexLM Eyeon License Server". (This runs the lmgrd.exe binary.) You should also have an eyeon.exe binary and dfusion.dat in the install directory of FlexLM. The environment variable EYEON_LICENSE_FILE should have value similar to "@192.168.0.1;" (without the quotes) where the network address is where you are running the license server.

If you've configured your installation for License File rather than Services, all of the above may be different.

Added in edit: Oh, the other thing that comes to mind is double-checking that your system is actually recognizing the security dongle. Check in the Device Manager that it shows up as a USB device with proper drivers, and that it appears under Devices & Printers (probably as a HASP or USB UltraPro device). From your original description of the problem, I don't think this is the cause, but it's been a pain point for me in the past. Once you get a set of drivers that actually work for the dongle, don't upgrade. ;)

Re: Fusion Flexlm Question and problem

PostPosted: Fri Jan 02, 2015 9:41 am
by FrankGarza
The way to a little while since i have setup my FlexLM program for Fusion, although Used to do disregard anything when i obtained my most current. dat report, that will be applicable. You have to modify the actual setting then it names ones FlexLM server appliance (which may very well be localhost, or maybe anything much more elaborate) as opposed to the placeholder server inside report since you been given this.