Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »


This Guide is how to configure SpinFire and ActifyD.exe to use specific ports. This may be due to consistant port clashes with other FLoating licenses or other products installed on the server or if there is high latency issues on your network it is nessesary to have specified ports so SpinFire does not auto-scan for ports for too long (It will scan for 27000 to 27009 to see if any of those ports are available). Please note that your I.T Administator should ensure whichever ports you decide to use for SpinFire or ActifyD.exe (Vendor Daemon) that it is not being used by any other applications on the Server. 


  1. Setting up Specified Ports for SpinFire and ActifyD.exe


  1. First Edit the sfpflv2.dat to use 27500 for the lmgrd and 52500 for ActifyD and then edit license.al to use 27500

     2. Next you need to edit the license.al to use 27500 port. A copy of this should then be kept on the Floating License Manager so this copy of the file can be given to the SpinFire users in the future when activation through "Activate Floating License" does not function or there is a licensing issue occuring on specific end user machines.


You should now see the updated sfpflv2.dat and License.al in your Floating License Manager.


3. Stop, Start and Re-read the sfpflv2.dat file, you will see a success or error message along the bottom. After the confirmation that the sfpflv2.dat has been successfully loaded into the Floatng License Manager proceed to the next step.

4. After the confirmation that the sfpflv2.dat has been successfully loaded into the Floatng License Manager you will now pass these two license files to the SpinFire users, they must place these files in this folder: C:\ProgramData\Actify\SpinFire11


Listed below are some guidelines to follow when it comes to SpinFire/Floating License Manager configurations:


  1. If a port for SpinFire has been specified on the Floating License Manage, all SpinFire Clients must be using the same port or they will be unable to activate. They must specify the port in the "Activate Floating License" as well as the other server details.

  2. If Activate Floating License is not successful, copy the two license files (License.al and sfpflv2.dat) to the Spinfire license folders on the end user machines.

  3. If their license folder is empty after trying to do Activate Floating License, it may be that there is insufficient permissions on the license folder.

  4. When the Floating License Manager has been updated with a new SFPFLV2.dat file that has a new End of Maintenance date, the end users must also update. Normally by Activate Floating License, they will of course need to know the server details AND the specified port in the SFPFLV2.DAT file otherwise they will be unable to activate.

  5. When a specified port is being used for SpinFire or ActifyD.exe , it is your Network Administrator's responsbility to ensure that no other products on that Server is using the port to avoid problems later.

  6. Please note that the latest Floating License Manager is mandatory to use 11.7.x release!



2. If there are issues after following this page's steps, please provide the following to Actify Support:


  1. Provide a copy of the SpinFire.log from one or more machines suffering the Floating License issue:

2. Provide a copy of the debug.log from the Floating License Manager folder. If one does not exist in the FLM folder, Create a .txt file and name it debug.log (with the .log extension) and save, then go to the LMTOOLS > Config Services and add the path to this file. You may need to stop and start the Service to get an output of information to the debug.log if it is empty.



3. Ensure the relevant Service is currently running and is pointing to the correct files (LMGRD.exe, sfpflv2.dat and the debug.log and is ticked along the bottom as shown in the screenshot below.




4. Click Perform Status Enquiry on the Server Status page and copy the output to an email or file to share with Actify. Repeat the same for the Perform Diagnostics on the Server Diags page.


5. Can one of the effected SpinFire End Users Telnet the server?  "telnet <yourserver> 27500" through command prompt?








  • No labels