Below are some of the commonly encountered issues users may encounter when using a floating license.
Some of these errors may be encountered on the server side and be presented either in RLM or the DLOG file output by RLM, or the errors can occur on the client while using Yeti in Maya or rendering.
If you don’t see the issue you are experiencing here, or the solution provided does not resolve the problem, please contact us at firstname.lastname@example.org.
- WARNING: No license file for this host (example-1). The hostname in the license file(s) may be incorrect
This warning message will display on the RLM utility on the server and may be presented in the DLOG. In most cases, this error message can be ignored and is a common warning message during server startup, especially when the license file uses an IP address instead of a host/computer name. What you should see following this warning message, is a further message identifying the name of the license file found followed by the port and ISV port startups.
If the warning persists, please ensure that your license file does contain the appropriate extension (.lic) and is located in the correct spot within the RLM folder on the server.
- The license server does not support this product (Server-side). License is out of date (Client-side)
This error occurs when you are trying to use a newer version of Yeti than what the license on the server currently allows. As a result, two different error messages will be presented - one on the server/DLOG, and the other on the client-side from within Yeti. To resolve this:
- Ensure that you are using the appropriate software version for the license file on the server (e.g if you have a license file for 3.0 and you are trying to access 4.2, this will not work). License files will work for any releases matching the major version in the file and earlier, ie. a 4.0 license can be used with any 4.x release or earlier.
- If needed request a new license file by contacting us at email@example.com.
- CreateProcess failed on command line: <license file location> (Server-side)
This error generally means that the ISV server binary is not in the place that RLM and the software is expecting it to be. To resolve this please check the following:
- Is the peregrinel.set file located in the same location as rlm.exe?
- If you need to reinstall the RLM directories, please see Where can I download your license tools?
- Ensure that RLM has access to the file and that the permissions are appropriate (read/write)
- <No valid licenses found> (Server-side)
This error usually indicates an error with the license file itself. To resolve this issue:
- Ensure the license file is in the correct location within the RLM directory on the server
- If you need to make any modifications to the license file, please ensure that you are only changing the computer name/IP address, or adding the host or isv port. If you change anything else within the file (e.g. the machine ID, dates, etc.) the license will no longer be valid and will need to be re-issued by our licensing team.
- Wrong Hostid - licenses may not be available (Server-side)
This error occurs if the host id of the computer does not match what is in the license file. To resolve this issue:
- When requesting a license file, ensure you are providing the correct details
- Try changing the host id (computer name/IP address) on the license file to match the machine you are using
- In some cases, the machine ID can be wrong, if this is the case, please double check the machine ID you provided our licensing team, and if it is different you will need to request a new license using the form found here - https://peregrinelabs.com/pages/license-transfer
- Port 5053 in use, waiting... (Server-side)
This error is caused if the port that RLM is trying to use (5053 by default) is being used by something else. To resolve this issue:
- Ensure that another software is not using port 5053 (this can be another instance of RLM or another software completely)
- To check if another instance of RLM is running please use Activity Monitor on Mac, or Task Manager on PC
- Ensure that firewall settings allow port 5053 to be used
- If another software is using port 5053, or your firewall settings don’t allow its use, specify a different port in the license file. The port can be any available and open port that your system allows. To change the license file, please open the .lic in a text editor and change the first line to add the port at the end of the first line, as demonstrated below. Be sure to save the license file, ensuring the extension remains as .lic
HOST <machine name/ip address> <machine ID > <port number> E.g. HOST LicenseServerName 123456789asd 5064
- Cannot bind Web Server port 5054, exiting (Server-side)
Port 5054 is the default web port for RLM, and allows administrators access to monitor license usage, server status, and server run time through a web portal. If you are running into this error, please see the steps below to resolve the issue:
- Ensure port 5054 (or the specified port) is free/open using the “netstat” command
- If the port is not free close the other program using port 5054
- Ensure there are no firewalls blocking port 5054
- If this is the case, either adjust the firewall accordingly or specify a different port for the web portal during the RLM setup using the -ws #### command (replace #### with the desired port)
- <No ISV servers to start> (Server-side)
This error means that the ISV line, or section of the line is missing from the license file. The ISV line should read as follows:
- peregrinel - lockfile problems (Server-side)
If this error occurs, it generally means that there is another instance of RLM running. To correct this:
- Close all instances of RLM (including the newly started instance)
- Restart RLM
Please note, that if you have RLM running as a service, you will need to stop the service and restart in order to get things running again.
- peregrinel - communication (socket) problems (Server-side)
If you run into any errors that point to a socket connection or communication issue, this is often a corruption issue with the computer registry and is not caused by RLM or Yeti. To fix this:
Open a command prompt window and type the command:
$ netsh winsock reset
For more details on this error, please see the following link - http://www.reprisesoftware.com/blog/2012/10/windows-isv-server-fails-to-start-or-shuts-down-after-starting/