Error: -97 The desired vendor daemon is down.

Problem:

The machine cannot connect to the Thinkbox vendor daemon on the host machine.

Cause:

Firewall

The firewall may be blocking the port used by thinkbox. While traditionally thinkbox itself will by default listen using IPv6 on a random port, you can tell the vendor daemon to use a custom port. This is done by editing the license file and may be necessary if the firewall or security protocols require a static port. This is covered in another section (See Ports).

Vendor Daemon is not running

The vendor daemon application thinkbox isn’t running for one of many reasons.

The hostname may not be resolvable

If the client machine is using a host name instead of an IP address to refer to the license server, it’s possible that the client machine trying to connect is unable resolve the IP address for that name.

Solution:

Firewall

Solution: To verify that the firewall is in fact the cause, temporarily disable it if it is safe to do so. If disabling the firewall allows licenses to be checked out, you will need to allow thinkbox and likely lmgrd to pass through. It should be possible on OS X and Windows to either create program-based exceptions to the firewall allowing any ports from thinkbox, regardless of number, or set a custom port for the vendor daemon. On Linux, you must use the port number.

If you need or want to set a specific port for the vendor daemon, as it will be randomly chosen on each restart otherwise, we have documentation to walk you through this on our Setting License Server Ports page. If you need to test your Firewall, refer to our page on disabling or configuring your firewall for instructions on this.

Vendor Daemon is not running

Solution: In the list of running programs for your operating system, ensure that you are viewing all processes for all users, verify that the thinkbox vendor daemon is running. If not, you will need to refer to the license server log file which should be named ‘Thinkbox.log’ in the root of the license server installation directory (see here for location.

If the problem is not immediately obvious, don’t hesitate to contact Thinkbox Support.

The hostname may not be resolvable

A simple test would be to try to run the command ‘ping hostname’ where hostname is the one you entered for the server name. If no answer returns, this is likely the problem. To close the command on Linux and OS X, hold the control (‘ctrl’) key, and press the ‘c’ key.

Solution: If the ping command was unsuccessful and you know the IP address of the license server, you may use that on the client, in place of the host name. If you have a systems administrator, it would be best to bring up this error with them.