.

Summary

Tips for resolving the dreaded "Unable to communicate with license manager" error.

Version

Rhino 3.0, Rhino 4.0

Note

This error can occur in both Stand alone and Network node (Zoo) installations.

Problem

When you run either Rhino 3.0 or Rhino 4.0, you receive the following error message:

Cause

The "Unable to communicate with license manager" message is caused by Rhino's inability to communicate with its license manager module listed below. This can be from one of the following:

1. Missing license manager files.
2. Missing Windows System Registry entries.
3. Old runtime library support files.
4. Registry security issue.

Solution 1 - Missing license manager files

Rhino's license managment module is located in the following folder (on English-language Windows where C: is the system drive):

  C:\Program Files\Common Files\McNeel Shared\License Manager

Rhino 3.0 and Rhino 4.0 use different license management modules:

• The Rhino 3.0 license manager is named MCNEELLM.EXE.
• The Rhino 4.0 license manager is named RHINOLM.EXE.

If the license manager module for the version of Rhino that you are using does not exist, then you will need to re-install Rhino from your CD.

Solution 2 - Missing Windows System Registry entries

If the license manager module for the version of Rhino that you are using is present, then the module might not be registered - there might not be information in the Windows Registry that allows Rhino to locate this module. To solve this issue:

1. Make sure you are logged into your workstation as the Administrator or an equivalent user.
2. Make sure to disable virus detectors and anti-spyware agents.
3. Get to a Windows operating system command prompt (click Start->Run. Then, enter "CMD.EXE" and click "OK".)
4. Navigate to the above mentioned folder. ( cd \Program Files\Common Files\McNeel Shared\License Manager )

Note to Windows Vista Users - make sure the run the command prompt as an Administrator. On Windows Vista, click Start->All Programs->Accessories. Then, right-click on "Command Prompt" and click "Run as administrator".

Rhino 3.0

If the error occurred running Rhino 3.0, then Download and unzip this file in the same folder as MCNEELLM.EXE.

From the command prompt and from the "License Manager" folder, run MCNEELLM.BAT. For example:

  C:\Program Files\Common Files\McNeel Shared\License Manager> MCNEELLM <enter>

The batch file will echo the results to the command line, thus verifying success or failure. Note, double-clicking on the batch file from Explorer will also work, but you will not be able to tell if the command succeeded or failed. To confirm this method resolved the problem, run Rhino 3.0.

Rhino 4.0

If the error occurred running Rhino 4.0, then Download and unzip this file in the same folder as RHINOLM.EXE.

From the command prompt and from the "License Manager" folder, run REGISTERRHINOLM.BAT. For example:

  C:\Program Files\Common Files\McNeel Shared\License Manager> REGISTERRHINOLM <enter>

The batch file will echo the results to the command line, thus verifying success or failure. Note, double-clicking on the batch file from Explorer will also work, but you will not be able to tell if the command succeeded or failed. To confirm this method resolved the problem, run Rhino 4.0.

Solution 3 - Old runtime library support files

If running the above batch file returns an error, then download and install the latest Microsoft runtime libraries and try again.

Solution 4 - Registry security issue

If the license manager module for the version of Rhino that you are using is present and the module us registered - you might not have enough rights to read the Windows Registry.

Run REGEDIT.EXE. When open, find the "RhinoLicenseManager.RhinoLicense" key in HKEY_CLASSES_ROOT. For example:

Right-click on the key (in the left pane) and pick "Permissions..." from the context menu. For example:

Administrators should have Full Control and Read checked (under the Allow column) and Users should have Read checked. If this is not the case, then the users permissions have been modified, which is causing Rhino to not be able to read this key. Registry permissions issues are often caused by security policies have been pushed down onto the workstations that are members of an Active Directory domain. But, they have been known to have been caused by Windows Updates as well.

To set the permissions, navigate to the top of the hive (HKEY_CLASSES_ROOT) and try to set the proper permissions from there. In doing this, all keys below this hive will inherit the permissions (and hopefully the problem will be solved). If you are unable to do this, then you will need to contact your computer support staff and ask for assistance.

Another solution, for Windows Vista users, is to turn of User Account Control.