Render node update breaks licensing

For some reason updating our render nodes from 1.6.0.43376 to 1.6.1.43756 has broken the licensing information (link to the license server). I’ve tried re-downloading, editing, and running the .reg files to set the correct server information, but from what I can gather from the error log, it’s being ignored (still looking for C:\flexlm).

Here’s the relevant section of the error log:

=======================================================
Slave Log

01/19 17:30:57 ERR: Cannot find license file. The license files (or license server system network addresses) attempted are listed below. Use LM_LICENSE_FILE to use a different license file, or contact your software provider for a license file. Feature: krakatoa-max-render Filename: C:\flexlm\license.dat License path: C:\flexlm\license.dat; FLEXnet Licensing error:-1,359. System Error: 2 “No such file or directory” For further information, refer to the FLEXnet Licensing documentation, available at “www.flexerasoftware.com”.

I am also having this issue - on two clean rendernode installs, where only 1.6.1.43756 has been installed…

Can you tell me what OS and Max version these render nodes are running? We modified the licensing to better handle the permission changes made to the registry in Vista and Win 7, so I think that might be the culprit. Perhaps I broke XP in the process.

Try this registry key out. You’ll need to edit the section YOUR LICENSE FILE HERE, and change it to the name or IP of your license server. Remeber to keep the @ symbol though! Also, to optimize our chances of doing this right, make sure to log in as the user that the render node typically works under.
krakatoa_license.zip (319 Bytes)

Thanks for the response. The nodes are running Vista Business x64, and the new registry patch works perfectly. :smiley:

Any special reason this is done in the HKEY_CURRENT_USER?

Well, that’s what MSDN suggested to avoid permission issues on Vista & 7. Only admins can write to the HKLM tree, and I didn’t have a satisfying way to elevate privileges.

I suggest that you do the license’s check for HKCU first, then ALSO check HKLM if that fails. Sure the user can only change HKCU, but the admin now has no way to install a setting. I ended up distributing a startup script that sets a key. Boo.

Ben.

That’s a good idea, and an oversight on my part. I thought that FLEXlm would be doing that themselves, but I was all kinds of wrong.

Thanks… All working fine now…