Common Licensing Problems and Solutions

Note: Some solutions contained in this section assume that you have access to the License Manager GUI. If you are using AppInternals, you may have access to the License Manager GUI through another Riverbed application. The GUI is the preferred method for managing and troubleshooting licenses, where available.

Cannot Find License Server You Want to Use

  • If you cannot see the license server you want in the license treeview, you can add it to your "license_managed_servers" preference. After editing the preference, choose File > Refresh Server Information in the License Manager.
  • If the above method is problematic, you can also set the default license server by directly changing the "license_server" preference to the hostname or IP address of the computer that has the licenses you want to use.
  • For non-enterprise licensing, the license server you choose must be in the same classful IP network as the computer on which you are running Riverbed analysis software.

License Not Obtained

If you see a dialog box telling you that a license was not obtained, consider the following possible solutions for each type of problem. The type of problem is described in the "What Happened?" section of the dialog box.

  • There was no response from the license server
    • Are the "license_server" and "license_port" preferences set to the correct values, and are they spelled correctly? Use the hostname command to determine the exact spelling and capitalization.
    • Is the specified license server running?
    • Can the client ping the server? Can the server ping the client? This applies even if the server is the client. TCP/IP must be installed and running, even in standalone mode.
    • Is the license server an older release of Riverbed analysis software? Run the latest release of the License Server.
    • Rarely this may be accompanied by errors saying the op_models directory does not exist. It could be the case that changes to the preferences cannot be stored because Riverbed analysis software cannot write to the home directory. This can be due to permissions or because the directory does not exist.
  • There are no licenses in the server's license file.
    • Set the "license_server" preference to a host with available licenses.
    • Use the Add Licenses button in the License Manager to add licenses to the server's license file.
  • The license server did not grant your request for licenses.
    • You may be running a License Server that is too old for your licenses. In that case upgrade to the latest available License Server.
    • Set the "license_server" preference to a computer with available licenses.
    • Use the Add Licenses button in the License Manager to add licenses to the server's license file.
    • Deselect any product modules that are not in use.
  • The only available license has expired or The only available license's maintenance has expired.
    • Perform the Change Maintenance Expiration operation if the current authorized maintenance date is not reflected in the license file.
    • Perform the Change License Expiration operation if the current authorized expiration date is not reflected in the license file.
    • Be sure to use Select Product Modules to deselect product modules that are unavailable.
    • In rare instances you may need to perform the Update System Date operation, if License Server date is too far in the future.
  • The requested license was found in the license server's license file but it is in use.
    • The most common cause of this message is that the license is in use by another user.

    • If Riverbed analysis software exited ungracefully, select the license in the License Manager, then click on the Revoke License button to revoke the permits that are erroneously listed as "in use". (Riverbed analysis software will automatically recover from this situation after no more than one hour without intervention).

      Note: NetCollector licenses are not recovered in the one-hour time period. A license might not be automatically revoked for several days.

  • The license server is a "standalone" license server. A standalone license server cannot issue licenses to other applications.
    • An obvious remedy is to make sure you are selecting a License Server that is not in standalone mode.
    • If you are certain you have selected the correct default server, switch the License Server to server mode. Stop the license server and (re)install the latest software patch level (on the server machine). During the installation, choose Floating: Serve licenses from this computer.
  • Your machine's IP network address is different from the IP network address of the license server.
    • You must use a License Server on your local IP network. Check to be sure you are using a License Server on your local IP network.
    • This error can also occur if the computer running the License Server received a new IP address after the License Server was started. The solution is to restart the License Server by stopping it, then starting it again in the License Manager.
  • The license server cannot write to its license file. A license server cannot give licenses unless it can write to its license file.
    • Make sure the owner of the License Server process/daemon has permissions to write to the license file.
  • The license server cannot lock its license file. A license server cannot give licenses unless it can lock its license file.
    • Make sure the owner of the License Server process/daemon has permissions to create/delete files and directories in the OPNET_license directory.

    • Make sure enough disk space is available to create a small file or directory in the OPNET_license directory.

      Note: A standalone License Server has the same permissions as the user logged in, while a License Server running in server mode typically has root or Administrator privileges.

  • The license server's license file is invalid. A license server cannot give licenses from an invalid file.
    • Make sure you are running the latest version of License Server. If you are not running the latest version of License Server, you may encounter problems when adding, deregistering, or obtaining licenses.
    • If you receive this error, refer to "Validate License File (Button)" on page 25.
  • A license server's license file does not exist. A license server cannot give out licenses without a license file.
    • The license file may have been deleted, or the license server does not have permissions to create a new license file upon startup. If the license server should have a license file, check to see if it was deleted.
    • Otherwise, select a different license server.
    • If necessary, refer to "Create License File (Button)" on page 22.
  • Your username/hostname is not authorized to obtain licenses from the license server.
    • The user account or computer from which you are trying to access the license server is not authorized in the user_auth file. Check the user_auth file on the computer where the license server is running.
    • For more information, refer to "Restricting License Users".
    • Try to login from an authorized account or computer.

No licenses in file

If there are no licenses in your license file, you may need to sign your Electronic Licensing Agreement (ELA). To do this:

  1. Point your browser to the Riverbed Support Center at https://support.riverbed.com. When prompted, log in with your Riverbed support username and password.
  2. Click on the LICENSES > OPNET Licenses link.
  3. Click on the Review My Electronic License Agreements link.
  4. Find the agreement that you are interested in signing. On the left side of this agreement, click on the Sign link.
  5. Read the license agreement, then click on the Continue button at the bottom of the page.
  6. The next page asks if you are authorized by your organization to sign the license agreement. Read the page, and if you agree, click the I Agree button.
  7. The next page is the actual acceptance of the legal agreement. Read the page, and if you agree, click on the I Agree button.

Note: Each set of licenses has two agreements: Usage and Maintenance. You need to sign both agreements before your licenses are available for use.

Error: A "SERVERS" license is required to use the "server_definer" process model

The SERVERS license, also called Server Specialized Model (SSM) is used for studying advanced server characteristics, such as the effect of disk access time, CPU usage, and other detailed aspects of server usage.

  • If you intended to use this feature, but don't have access to a server license, contact your Riverbed sales account manager.
  • If you did NOT intend to use this feature, you can fix the problem by
    • making sure that the "Server: Modeling Method" on all nodes is set to "Simple CPU", and
    • removing any "Server Definition" utility nodes from the network

You may see a similar error for other specialized models, including those in the following table:

Table 10: Specialized Models

Model License
Server SERVERS
GPRS GPRS
PNNI PNNI
UMTS UMTS
IPv6 IPV6
MPLS MPLS
Mainframe MFRAME

Error: License Server's IP Address Does Not Match the IP Address of Co-Located Workstation

When you install a license server on your computer, the license is manipulated by a system service: op_license_server. If your computer's IP address changes (due to a dial-up or VPN connection, for example) between the time the License Server started and the time Riverbed analysis software is launched, the License Server process does not pick up the change. Restarting the license server will refresh its awareness of its IP address.

  1. - Run the License Manager
  2. - Choose the local license server process (green dot) from the server treeview
  3. - Click the Stop Server button. After a moment, the license server stops.
  4. - Click the Start Server button. After a moment, the license server starts.

Error: Bad checksum [error -16111]

The "bad checksum" error during license registration usually indicates one of two things:

  • The Transaction Code was mistyped. Make sure that the complete Transaction Code was entered and that it doesn't have extra spaces or characters.
  • The hostname was mistyped. Make sure you used the correct capitalization--this field is case-sensitive. Also check for extra spaces or characters.

Entries in License Server Authorization Files Do Not Work

  • Make sure your license authorization files contain the correct format. A '+' may replace either or both fields to indicate that you want to allow all. hostname username
  • After making any necessary changes to the authorization files, use the License Manager menu item Tools > Refresh Server Authorization Files, so the License Server uses the latest changes.

When Entering Approval Code on the Web, Receive Error: "Multiple Decryption Choices"

This message is most common with older releases of Riverbed analysis software. Older versions of the licensing system generated Transaction Codes that were less specific than they are now. Therefore, many times a Transaction Code made from either version could be confused with transaction codes from the other. That is what is meant by "Multiple Decryption Choices." To avoid this problem:

  • If you are using the Express method, simply try the operation again.
  • If you are using the Browser method to perform a license operation, discard the Transaction Code that caused this error message, and try again with a new Transaction Code.

Lost Confirmation Code during Registration

If you lost your Confirmation Code during a registration, you may see the error, "This license has a pending registration". Confirmation codes are stored in the session log of the machine running the License Server.

You can view the session log by choosing Help > Session Log > Open.

Note: Confirmation codes are not necessary with the Express method of license registration.

Potential Server or DNS Configuration Error

If you receive an error similar to this, there is usually not a true problem:

<<< Diagnostic Error >>>
* Package: Vos (Virtual Operating System)
* Function: Vos_Sec_Fl_Dmn_Versioned_Ping
* Error: Potential server or DNS configuration error:
License server (X) returned (Y) as its host name.

This means that your preference settings for the License Server differ from what the server reports. This can happen when the server has multiple hostnames or interfaces.

To prevent the message:

  • Refer to the server in your preferences by the correct hostname or IP address.
  • Suppress this and other diagnostic error messages by setting the diag_enable preference to FALSE.