These are the NCPX error codes included in this section:
138 0x8A NO DELETE PRIVILEGES
Source:
NCPX
Explanation:
If this message is received, the user probably does not have rights to the sys:system\ndsdm directory on the NetWare® server.
Action:
If appropriate, make the user a trustee of the sys:system\ndsdm directory. NetWare Administrator is one utility that can be used to accomplish this task.
Source:
NCPX
Explanation:
This error could be received for several reasons:
-
The user did a bindery login.
-
The user was logged in through eDirectory™ or NDS™ but to a different tree.
-
The user object was removed from eDirectory or NDS between the time the user logged in and the time the NCPX extension was executed.
Action:
Make sure the user is connected to the network and applicable server, and verify that the user has a valid eDirectory or NDS connection.
125 0x7D CONNECTION NOT LOGGED IN
Source:
NCPX
Explanation:
The Integration Utility, igrate.exe, or the Object Replication Service (ORS) agent tried to execute an NCPX extension without an authenticated connection; or, at the server console, someone removed the NetWare connection.
Action:
From the Windows* NT* Explorer, go to Network Neighborhood and verify that you have an authenticated connection. If you do not have an authenticated connection to the NetWare server you want to work with, make one.
150 0x96 SERVER OUT OF MEMORY
Source:
NCPX
Explanation:
The NetWare server has run out of memory.
Action:
Add memory or unload some unnecessary NetWare Loadable Module (NLM™) programs.
192 0xC0 NO ACCOUNT PRIVILEGES
Source:
NCPX
Explanation:
The user does not have sufficient rights to run operations in igrate.exe, on the NetWare server where the ndsds.nlm resides.
Action:
Before operating the igrate.exe, make sure the user has Supervisor rights to the NetWare server where the ndsds.nlm resides.
254 0xFE NCPEXT NO HANDLER
Source:
NCPX
Possible Cause:
The ndsdm.nlm program has been unloaded.
Action:
At the server console, type modules. If the ndsdm.nlm is not loaded, it will not appear in the list of modules displayed.
Possible Cause:
Igrate.exe or the ORS agent on an NT system tried to access the NLM program, and the file was not available.
Action:
If the NLM program is not loaded, load the program by typing load ndsdm.
Possible Cause:
The ndsdm.nlm program tried to access a NetWare server that did not have the NLM loaded and active.
255 0xFF NO RESPONSE FROM SERVER
Source:
NCPX
Explanation:
Igrate.exe issued a command and the ORS agent was busy, down, or not responding on the Windows NT machine.
Action:
Try the following actions:
-
Retry the operation. If the error still occurs, go to the NT machine, open Control panel, then launch the Services applet. Locate the NDS Object Replication Service (MWAAgent). This service should be started and left to run on automatic.
-
If the service is not started, reboot the machine.
Possible Cause:
If the NT Client was removed from the NT machine, one of the agent's dependencies might be hampered.