Unable to Create NLS_LSP Object

(Last modified: 20Aug2002)

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

fact

Novell NetWare 5.1

Novell NetWare 5.0

Novell NetWare 4.2

Novell BorderManager 3.0

Novell BorderManager 3.5

Formerly TID 2948915

symptom

Unable to Create NLS_LSP Object

Running SETUPNLS and Install Licensing Services return errors.

Error:"No license provider available"

Error: Unable to create LSP object

NLSI.DGB contains C0001008 errors.**

cause

There is a problem with NDS.  Running SETUPNLS does two things, it extends the schema and places the NLS_LSP_server name object in NDS.  If the server can not do either of these two things, there is something wrong with NDS.

fix

For each, NDS error in the SYS:SYSTEM\NLSI.DBG file there is a separate solution.

The SYS:SYSTEM\NLSI.DBG file shows the following information:
91:Adding CN=NLS_LSP_NOBEL1.OU=UK.O=NOBEL object
91:Current server is BORDER_MANAGER.UK.NOBEL
91:NLSLSP.NLM: Directory Services error -608 encountered (nlssetup.cpp:420).
91:CreateLSPObjectForServer returned c0001008
91:NLSLSP.NLM: NLS error c0001008 encountered (nlssetup.cpp:944).
91:NLSIInstallLSP returning c0001008
91:NLSLSP.NLM: NLS error c0001008 encountered (nlssetup.cpp:796).
91:NLSISetupNLS_NoSwitch returned c0001008
89:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1271).
89:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1271).
89:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1271).
89:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1271).

NDS error -608 is an Illegal_Attribute.  SETUPNLS was trying to add a property that does not exist for this object.  NLS needs to be an attribute of the NCP Server object. To do this launch NDSMGR32.EXE (found in SYS:PUBLIC\WIN32), toolbar | Object | Schema Manager | select the NCP Server object.  Double click to open the attributes list.  NLS:Licensing Service Provider should in the list, but is not.  Click the Add attribute button and drag NLS:Licensing Service Provider form the Available Attributes list to the Current Attributes list.

The SYS:SYSTEM\NLSI.DBG file shows the following information:
87:Adding LSP object for CN=PCHCMPFS02.OU=campus.O=pch
87:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1271).
87:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1271).
87:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1271).
87:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1271).
87:Verifying class NLS:License Server
87:Verifying class NLS:Product Container
87:Verifying class NLS:License Certificate
87:Verifying class Top
87:Verifying class NCP Server
87:Adding CN=NLS_LSP_PCHCMPFS02.OU=campus.O=pch object
87:Current server is PCHNDS.pch
87:NLSLSP.NLM: Directory Services error -684 encountered (nlssetup.cpp:420).
87:CreateLSPObjectForServer returned c0001008

To get rid of the the -684 error youll need to check the server parameter NCP Packet Signature Options.  If you type SET at the server console and select NCP then look at the value of the NCP Packet Signature Options parameter take note of that value.  Then check the value on your other servers.  If some servers are set to a higher value than the rest it wont allow the servers to communicate because of the signature security level.  The Default setting is 1 and to change the setting you have to set it in the STARTUP.NCF file and reboot the server but once all servers are at the same level thhe -684 error will go away.

The SYS:SYSTEM\NLSI.DBG file shows the following information:
136:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1200).
136:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1200).
136:Verifying class NLS:License Server
136:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1200).
136:NLSIDataStatus returned 0
136:NLSLSP.NLM: Directory Services error -659 encountered (nlssetup.cpp:3113).
136:NLSLSP.NLM: NLS error c0001008 encountered (nlssetup.cpp:3173).
136:NLSLSP.NLM: NLS error c0001008 encountered (nlssetup.cpp:3207).
136:NLSIDataStatus returned c0001008

NDS error -659 means the schema time stamp is set for a future date and will not allow the changes necessary to complete the SETUPNLS.  The following steps will fix this error.
1- Verify time is synchronized on all the servers in the tree by typing the following commands at the server console prompt.
SET DSTRACE=ON
SET DSTRACE=+SCHEMA
SET DSTRACE=*SSD
SET DSTRACE=*SSA
Toggle to the Directory Services screen on the server and verify Schema completes a synch.  It will come back with All Processed=YES.  If there are errors, it will say All Processed=No.  Please fix the errors, before proceeding to the next step.
2- Load DSREPAIR -a | Advanced Options | Global Schema operations | Login | Declare a new epoch.
3- Toggle back to the Directory Services trace screen and verify Schema synch completes a synch will all the servers in the tree.  In needs to come back and say All Processed=YES, if All Processed=NO, resolve the errors before proceeding to the next step.
4- At the server console, LOAD SETUPNLS.  It will make you log in as ADMIN and should create the object without errors.

414:Verifying class NLS:License Server
414:Verifying class NLS:Product Container
414:Verifying class NLS:License Certificate
414:Verifying class Top
414:Verifying class NCP Server
414:NLSIDataStatus returned 0
414:Adding LSP object for CN=ABQ2.OU=SERVERS.OU=ABQE.OU=NM.O=HCSC
414:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1348).
414:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1348).
414:Verifying class NLS:License Server
414:Verifying class NLS:Product Container
414:Verifying class NLS:License Certificate
414:Verifying class Top
414:Verifying class NCP Server
414:Adding CN=NLS_LSP_ABQ2.OU=SERVERS.OU=ABQE.OU=NM.O=HCSC object
414:Current server is ABQ2.SERVERS.ABQE.NM.HCSC
414:NLSLSP.NLM: Directory Services error -601 encountered (nlssetup.cpp:420).
414:CreateLSPObjectForServer returned c0001008
414:NLSLSP.NLM: NLS error c0001008 encountered (nlssetup.cpp:944).
414:NLSIInstallLSP returning c0001008
414:NLSLSP.NLM: NLS error c0001008 encountered (nlssetup.cpp:796).
414:NLSISetupNLS_NoSwitch returned c0001008
421:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1348).
421:NLSLSP.NLM: NLS error c000400f encountered (..\common\src\dsclib.cpp:1348).

Added replica to the target server, then created the license provider via NWConfig.

648:NLSLSP.NLM: NLS error c000400f encountered
(..\common\src\dsclib.cpp:1369).
648:NLSLSP.NLM: NLS error c000400f encountered
(..\common\src\dsclib.cpp:1369).
648:NLSLSP.NLM: NLS error c000400f encountered
(..\common\src\dsclib.cpp:1369).
648:NLSLSP.NLM: NLS error c000400f encountered
(..\common\src\dsclib.cpp:1369).
648:Verifying class NLS:License Server
648:Verifying class NLS:Product Container
648:Verifying class NLS:License Certificate
648:Verifying class Top
648:Verifying class NCP Server
648:NLSIDataStatus returned 0
648:Adding LSP object for CN=ASUB.OU=ASUB.O=ASUBORG
648:NLSLSP.NLM: NLS error c000400f encountered
(..\common\src\dsclib.cpp:1369).
648:NLSLSP.NLM: NLS error c000400f encountered
(..\common\src\dsclib.cpp:1369).
648:NLSLSP.NLM: NLS error c000400f encountered
(..\common\src\dsclib.cpp:1369).
648:NLSLSP.NLM: NLS error c000400f encountered
(..\common\src\dsclib.cpp:1369).
648:Verifying class NLS:License Server
648:Verifying class NLS:Product Container
648:Verifying class NLS:License Certificate
648:Verifying class Top
648:Verifying class NCP Server
648:Adding CN=NLS_LSP_ASUB.OU=ASUB.O=ASUBORG object
648:Current server is ASUB.ASUB.ASUBORG
648:NLSLSP.NLM: Directory Services error -255 encountered
(nlssetup.cpp:420).
648:CreateLSPObjectForServer returned c0001008
648:NLSLSP.NLM: NLS error c0001008 encountered (nlssetup.cpp:944).
648:NLSIInstallLSP returning c0001008
648:NLSLSP.NLM: NLS error c0001008 encountered (nlssetup.cpp:796).
648:NLSISetupNLS_NoSwitch returned c0001008

The error -255 could be related to a file creation error, or a bad paramter. Do a CLEAR STATION ALL at the console prompt, run a DSREPAIR on the local database, and rebuild operational schema. Also, look in the _NETWARE directory, and check for any old .OLD files.

**Note: NLSI.DBG is created when NLS_LSP_Servername object is being created automatically.  It is found in SYS:SYSTEM\NLSI.DBG.

document

Document Title: Unable to Create NLS_LSP Object
Document ID: 10022060
Solution ID: 1.0.40438242.2413205
Creation Date: 18Nov1999
Modified Date: 20Aug2002
Novell Product Class:NetWare
Novell BorderManager Services

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.