Once you have set up a license file for your machine, you are ready to test your license using the Gurobi Command Line Tool (gurobi_cl). To do this, type gurobi_cl --license in a command shell window or in a terminal. It should produce the following output:
Set parameter LogFile to value "gurobi.log"
Using license file C:\gurobi\gurobi.lic
The above message will be preceded by another message if you are using a Token Server Client, Compute Server Client, Gurobi Instant Cloud or a Web License Service (WLS) license.
Token Server Client License
If you are running as a client of a Gurobi Token Server, the message above will be preceded by a message like this:
Set parameter TokenServer to value "mymachine.mydomain.com"Compute Server Client License
If you are running as a client of a Gurobi Compute Server, the message above will be preceded by a message like this:
Set parameter ComputeServer to value 'myserver'
Set parameter ServerPassword
Capacity available on 'myserver' - connecting...
Established HTTP unencrypted connection
Gurobi Instant Cloud
If you are using a Gurobi Instant Cloud license, the message above will be preceded by a message like this:
Set parameter CloudAccessID
Set parameter CloudSecretKey
Set parameter CloudPool to value 'default'
Set parameter LicenseID to value xxxxxx
Waiting for cloud server to start (pool default)...
Capacity available on 'default' cloud pool - connecting...
Established HTTPS encrypted connection
Web License Service (WLS)
If you are using a Web License Service (WLS) license, the message above will be preceded by a message like this:
Set parameter WLSAccessID
Set parameter WLSSecret
Set parameter LicenseID to value xxxxxCongratulations, your license is functioning correctly! You are now ready to use Gurobi Optimizer.
Some possible errors
If the command gurobi_cl --license didn't produce the desired output, there's a problem with your license. We'll list a few common errors here.
No license found
The message
ERROR: No Gurobi license found (user smith, host mymachine, hostid 9d3128ce)
indicates that your gurobi.lic file couldn't be found.
Do you have the appropriate permissions to read the file? Missing read permissions for the file or the directory is a common problem, particularly if someone else performed the installation.
Did you use a non-default license file location? See Where do I place the Gurobi license file (gurobi.lic)? for further information.
HostID mismatch
The message:
ERROR: HostID mismatch (licensed to 9d3128ce, hostid is 7de025e9)
indicates that your gurobi.lic isn't valid for this machine. You should make sure that you are using the right gurobi.lic file. Please see How do I resolve an "ERROR 10009: HostID mismatch"?.
Token server issues
If you are running as a client of a Gurobi token server, the message:
ERROR: Failed to connect to token server 'myserver' (port 41954)
indicates that the token server isn't currently running. Please see How to resolve the error "Failed to connect to token.gurobi.com port 443"?.
The message:
ERROR: No TOKENSERVER specified for TOKEN license
indicates that your license file is missing the TOKENSERVER= line that provides the name of your token server. Please consult How do I start a token server?
Compute server issues
If you are running as a client of a Gurobi Compute Server, the message:
ERROR: Failed to connect to 'myserver' port 80
indicates that the Compute Server isn't currently running. Please consult How do I set up and use a Compute Server license?