Novell Home

My Favorites

Close

Please to see your favorites.

Understanding NetWare 5 Licensing

(Last modified: 17Feb2003)

This document (10013723) is provided subject to the disclaimer at the end of this document.

goal

Understanding NetWare 5 Licensing

How to troubleshoot Licensing errors

fact

Novell NetWare 5.0

Formerly  TID 2943750

symptom

Policy Manager Error: C0001001 (Bad Handle).

Policy Manager Error: C0001002 (No license has been installed at or above the server's context).

Policy Manager Error: C0001003 (The NLSLSP.NLM is not running, DS is not running, or you must "Setup licensing service" using NWCONFIG).

Policy Manager Error: C0001004 (License Terminated).

Policy Manager Error: C0001005 (License is assigned to different file server.  If user assignments have been made, then the user is not assigned to the license).

Policy Manager Error: C0001006 (License has been installed but all units are in use).

Policy Manager Error: C0001007 (Resources Unavailable).

Policy Manager Error: C0001008 (Network problem.  This is usually some sort of NDS issue).

Policy Manager Error: 80001009 (Text Unavailable).

Policy Manager Error: C000100A (Unknown Status).

Policy Manager Error: C000100B (Bad Index).

Policy Manager Error: 8000100C (License is expired).

Policy Manager Error: C000100D (Buffer To Small).

Policy Manager Error: C000100E (Bad argument).

Policy Manager Error: C0004001 (Mismatched versions of NLSLSP.NLM on servers).

Policy Manager Error: C0004002 (License is already installed).

NLS Error: C000400F encountered (..\..\common\src\dsdclien.cpp:1774) - Indicates that NLS couldn't find an NDS schema attribute it is searching for.  It is cosmetic only and does not indicate a problem with licensing.

Error: NWAdmin does not contain the "NLS_LSP_<ServerName>" object in the same context as the <ServerName> object.

fix

Understanding NetWare 5 licensing:

NetWare 5 Licensing uses DS to store the license information. There are three objects, which are stored in the tree: NLS License Server, NLS Product Container and NLS License Certificate.  There is a license container for a server license and a license container for a connection license.  

Initially the NLS_LSP object will reside in the same container as the server object and will reflect the name of the server "NLS_LSP_<ServerName>".  The server object has an attribute that tells it where the LSP object is in the tree.  The NLS_LSP object is created when the schema is extended with SETUPNLS.NLM or NWCONFIG  License Options  Set up Licensing service.

Initially the SERVER LICENSE is created when installing the server license and will reside in a container, which is created in the same container as the server object. The license container name "Novell+NetWare 5 Server+500" describes the type of license and the count.  The license container will store the trending information for the previous 15 months. This container can be moved up the tree to centralize licensing with out moving the server object.  If the license container is moved down the tree and the server object is not moved to the same location, licensing will cease to function. The license certificate is stored within the license container and is named the same as the serial number.  Both licensing containers ("Novell+NetWare 5 Server+500", "Novell+NetWare 5 Conn SCL+500") should be in the same container

Initially the CONNECTION LICENSE is created when installing the server license and will reside in a container, which is created in the same container as the server object. The license container name "Novell+NetWare 5 Conn SCL+500" describes the type of license and the count.  The license container will store the trending information for the previous 15 months. This container can be moved up the tree to centralize licensing with out moving the server object.  If the license container is moved down the tree and the server object is not moved to the same location,
licensing will cease to function. The license certificate is stored within the license container and is named the same as the serial number.  Both licensing containers ("Novell+NetWare 5Server+500", "Novell+NetWare 5 ConnSCL+500") should be in the same container.

When Directory Services is loaded and the DS database is open, the License Server Provider will then discover the NLS: License Service Provider object of the server in the tree to provide the license service.

There are two types of licenses which can be installed;  Non-restricted License "MLA" and/or restricted License "Unique license per server".  

The non-restricted license is a generic license, which can be installed on many servers.  All servers will report the same serial number.  The server does not report any duplicate license messages.  This license will allow the network administrator to change the name of the server in the AUTOEXEC.NCF file with out any adverse effect.

The restricted license is not a generic license. Each server is required to have a unique base server license. In addition one or more connection licenses may be installed per server . In the event that two servers have the same license installed, the server will report a duplicate license message. This license will NOT allow the network administrator to change the name of the server in the AUTOEXEC.NCF file with out any adverse effect.  If the server name is changed in the AUTOEXEC.NCF, the file server assignment must be changed using NWADMIN.  NetWare 5 will allow two grace logins connections without any license installed.  If there is no license installed error messages will be displayed at the server console.  Each License Envelope contains within it a server license and a user license.

NetWare 5 has two debug tools built in which may help troubleshoot licensing issues.  At install time a file called
SYS:SYSTEM\NLSI.DBG will be created to trace NetWare Licensing. After NetWare is installed there is a SET parameter "SET NLSTRACE=2".  This will create a file called SYS:SYSTEM\NLSTRACE.DBG.  Below are the options describing the SET parameter.

NLSTRACE = 0Write file
NLSTRACE = 1Output to screen
NLSTRACE = 2Create file

There are two SET parameters which deal with licensing:
SET Dirty Certificate Cache Delay Time = <value>
<value> can be range from 1 minute to 1 hour and can be set in the STARTUP.NCF file.
Description:  Minimum time the licensing services wait before writing a dirty certificate cache to DS.
Example: SET Dirty Certificate Cache Delay Time = 1 Min

Set NLS Search Type =<value>
<value can be either  0 or 1
Description:0 = Stop upward search for license certificate at tree root
1 = Stop upward search at partition root
Example: SET NLS Search Type = 0

What do the following licensing errors reported by the policy manager?
0 Success
C0001001 Bad Handle
C0001002 No license has been installed at or above the server's context.
C0001003 The NLSLSP.NLM is not running, DS is not running, or you must "Setup licensing service" using NWCONFIG.
C0001004 License Terminated
C0001005 License is assigned to different file server.  If user assignments have been made, then the user is not assigned to the license.
C0001006 License has been installed but all units are in use.
C0001007 Resources Unavailable
C0001008 Network problem.  This is usually some sort of NDS issue.
80001009 Text Unavailable
C000100A Unknown Status
C000100B Bad Index
8000100C License is expired.
C000100D Buffer To Small
C000100E Bad argument
C0004001 Mismatched versions of NLSLSP.NLM on servers
C0004002 License is already installed.
C000400F Indicates that NLS couldn't find an NDS schema attribute it is searching for.  It is cosmetic only and does not indicate a problem with licensing.

Troubleshooting licensing issues:

DS needs to be healthy for NLS to function properly.  In order to test the DS, do the following at the console prompt:
SET DSTRACE=ON  
SET TTF=ON
SET DSTRACE=*R
SET DSTRACE=*U  --sets everybody to an ' up state'.  This helps them to communicate
SET DSTRACE=+s   -- skulker.  Sets the filter to see the partition synchronization
SET DSTRACE=+schema  --See what's happening with the schema
SET DSTRACE=*ss  --Starts the schema sync
SET DSTRACE=*h  --heart beat

Look at the DS Trace screen.  Check for all processes=YES. If you see all process DO NOT = yes, then you need to work out any DS issue before you can move on to correct NLS issues.

SET TTF=OFF
SET DSTRACE=OFF
This will capture your DSTRACE and send it to SYS:SYSTEM\DSTRACE.DBG.  If calling technical support, make sure you have this file in hand.

Also, you want to download and apply NLSLSPX.EXE, (where x is number of the revision of the file).   This has all known NLS issues resolved.  You can download this from our website:
http://support.novell.com

The container that holds the licensing objects must have browse rights to [Root].

 ++++++++++++++++++++++++++++++++++++++++++++++++++
1. Licenses can be installed via any of the following:
- During the NetWare 5 installation with the graphical user interface
- NWCONFIG | License Options | Install Licenses
- NWAdmin | Tools | Install License | Install Envelop

 ++++++++++++++++++++++++++++++++++++++++++++++++++
2. Licenses with a 9-digit serial number cannot be installed while upgrading an existing server to NetWare 5. If the serial number printed on your license diskette label has 9 digits, you must check the "Install without licenses" box on the License Installation screen during the server install. (See page 192 in the NetWare 5 Overview and Installation manual.)

After the server installation, you can use NWCONFIG (or the NetWare Administrator utility) to install licenses. Refer to Contents &GT; Novell Licensing Services &GT; Setting Up &GT; How to Install a NetWare 5 Server in the NetWare 5 Online Documentation for detailed instructions.

ò NOTE: If you first attempt to install a 9-digit license, selecting "Install without a license" may fail. In some cases it
will be necessary to start the installation again and select "Install without a license" without first browsing for a license.
++++++++++++++++++++++++++++++++++++++++++++++++++
3. The GUI install will give the user the ability to enter an Activation key which has been processed by the Activation web page.  This will only work on EPFIGS NetWare 5 CDs due to the problem described in problem 2.  The activation web site can be found at:

http://www.novell.com/products/activation/

 ++++++++++++++++++++++++++++++++++++++++++++++++++
4. NWCONFIG will allow the user the ability to enter an Activation key  obtained from the web page even if the serial
number is 9-digits long.  NUNLOCK is not needed or provided with NetWare 5.  

 ++++++++++++++++++++++++++++++++++++++++++++++++++
5. During license installation, the license objects will be created in the same container as the server object.

 ++++++++++++++++++++++++++++++++++++++++++++++++++
6. In order to obtain a licensed connection, the license container must be in the same container as the server object or in a container above the one which contains the server object.
ò The Policy Manager will walk up the tree to find the License container and not down the tree.  
ò The NLS_LSP object will govern how far to walk the tree:
  - To the root of the tree.
  - To the root of the local partition.

 ++++++++++++++++++++++++++++++++++++++++++++++++++
7. How do I move my server to a container above the one it is currently in?  
  - Run NWAdmin.
  - Delete the license objects and license containers.  
  - Delete NLS_LSP object.  
  - Move the server object.  
  - Setup licensing service through NWCONFIG
  - Install the license through NWCONFIG.

 ++++++++++++++++++++++++++++++++++++++++++++++++++
8. Will changing the name of my file server affect licensing ?
YES
ò The AUTOEXEC.NCF contains the following warning: If you change the name of this server, you must update all the licenses that are assigned to this server.  Using NWAdmin, double-click on a license object and click on the Assignments button.  If the old name of this server appears, you must delete it and add the new server name. Do this for both server and connection licenses.

ò However if there is any type of DS corruption then you may have to do the following procedure:
  - Run NWAdmin.
  - Delete the license objects and license containers.  
  - Delete NLS_LSP object.  
  - Move the server object.  
  - Setup licensing service through NWCONFIG
  - Install the license through NWCONFIG.

ò NOTE: Changing a file server's name may have other
consequences, which may affect other products.

 ++++++++++++++++++++++++++++++++++++++++++++++++++
9. A base license must be installed with a number of connection licenses.  If no base license is installed, the server will generate a message similar to:

Policy Manager 5.00-89: Server &LT;ServerName&GT; was unable to obtain a valid server base license.  Connection to this server will not be allowed.

 ++++++++++++++++++++++++++++++++++++++++++++++++++
10.  NetWare 5 requires a NetWare 5 license.  No license from a previous version of NetWare will function i.e. NetWare v4.11, NetWare v4.10, NetWare v3.12

 ++++++++++++++++++++++++++++++++++++++++++++++++++
11. When running SERVER  -NA, the following messages will be displayed?

"POLICY MANAGER: Failed to get the Server's DS context. ccode =FFFFFD88"
"POLICY MANAGER: Failed to get the Server's DS context. ccode =FFFFFD8"

"9:35:02 am:  SERVER-5.0-3651 [nmID=50020]
POLICY MANAGER- (5.00-95): ALERT: The Server &LT;ServerName&GT; is running without a Server Base License.  Please install a Server Base License immediately to say in compliance with the license agreement for this server."

NLSLSP.NLM
NLS License Service Provider
Version 4.09September 24, 1998

DS.NLM
NetWare 5.00 Directory Services.
Version 7.09August 27, 1998

 ++++++++++++++++++++++++++++++++++++++++++++++++++
12. When attempting to install a license on a NetWare 5 server the following error is displayed:  " Can not install this license."
"Error OX40002"  
"License_Install-5.13".

Suggested solutions:

  - Disconnect the network cable from the NetWare 5 server, and attempt to install the license. Reconnect the network cable.
  - Make the replica on the NetWare 5 server Master.
  - Install the Support Pack 6 on the NetWare 4.11.  This will update NLS and other modules.

The justification for this is the following: The NetWare 5 server has a Read/Write replica of DS.  The NetWare 4.11 server has the Master replica of DS and DS v5.99 or greater.  When the NetWare 5 server attempts to install the license, it has to authenticate to the 4.11 server with the Master replica.  The NetWare 4.11 server fails because it has an out of date NLS.NLM.

 ++++++++++++++++++++++++++++++++++++++++++++++++++
13. Details of a license certificate show "In use = 0" "Available = 0".  This issue is cosmetic in nature, the cause of
this problem is The server you first queried is not the default server.   If you change default server to be the server to which this certificate is assigned to, then the correct information will be displayed. Engineering is addressing this issue.

 ++++++++++++++++++++++++++++++++++++++++++++++++++
14.
Symptom:

NLSTRACE file information while trying to view the details of the certificate with NWAdmin32:

InternalNLSGetCertificate returned c0001005

NLSTRACE file information while trying to install a license:

InternalNLSInstallCertificate returned c0004002

NLSTrace file information while trying to load PROXY.NLM:

SearchSpecifiedUnits found 0 certificates on upward search
Request for license units failed. Error is c0001002
LSRequest returned c0001002.  Handle is 16821708

LSRelease returned c0001001. Handle is 16821708

Other error message may be displayed on the server console.

Solution:

The server object MUST have the "Browse" right to the certificate objects, and the "Read" property right to "All
properties".

To verify this information:
launch NWAdmin32
Browse and select the certificate in question,
Right click on the certificate object,
Select "Trustees of this Objects",
Select "Effective Rights",
Browse and select the server object
The "Objects rights" box should list "Browse".
The "Property rights" box should have the "All Properties" selected and the "Read" right.

If the rights are not granted to the object, check for Inherited Rights Filters (IRF).

Public also MUST have the "Browse" object right to the container where the certificate will be installed.  By default Public is a trustee of the [Root] object in the tree with object "Browse" rights to the entire tree (through inheritance).  Make sure no IRFs or other trustee assignments have changed this - use the above steps to verify this by checking trustees of the container.
++++++++++++++++++++++++++++++++++++++++++++++++++
Problem:  Servers are walking to the top of the tree for licenses.

Solution:  In NWADMIN go to the NLS_LSP_'server name' object.  Highlight the object.  Double click on or right mouse click and then choose detailst.  Choose search to the root  of the local partition, then choose OK.  This will cause your servers to search for licensing only in the partition that they reside in..

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10013723
  • Solution ID: 4.0.15236745.2262810
  • Creation Date: 05Aug1999
  • Modified Date: 17Feb2003
    • NovellConnectivity Products

      End of Life

      Groupware

      Management Products

      NetWare

      BorderManager Services

      eDirectory

      Other

Did this document solve your problem? Provide Feedback