These are the NDPS error codes included in this section:
-801 0xFFFFFCDF NDPS E NO MEMORY
Source:
NDPS, NDPS Manager NLM program
Explanation:
The server has insufficient memory to support the requested operation.
Possible Cause:
The server does not have enough memory installed.
Action:
Add memory to the server.
Possible Cause:
A program is running that is using too much memory.
Action:
Identify the program that is using too much memory and unload it.
-803 0xFFFFFCDD NDPS E JOB STORAGE LIMIT
Source:
NDPS, NDPS Manager NLM program
Explanation:
The Total Job Space Limit used by print jobs and retained jobs has reached the limit set for the Printer Agent.
Action:
Do one or more of the following actions:
-
Raise the total job space limit for the Printer Agent.
-
Remove some retained jobs.
-
Cancel some pending print jobs.
-
Wait for any pending jobs to process.
-804 0xFFFFFCDC NDPS E JOB RETENTION LIMIT
Source:
NDPS, NDPS Manager NLM program
Explanation:
The Retained Job Space Limit used by retained print jobs has reached the limit set for the Printer Agent.
Action:
Do one or more of the following actions:
-805 0xFFFFFCDB NDPS E UNSUPPORTED TYPE
Source:
NDPS, NDPS Manager NLM program
Explanation:
A referenced object class or object attribute value is not supported in a client application.
Possible Cause:
A programming error occurred in the application you are running.
Action:
If the problem persists, contact the developer of the application.
-806 0xFFFFFCDA NDPS E UNDEFINED TYPE
Source:
NDPS, NDPS Manager NLM program
Explanation:
A referenced object class is not defined for NDPS.
Possible Cause:
A programming error was encountered in the application you are running. An object class that is not defined for NDPS was used in a client application.
Action:
Notify the developer of the application program about the problem.
-807 0xFFFFFCD9 NDPS E UNSUPPORTED OP
Source:
NDPS, NDPS Manager NLM program
Explanation:
An operation was requested that is not supported by the NDPS Manager.
Possible Cause:
The application you are running encountered a programming error. An unsupported operation was requested by a client application.
Action:
Notify the developer of the application program about the problem.
-809 0xFFFFFCD7 NDPS E NO PDS
Source:
NDPS, NDPS Manager NLM program
Explanation:
A Print Device Subsystem (PDS) or third-party gateway is not bound to the Printer Agent.
Possible Cause:
The Printer Agent has not been configured with a valid PDS or third-party gateway.
Action:
Make sure the Printer Agent is configured with a valid PDS or third-party gateway.
Possible Cause:
The PDS or third-party gateway has been unloaded.
Action:
Load the PDS or third-party gateway. Try shutting down and starting up the Printer Agent from the NDPS Manager to see if the PDS or third-party gateway loads as part of the Printer Agent startup procedure. You can do this in NetWare® Administrator through the Public Access Printers list for the NDPS Manager, or at the server console by selecting the Printer Agent from the list of Printer Agents.
-810 0xFFFFFCD6 NDPS E INVALID CLASS
Source:
NDPS, NDPS Manager NLM program
Explanation:
A referenced object class is not defined for NDPS.
Possible Cause:
The application you are running encountered a programming error. An object class that is not defined for NDPS was used in a client application.
Action:
Notify the developer of the application program about the problem.
-811 0xFFFFFCD5 NDPS E BAD PARAMETER
Source:
NDPS, NDPS Manager NLM program
Explanation:
An operation request included a bad parameter.
Possible Cause:
The application you are running encountered a programming error. A bad parameter was included in a request from a client application.
Action:
Notify the developer of the application program about the problem.
-812 0xFFFFFCD4 NDPS E OBJECT NOT FOUND
Source:
NDPS, NDPS Manager NLM program
Explanation:
The requested object for an operation was not found.
Possible Cause:
The object was not created or has been deleted.
Action:
Make sure the object exists.
Possible Cause:
The ID for an object is invalid.
Action:
Make sure the object ID is valid.
-813 0xFFFFFCD3 NDPS E ATTRIBUTE NOT FOUND
Source:
NDPS, NDPS Manager NLM program
Explanation:
The requested object attribute for an operation was not found.
Possible Cause:
The attribute was not created or has been deleted.
Action:
Make sure the attribute exists.
Possible Cause:
The ID for the attribute is invalid.
Action:
Make sure the attribute ID is valid.
-814 0xFFFFFCD2 NDPS E VALUE NOT FOUND
Source:
NDPS, NDPS Manager NLM program
Explanation:
The attribute value for an object that was requested for an operation was not found.
Possible Cause:
The attribute or attribute value was not created or has been deleted.
Action:
Make sure the attribute or attribute value exists.
Possible Cause:
The ID for the attribute is invalid.
Action:
If the attribute value was expected to be found, make sure the attribute ID is valid.
-815 0xFFFFFCD1 NDPS E VALUES NOT COMPARABLE
Source:
NDPS, NDPS Manager NLM program
Explanation:
A request to list objects includes a filter whose syntax is not valid for the specified attribute.
Possible Cause:
The application you are running encountered a programming error. An object query filter with invalid syntax for the attribute value was used in a client application.
Action:
Notify the developer of the application program about the problem.
-816 0xFFFFFCD0 NDPS E INVALID VALUE SYNTAX
Source:
NDPS, NDPS Manager NLM program
Explanation:
An attribute value contains an invalid syntax.
Possible Cause:
The application you are running encountered a programming error. An invalid attribute value syntax was used in a client application.
Action:
Notify the developer of the application program about the problem.
-817 0xFFFFFCCF NDPS E JOB NOT FOUND
Source:
NDPS, NDPS Manager NLM program
Explanation:
An operation request specified a print job that is not found.
Possible Cause:
The print job has been canceled.
Action:
Send the job again.
Possible Cause:
The job has already been processed.
Action:
Check the job ID to see if the job has already been processed.
-818 0xFFFFFCCE NDPS E COMMUNICATION
Source:
NDPS, NDPS Manager NLM program
Explanation:
The Printer Agent was unable to communicate with an NDPS Broker or with another Printer Agent.
Possible Cause:
The server does not have sufficient memory to complete the operation.
Action:
Add more memory to the server or unload unnecessary NetWare Loadable Module™ (NLM) programs.
Possible Cause:
The target NDPS Broker or Printer Agent is not loaded.
Action:
Make sure the target NDPS Broker or Printer Agent is loaded.
Possible Cause:
Network problems exist.
Action:
Check the system console and error log for reported errors. Resolve any network errors indicated and try the task again.
-819 0xFFFFFCCD NDPS E PA INITIALIZING
Source:
NDPS, NDPS Manager NLM program
Explanation:
The Printer Agent is still initializing.
Possible Cause:
A service request was received while the Printer Agent was still initializing.
Action:
Wait for the Printer Agent to finish initializing, then try the request again.
-820 0xFFFFFCCC NDPS E PA GOING DOWN
Source:
NDPS, NDPS Manager NLM program
Explanation:
A service request was received while the Printer Agent was going down.
Action:
Start up the Printer Agent from the NDPS Manager in NetWare Administrator or at the server console, then try the request again.
-821 0xFFFFFCCB NDPS E PA DISABLED
Source:
NDPS, NDPS Manager NLM program
Explanation:
The Printer Agent is disabled, probably because input to the printer has been paused. No new print jobs are accepted while the Printer Agent is disabled.
Action:
Resume input to the printer.
-822 0xFFFFFCCA NDPS E PA PAUSED
Source:
NDPS, NDPS Manager NLM program
Explanation:
Printer output has been paused. No jobs can be supplied to the PDS or third-party gateway while output is paused.
Action:
Resume printer output.
-823 0xFFFFFCC9 NDPS E BAD PA HANDLE
Source:
NDPS, NDPS Manager NLM program
Explanation:
A bad Printer Agent handle has been referenced in the NDPS Manager.
Possible Cause:
An internal programming error was encountered in the NDPS Manager.
-824 0xFFFFFCC8 NDPS E OBJECT NOT LOCKED
Source:
NDPS, NDPS Manager NLM program
Explanation:
An attempt has been made to modify an object that is not locked.
Possible Cause:
An internal programming error was encountered in the NDPS Manager.
-826 0xFFFFFCC6 NDPS E PSM INITIALIZING
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager is initializing.
Possible Cause:
A service request was received while the NDPS Manager was initializing.
Action:
Wait for the NDPS Manager to finish initializing, then try the request again.
-827 0xFFFFFCC5 NDPS E PSM GOING DOWN
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager is going down.
Possible Cause:
A service request was received while the NDPS Manager was going down.
Action:
Load the NDPS Manager, then try the request again.
-828 0xFFFFFCC4 NDPS E NOTIF SVC ERROR
Source:
NDPS, NDPS Manager NLM program
Explanation:
The Notification Service returned an error code for a service request.
Possible Cause:
A referenced event profile was not recognized by the Notification Service.
Action:
See the documentation for the error code that was returned by the Notification Service.
-829 0xFFFFFCC3 NDPS E MEDIUM NEEDS MOUNTED
Source:
NDPS, NDPS Manager NLM program
Explanation:
The medium requested for the current print job needs to be mounted.
Possible Cause:
The current print job needs a medium that is not ready.
Action:
Mount the required medium, then set the current medium information for the Printer Agent.
-830 0xFFFFFCC2 NDPS E PDS NOT RESPONDING
Source:
NDPS, NDPS Manager NLM program
Explanation:
The PDS or gateway is not responding to a request from the Printer Agent.
Possible Cause:
The request timed out on a query because the PDS or gateway is very busy or the connection to its printer is slow.
Action:
If the error occurs repeatedly, check the performance of the PDS or gateway and the connection to its printer.
-831 0xFFFFFCC1 NDPS E SESSION NOT FOUND
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager could not find a client session for the client making a service request.
Possible Cause:
The client has not performed a bind operation or the client connection has been lost at the server.
-832 0xFFFFFCC0 NDPS E RPC FAILURE
Source:
NDPS, NDPS Manager NLM program
Explanation:
A remote procedure call (RPC) error occurred during an attempt by the Printer Agent to communicate with an NDPS Broker or another Printer Agent.
Possible Cause:
The target NDPS Broker or Printer Agent has unloaded.
Action:
Make sure the target NDPS Broker or Printer Agent is loaded.
Possible Cause:
A network communication problem has occurred.
-833 0xFFFFFCBF NDPS E DUPLICATE VALUE
Source:
NDPS, NDPS Manager NLM program
Explanation:
An attempt was made to create a Printer Agent that already exists or to duplicate an association of a Printer object with a Printer Agent.
Possible Cause:
A second request was made for an operation that had already succeeded. No action is required.
-834 0xFFFFFCBE NDPS E PDS REFUSES RENAME
Source:
NDPS, NDPS Manager NLM program
Explanation:
The PDS or gateway refused a request to rename a Printer Agent.
Possible Cause:
The PDS or gateway might not support changing the name of a Printer Agent or might be in a temporary state that prevents the name change.
Action:
Try the operation again to see if it succeeds. If it does not succeed, unload the PDS or gateway that is bound to the Printer Agent, and rename the Printer Agent.
-836 0xFFFFFCBC NDPS E ALREADY ATTACHED
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager attempted to log in to a file server to which it was already attached.
Possible Cause:
An internal programming error was encountered in the NDPS Manager.
-837 0xFFFFFCBB NDPS E CANT ATTACH
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to log in to a file server.
Possible Cause:
The NDPS Manager was unable to establish a new connection to a file server. This might be due to network problems, such as a router being down.
Action:
Make sure the equipment for establishing a connection is up. If the problem persists, contact a Novell Support Provider.
-838 0xFFFFFCBA NDPS E TOO MANY NW SERVERS
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager has reached the limit for the number of servers to which it can log in.
Possible Cause:
The Printer Agents supported by this NDPS manager are assigned to too many separate NDPS Brokers.
Action:
Where practical, use the same Broker for multiple Printer Agents.
Possible Cause:
The Printer Agents are configured to support print queues on too many servers.
Action:
Check the assignment of print queues to the Printer objects for the Printer Agents supported by this NDPS Manager.
-839 0xFFFFFCB9 NDPS E CANT CREATE DOC FILE
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to create a document data file for a print job.
Possible Cause:
The file server volume might be dismounted.
Action:
Make sure the file server volume is mounted.
Possible Cause:
The file server volume might be full.
Action:
Make sure the volume is not full.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. If possible, resolve any errors and try the task again.
-840 0xFFFFFCB8 NDPS E CANT DELETE DOC FILE
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to delete a document data file for a print job.
Possible Cause:
File attributes were modified.
Action:
If appropriate, make sure the file attributes allow the user to delete a document data file for a print job.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors and try the task again. If the problem persists, contact a Novell Support Provider.
-841 0xFFFFFCB7 NDPS E CANT OPEN DOC FILE
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to open a document data file for a print job.
Possible Cause:
File attributes were modified.
Action:
If appropriate, make sure the file attributes allow the user to open a document data file for a print job.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors and try the task again. If the problem persists, contact a Novell Support Provider.
-842 0xFFFFFCB6 NDPS E CANT WRITE DOC FILE
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to write data to a document data file for a print job.
Possible Cause:
The file server volume might be dismounted.
Action:
Make sure the volume is mounted.
Possible Cause:
The file server volume might be full.
Action:
Make sure the volume is not full.
Possible Cause:
File attributes have been modified.
Action:
If appropriate, make sure the file attributes allow the user to write data to a document data file for a print job.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors found and try the task again. If the problem persists, contact a Novell Support Provider.
-844 0xFFFFFCB4 NDPS E NO SCHEDULER
Source:
NDPS, NDPS Manager NLM program
Explanation:
A Printer Agent is not bound to a scheduler.
Possible Cause:
The scheduler has been unloaded or a problem has occurred in the scheduler.
-845 0xFFFFFCB3 NDPS E CHANGING CONNECTION
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to change its current file server connection.
Possible Cause:
A network problem or a system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors found and try the task again. If the problem persists, contact a Novell Support Provider.
-846 0xFFFFFCB2 NDPS E COULD NOT CREATE ACC REF
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to initialize access to the NDPS Library.
Possible Cause:
The server is low on memory.
Action:
Add memory to the server, or identify the program that is using too much memory and unload it.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors found and try the task again. If the problem persists, contact a Novell Support Provider.
-900 0xFFFFFC7C NWDP OE RM OUT OF MEMORY
Source:
NDPS, Resource Manager NLM program
Explanation:
The Resource Manager is out of memory.
Possible Cause:
The server is out of available memory to allocate.
Action:
Make more memory available to the Resource Manager by adding more memory to the server or by unloading unused NLM programs.
-901 0xFFFFFC7B DB E CANT CREATE FILE
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to create a Managed Object Database (MODB) file.
Possible Cause:
The file server volume might be dismounted.
Action:
Make sure the file server volume is mounted.
Possible Cause:
The file server volume might be full.
Action:
Make sure the volume is not full.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors and try the task again. If the problem persists, contact a Novell Support Provider.
-901 0xFFFFFC7B NWDP OE RM BAD NETWARE VERSION
Source:
NDPS, Resource Manager NLM program
Explanation:
The Resource Manager encountered a version of NetWare with which it is not compatible.
Possible Cause:
The Resource Manager requires a NetWare 4.11 or later server operating system.
Action:
Run NDPS on NetWare 4.11 or later.
-902 0xFFFFFC7A DB E CANT FIND DATA FILE
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to find a MODB file.
Possible Cause:
The database file has been deleted.
Action:
Restore the MODB from its backup.
-903 0xFFFFFC79 DB E CANT OPEN DATA FILE
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to open the MODB data file.
Possible Cause:
The file server volume might be dismounted.
Action:
Make sure the volume is mounted.
Possible Cause:
Another program might have opened the file.
Action:
Make sure the file is not already opened by another program.
Possible Cause:
File attributes were modified.
Action:
If appropriate, make sure the file attributes allow the user to open the MODB data file.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors found and try the task again. If the problem persists, contact a Novell Support Provider.
-904 0xFFFFFC78 DB E CANT OPEN INDEX FILE
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to open the MODB index file.
Possible Cause:
The file server volume might be dismounted.
Action:
Make sure the volume is mounted.
Possible Cause:
Another program might have opened the file.
Action:
Make sure the file is not already opened by another program.
Possible Cause:
File attributes were modified.
Action:
If appropriate, make sure the file attributes allow the user to open the MODB index file.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors found and try the task again. If the problem persists, contact a Novell Support Provider.
-905 0xFFFFFC77 DB E INDEX FILE NOT OPEN
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager MODB index file is not open.
Possible Cause:
An internal programming error was encountered in the NDPS Manager.
-906 0xFFFFFC76 DB E CANT RENAME FILE
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to rename a file.
Possible Cause:
The file server volume might be dismounted.
Action:
Make sure the volume is mounted.
Possible Cause:
File attributes were modified.
Action:
If appropriate, make sure the file attributes allow the user to rename the specified file.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors found and try the task again. If the problem persists, contact a Novell Support Provider.
-906 0xFFFFFC76 NWDP OE RM FAILED TO CRTE THRED
Source:
NDPS, Resource Manager NLM program
Explanation:
The NetWare operating system was unable to create a thread to run the Resource Management Service (RMS) main thread.
-907 0xFFFFFC75 DB E CANT READ DATA FILE
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to read the MODB data file.
Possible Cause:
The file server volume might be dismounted.
Action:
Make sure the volume is mounted.
Possible Cause:
File attributes were modified.
Action:
If appropriate, make sure the file attributes allow the user to read the MODB data file.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors found and try the task again. If the problem persists, contact a Novell Support Provider.
-907 0xFFFFFC75 NWDP OE RM SVC MUST BE FULL DIS
Source:
NDPS, Resource Manager NLM program
Explanation:
The Resource Manager services must be fully disconnected.
Possible Cause:
The Resource Manager is already starting up or is in the process of going down.
Action:
Make sure the Resource Manager is fully disabled before enabling it.
-908 0xFFFFFC74 DB E CANT READ INDEX FILE
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to read the MODB index file.
Possible Cause:
The file server volume might be dismounted.
Action:
Make sure the volume is mounted.
Possible Cause:
File attributes were modified.
Action:
If appropriate, make sure the file attributes allow the user to read the MODB index file.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors found and try the task again. If the problem persists, contact a Novell Support Provider.
-908 0xFFFFFC74 NWDP OE RM DS VAL SIZE TOO LARG
Source:
NDPS, Resource Manager NLM program
Explanation:
An attribute value on an eDirectory™ or NDS™ object that the RMS was trying to read is too large.
Possible Cause:
The attribute value size on the Broker object is larger than the buffer allowed (1024 bytes) to get the data.
Action:
Use NLIST to check the attributes of the Broker object and change them if necessary.
-909 0xFFFFFC73 DB E CANT WRITE DATA FILE
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to write information to the MODB data file.
Possible Cause:
The file server volume might be dismounted.
Action:
Make sure the volume is mounted.
Possible Cause:
File attributes were modified.
Action:
If appropriate, make sure the file attributes allow the user to write to the MODB data file.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors found and try the task again. If the problem persists, contact a Novell Support Provider.
-909 0xFFFFFC73 NWDP OE RM NO ATTRIBUTE VALUES
Source:
NDPS, Resource Manager NLM program
Explanation:
The Resource Manager tried to read the attribute for an object, but it has no value.
Possible Cause:
The value is not set on an object’s attribute.
Action:
Check attributes of the NDPS Broker object that have to do with the Resource Manager. Make sure they have valid values.
-910 0xFFFFFC72 DB E CANT WRITE INDEX FILE
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to write information to the MODB index file.
Possible Cause:
The file server volume might be dismounted.
Action:
Make sure the volume is mounted.
Possible Cause:
File attributes were modified.
Action:
If appropriate, make sure the file attributes allow the user to write to the MODB index file.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors found and try the task again. If the problem persists, contact a Novell Support Provider.
-910 0xFFFFFC72 NWDP OE RM UNKNOWN SESSION
Source:
NDPS, Resource Manager NLM program
Explanation:
A request is being made to get information from a Transport Independent Remote Procedure Call (TIRPC) connections session table and the session number passed in was invalid.
-911 0xFFFFFC71 DB E CANT DELETE PA DIR
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager was unable to remove the job data pool directory for a Printer Agent.
Possible Cause:
The file server volume might be dismounted.
Action:
Make sure the volume is mounted.
Possible Cause:
File attributes were modified.
Action:
If appropriate, make sure the file attributes allow the user to remove the job data pool directory for a Printer Agent.
Possible Cause:
A system error has occurred.
Action:
Check the server console and error log file for system errors. Resolve any errors found and try the task again. If the problem persists, contact a Novell Support Provider.
-911 0xFFFFFC71 NWDP OE RM ERROR READING FILE
Source:
NDPS, Resource Manager NLM program
Explanation:
An error occurred while reading a file during a call to get a resource file from the RMS data storage area.
Possible Cause:
Rights to read the file were not assigned to the Broker object.
Action:
Make sure the Broker object has the Read right to the specified file.
-912 0xFFFFFC70 DB E ALREADY DELETED
Source:
NDPS, NDPS Manager NLM program
Explanation:
The NDPS Manager tried to delete a data record that was already deleted.
Possible Cause:
An internal programming error occurred in the NDPS Manager.
-913 0xFFFFFC6F DB E OBJECT EXISTS
Source:
NDPS, NDPS Manager NLM program
Explanation:
A request was made to create an object that already exists.
Possible Cause:
The user or a client application requested creation of a Printer Agent, medium, or other object that already exists.
-913 0xFFFFFC6F NWDP OE RM SERVICE DISABLED
Source:
NDPS, Resource Manager NLM program
Explanation:
The RMS status flag was set to disabled.
Possible Cause:
The RMS was disabled when it was expected to be available.
Action:
Check the server console screen to ensure the RMS status is Enabled.
-914 0xFFFFFC6E DB E DESCRIPTOR IN USE
Source:
NDPS, NDPS Manager NLM program
Explanation:
A process in the NDPS Manager failed to release an object descriptor in a timely manner.
Possible Cause:
The processor utilization on the server is too high, preventing timely execution in the NDPS Manager.
Action:
Solve the utilization problem on the server, then try the task again. If the problem persists, contact a Novell Support Provider.
Possible Cause:
An internal problem occurred in the NDPS Manager.
-914 0xFFFFFC6E NWDP OE RM UNKNOWN MODIFY OPER
Source:
NDPS, Resource Manager NLM program
Explanation:
An unknown modify operation was attempted on an eDirectory or NDS object attribute.
-915 0xFFFFFC6D DB E DESCRIPTOR BEING DELETED
Source:
NDPS, NDPS Manager NLM program
Explanation:
A process in the NDPS Manager attempted to access an object that was being deleted.
Possible Cause:
An internal programming error was encountered in the NDPS Manager.
-915 0xFFFFFC6D NWDP OE RM DUPLICATE SESSION ID
Source:
NDPS, Resource Manager NLM program
Explanation:
A duplicate session number is being used during a bind to the RMS.
Possible Cause:
The connection from client to server is being scrambled.
-916 0xFFFFFC6C NWDP OE RM INVALID CREDENTIAL
Source:
NDPS, Resource Manager NLM program
Explanation:
An invalid credential was passed to RMS bind process on the server.
Possible Cause:
An error occurred in the ResRef that was created to talk to the RMS.
-919 0xFFFFFC69 NWDP OE RM FAIL TO GET MSGS
Source:
NDPS, Resource Manager NLM program
Explanation:
The program could not get the message file for the RMS NLM program.
Possible Cause:
The file rmansrvr.msg is missing or corrupted.
-920 0xFFFFFC68 NWDP OE RM FAIL TO CRTE CONTEXT
Source:
NDPS, Resource Manager NLM program
Explanation:
The program could not create an eDirectory or NDS context while trying to initialize the identity facility of the RMS.
-921 0xFFFFFC67 NWDP OE RM FAIL TO LOGIN
Source:
NDPS, Resource Manager NLM program
Explanation:
RMS could not login to eDirectory or NDS using the Broker's account.
Possible Cause:
The eDirectory or NDS account for the Broker is not in working condition.
Action:
Use NetWare Administrator to the check status of the Broker’s account and make sure it is in working condition.
-922 0xFFFFFC66 NWDP OE RM NPD FILE GEN ERR
Source:
NDPS, Resource Manager NLM program
Explanation:
The Resource Manager could not generate a printer definition file (.npd) while creating a Printer Agent.
Possible Cause:
Some files in the ndps\resdir\prndef\novell directory might be corrupted.
Action:
Replace the corrupted files by reinstalling NDPS or copying the resdir\prndef subdirectory from the Installation CD to the installed resdir directory on the server.
-923 0xFFFFFC65 NWDP OE RM INF FILE FORMAT ERR
Source:
NDPS, Resource Manager NLM program
Explanation:
An index file (.inf) being processed for printer drivers or printer definitions has a problem with its format.
Possible Cause:
An unusable index file was on the vendor-supplied printer driver disk.
Action:
Contact the vendor of the printer driver.
Possible Cause:
An unusable index file was in the preinstalled drivers shipped with NDPS.
-924 0xFFFFFC64 NWDP OE RM NO PRT TYPE IN INF
Source:
NDPS, Resource Manager NLM program
Explanation:
The printer type specified does not exist in the printer driver or printer definition index file.
Possible Cause:
The index file is corrupted.
Action:
Replace the corrupted index file by reinstalling NDPS.
Possible Cause:
A programming error occurred in which faulty input data was supplied to a library API function.
Action:
Contact the developer of the application.
-925 0xFFFFFC63 NWDP OE RM NO INF FILES PRESENT
Source:
NDPS, Resource Manager NLM program
Explanation:
No printer driver or printer definition index files are present from which to create a list.
Possible Cause:
The RMS data area on the server is corrupted or missing.
Action:
Make sure the resdir directory is in the correct location.
Possible Cause:
No index files were present on a developer-supplied floppy diskette.
Action:
See if an .inf or .ndx file exists on a floppy diskette supplied by the vendor. If one does exist, copy the file to the RMS data area on the server.
-926 0xFFFFFC62 NWDP OE RM FILE OPEN ERROR
Source:
NDPS, Resource Manager NLM program
Explanation:
The RMS could not open a file.
Possible Cause:
A file is missing or RMS does not have the appropriate rights to a file.
Action:
Check the system console for reported errors. If necessary, assign the appropriate rights to the file referenced.
-927 0xFFFFFC61 NWDP OE RM READ FILE ERROR
Source:
NDPS, Resource Manager NLM program
Explanation:
The RMS could not read a file.
Possible Cause:
The RMS does not have the appropriate rights to read the file.
Action:
Check the system console for reported errors. Make sure the RMS has rights to read the file that is referenced.
-928 0xFFFFFC60 NWDP OE RM WRITE FILE ERROR
Source:
NDPS, Resource Manager NLM program
Explanation:
The RMS could not write to a file.
Possible Cause:
The RMS does not have rights to write to the file.
Action:
Check the system console for reported errors. Make sure the RMS has rights to write to the file that is referenced.
-929 0xFFFFFC5F NWDP OE RM RESRC TYPE INVALID
Source:
NDPS, Resource Manager NLM program
Explanation:
A resource type enum that is invalid was passed to an NDPS library API.
Action:
If you are trying to debug a program, check the resource type passed in against the allowed resource enum values in the nwdprms.h file.
-930 0xFFFFFC5E NWDP OE RM NO SUCH FILENAME
Source:
NDPS, Resource Manager NLM program
Explanation:
A file operation was attempted on a file that did not exist.
Possible Cause:
The RMS attempted an operation that did not find the file referenced.
-931 0xFFFFFC5D NWDP OE RM BANR TYPE INVALID
Source:
NDPS, Resource Manager NLM program
Explanation:
The banner, enum type, passed to an NDPS library API is invalid.
Possible Cause:
A calling code error has occurred.
Action:
Contact the developer of the program.
Action:
If you are trying to debug a program, check the calling code and pass a valid enum.
-932 0xFFFFFC5C NWDP OE RM LIST TYPE UNKNOWN
Source:
NDPS, Resource Manager NLM program
Explanation:
The list type, enum type, passed to an NDPS library API (nwdpreslistresource) is invalid.
Possible Cause:
A calling code error has occurred.
Action:
Contact the developer of the program.
Action:
If you are trying to debug a program, check the calling code and pass a valid enum.
-933 0xFFFFFC5B NWDP OE RM OS NOT SUPPORTED
Source:
NDPS, Resource Manager NLM program
Explanation:
The operating system type, enum type, passed to an NDPS library API is not currently supported.
Possible Cause:
A calling code error has occurred.
Action:
Contact the developer of the program.
Action:
If you are trying to debug a program, check the calling code and pass a valid enum.
-934 0xFFFFFC5A NWDP OE RM NO BANR FILES PRESNT
Source:
NDPS, Resource Manager NLM program
Explanation:
No banner files were present in the NDPS resdir or on a user-supplied floppy diskette.
Possible Cause:
No banner files are present.
Action:
Check the location and condition of the resdir directory.
-936 0xFFFFFC58 NWDP OE RM NO PRN TYPES IN LIST
Source:
NDPS, Resource Manager NLM program
Explanation:
No valid printer types were found while the Resource Manager was trying to list printer drivers or printer definitions from the common resource storage area.
Possible Cause:
The common resource storage area is missing or corrupted.
Action:
Check the condition of the common resource storage area in the resdir directory.
-937 0xFFFFFC57 NWDP OE RM OPTION NOT SUPPORTED
Source:
NDPS, Resource Manager NLM program
Explanation:
A designator or enum value that is not supported was passed to the RMS.
Possible Cause:
A bad enum was passed to an NDPS library call.
Action:
Contact the developer of the application.
Action:
If you are trying to debug a program, check the calling code.
-938 0xFFFFFC56 NWDP OE RM UNICODE CONV ERR
Source:
NDPS, Resource Manager NLM program
Explanation:
An error occurred while trying to convert from local code page to Unicode* or from Unicode to a local code page.
Possible Cause:
Invalid Unicode data was input to an NDPS library call.
Action:
Contact the developer of the application.
Action:
If you are trying to debug a program, check the calling code.
-939 0xFFFFFC55 NWDP OE RM INVALID ARGUMENTS
Source:
NDPS, Resource Manager NLM program
Explanation:
Invalid arguments were passed to the RMS NLM program.
Possible Cause:
Invalid arguments were passed to an NDPS library API.
Action:
Contact the developer of the application.
Action:
If you are trying to debug a program, check the calling code.
-940 0xFFFFFC54 NWDP OE RM INITIALIZATION ERROR
Source:
NDPS, Resource Manager NLM program
Explanation:
An error occurred while initializing the RMS on the server.
-941 0xFFFFFC53 NWDP OE RM NO SRV REG AVAILABLE
Source:
NDPS, Resource Manager NLM program
Explanation:
No Service Registry Service (SRS) was available for the RMS to register with.
Possible Cause:
The SRS is not enabled, or one could not be found.
Action:
Enable the SRS and try the task again.
-942 0xFFFFFC52 NWDP OE RM FAIL RGSTR TO ANY SR
Source:
NDPS, Resource Manager NLM program
Explanation:
The Resource Manager could not register with a SRS.
Possible Cause:
No SRS is available, or a problem exists with the SRS.
Action:
Enable the SRS, or shut down the SRS and bring it back up, then try the task again.
-944 0xFFFFFC50 NWDP OE RM NOT ADMIN SESSION
Source:
NDPS, Resource Manager NLM program
Explanation:
The RMS bind attempted an operation that requires Admin rights.
Possible Cause:
The user is not an Admin of the Broker object.
Action:
Log in as the user Admin or as a user with equivalent rights.
-945 0xFFFFFC4F NWDP OE RM NO EFFECTIVE RIGHTS
Source:
NDPS, Resource Manager NLM program
Explanation:
No rights are available to read attributes of the Broker object.
Possible Cause:
The RMS is not logged in correctly.
-946 0xFFFFFC4E NWDP OE RM BAD FILE ATTRIBUTE
Source:
NDPS, Resource Manager NLM program
Explanation:
The Resource Manager could not set the share attribute on a file that was added to the resdir directory.
Possible Cause:
The rights in the common resource storage area, the resdir directory, have been modified.
Action:
Make sure the Resource Manager has the appropriate rights.
-947 0xFFFFFC4D NWDP OE RM DID FORMAT ERROR
Source:
NDPS, Resource Manager NLM program
Explanation:
The P1284 Device ID being returned from the hardware is flawed.
Possible Cause:
The standard format for Device ID was not followed.
Action:
Contact the developer of the device (printer).
-948 0xFFFFFC4C NWDP OE RM UNKNOWN RPC SESSION
Source:
NDPS, Resource Manager NLM program
Explanation:
An attempt was made to authenticate to an unknown RPC session or an unknown RPC session was generated.
Possible Cause:
An internal NDPS error occurred.
-949 0xFFFFFC4B NWDP OE RM SESSN BEING REMOVED
Source:
NDPS, Resource Manager NLM program
Explanation:
An attempt was made to obtain a list of resources operations while the RMS was being shut down.
Possible Cause:
The RMS was being shut down.
Action:
Wait until the RMS is up again.
-951 0xFFFFFC49 NWDP OE RM FMGR IO ERROR
Source:
NDPS, Resource Manager, Font Manager
Explanation:
The Resource Manager has a problem accessing font files in the RMS common storage area. An error occurred while opening, reading, writing, or closing a needed file.
Possible Cause:
The files in the RMS common storage area, resdir directory, are corrupted or missing.
Action:
Check the resdir directory.
Possible Cause:
The font index file or a font file in the repository has been deleted or is no longer available.
Action:
Rebuild the font index file or recopy the appropriate font file to the font repository.
-952 0xFFFFFC48 NWDP OE RM FMGR REENTRANCY
Source:
NDPS, Resource Manager, Font Manager
Explanation:
The Font Manager is currently processing a client request.
Possible Cause:
Overlapping procedure calls to the Font Manager module might exist.
Action:
Retry the call until the Font Manager completes its previous operation.
-953 0xFFFFFC47 NWDP OE RM FMGR SEQ ERROR
Source:
NDPS, Resource Manager, Font Manager
Explanation:
A packet of font file data was received out of order by the Font Manager during the font file copy routine.
Action:
Retry the font file copy request.
-954 0xFFFFFC46 NWDP OE RM FMGR CRPT INDEX FILE
Source:
NDPS, Resource Manager, Font Manager
Explanation:
The check sum of the memory resident copy of the Font Manager index file is invalid.
Possible Cause:
A memory block has become corrupted.
Action:
Contact a Novell Support Provider.
If you are debugging a program, close the Font Manager using FontMgrDeInit() and reinitialize the Font Manager using FontMgrInit().
-955 0xFFFFFC45 NWDP OE RM FMGR NO SUCH FONT
Source:
NDPS, Resource Manager, Font Manager
Explanation:
A requested font does not exist in the font repository. The user will be unable to use the requested font.
Possible Cause:
The desired font has not been added to the font repository.
Action:
Contact the developer of the application.
-956 0xFFFFFC44 NWDP OE RM FMGR NOT INITIALIZED
Source:
NDPS, Resource Manager, Font Manager
Explanation:
An attempt was made to use the Font Manager without first initializing the Font Manager.
Possible Cause:
A mistake was made in the program code.
Action:
Contact the developer of the application.
If you are debugging a program, initialize the Font Manager using FontMgrInit() and retry the desired operation.
-957 0xFFFFFC43 NWDP OE RM FMGR SYSTEM ERROR
Source:
NDPS, Resource Manager, Font Manager
Explanation:
A memory allocation malloc or calloc request has failed.
Possible Cause:
The server is out of available memory.
Action:
Make more memory available to the Font Manager by adding more memory to the server or by unloading unused NLM programs.
-958 0xFFFFFC42 NWDP OE RM FMGR BAD PARM
Source:
NDPS, Resource Manager, Font Manager
Explanation:
An invalid parameter was passed to a Font Manager function.
Possible Cause:
A mistake was made in the program code.
Action:
Contact a Novell Support Provider for an update to NDPS.
If debugging a program, bypass the font causing this error.
-960 0xFFFFFC40 NWDP OE RM FMGR FAILURE
Source:
NDPS, Resource Manager, Font Manager
Explanation:
An error occurred by a Font Manager private function. This error code is not returned by any Font Manager public function.
Possible Cause:
A requested font does not exist in the font repository.
Action:
Contact a Novell Support Provider for an update to NDPS.
If you are debugging the program, handle the error code returned by the Font Manager public function that fails.
-961 0xFFFFFC3F NWDP OE RM DUP TIRPC SESSION
Source:
NDPS, Resource Manager NLM program
Explanation:
An attempt was made to authenticate a duplicate RPC session.
Possible Cause:
An internal NDPS error occurred.
Explanation:
A duplicate TIRPC session number is being used during a bind to the RMS.
Possible Cause:
An intermittent problem has been noticed in this area during the bind to the RMS on the server.
-962 0xFFFFFC3E NWDP OE RM CONN LOST RMS DATA
Source:
NDPS, Resource Manager NLM program
Explanation:
The remote server lost the connection to the RMS data storage area located on a different server on which the RMS is running.
Possible Cause:
The remote file server has been shut down or is abended.
Action:
Check and resolve the condition of the remote file server.
-1000 0xFFFFFC18 NWDP OE BK OUT OF MEMORY
Source:
NDPS, Broker NLM program
Explanation:
The Broker is out of memory.
Possible Cause:
The server is out of available memory.
Action:
Make more memory available to the Broker by adding more memory to the server or by unloading unused NLM programs.
-1001 0xFFFFFC17 NWDP OE BK BAD NETWARE VERSION
Source:
NDPS, Broker NLM program
Explanation:
The server is running a version of NetWare that is older than the minimum required by the Broker.
Action:
Upgrade the server to NetWare 4.11 or later.
-1002 0xFFFFFC16 NWDP OE BK WRONG CMD LINE ARGS
Source:
NDPS, Broker NLM program
Explanation:
The arguments provided in the command line that loaded the Broker were incorrect.
Action:
To get the correct syntax for the Broker NLM program, type the following at the server console:
load Broker /?
NOTE:This command works only if a Broker is not currently loaded on the server.
-1003 0xFFFFFC15 NWDP OE BK BROKER NAME NOT GIVN
Source:
NDPS, Broker NLM program
Explanation:
The Broker did not receive a name.
Possible Cause:
The console operator failed to provide a Broker name when prompted.
Action:
Type a valid Broker name in the command line that loads the Broker, or enter a valid name when prompted by the Broker.
-1004 0xFFFFFC14 NWDP OE BK NOT BROKER CLASS
Source:
NDPS, Broker NLM program
Explanation:
The name provided when loading the Broker identifies an eDirectory or NDS object whose type is not NDPS Broker.
Action:
Make sure the name provided identifies a Broker object.
-1005 0xFFFFFC13 NWDP OE BK INVALID BROKER PWORD
Source:
NDPS, Broker NLM program
Explanation:
The password provided by the console operator when loading the Broker is incorrect.
Possible Cause:
Occasionally this error is reported when a discrepancy exists in eDirectory or NDS. When this is the case, the error is reported before the operator is even prompted to enter a password.
Action:
If the console operator entered a password and it failed, try reloading the Broker with the correct password.
If the error was reported before the operator was prompted for a password, allow some time for eDirectory or NDS to synchronize and try again.
If the problem persists, run dsrepair.nlm on the server and then try again.
-1006 0xFFFFFC12 NWDP OE BK INVALID BROKER NAME
Source:
NDPS, Broker NLM program
Explanation:
The name provided when loading the Broker does not identify an eDirectory or NDS object.
Action:
Make sure the fully qualified name (FQN) of the Broker object is provided. The name should contain a dot (.) as its first character.
-1007 0xFFFFFC11 NWDP OE BK FAILED TO CRTE THRED
Source:
NDPS, Broker NLM program
Explanation:
The Broker failed to spawn the threads needed to handle incoming requests.
Possible Cause:
The server is out of available memory.
Action:
Make more memory available to the Broker by adding more memory to the server or unloading unnecessary NLM programs.
-1008 0xFFFFFC10 NWDP OE BK FAILED TO INIT NUT
Source:
NDPS, Broker NLM program
Explanation:
The Broker was unable to initialize the modules that support the user interface, NUT.
Possible Cause:
The server is out of available memory.
Action:
Make more memory available to the Broker by adding more memory to the server or unloading unnecessary NLM programs.
-1009 0xFFFFFC0F NWDP OE BK FAILED TO GET MSGS
Source:
NDPS, Broker NLM program
Explanation:
The Broker NLM program could not find its message file, broker.msg, while loading.
Possible Cause:
The broker.msg file does not exist or was deleted from the appropriate directory on the server.
Action:
Make sure the file, broker.msg, is located in the appropriate message directory on the server, then try reloading the Broker NLM program.
-1010 0xFFFFFC0E NWDP OE BK FAILED TO ALLOC RES
Source:
NDPS, Broker NLM program
Explanation:
The Broker was unable to initialize the modules that support the user interface, NUT.
Possible Cause:
The server is out of available memory.
Action:
Make more memory available to the Broker by adding more memory to the server or unloading unnecessary NLM programs.
-1011 0xFFFFFC0D NWDP OE BK SVC MUST BE FULL DIS
Source:
NDPS, Broker NLM program
Explanation:
The Broker must be fully unloaded.
Possible Cause:
An attempt was made to restart the Broker while it was being unloaded.
Action:
Wait until the Broker is fully unloaded before loading it again.
-1012 0xFFFFFC0C NWDP OE BK UNINITIALIZED MODULE
Source:
NDPS, Broker NLM program
Explanation:
The Broker has an uninitialized module.
Possible Cause:
An error occurred while the Broker was loaded in memory.
Action:
Make sure the Broker has unloaded entirely, and then try loading it again.
-1013 0xFFFFFC0B NWDP OE BK DS VAL SIZE TOO LARG
Source:
NDPS, Broker NLM program
Explanation:
The Broker attempted to read an eDirectory or NDS attribute whose value occupies a larger buffer than supported.
Action:
The Broker will resolve the error internally.
-1014 0xFFFFFC0A NWDP OE BK NO ATTRIBUTE VALUES
Source:
NDPS, Broker NLM program
Explanation:
The Broker attempted to read an eDirectory or NDS attribute that had no values assigned.
Action:
The Broker will resolve the error internally.
-1015 0xFFFFFC09 NWDP OE BK UNKNOWN SESSION
Source:
NDPS, Broker NLM program
Explanation:
An application attempted to communicate with the Broker over an unknown session.
Possible Cause:
The application you are running encountered a programming error.
-1016 0xFFFFFC08 NWDP OE BK SERVICE DISABLED
Source:
NDPS, Broker NLM program
Explanation:
The Broker service is disabled.
Possible Cause:
An application tried to communicate with a Broker while the Broker was being unloaded.
Action:
After the Broker is fully unloaded, reload it and run the application again.
-1017 0xFFFFFC07 NWDP OE BK UNKNOWN MODIFY OPER
Source:
NDPS, Broker NLM program
Explanation:
The Broker tried to modify an eDirectory or NDS object using an unsupported option.
Action:
The Broker will resolve the error internally.
-1018 0xFFFFFC06 NWDP OE BK INVALID ARGUMENTS
Source:
NDPS, Broker NLM program
Explanation:
The Broker received an invalid list mode.
Possible Cause:
The application you are running encountered a programming error. An application specified an invalid list mode when requesting a list of the services supported by the Broker.
Action:
The application must specify a correct list mode while listing the Broker services. If the problem persists, contact the developer of the application or a Novell Support Provider.
-1019 0xFFFFFC05 NWDP OE BK DUPLICATE SESSION ID
Source:
NDPS, Broker NLM program
Explanation:
The communications layer reported two sessions with the same ID.
Action:
The Broker will resolve the error internally.
-1020 0xFFFFFC04 NWDP OE BK UNKNOWN SERVICE
Source:
NDPS, Broker NLM program
Explanation:
An application requested the Broker to enable a service that is already enabled or to disable an unknown service.
Possible Cause:
The application you are running encountered a programming error.
Action:
The application should ensure that the service is currently disabled before sending the Broker’s request to enable that service.
The application must also ensure that the request specifies one of the three supported services, NWDP SERVICE TYPE SRS, NWDP SERVICE TYPE ENS, or NWDP SERVICE TYPE RMS.
If the problem persists, contact the developer of the application.
-1021 0xFFFFFC03 NWDP OE BK SRVC ALREADY ENABLED
Source:
NDPS, Broker NLM program
Explanation:
An application requested the Broker to enable a service that is already enabled.
Possible Cause:
The application you are running encountered a programming error.
Action:
The application should determine that the service is currently disabled before sending the Broker a request to enable that service.
If the problem persists, contact the the developer of the application.
-1022 0xFFFFFC02 NWDP OE BK SRVC ALREADY DISABLD
Source:
NDPS, Broker NLM program
Explanation:
An application requested the Broker to disable a service that is already disabled.
Possible Cause:
The application you are running encountered a programming error.
Action:
The application should determine that the service is currently enabled before sending the Broker a request to disable that service.
If the problem persists, contact the developer of theapplication.
-1023 0xFFFFFC01 NWDP OE BK INVALID CREDENTIAL
Source:
NDPS, Broker NLM program
Explanation:
The request submitted by an application to bind to a Broker included a defective credential.
Possible Cause:
The application you are running encountered a programming error.
Action:
The application should make sure that all the fields in the credential are properly initialized. If an optional field is not used, the application should initialize the field to zero or NULL as the case might require.
If the problem persists, contact the developer of the application.
-1026 0xFFFFFBFE NWDP OE BK NOT ADMIN TYPE SESN
Source:
NDPS, Broker NLM program
Explanation:
An application without Manager access control rights requested an operation reserved for Broker Managers.
Action:
Make sure the application is logged in to eDirectory or NDS as an object with Broker Manager access control rights. Add Managers for a Broker object.
-1027 0xFFFFFBFD NWDP OE BK OPTION NOT SUPPORTED
Source:
NDPS, Broker NLM program
Explanation:
The request submitted by an application to bind to a Broker included a defective credential.
Action:
The application should make sure that all the fields in the credential are properly initialized. If an optional field is not used, the application should initialize the field to zero or NULL as the case might require.
If the problem persists, contact the developer of the application.
-1029 0xFFFFFBFB NWDP OE BK COULD NOT FIND FILE
Source:
NDPS, Broker NLM program
Explanation:
The Broker could not find the NLM program that implements one of the Brokered services.
Possible Cause:
One or more of the NLM programs that implement Brokered services did not exist in the system directory on the server.
Action:
Make sure that the NLM programs that implement all Brokered services exist in the system directory of the server. These programs are
-
regsrvr.nlm
-
ntfysrvr.nlm
-
rmansrvr.nlm
-1030 0xFFFFFBFA NWDP OE BK ERROR READING FILE
Source:
NDPS, Broker NLM program
Explanation:
The Broker was unable to read the NLM program file that implements one of the Brokered services.
Possible Cause:
One or more of the NLM programs that implement Brokered services did not exist in the system directory on the server.
Action:
Make sure that the NLM programs that implement all Brokered services exist in the system directory of the server. These programs are
-
regsrvr.nlm
-
ntfysrvr.nlm
-
rmansrvr.nlm
-1031 0xFFFFFBF9 NWDP OE BK NOT NLM FILE FORMAT
Source:
NDPS, Broker NLM program
Explanation:
The format of one of the NLM program files that implement the Brokered services is corrupted.
Action:
Reinstall NDPS on this server.
Action:
Manually copy the three NLM programs that implement the Brokered services. These programs are
-
regsrvr.nlm
-
ntfysrvr.nlm
-
rmansrvr.nlm
-1032 0xFFFFFBF8 NWDP OE BK WRONG NLM FILE VER
Source:
NDPS, Broker NLM program
Explanation:
The version of the NLM program that implements one of the Brokered services is obsolete with this version of NetWare.
-1034 0xFFFFFBF6 NWDP OE BK ALREADY IN PROGRESS
Source:
NDPS, Broker NLM program
Explanation:
The Broker service is already in progress.
Possible Cause:
The Broker tried to load a NLM program that implements Brokered services while it was already being loaded.
Action:
Wait until the NLM program in question is fully loaded or unloaded before enabling or disabling the corresponding Brokered service.
-1035 0xFFFFFBF5 NWDP OE BK INITIALIZE FAILURE
Source:
NDPS, Broker NLM program
Explanation:
The server failed to initialize a support NLM program as it was being loaded by the Broker.
Action:
Unload and reload the Broker and try the task again.
-1038 0xFFFFFBF2 NWDP OE BK AUTO MODULS NOT LOAD
Source:
NDPS, Broker NLM program
Explanation:
Some of the NLM programs that the Broker needs to be able to execute cannot be found.
Action:
From the server console, note the names of the support modules that could not be found. Make sure those files exist in the system directory of the server.
-1039 0xFFFFFBF1 NWDP OE BK UNRESOLVED EXTERNAL
Source:
NDPS, Broker NLM program
Explanation:
The Broker has received an unresolved external command.
Possible Cause:
Some of the NLM programs that the Broker needs to be able to execute are outdated.
Action:
Update the files by doing a complete installation of NDPS on the server.
-1041 0xFFFFFBEF NWDP OE BK OTHER BRKR USING OBJ
Source:
NDPS, Broker NLM program
Possible Cause:
The Broker failed to load because the Broker object it was given is already being used by another Broker on the network.
Action:
Create a Broker object for this Broker to use, or unload the other Broker on the network before loading this one.
-1042 0xFFFFFBEE NWDP OE BK SRVC FAILED TO INIT
Source:
NDPS, Broker NLM program
Possible Cause:
The Broker failed to enable one of the Brokered services.
Action:
Examine the extended error that accompanies this error code for additional explanation on what caused the operation to fail.
-1100 0xFFFFFBB4 NWDP OE RG OUT OF MEMORY
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS is out of memory.
Possible Cause:
The server is out of available memory.
Action:
Make more memory available to the SRS by adding more memory to the server or by unloading unused NLM programs.
-1101 0xFFFFFBB3 NWDP OE RG BAD NETWARE VERSION
Source:
NDPS, Service Registry NLM program
Explanation:
The server is running a version of NetWare that is earlier than the minimum required by the SRS.
Action:
Upgrade the server to NetWare 4.11 or later.
-1102 0xFFFFFBB2 NWDP OE RG FAIL CREATE CONTEXT
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS failed to create an eDirectory or NDS context.
Possible Cause:
The server is out of available memory.
Action:
Make more memory available to the SRS by adding more memory to the server or by unloading unused NLM programs.
-1103 0xFFFFFBB1 NWDP OE RG FAIL LOGIN
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS failed to log in to eDirectory or NDS.
Action:
Unload the Broker (which will unload the SRS as well if it is still loaded). Reload the Broker and try enabling the SRS again. If the failure continues, run dsrepair.nlm.
-1104 0xFFFFFBB0 NWDP OE RG FAIL CREATE THREAD
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS failed to spawn the threads needed to handle incoming requests.
Possible Cause:
The server is out of available memory.
Action:
Make more memory available to the SRS by adding more memory to the server or unloading unnecessary NLM programs.
-1105 0xFFFFFBAF NWDP OE RG FAIL GET MSGS
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS could not find its message file (regsrvr.msg) while loading.
Action:
Make sure the regsrvr.msg file is located in the appropriate message directory on the server.
-1106 0xFFFFFBAE NWDP OE RG SVC MUST BE FULL DIS
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS must be fully disconnected.
Possible Cause:
An attempt was made to restart the SRS while it was being unloaded.
Action:
Wait until the SRS is fully unloaded before loading it again.
-1107 0xFFFFFBAD NWDP OE RG DS VAL SIZE TOO LARG
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS tried to read an eDirectory or NDS attribute whose value necessitates a larger buffer than supported.
Action:
The SRS will resolve the error internally.
-1108 0xFFFFFBAC NWDP OE RG NO ATTRIBUTE VALUES
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS tried to read an eDirectory or NDS attribute that had no values assigned.
Action:
The SRS will resolve the error internally.
-1109 0xFFFFFBAB NWDP OE RG UNKNOWN SESSION
Source:
NDPS, Service Registry NLM program
Explanation:
An application tried to communicate with the SRS over an unknown session.
Possible Cause:
The application you are running encountered a programming error
Action:
The application must ensure the necessary SRS APIs have been invoked in the correct order. If the problem persists, contact the developer of theapplication.
-1110 0xFFFFFBAA NWDP OE RG SERVICE DISABLED
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS must be disabled.
Possible Cause:
An application tried to communicate with the SRS while it was being unloaded.
Action:
After the SRS is fully unloaded, reload it and run the application again.
-1111 0xFFFFFBA9 NWDP OE RG UNKNOWN MODIFY OPER
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS tried to modify an eDirectory or NDS object using an unsupported option.
Action:
The SRS will resolve the error internally.
-1112 0xFFFFFBA8 NWDP OE RG CANT START ADVERTISE
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS is unable to advertise its availability through SAP.
Possible Cause:
The server is out of available memeory.
Action:
Make more memory available to the SRS by adding more memory to the server or by unloading unused NLM programs.
-1114 0xFFFFFBA6 NWDP OE RG CANT BIND 2 REGISTRY
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS was unable to establish a session to another SRS on the network.
Action:
The SRS will resolve the error internally.
-1115 0xFFFFFBA5 NWDP OE RG CANT CREATE CLIENT
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS was unable to establish a session to another SRS on the network.
Action:
The SRS will resolve the problem internally.
-1116 0xFFFFFBA4 NWDP OE RG INVALID ARGUMENTS
Source:
NDPS, Service Registry NLM program
Explanation:
The SRS received invalid arguments.
Possible Cause:
The application you are running encountered a programming error. An application requested a list of the services registered with the SRS but specified an invalid continuation mode.
Possible Cause:
A printer attempted to register with the SRS but failed to specify all the required information.
Action:
The application should make sure that all the fields in the request are properly initialized. If an optional field is not used, the application should initialize the field to zero or NULL as the case might require.
If the problem persists, contact the developer of the application.
-1117 0xFFFFFBA3 NWDP OE RG DUPLICATE SESSION ID
Source:
NDPS, Service Registry NLM program
Explanation:
The communications layer reported two sessions with the same ID.
Action:
The SRS will resolve the error internally.
-1118 0xFFFFFBA2 NWDP OE RG UNKNOWN SERVER ENTRY
Source:
NDPS, Service Registry NLM program
Explanation:
The Service Registry received an unknown server entry.
Possible Cause:
A service provider, such as a printer, tried to deregister from the SRS without having registered previously.
Action:
The service provider should make sure its registration to the SRS was successful.
Possible Cause:
The information in the deregistration did not match the information in the registration.
Action:
The service provider should make sure that the information provided in the deregistration matches the information provided in the registration.
-1119 0xFFFFFBA1 NWDP OE RG INVALID CREDENTIAL
Source:
NDPS, Service Registry NLM program
Explanation:
The registry received an invalid credential.
Possible Cause:
The application you are running encountered a programming error. The request submitted by an application to bind to a SRS included a defective credential.
Action:
The application should make sure that all the fields in the credential are properly initialized. If an optional field is not used, the application should initialize the field to zero or NULL as the case might require.
If the problem persists, contact the developer of the application.
-1125 0xFFFFFB9B NWDP OE RG OPTION NOT SUPPORTED
Source:
NDPS, Service Registry NLM program
Explanation:
The Service Registry received an option that is not supported.
Possible Cause:
The application you are running encountered one of the following programming errors.
Action:
The application should make sure that all the fields in the credential are properly initialized. If an optional field is not used, the application should initialize the field to zero or NULL as the case might require.
If this problem persists, contact the developer of the application.
-1127 0xFFFFFB99 NWDP OE RG INVLD CONTNUATN HNDL
Source:
NDPS, Service Registry NLM program
Explanation:
The Service Registry received an invalid continuation handle.
Possible Cause:
The application you are running encountered a programming error. The request submitted by an application to list servers registered with a SRS included an invalid continuation handle.
Action:
The SRS will resolve the error internally.
-1200 0xFFFFFB50 NWDP OE NF OUT OF MEMORY
Source:
NDPS, Notification Service NLM program
Explanation:
The Event Notification Service (ENS) is out of memory.
Possible Cause:
The server is out of available memory.
Action:
Make more memory available to the ENS by adding more memory to the server or by unloading unused NLM programs.
-1201 0xFFFFFB4F NWDP OE NF BAD NETWARE VERSION
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received a bad NetWare version.
Possible Cause:
The server is running a version of NetWare that is earlier than the minimum required by the ENS.
Action:
Upgrade the server to NetWare 4.11 or later.
-1202 0xFFFFFB4E NWDP OE NF FAIL CREATE THREAD
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS failed to spawn the threads needed to handle incoming requests.
Action:
Make more memory available to the ENS by either adding more memory to the server or unloading unnecessary NLM programs.
-1203 0xFFFFFB4D NWDP OE NF FAIL GET MSGS
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS could not find its message file, ntfysrvr.msg, while loading.
Action:
Make sure the file ntfysrvr.msg is located in the appropriate message directory on the server.
-1204 0xFFFFFB4C NWDP OE NF FAIL CREATE CONTEXT
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS failed to create an eDirectory or NDS context.
Possible Cause:
The server is out of available memory.
Action:
Make more memory available to the ENS by adding more memory to the server or by unloading unused NLM programs.
-1205 0xFFFFFB4B NWDP OE NF FAIL LOGIN
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS failed to log in to eDirectory or NDS.
Action:
Unload the Broker (which will unload the ENS as well if it is still loaded). Reload the Broker and try enabling the ENS again. If the failure continues, run dsrepair.nlm.
-1206 0xFFFFFB4A NWDP OE NF SVC MUST BE FULL DIS
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS must be fully disconnected before loading.
Possible Cause:
An attempt was made to restart the ENS while it was being unloaded.
Action:
Wait until the ENS is fully unloaded before loading it again.
-1207 0xFFFFFB49 NWDP OE NF DS VAL SIZE TOO LARG
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS tried to read an eDirectory or NDS attribute whose value necessitates a larger buffer than supported.
Action:
The ENS will resolve the problem internally.
-1208 0xFFFFFB48 NWDP OE NF NO ATTRIBUTE VALUES
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS tried to read an eDirectory or NDS attribute that had no values assigned.
Action:
The ENS will resolve the problem internally.
-1209 0xFFFFFB47 NWDP OE NF UNKNOWN SESSION
Source:
NDPS, Notification Service NLM program
Explanation:
An application tried to communicate with the ENS over an unknown session.
Possible Cause:
The application you are running encountered a programming error.
Action:
The application must make sure the necessary ENS APIs have been invoked in the correct order.
If the problem persists, contact the developer of the application.
-1210 0xFFFFFB46 NWDP OE NF UNKNOWN NOTIFY PROF
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received an unknown profile handle.
Possible Cause:
The application you are running encountered a programming error. An application tried to modify or delete a profile using an invalid profile handle.
Action:
The application must make sure that the profile ID provided in the modify or delete operation matches the one obtained from operations add profile or list profiles. If the problem persists, contact the developer of the application.
-1211 0xFFFFFB45 NWDP OE NF ERROR READING FILE
Source:
NDPS, Notification Service NLM program
Explanation:
The Notification Service received an error when it attempted to read the notification profile.
Possible Cause:
The attribute that contains the notification profile in your Printer object is corrupted.
Action:
Delete the Printer object with the corrupted attribute. Create a new Printer object to represent your controlled access printer.
-1212 0xFFFFFB44 NWDP OE NF ERROR WRITING FILE
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS was unable to save a change to the persistent notification registration database.
Action:
The ENS will resolve the problem internally.
-1213 0xFFFFFB43 NWDP OE NF WRONG NOTIFY DB VERS
Source:
NDPS, Notification Service NLM program
Explanation:
This ENS does not support the version of the database that contains the notification registrations.
Action:
Upgrade NDPS on this server.
-1214 0xFFFFFB42 NWDP OE NF CORRUPTED NOTIFY DB
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received a corrupted file from the notification database.
Possible Cause:
The attribute that contains the notification profile in your Printer object is corrupted.
Action:
Delete the Printer object with the corrupted attributes. Create a new Printer object to represent your controlled access printer.
-1216 0xFFFFFB40 NWDP OE NF METHOD ALREADY INST
Source:
NDPS, Notification Service NLM program
Explanation:
An application requested the ENS to install a delivery method that is already installed.
Possible Cause:
The application you are running encountered a programming error.
Action:
To avoid this error, the application should list the delivery methods currently installed before requesting a new one to be installed. If the problem persists, contact the developer of the application.
-1217 0xFFFFFB3F NWDP OE NF UNKNOWN METHOD
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received an unknown delivery method.
Possible Cause:
The application you are running encountered a programming error. The identifier for the delivery method was not correct.
Action:
Make sure the identifier for the delivery method is correct.
Possible Cause:
An application sent the ENS a request that specified a delivery method that is not currently installed.
Action:
Make sure the delivery method being requested is installed on the server. You can installed a delivery method remotely by sending an Add Method request to the ENS or by loading the appropriate .ens file on the server.
If the problem persists, contact the developer of the application.
-1218 0xFFFFFB3E NWDP OE NF SERVICE DISABLED
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS is disabled.
Possible Cause:
An application tried to communicate with an ENS while the ENS was being unloaded.
Action:
After the ENS is fully unloaded, reload it and run the application again.
-1219 0xFFFFFB3D NWDP OE NF UNKNOWN MODIFY OP
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS used an unknown modify option.
Possible Cause:
The ENS tried to modify an eDirectory or NDS object using an unsupported option.
Action:
The ENS will resolve the problem internally.
-1222 0xFFFFFB3A NWDP OE NF NOTIFY QUEUE EMPTY
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS uses this code to inform delivery methods that currently there are not any notifications in their queues.
Action:
The delivery method should wait until it receives a ping from the ENS indicating that there are some notifications in its queue waiting to be dispatched.
-1223 0xFFFFFB39 NWDP OE NF CANT LOAD DELVR METH
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS failed to load a delivery method.
Action:
Determine the reasons the delivery method failed to load by examining the Broker screen and the console screen of the server where the ENS is loaded.
-1224 0xFFFFFB38 NWDP OE NF INVALID ARGUMENTS
Source:
NDPS, Notification Service NLM program
Explanation:
An application submitted a request to the ENS and failed to initialize all the fields in the request.
Possible Cause:
The application you are running encountered a programming error. All the fields in the request were not properly initialized.
Action:
The application should make sure that all the fields in the request are properly initialized. If an optional field is not used, the application should initialize the field to zero or NULL as the case might require.
If the error persists, contact the applicaton developer.
-1225 0xFFFFFB37 NWDP OE NF DUPLICATE SESSION ID
Source:
NDPS, Notification Service NLM program
Explanation:
The communications layer reported two sessions with the same ID.
Action:
The ENS will resolve the problem internally.
-1226 0xFFFFFB36 NWDP OE NF INVALID CREDENTIAL
Source:
NDPS, Notification Service NLM program
Explanation:
An invalid credential was received by a Notification Service.
Possible Cause:
The application you are running encountered a programming error. The request submitted by an application to bind to an ENS included a defective credential.
Action:
The application should make sure that all the fields in the credential are properly initialized. If an optional field is not used, the application should initialize the field to zero or NULL as the case might require.
If the error persists, contact the developer of the application.
-1227 0xFFFFFB35 NWDP OE NF UNKNOWN CHOICE
Source:
NDPS, Notification Service NLM program
Explanation:
The Notification Service received an unknown choice.
Possible Cause:
The application you are running encountered a programming error. An application requested a list of profiles in the ENS but specified an invalid value for the type of list desired.
Action:
When listing profiles, an application should make sure to specify NWDP LIST CHOICE FILTER or NWDP LIST CHOICE ID.
If the problem persists, contact the developer of the application.
-1228 0xFFFFFB34 NWDP OE NF UNKNOWN ATTR VALUE
Source:
NDPS, Notification Service NLM program
Explanation:
An unknown value was reported.
Action:
The ENS will resolve the problem internally.
-1230 0xFFFFFB32 NWDP OE NF UNKNOWN OBJECT ID
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received an unknown object ID.
Possible Cause:
A printer generated an event in which no one has a registered interest.
Action:
The ENS will resolve the problem internally.
-1232 0xFFFFFB30 NWDP OE NF FAIL MAKE CHG PERMNT
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS was unable to save a change to the persistent notification registration database.
Possible Cause:
The application you are running encountered a programming error. An application requesting the modification did not flag the modification as persistent while communicating with a public access printer.
Action:
Make sure that the application requesting the modification is flagging the modification as persistent while communicating with a public access printer.
If the problem persists, contact the developer of the application.
-1234 0xFFFFFB2E NWDP OE NF NOT SUPPLY TYPE SESN
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received a request that did not supply the type of session.
Possible Cause:
The application you are running encountered a programming error. An application made a request that only printers are authorized to make.
Action:
If the problem persists, contact the developer of the application.
-1235 0xFFFFFB2D NWDP OE NF NOT ADMIN TYPE SESN
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received a request that was not an administrator type session.
Possible Cause:
The application you are running encountered a programming error. An application made a request that only administrators of the ENS are authorized to make.
Action:
Make sure the eDirectory or NDS account used by the application is assigned as an administrator of the Broker object associated with this ENS.
If the problem persists, contact the developer of the application.
-1236 0xFFFFFB2C NWDP OE NF NO SRVC REGIST AVAIL
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS could not find a SRS on the network to advertise its availability.
Possible Cause:
No SRS was enabled within the SAP-query range of this ENS.
Action:
Make sure that there is at least one SRS enabled within the SAP-query range of this ENS.
-1237 0xFFFFFB2B NWDP OE NF FAIL TO REG W ANY SR
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS could not register with any SRS on the network to advertise its availability.
Possible Cause:
No SRS was enabled within the SAP-query range of this ENS.
Action:
Make sure that there is at least one SRS enabled within the SAP-query range of this ENS.
-1238 0xFFFFFB2A NWDP OE NF EMPTY EVENT OBJ SET
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received an Event object set that was empty.
Possible Cause:
The application you are running encountered a programming error. An application requested that the ENS add a profile but failed to provide a set of events of interest.
Action:
When adding a profile, an application should specify one or more Event objects.
If the problem persists, contact the developer of the application.
-1239 0xFFFFFB29 NWDP OE NF UNKNOWN NTFY HANDLE
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received an unknown notification handle.
Action:
The ENS will resolve the problem internally.
-1240 0xFFFFFB28 NWDP OE NF OPTION NOT SUPPORTED
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received an option that is not supported.
Possible Cause:
The application you are running encountered a programming error. An application submitted a request using options not supported by this ENS.
Action:
If the problem persists, contact the developer of the application.
If you are debugging a program, consult the SDK documentation to determine what options are supported by this version of the ENS.
-1241 0xFFFFFB27 NWDP OE NF UNKNOWN RPC SESSION
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received an unknown RPC session.
Action:
The ENS will resolve the problem internally.
-1242 0xFFFFFB26 NWDP OE NF INITIALIZATION ERROR
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received an initialization error.
Action:
The ENS will resolve the problem internally.
-1244 0xFFFFFB24 NWDP OE NF NO PERSISTENT STORAG
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS did not receive a persistent storage option.
Possible Cause:
A printer requested to add a profile and store it persistently but failed to properly populate the supplier alias option.
Action:
The printer should specify in the supplier alias option the name of the Printer object where the profile should be stored persistently.
If the problem persists, contact the printer vendor or a Novell Support Provider.
-1245 0xFFFFFB23 NWDP OE NF BAD METHOD FILENAME
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received an invalid method filename.
Possible Cause:
The application you are running encountered a programming error. An application requested to load a delivery method but provided an invalid filename to be loaded.
Action:
Make sure the application only requests to load a delivery method whose filename is NULL-terminated string with extension ".ENM" or no extension at all and that does not have any "\"or "/"characters as part of the name string.
If the problem persists, contact the developer of the application.
-1246 0xFFFFFB22 NWDP OE NF UNKNOWN CONT HANDLE
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received an unknown continuation handle.
Possible Cause:
The application you are running encountered a programming error. An application provided an invalid continuation handle when requesting to list profiles.
Action:
The application should only send a continuation handle when more than one call to list profiles is needed to get a complete listing. The first call to list profiles should contain a NULL continuation handle. The result from this call informs the application if subsequent calls are needed. If so, a continuation handle is returned that the application should use in the next call. Each call returns an updated continuation call, if one is needed, which the application should submit with the next invocation.
If the problem persists, contact the developer of the application.
-1247 0xFFFFFB21 NWDP OE NF INVALID CONT HANDLE
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received an invalid continuation handle.
Possible Cause:
The application you are running encountered a programming error. An application provided an invalid continuation handle when requesting to list profiles.
Action:
The application should only send a continuation handle when more than one call to list profiles is needed to get a complete listing. The first call to list profiles should contain a NULL continuation handle. The result from this call informs the application if subsequent calls are needed. If so, a continuation handle is returned that the application should use in the next call. Each call returns an updated continuation call, if one is needed, which the application should submit with the next invocation.
If the problem persists, contact the developer of the application.
-1248 0xFFFFFB20 NWDP OE NF COULD NOT FIND FILE
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS could not find the NLM program that implements one of the delivery methods.
Possible Cause:
An NLM program that implements a delivery method did not exist in the system directory of the server.
Action:
Make sure that the all NLM programs that implement all delivery methods (files with the .enm extension) reside in the system directory of the server.
-1249 0xFFFFFB1F NWDP OE NF L ERROR READING FILE
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS could not find the NLM program that implements one of the delivery methods.
Possible Cause:
An NLM program that implements a delivery method did not exist in the system directory of the server.
Action:
Make sure that the NLM programs that implement all delivery methods (files with the .enm extension) reside in the system directory of the server.
-1250 0xFFFFFB1E NWDP OE NF NOT NLM FILE FORMAT
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received a file that was not in the NLM file format.
Possible Cause:
The format of one of the NLM files that implement the Brokered services is corrupted.
Action:
Reinstall NDPS on this server, or manually copy the NLM programs that implement the delivery methods. All the files that implement delivery methods have an .enm extension.
-1251 0xFFFFFB1D NWDP OE NF WRONG NLM FILE VER
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received a NLM program with the wrong version.
Possible Cause:
The version of the NLM program that implements one of the delivery methods is obsolete with this version of NetWare.
-1253 0xFFFFFB1B NWDP OE NF ALREADY IN PROGRESS
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS tried to load a NLM program that implements a delivery method while it was already being loaded.
Action:
Wait until the NLM program in question is fully loaded or unloaded before proceeding to enable or disable the corresponding delivery method.
-1254 0xFFFFFB1A NWDP OE NF INITIALIZE FAILURE
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS failed to initialize.
Possible Cause:
The server loader failed to initialize a support NLM program as it was being loaded by the ENS.
Action:
Disable and reenable the ENS, then try the task again.
-1257 0xFFFFFB17 NWDP OE NF AUTO MODULS NOT LOAD
Source:
NDPS, Notification Service NLM program
Explanation:
The attempt made by the Event Notification Service (ENS) to automatically load some modules it depends on failed.
Possible Cause:
Some of the NLM programs that the ENS depends on to execute are not present in the system directory of the server.
Action:
From the server console, note the names of the support modules that could not be found. Make sure those files exist in the system directory of the server.
-1258 0xFFFFFB16 NWDP OE NF UNRESOLVED EXTERNAL
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received a NLM program file on which it was unable to resolve its external dependencies.
Possible Cause:
Some of the NLM programs that the ENS depends on to execute need to be updated.
Action:
Make sure you have a current version of NDPS and do a complete installation of NDPS on the server.
-1260 0xFFFFFB14 NWDP OE NF USING UNKNOWN METHDS
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS received a profile that specified a delivery method which is unknown.
Possible Cause:
While trying to dispatch an event to an interested party, the ENS came across a profile that specified a delivery method that is not currently loaded.
Action:
Using NetWare Administrator, review the current registrations to the ENS, and make sure that all the delivery methods needed are loaded.
-1261 0xFFFFFB13 NWDP OE NF SRVC NOT FULL ENABLD
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS is not fully enabled.
Possible Cause:
A delivery method tried to register itself with the ENS while it was still coming up.
Action:
Wait for the ENS to finish coming up, they try again.
-1262 0xFFFFFB12 NWDP OE NF FOREIGN NDS TREE NAM
Source:
NDPS, Notification Service NLM program
Explanation:
The ENS found that the eDirectory or NDS tree name specified as part of the supplier alias or consumer file does not match its own. A controlled access printer must bind with an ENS that exists in the same eDirectory or NDS tree for the ENS to be able to save persistent information in the printer's eDirectory or NDS object.
Action:
Make sure the ENS you want the printer to bind to is in the same eDirectory or NDS tree as the Printer object.
-1263 0xFFFFFB11 NWDP OE NF DLVYMETH REJCTD ADDR
Source:
NDPS, Notification Service NLM program
Explanation:
The delivery address submitted with a profile to be added was rejected by a delivery method.
Possible Cause:
The application you are running encountered a programming error.
Action:
The application that submitted the profile should make sure that the delivery address provides all the information expected by the delivery method specified in the profile. The application can find this information from the delivery method by calling the Getmethodinfo function.
If the problem persists, contact the developer of the application.
-1264 0xFFFFFB10 NWDP OE NF UNSUPRT DLVYADDRTYPE
Source:
NDPS, Notification Service NLM program
Explanation:
An application submitted a delivery address using options that are not supported by the version of a loaded delivery method.
Action:
Upgrade the delivery method in question. If the problem persists, contact the developer of the application.
-1265 0xFFFFFB0F NWDP OE NF USR OBJ NO DEFLTSERV
Source:
NDPS, Notification Service NLM program
Explanation:
The pop-up delivery method failed to validate a delivery address.
Possible Cause:
The specified user did not have a default server assigned to it.
Action:
Use NetWare Administrator to assign the user a default server.
-1266 0xFFFFFB0E NWDP OE NF FAILED TO SEND NOTIF
Source:
NDPS, Notification Service NLM program
Explanation:
An attempt to send notification failed.
Action:
The ENS will resolve the problem internally.
-1267 0xFFFFFB0D NWDP OE NF BAD VOLUME IN ADDR
Source:
NDPS, Notification Service NLM program
Explanation:
The log-file delivery method failed to validate a delivery address.
Possible Cause:
The application you are running encountered a programming error. The volume specified in the log file was invalid.
Action:
The application submitting the profile should make sure that the specified volume name is fully qualified and that it includes a leading period.
If the problem persists, contact the developer of the application.
-1268 0xFFFFFB0C NWDP OE NF BROKER NO FILE RIGHT
Source:
NDPS, Notification Service NLM program
Explanation:
The Log-file delivery method failed to validate a delivery address.
Possible Cause:
The Broker object associated with the delivery method does not have rights to modify the specified log file.
Action:
Using NetWare Administrator, grant the Broker object associated with the delivery method the Write and Create rights to the log file. If the log file does not exist yet, assign the rights to the directory where the delivery method is supposed to create it.
801 0x321 NDPS W OBJECT NOT FOUND
Source:
NDPS, NDPS Manager NLM program
Explanation:
The requested object for an operation was not found.
Possible Cause:
The object was not created or has been deleted.
Action:
Make sure the object exists.
Possible Cause:
The object ID is invalid.
Action:
Make sure the object ID is valid.
802 0x322 NDPS W ATTRIBUTE NOT FOUND
Source:
NDPS, NDPS Manager NLM program
Explanation:
The requested object attribute for an operation was not found.
Possible Cause:
The attribute was not created or has been deleted.
Action:
Make sure the attribute exists.
Possible Cause:
The ID of the attribute is invalid.
Action:
Make sure the attribute ID is valid.
803 0x323 NDPS W VALUE NOT FOUND
Source:
NDPS, NDPS Manager NLM program
Explanation:
The requested object attribute value for an operation was not found.
Possible Cause:
The attribute or attribute value was not created or has been deleted.
Action:
Make sure the attribute or attribute value exists.
Possible Cause:
The attribute ID is invalid.
Action:
Make sure the attribute ID is valid.
804 0x324 NDPS W REQUESTED SCH NOT LOADED
Source:
NDPS, NDPS Manager NLM program
Explanation:
The requested scheduler failed to load. The Printer Agent is using the First In First Out (FIFO) scheduler instead.
Possible Cause:
The scheduler is not in the load path.
Action:
Make sure the requested scheduler is in the load path and try loading it again. If the requested scheduler is in the load path but fails to load, check for an error report on the system console and error log. If possible, resolve any errors found and try the task again.
Possible Cause:
The scheduler encountered a problem that prevented successful operation.
196609 0x00030001 NWDP LE PSM CONNECTION LOST
Source:
NDPS, Library error
Explanation:
The connection to the NDPS Manager was lost.
Action:
Reestablish a connection, then try the task again.
262145 0x00040001 NWDP LE FILE NO ACCESS RIGHTS
Source:
NDPS, Library Error
Explanation:
An attempt was made to access a file without access rights to the file.
Action:
Make sure the necessary rights are assigned for the task being done and try the task again.
262146 0x00040002 NWDP LE FILE NOT FOUND
Source:
NDPS, Library Error
Explanation:
A file was not found.
327681 0x00050001 NWDP LE SRS CONNECTION LOST
Source:
NDPS, Library Error
Explanation:
The connection to the SRS has been lost.
327682 0x00050002 NWDP LE SRS NO SRVC REG FOUND
Source:
NDPS, Library Error
Explanation:
The Service Registry was not found.
327683 0x00050003 NWDP LE SRS NOT ENABLED
Source:
NDPS, Library Error
Explanation:
The SRS is not enabled.
Action:
Make sure the SRS is enabled, then try the task again.
393217 0x00060001 NWDP LE BRK CONNECTION LOST
Source:
NDPS, Library Error
Explanation:
The connection to the NDPS Broker has been lost.
Action:
Reestablish a connection to the Broker, then try the task again.
524290 0x00080002 NWDP LE DOC ZERO LENGTH
Source:
NDPS, Library Error
Explanation:
The document has zero length.
524292 0x00080004 NWDP LE DOC NO SUCH DOC
Source:
NDPS, Library Error
Explanation:
The document object cannot be found in the Managed Objects database.
589829 0x00090005 NWDP LE JOB NO SUCH JOB
Source:
NDPS, Library Error
Explanation:
The job object cannot be found in the Managed Objects database.
655365 0x000A0005 NWDP LE UNKNOWN CALLBACK ERR
Source:
NDPS, Library Error
Explanation:
An unknown error occurred in the callback routine.
655367 0x000A0007 NWDP LE INVALID INTERNAL OP
Source:
NDPS, Library Error
Explanation:
An internal library error occurred.
655369 0x000A0009 NWDP LE FQN NOT NDPS MANAGER
Source:
NDPS, Library Error
Explanation:
An FQN does not identify an NDPS Manager.
655370 0x000A000A NWDP LE FQN NOT NDPS PRINTER
Source:
NDPS, Library Error
Explanation:
An FQN does not identify an NDPS printer.
655371 0x000A000B NWDP LE FQN NOT NDPS BROKER
Source:
NDPS, Library Error
Explanation:
The fully qualified eDirectory or NDS name provided does not identify an NDPS Broker.
720898 0x000B0002 NWDP LE NSRV OBJECT EXISTS
Source:
NDPS, Library Error
Explanation:
The object already exists in eDirectory or NDS.
720899 0x000B0003 NWDP LE NSRV NO SUCH OBJECT
Source:
NDPS, Library Error
Explanation:
The object cannot be found in eDirectory or NDS.
720900 0x000B0004 NWDP LE NSRV WRONG OBJECT TYPE
Source:
NDPS, Library Error
Explanation:
The object is the wrong object type.
720901 0x000B0005 NWDP LE NSRV NO ADDRESS
Source:
NDPS, Library Error
Explanation:
The network address is empty for the eDirectory or NDS object.
Action:
Make sure the object is loaded, then try the action again.
720902 0x000B0006 NWDP LE NSRV VAL SIZE TOO LARGE
Source:
NDPS, Library Error
Explanation:
A Broker network address value is too large.
Action:
Make sure the values for the Broker network address are under 32 bytes.
720903 0x000B0007 NWDP LE NSRV NOT SAME TREE
Source:
NDPS, Library Error
Explanation:
The eDirectory or NDS object is not in the same tree.
Action:
Make sure the object is in the same tree, and then try the action again.
720904 0x000B0008 NWDP LE NSRV INTERNAL
Source:
NDPS, Library Error
Explanation:
An internal name service error has occurred.
720907 0x000B000B NWDP LE NSRV INVALID RES PATH
Source:
NDPS, Library Error
Explanation:
The path to the resource directory and its subdirectories does not exist.
Action:
Under the \ndps\resdir directory, create the following directories: \prndrv, \font, \prndef, and \banner. Under the ndps\resdir\font directory, create a file with a .sys extension.
786433 0x000C0001 NWDP LE PRT NO SUCH LABEL
Source:
NDPS, Library Error
Explanation:
A label in the Installed Printers list cannot be found.
786434 0x000C0002 NWDP LE PRT NO DEFAULT
Source:
NDPS, Library Error
Explanation:
No default printer has been assigned.
Action:
Make sure a default printer has been assigned, and then try the task again.
786436 0x000C0004 NWDP LE PRT DUPLICATE LABEL
Source:
NDPS, Library Error
Explanation:
An attempt was made to add a printer to the Installed Printers list with a label that is already in the list.
786439 0x000C0007 NWDP LE PRT JOB CFG EXISTS
Source:
NDPS, Library Error
Explanation:
The job configuration already exists for this Installed List printer. Or a job configuration by the name specified already exists for this NDPS Printer object.
Action:
Make sure the job configuration is unique, then try the task again.
786440 0x000C0008 NWDP LE PRT INVALID JOB CFG FMT
Source:
NDPS, Library Error
Explanation:
The job configuration is in an invalid format.
Possible Cause:
The file data is unrecognizable.
Action:
Make sure the syntax for the print job is correct, then try the task again.
786441 0x000C0009 NWDP LE PRT INTERNAL ERROR
Source:
NDPS, Library Error
Explanation:
An internal error occurred during attempt to marshall job configurations.
786442 0x000C000A NWDP LE PRT JOB CFG NOT FOUND
Source:
NDPS, Library Error
Explanation:
The requested job configuration cannot be found or no job configurations have been created for the specified printer.
786444 0x000C000C NWDP LE PRT DEST TREE DIFFERS
Source:
NDPS, Library Error
Explanation:
The destination tree is different from the source tree.
Possible Cause:
Moving jobs between trees is not currently supported by NDPS.
786446 0x000C000E NWDP LE PRT ADDR NO LONGR VALID
Source:
NDPS, Library Error
Explanation:
The previously valid network address for the installed printer is no longer valid.
Action:
Make sure the network address is current, then try the task again.
786447 0x000C000F NWDP LE PRT BAD CFG FILE VER
Source:
NDPS, Library Error
Explanation:
The Installed Printers list file is the wrong version.
Action:
Make sure the configuration file contains the correct version of the shortlist, then try the task again.
786448 0x000C0010 NWDP LE PRT PO ALREADY ASSIGNED
Source:
NDPS, Library Error
Explanation:
The Printer object specified has already been assigned to the Printer Agent.
Action:
Make sure the correct object is being specified, and if necessary try the task again.
786449 0x000C0011 NWDP LE PRT PO NOT ASSIGNED
Source:
NDPS, Library Error
Explanation:
The Printer object is not assigned to the Printer Agent.
786450 0x000C0012 NWDP LE PRT PA NOT FOUND
Source:
NDPS, Library Error
Explanation:
The Printer Agent was not found.
786451 0x000C0013 NWDP LE PRT SHORTLIST NOT FOUND
Source:
NDPS, Library Error
Explanation:
The Installed Printer list file was not found.
786452 0x000C0014 NWDP LE PRT WARNING WIN INI CHG
Source:
NDPS, Library Error
Explanation:
The WIN.INI file has changed.
786453 0x000C0015 NWDP LE PRT INSTALLR NOT A USER
Source:
NDPS, Library Error
Explanation:
The person adding the NDPS Printer object to the Installed Printer List is not a user of that Printer object.
851969 0x000D0001 NWDP LE OID INVALID ASCII
Source:
NDPS, Library Error
Explanation:
The numbers of the form, 1.33.74.96, are expected. Any other syntax is invalid.
851970 0x000D0002 NWDP LE OID NOT IN DATABASE
Source:
NDPS, Library Error
Explanation:
The object ID given is not in the database, and it cannot be translated to a human readable string.
851971 0x000D0003 NWDP LE OID UNSUPPORTED FORMAT
Source:
NDPS, Library Error
Explanation:
The format value given is not supported in this version of the library.
851972 0x000D0004 NWDP LE OID STRING NOT FOUND
Source:
NDPS, Library Error
Explanation:
The reverse string-to-object ID lookup failed.
Possible Cause:
No matching string was found in the monoid.idx index file.
Action:
Check for errors associated with the string specified such as spellings, word order, code page.
851973 0x000D0005 NWDP LE OID NO STRING THAT KIND
Source:
NDPS, Library Error
Explanation:
Although the string exists in the monoid.idx as translatable to an object ID, this string's Kind is not what was requested. For example, if an attribute name is requested, but a value of the same name is found, then the string is found but not the right Kind.
851974 0x000D0006 NWDP LE OID MSG FILE NOT FOUND
Source:
NDPS, Library Error
Explanation:
The oidname.msg file was not found.
Possible Cause:
The oidname.msg file is not in the expected location in a language-specific subdirectory under the NLS that contains the oidmsg.idx file. The following areas were searched:
-
The current directory.
-
The nwlanguage environment variable directory. If the nwlanguage variable is set, it should contain a directory name or names which specify a language (for example, english or french). The files are searched for in a child directory of the NLS directory as specified by the nwlanguage variable. The NLS directory in this instance is itself a child directory of the load directory. (The load directory contains the current utility’s .exe file.)
-
The directories found under the child NLS subdirectory of the load directory.
-
The directories found under the sibling NLS subdirectory of the load directory.
Action:
Find a current version of the message file. Then, copy it to a directory that is mapped to an existing search drive, or map a search drive to the directory containing the file.
851975 0x000D0007 NWDP LE OID MSTR IDX NOT FOUND
Source:
NDPS, Library Error
Explanation:
The oidmsg.idx file was not found.
Possible Cause:
The oidmsg.idx file is not in the expected NLS subdirectory. The following areas were searched:
-
The current directory.
-
The nwlanguage environment variable directory. If the nwlanguage variable is set, it should contain a directory name or names which specify a language (for example, ENGLISH or FRENCH). The files are searched for in a child directory of the NLS directory as specified by the nwlanguage variable. The NLS directory in this instance is itself a child directory of the load directory. (The load directory contains the current utility’s .EXE file.)
-
The directories found under the child NLS subdirectory of the load directory.
-
The directories found under the sibling NLS subdirectory of the load directory.
Action:
Find a current version of the message file. Then, copy it to a directory that is mapped to an existing search drive, or map a search drive to the directory containing the file.
851976 0x000D0008 NWDP LE OID MONOCASE NOT FOUND
Source:
NDPS, Library Error
Explanation:
The monoid.idx file was not found.
Possible Cause:
The monoid.idx file was not in the expected location in a language-specific subdirectory under the NLS that contains the OIDMSG.IDX. The following areas were searched:
-
The current directory.
-
The nwlanguage environment variable directory. If the nwlanguage variable is set, it should contain a directory name or names which specify a language (for example, english or french). The files are searched for in a child directory of the NLS directory as specified by the nwlanguage variable. The NLS directory in this instance is itself a child directory of the load directory. (The load directory contains the current utility’s .exe file.)
-
The directories found under the child NLS subdirectory of the load directory.
-
The directories found under the sibling NLS subdirectory of the load directory.
Action:
Find a current version of the message file. Then, copy it to a directory that is mapped to an existing search drive, or map a search drive to the directory containing the file.
851977 0x000D0009 NWDP LE OID ENUM XLAT NOT FOUND
Source:
NDPS, Library Error
Explanation:
The translation for a specific enum value below the specified object ID was not found in this release of the object ID database.
851978 0x000D000A NWDP LE OID NOT LANG CONTEXT
Source:
NDPS, Library Error
Explanation:
The Language Context ID used is not supported by this release of the library.
851982 0x000D000E NWDP LE OID INVALID ASN1 TYPE
Source:
NDPS, Library Error
Explanation:
The first byte of an ASN.1 formatted object ID must contain a six (0x06), and the object ID given to the library routine does not conform.
851983 0x000D000F NWDP LE OID IS OBJECT CLASS
Source:
NDPS, Library Error
Explanation:
An attempt to get Attribute Characteristics failed. The object ID in question is an Object Class.
Possible Cause:
The object ID in question is not an attribute. Attribute characteristics can only be obtained on an object ID that is an attribute.
Action:
Make sure the object ID is an attribute.
851984 0x000D0010 NWDP LE OID IS VALUE CLASS
Source:
NDPS, Library Error
Explanation:
An attempt to get Attribute Characteristics failed. The object ID in question is a Value Class.
Possible Cause:
The object ID in question is not an attribute. Attribute characteristics can only be obtained on an object ID that is an attribute.
Action:
Make sure the object ID is an attribute.
851985 0x000D0011 NWDP LE OID IS VALUE
Source:
NDPS, Library Error
Explanation:
An attempt to get Attribute Characteristics failed. The object ID in question is a Value.
Possible Cause:
The object ID in question is not an attribute. Attribute characteristics can only be obtained on an object ID that is an attribute.
Action:
Make sure the object ID is an attribute.
851986 0x000D0012 NWDP LE OID NO LANGUAGE PATH
Source:
NDPS, Library Error
Explanation:
For the given language number, no corresponding language name string exists. No lookup is possible because the name of the directory is derived from the language name string.
917505 0x000E0001 NWDP LE TIRPC TRANSPORT UNSUP
Source:
NDPS
Explanation:
An attempt to establish a connection with an NDPS entity failed, because an address was specified using an unsupported transport type.
Possible Cause:
The requested transportation protocol stack is not loaded on the computer where the error occurred.
Action:
Verify that the requested protocol is loaded and that it is supported by NDPS.
Possible Cause:
A protocol that is not supported by NDPS was requested.
Action:
If you are debugging the program, verify that the address and netconfig parameters are correct.
983041 0x000F0001 NWDP LE MODB NO SUCH OBJECT
Source:
NDPS, Library Error
Explanation:
The object cannot be found in the Managed Objects Database.
983042 0x000F0002 NWDP LE MODB NO SUCH ATTRIBUTE
Source:
NDPS, Library Error
Explanation:
The attribute cannot be found on the Managed Objects Database object.
983043 0x000F0003 NWDP LE MODB OBJ ALREADY EXISTS
Source:
NDPS, Library Error
Explanation:
The object already exists in the Managed Objects Database.
1048577 0x00100001 NWDP LE ATR NOT IN SET
Source:
NDPS, Library Error
Explanation:
The specified attribute is not in the set.
1114113 0x00110001 NWDP LE RES NO NET ADDR ATTR
Source:
NDPS, Library Error
Explanation:
The network address attribute is empty for the eDirectory or NDS Broker object.
Action:
Make sure the Broker object is loaded on a server, then try the action again.
1179649 0x00120001 NWDP LE NTFY NO NET ADDR ATTR
Source:
NDPS, Library Error
Explanation:
The network address attribute is empty for the eDirectory or NDS Broker object.
Action:
Make sure the Broker object is loaded on a server, then try the action again.
1179652 0x00120004 NWDP LE NTFY NO SUCH PROFILE
Source:
NDPS, Library Error
Explanation:
The profile cannot be found.
1245186 0x00130002 NWDP LE PRT SPCD BROKER NOT FND
Source:
NDPS, Library Error
Explanation:
An error occurred while downloading the drivers. The specified Broker was not found for the driver download.
1245188 0x00130004 NWDP LE PRT NO DEST PATH
Source:
NDPS, Library Error
Explanation:
An error occurred while downloading the drivers. No destination path was specified in the driver download.
Action:
Specify a destination path, then try the task again.
1245189 0x00130005 NWDP LE PRT DEVICE ID FMT BAD
Source:
NDPS, Library Error
Explanation:
An error occurred while downloading the drivers. The Device ID format is invalid in the driver download.
1245190 0x00130006 NWDP LE PRT NO TMP DEST PATH
Source:
NDPS, Library Error
Explanation:
An error occurred while downloading the drivers. No temporary destination path exists.
1245191 0x00130007 NWDP LE PRT WINDOWS RESTART RQD
Source:
NDPS, Library Error
Explanation:
An error occurred while downloading the drivers.
Action:
Restart Windows*.
1310721 0x00140001 NWDP LE COMPARE RESULT LT
Source:
NDPS, Library Error
Explanation:
In a comparison of a:b, the result is that a is less than b.
1310722 0x00140002 NWDP LE COMPARE RESULT EQ
Source:
NDPS, Library Error
Explanation:
In a comparison of a:b, the result is that a is equal to b.
1310723 0x00140003 NWDP LE COMPARE RESULT GT
Source:
NDPS, Library Error
Explanation:
In a comparison of a:b, the result is that a is greater than b.
1310724 0x00140004 NWDP LE COMPARE RESULT NE
Source:
NDPS, Library Error
Explanation:
In a comparison of a:b, the result is that a is not equal to b.
1376257 0x00150001 NWDP LE OTHER NDPS ERROR RETURN
Source:
NDPS, Library Error
Explanation:
The otherNDPSErrorReturnPtr of the accessorRef contains valid data.
7340037 0x00700005 NWDP LE RPC TIMEDOUT
Source:
NDPS, RPC
Explanation:
An RPC timed out trying to communicate.
Possible Cause:
The requested system component is no longer available at the specified address.
Action:
Verify that the requested system component is loaded and functioning properly.
Possible Cause:
A general network packet routing problems exists.
Action:
Verify that the network is functioning properly.
Possible Cause:
An invalid address was used while to trying to communicate with an NDPS system component (Broker, RMS, SRS, ENS, PSM, or PA).
Action:
Contact a Novell Support Provider.
If you are debugging the program, verify that the network address is valid.
7340040 0x00700008 NWDP LE RPC PROGUNAVAIL
Source:
NDPS, RPC
Explanation:
The requested NDPS system component is not loaded or is not functioning properly at the requested address.
Possible Cause:
The requested component is not currently active or is malfunctioning.
Action:
Verify that the requested component is loaded and functioning properly at the indicated address. Verify that the address used is correct.
Action:
If you are debugging the program, verify that the program number and version are correct.
7340042 0x0070000A NWDP LE RPC PROCUNAVAIL
Source:
NDPS, RPC
Explanation:
The function requested is not supported by the version of the NDPS system component that is being addressed.
Possible Cause:
A mismatch between the client and server components of NDPS exists.
Action:
Verify that the latest NDPS components are installed on both the client and server.
Possible Cause:
The implementation of the NDPS component that is being addressed does not support the requested function.
Action:
Contact a Novell Support Provider.
If you are debugging the program, verify that the program number and version are correct.
7340043 0x0070000B NWDP LE RPC CANTDECODEARGS
Source:
NDPS, RPC
Explanation:
The NDPS system component is unable to decode the request that it received.
Possible Cause:
A mismatched version of NDPS exists on the client or server.
Action:
Verify that the client and server have the latest version of NDPS.
Possible Cause:
Packet corruption has occurred.
Action:
Verify that the network is functioning properly.
Possible Cause:
An internal NDPS error occurred.
7340044 0x0070000C NWDP LE RPC SYSTEMERROR
Source:
NDPS, RPC
Explanation:
An unexpected system error has occurred.
Possible Cause:
NDPS failed to initialize the transport layer because the winsock.dll or wsock32.dll file cannot be found.
Action:
Verify that you have the correct version of winsock available in the path, the Windows or Windows system directory and that a correct version is being loaded.
Possible Cause:
The spx_skts.nlm is not loaded on the client.
Action:
Verify that spx_skts.nlm is loaded on the client and that it is the correct version.
Possible Cause:
An internal NDPS error occurred.
7340048 0x00700010 NWDP LE RPC FAILED
Source:
NDPS, RPC
Explanation:
An unexpected error occurred.
Possible Cause:
An internal NDPS error occurred.
1441793L 0x00160001 NWDP LE NIOS INIT FAILURE
Source:
NDPS, Library Error
Explanation:
The nios.nlm failed to initialize. Nios is a component of the Novell Client for DOS or Windows 3.1, Windows 95, and Windows NT.
1441794L 0x00160002 NWDP LE NIOS GET SYSTEMDIR FAIL
Source:
NDPS, Library Error
Explanation:
An attempt to get the system directory for the Novell Client failed.
16777220 0x01000004 NWDP EC STDIO
Source:
NDPS, Library Error
Explanation:
This error indicates that a standard IO error occurred.
Action:
Take the appropriate action for the actual IO error. For the actual error, see the other error codes displayed with this error.
16777221 0x01000005 NWDP EC NDS
Source:
NDPS, Library Error
Explanation:
This error code indicates that an eDirectory or NDS error occurred.
Action:
Take the appropriate action for the actual eDirectory or NDS error. For the actual eDirectory or NDS error, see the other error codes displayed with this error.
16777222 0x01000006 NWDP EC UNICODE
Source:
NDPS, Library Error
Explanation:
This error code indicates that a Unicode error occurred.
Action:
Take the appropriate action for the actual Unicode error. For the actual Unicode error, see the other error codes displayed with this error.
17498119 0x010B0007 NWDP EC NSRV ATTR NOT IN SCHEMA
Source:
NDPS, Library Error
Explanation:
The requested attribute is not in the eDirectory or NDS schema. "Other" error is the index of the attribute object ID within the set of object IDs.
24117251 0x03700003 NWDP EC RPC CANTSEND
Source:
NDPS, RPC
Explanation:
The client workstation is unable to send the request.
Possible Cause:
A network error has occurred.
Action:
Verify that the network is functioning properly.
Possible Cause:
A transport layer error has occurred.
Action:
Verify that the correct versions of the winsock and spx_skts files are loaded.
Possible Cause:
The client handle is already in use at the time the request was made.
Action:
Contact the developer of the application.
Possible Cause:
An internal NDPS error has occurred.
24117252 0x03700004 NWDP EC RPC CANTRECV
Source:
NDPS, RPC
Explanation:
The client or NDPS system component is unable to receive data.
Possible Cause:
A network error has occurred.
Action:
Verify that the network is functioning properly.
Possible Cause:
A transport layer error has occurred.
Action:
Verify that the correct versions of the winsock and spx_skts files are loaded.
Possible Cause:
The client handle is already in use at the time the request was made.
Action:
Contact the developer of the software.
Possible Cause:
An internal NDPS error has occurred.
24117254 0x03700006 NWDP EC RPC VERSMISMATCH
Source:
NDPS, RPC
Explanation:
The version of the DPRPC being used by the client and the requested system component is incompatible.
Possible Cause:
A mismatch exists between the versions of the NDPS client and the NDPS server components.
Action:
Verify that the latest version of NDPS components is installed on the client and server.
24117255 0x01700007 NWDP EC RPC AUTHERROR
Source:
NDPS, RPC
Explanation:
The credential passed was rejected by the NDPS system component that is being addressed.
Possible Cause:
An internal NDPS error occurred.
24117257 0x03700009 NWDP EC RPC PROGVERSMISMATCH
Source:
NDPS, RPC
Explanation:
The version of the NDPS system component that is being addressed does not match what is expected by the client software.
Possible Cause:
A mismatch exists between the versions of the NDPS client and the NDPS server components.
Action:
Verify that the latest version of NDPS components is installed on the client and server.
If you are debugging the program, verify that the program and version numbers are correct.
24117266 0x03700012 NWDP EC RPC INTR
Source:
NDPS, RPC
Explanation:
An NDPS call was interrupted before it completed.
Possible Cause:
The user interrupted the request.
Possible Cause:
An internal NDPS error occurred.
24117268 0x03700014 NWDP EC RPC TLIERROR
Source:
NDPS, RPC, TLI
Explanation:
A Transport Layer Interface (TLI) error occurred.
Possible Cause:
An incorrect version of transport software (On the client dptliwxx.dll, winsock.dll, wsock32.dll, spx_skt.nlm. On the server tli.nlm, spxs.nlm, and streams.nlm).
Action:
Verify that the correct version of the transport software is installed.
Possible Cause:
The transport software was configured improperly.
Action:
Verify that the transport software is configured properly.
Possible Cause:
An internal NDPS or transport layer error occurred.
50331653 0x03000005 NWDP EC NDS WITH POSITION
Source:
NDPS, Library Error
Explanation:
An eDirectory or NDS error occurred. The position of the error is a zero-relative index into the array of attributes that indicates the extent to which modifications succeeded before this failure. If the index is 2, then two modify operations succeeded and a failure on the third stopped any further modifications. The index of 2 indicates that the third attribute in the set caused the eDirectory or NDS error reported by the otherError field.
Action:
Take the appropriate action for the actual eDirectory or NDS error. For the eDirectory or NDS error and its position, see the other error codes and information displayed with this error.
50724865 0x03060001 NWDP EC BROKER RESULT
Source:
NDPS, NDPS Broker NLM program
Explanation:
An error was generated by the NDPS Broker.
Action:
To obtain more information on the error condition, examine the other error codes reported with this error.
50724866 0x03060002 NWDP EC REGISTRY RESULT
Source:
NDPS, libError or N Failure
Explanation:
The SRS encountered an error condition.
Action:
Obtain more information on the error condition by examining the other error codes reported with this error.
50724867 0x03060003 NWDP EC NOTIFY RESULT
Source:
NDPS
Possible Cause:
The error was generated as a result of the ENS encountering an error condition.
Action:
Obtain more information on the error condition by examining the other error codes reported with this error.
50987009 0x030A0001 NWDP EC NO MEMORY
Source:
NDPS, Library Error
Explanation:
The server is out of available memory.
Possible Cause:
The server does not have enough memory installed.
Action:
View the other information displayed with this error to determine how much memory was supposed to be allocated and how much was actually allocated. Then add the required memory to the server.
Possible Cause:
A program is running that is using too much memory.
Action:
Identify the program that is using too much memory and unload it.
85131270 0x05130006 NWDP EC PRT NEEDED FILE MISSING
Source:
NDPS, Library Error
Explanation:
A file needed to download the driver is missing.
Action:
Make sure the needed file is in the specified directory.
85393409 0x05170001 NWDP EC PSM BOUND TO WRONG ONE
Source:
NDPS, Library Error
Explanation:
The bind for a Print Service Manager (PSM) returned the name of a different PSM than the one requested.
85458945 0x05180001 NWDP EC BRK BOUND TO WRONG ONE
Source:
NDPS, Library Error
Explanation:
The bind for the Broker returned the name of a different Broker than the one requested.
85458946 0x05180002 NWDP EC RES BOUND TO WRONG ONE
Source:
NDPS, Library Error
Explanation:
The bind for the Resource Manager returned the name of a different Broker than the one requested.
85458947 0x05180003 NWDP EC SRS BOUND TO WRONG ONE
Source:
NDPS, Library Error
Explanation:
The bind for the Service Registry returned the name of a different Broker than the one requested.
85458948 0x05180004 NWDP EC NTFY BOUND TO WRONG ONE
Source:
NDPS, Library Error
Explanation:
The bind for the Notification returned the name of a different Broker than the one requested.