54.0 PSERVER Messages

The following includes messages from PSERVER.NLM.

PSERVER-X-2: Insufficient memory is available to initialize client communications.

Source: PSERVER.NLM
Possible Cause: The server running PSERVER does not have enough available memory to run the print server.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-4: The program does not have enough available memory to continue.

Source: PSERVER.NLM
Possible Cause: The server does not have enough available memory to run the PSERVER.NLM.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-7: The program cannot create utilization processes.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-8: The program cannot initialize the kernel.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-9: The program cannot create a console process.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-11: The Service Advertising name, name, is already in use by another print server.

Source: PSERVER.NLM
Explanation: All print servers running on the same internet must have unique SAP names.
Possible Cause: Another print server with the same name is already running.
Action: Rename one of the print servers, or change the SAP name using PCONSOLE.

PSERVER-X-13: The program cannot create the advertising process.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-17: The program cannot open the client communications socket.

Source: PSERVER.NLM
Possible Cause: The socket number assigned to the print server for client communications is in use by another process.
Action: Determine which process is using the print servers socket and unload the process. If the problem persists, contact a Novell support provider.

PSERVER-X-18: There is insufficient memory for the print server to add an additional printer.

Source: PSERVER.NLM
Possible Cause: The print server does not have enough available memory for another printer.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-19: The program cannot create client service processes.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-20: All send buffers have been consumed.

Source: PSERVER.NLM
Possible Cause: A network communications error occurred, causing all the print server communication buffers to be consumed without being freed.
Action: Until you can locate the communication problem, unload and reload the print server to reinitialize its communication buffers.

PSERVER-X-26: The program cannot create the down monitor process.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-28: A bad process ID was passed to the kernel.

Source: PSERVER.NLM
Possible Cause: An internal print server error occurred.
Action: Until you can locate the problem, unload and reload the print server to reinitialize its communication buffers.

PSERVER-X-64: Insufficient memory is available to create the main menu. The print server console will be disabled.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-79: The program cannot create the server status form.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-80: The program cannot push the main menu.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-81: Insufficient memory is available to build a NetWare server list.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-88: The program cannot get the object ID for the print server.

Source: PSERVER.NLM
Possible Cause: eDirectory, which must be opened to get object IDs, is locked or corrupted. eDirectory is usually locked only momentarily.
Action: Try printing again in a few minutes. If the error persists, run DSREPAIR.

PSERVER-X-89: The print server is already attached to too many NetWare servers and cannot attach to NetWare server name.

Source: PSERVER.NLM
Possible Cause: A print server queue can be serviced by up to 25 print servers. Twenty-five servers are already attached and servicing this queue.
Action: If the print server needs to service this queue, detach one of the other print servers from the queue.

PSERVER-X-90: NetWare server name is unknown at this time.

Source: PSERVER.NLM
Possible Cause: The uesr might have mistyped the name of the server,
Action: Make sure to type the name of the server correctly.
Possible Cause: The user specified a server that is not on the network.
Action: List all the servers that the workstation can recognize by using NLIST.
Possible Cause: The user specified a server that is down for maintenance.
Action: If the server is down for maintenance, try the command when the server is back up.

PSERVER-X-91: The NetWare server’s bindery is locked. You cannot attach to NetWare server name at this time.

Source: PSERVER.NLM
Possible Cause: The network supervisor locked the bindery for maintenance. Usually this situation is only temporary.
Action: Try the command when the server is back up.

PSERVER-X-92: You cannot attach to NetWare server name because it has no more connections available.

Source: PSERVER.NLM
Possible Cause: The print server needs one connection slot to run. All 100 connection slots are in use.
Action: Wait until a connection slot becomes available. Or, you can use MONITOR to clear a connection.

PSERVER-X-93: NetWare server name does not respond.

Source: PSERVER.NLM
Possible Cause: The specified server is down.
Action: No action can be taken until the server is up and running again.

PSERVER-X-94: You cannot attach to NetWare server name at this time.

Source: PSERVER.NLM
Possible Cause: A network error prevented the print server from attaching to the specified server.
Action: Try again. If the problem persists, contact a Novell support provider.

PSERVER-X-95: The print server has no account balance on NetWare server name.

Source: PSERVER.NLM
Explanation: Accounting is installed on the specified server, but an error occurred that has given the print server a zero balance.
Action: Make sure that you are using a NetWare 4 version or later of NetWare Administrator with the specified server. Either delete the print server and re-create it, or remove accounting and reinstall accounting.

  • To delete the print server, run PCONSOLE, select Print Server Information, and delete the print server from the list. Then re-create the print server.

  • To delete accounting, run NetWare Administrator and select Accounting; then select Accounting Servers. Delete all servers from the list. Press <Esc> and answer Yes to the prompt to remove accounting. Then reinstall accounting.

PSERVER-X-96: The print server has no credit left on NetWare server name.

Source: PSERVER.NLM
Possible Cause: Accounting was installed on the specified server with a version of SYSCON below NetWare 3.11 or NetWare 2.2.
Action: Make sure that you are using a NetWare 4 version or later of NetWare Administrator with the specified server. Then either delete the print server and re-create it, or remove accounting and reinstall accounting.

  • To delete the print server, run PCONSOLE, select Print Server Information, and delete the print server from the list. Then re-create the print server.

  • To delete accounting, run NetWare Administrator and select Accounting, then select Accounting Servers. Delete all servers from the list. Press <Esc> and answer Yes to the prompt to remove accounting. Then reinstall accounting.

PSERVER-X-97: Account on NetWare server name was disabled because of intruder detection.

Source: PSERVER.NLM
Possible Cause: The login property for intruder detection is set. NetWare does not have a program that sets this property for print servers. Either the bindery is corrupted, or you have used a third-party program to set this property.
Action: Complete one of the following:

  • If you have not used a third-party utility to set this property, run DSREPAIR on the bindery server.

  • If you have a third-party program that sets this property, use it to remove the station restriction.

PSERVER-X-98: The supervisor has limited the number of concurrent connections the print server can have on NetWare server name.

Source: PSERVER.NLM
Possible Cause: The print server reached the allowed limit for concurrent connections to the file server.
Action: Wait until another user logs out, or free a connection using MONITOR.

PSERVER-X-99: The supervisor has disabled the print server’s account on NetWare server name.

Source: PSERVER.NLM
Explanation: The print server no longer has an account on the server.
Action: If you have appropriate rights, establish a new account for the print server.

PSERVER-X-100: Login was attempted at an unauthorized time. The supervisor on NetWare server name has limited the times when the print server can log in.

Source: PSERVER.NLM
Explanation: Specific time periods have been established when you can use the print server. You cannot use the print server until the next authorized time period.
Action: Give the user a list of authorized time periods.

PSERVER-X-101: Login was attempted from an unauthorized station. The supervisor on NetWare server name has limited the stations the print server can log in from.

Source: PSERVER.NLM
Explanation: The user tried to access a print server from an unauthorized workstation. A network supervisor can limit login access to a print server to one or more workstations.
Action: Make sure the user attempts to access the print server account only from authorized workstations.

PSERVER-X-102: The password on NetWare server name has expired. All grace logins have been used. Access is denied.

Source: PSERVER.NLM
Explanation: The login properties that force expiration of passwords and limit grace logins have been set. NetWare does not have a program that sets these properties for print servers. Either the bindery is corrupted, or a third-party programhas been used to set this property.
Action: Complete one of the following:

  • If a third-party program has been used to set this property, use it to remove the login properties.

  • Change the print server’s password, using using NetWare Administrator.

PSERVER-X-103: The supervisor on NetWare server name has disabled logins.

Source: PSERVER.NLM
Possible Cause: The user’s account is locked. The network supervisor can disable the login function temporarily to prevent users from logging in or attaching during maintenance. Most likely, the network supervisor is doing maintenance work.
Action: This condition is usually only temporary. The user should be able to log in after the login function is enabled. Meanwhile, the user can attach to another server and use its printer.

PSERVER-X-105: The print server’s password on NetWare server name has expired. Please change it.

Source: PSERVER.NLM
Possible Cause: The password for logging in to the print server must be changed periodically. The time period for using the current password expired.
Action: If you are an authorized print server operator or network supervisor, change the password.

PSERVER-X-106: Access to NetWare server name denied. Either there is no account for this print server on the NetWare server, or the password was incorrect.

Source: PSERVER.NLM
Action: Type the print server’s name and password correctly.

PSERVER-X-107: You cannot log in to NetWare server name at this time.

Source: PSERVER.NLM
Explanation: The specified server returned a condition that prevented the print server from logging in to the server.
Action: Try again later. If the problem persists, contact a Novell support provider.

PSERVER-X-108: The print server is already attached to NetWare server name.

Source: PSERVER.NLM
Explanation: You tried to attach to a server that you are already attached to.

PSERVER-X-110: The program cannot create the user interface because of problems in the current environment.

Source: PSERVER.NLM
Explanation: The print server might not have enough available memory to initialize.
Action: Reduce the number of printers configured, queues serviced, or users notified. Or, increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-111: Insufficient memory is available for the buffer for printer number, name. The printer was not initialized. Requested buffer size was number KB.

Source: PSERVER.NLM
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-112: Insufficient memory is available to initialize printer number, name.

Source: PSERVER.NLM
Possible Cause: The server that is running PSERVER does not have enough available memory to do one of the following:

  • Run the print server.

  • Service remote printers.

  • Add services.

  • Add the specified user to the notify list of the specified printer.

  • Add the specified printer.

Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-113: The program cannot read the configuration file for printer number. The printer was not initialized.

Source: PSERVER.NLM
Possible Cause: The configuration file for the specified printer is corrupted.
Action: Delete the printer from the print server and re-create the printer.

PSERVER-X-114: Printer number, name, is of an unknown type. The printer was not initialized.

Source: PSERVER.NLM
Explanation: The eDirectory for the specified printer might be corrupted.
Action: Run DSREPAIR.

PSERVER-X-115: The program cannot create the printer driver process for printer number, name. The printer is not initialized.

Source: PSERVER.NLM
Explanation: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-123: Network printer communications are not initialized. Network printers cannot be installed. Printer number, name was not installed.

Source: PSERVER.NLM
Explanation: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-124: The program cannot open a socket for network printer communications. Network printers will not be initialized.

Source: PSERVER.NLM
Explanation: The socket assigned to the print server for communication with remote printers is in use by another process.
Action: Find the process that opened the print servers communication socket and unload it.

PSERVER-X-125: Insufficient memory is available to initialize network printer communications. Network printers cannot be installed.

Source: PSERVER.NLM
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-127: Print queue name is unknown. The print queue will not be serviced by printer number, name.

Source: PSERVER.NLM
Possible Cause: The specified queue was deleted, but the specified printer’s configuration file was not modified to reflect the deletion.
Action: Either re-create the queue or delete the queue from the printer’s configuration file.

PSERVER-X-128: Print queue name was not added to the list of queues to be serviced by printer number, name, because it was already in the list.

Source: PSERVER.NLM
Explanation: Two queues in the list of queues to be serviced have the same name.
Action: Delete the duplicate queue named in the list.

PSERVER-X-129: Print queue name cannot be serviced by printer number, name, because a print queue operator has disabled print servers from attaching to the print queue.

Source: PSERVER.NLM
Possible Cause: A print server operator set the Servers Can Service Entries in Queue option in PCONSOLE to No. This prevents print servers from attaching and servicing the specified queue.
Action: Run PCONSOLE and set the Servers Can Service Entries in Queue option to Yes. This allows print servers to attach and service the queue.

PSERVER-X-130: This print server is not authorized to service queue name. Queue will not be serviced by printer number, name.

Source: PSERVER.NLM
Explanation: The print server must be authorized by the network supervisor to service print queues.
Action: Authorize the print server to service the desired queue.

PSERVER-X-131: Print queue name cannot be serviced by printer number, name, because you have already reached the maximum number of print servers that can be attached to the print queue.

Source: PSERVER.NLM
Action: Detach one of the print servers from the queue.

PSERVER-X-132: Print queue name cannot be serviced by printer number, name.

Source: PSERVER.NLM
Explanation: The server returned a condition that prevented the specified queue from being serviced by the specified printer.
Action: Try again. If the problem persists, contact a Novell support provider.

PSERVER-X-133: Insufficient memory is available to add queue name to printer number, name. The queue will not be serviced by this printer.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-137: Insufficient memory is available to create a printer list.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-164: The program cannot save the printer list.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-165: The program cannot create the printer status form.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-172: Insufficient memory is available to create a queue list.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-174: The program cannot create network printer communications processes.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-176: Insufficient memory is available to get an IPX socket resource tag for print server communication.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-178: Insufficient memory is available to get an alloc resource tag for the print server interface.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-179: The program cannot create a background process.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-180: Insufficient memory is available to get a polling resource tag for the print server.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-182: Insufficient memory is available to get an interrupt resource tag for the print server.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-183: An error occurred during attempt to write to the audit file name. The entry was not logged.

Source: PSERVER.NLM
Possible Cause: The print server has insufficient rights to the file or directory containing the log file.
Action: Determine where the print server is keeping its audit file.
Possible Cause: The directory that contained the file has been deleted.
Action: Make sure the directory exists and that the print server has sufficient rights to write to the directory and file.
Possible Cause: The file is flagged so that it cannot be written to.
Action: Make sure the file is not flagged Read Only.

PSERVER-X-184: Insufficient memory is available to get a resource tag for printer ports.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-185: The print server received error code during attempt to log in to the network. Access to the network was denied. Verify that the print server name and password are correct.

Source: PSERVER.NLM
Possible Cause: The user probably specified an invalid print server name or password.
Action: Try again, making sure that the print server is running and that you type a valid print server name and password. For information about the error code displayed, search the Error Codes online documentation.

PSERVER-X-186: Insufficient memory is available to get an AES event resource tag.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-190: Insufficient memory is available to add a new print queue.

Source: PSERVER.NLM
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-191: The program cannot save the current print queue list.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-205: Insufficient memory is available to add usertype username to the notification list for printer number, name.

Source: PSERVER.NLM
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-214: The print server was unable to login to server name specified in the print server’s Directory Services attribute list as the host device. Warning, the job audit logging feature may not function properly.

Program execution may not continue normally.

Source: PSERVER.NLM
Possible Cause: During login, if the server that contains the audit files is not available, this message will appear. If the user ignores the message, everything will proceed normally, but auditing will not be enabled.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-217: The print server could not get a Directory Services context handle. Error code: code.

Source: PSERVER.NLM
Explanation: eDirectory returned an error to PSERVER during an attempt to establish a context handle.
Action: For information about the error code displayed, search the Error Codes online documentation.

PSERVER-X-224: The program cannot initialize the notification process. Error notices will not be sent to users.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-228: Insufficient memory is available for the print server to service print jobs at this time.

Source: PSERVER.NLM
Possible Cause: The print server might not have enough available memory to initialize.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-240: Invalid or missing printer configuration information was specified for printer name.

Source: PSERVER.NLM
Explanation: The print server was unable to interpret the configuration information for the printer.
Action: Reconfigure the printer, or delete and add it again.

PSERVER-X-241: An error (code) occurred during attempt to add print queue name. This queue will not be serviced by printer_number, printer_name.

Source: PSERVER.NLM
Action: For information about the error code displayed, search the Error Codes online documentation.

PSERVER-X-242: An error (code) occurred during attempt to add object name to the notification list. This object will not be notified of printer errors for printer number, name.

Source: PSERVER.NLM
Action: For information about the error code displayed, search the Error Codes online documentation.

PSERVER-X-247: Attempt to add printer name as printer number failed. A printer already exists with that number.

Source: PSERVER.NLM
Possible Cause: The print server is configured to service two printers with the same number. Each printer serviced by the print server must have a unique number for that print server.
Action: Change one of the printers’ numbers.

PSERVER-X-268: There is insufficient memory for the print server to complete the requested task.

Source: PSERVER.NLM
Possible Cause: The print server does not have enough available memory.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-269: An error occurred attempting to read the audit file name. The audit file may be corrupted.

Source: PSERVER.NLM
Possible Cause: The file might be corrupted.
Action: If you suspect file corruption, delete the file; then enable audit tracking again.
Possible Cause: The print server has insufficient rights to the file or directory where it keeps its log file.
Action: Determine where the print server is keeping its audit.
Possible Cause: The file is flagged so that it cannot be written to.
Action: Make sure the file is not flagged Read Only.
Possible Cause: The directory where the print server configuration file is located has been deleted.
Action: Verify that the directory exists and that the print server has sufficient rights to write to the directory and file.

PSERVER-X-275: The print server encountered an error (code) while attempting to set a Directory Services context handle.

Source: PSERVER.NLM
Action: For information about the error code displayed, search the Error Codes online documentation.

PSERVER-X-276: There is insufficient memory to browse the directory.

Source: PSERVER.NLM
Possible Cause: The server does not have enough available memory.
Action: Increase the memory available at the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

PSERVER-X-277: The print server encountered an error (code) attempting to read a Directory Services context.

Source: PSERVER.NLM
Action: For information about the error code displayed, search the Error Codes online documentation.

PSERVER-X-278: The print server encountered an error (code) while attempting to search the directory.

Source: PSERVER.NLM
Action: For information about the error code displayed, search the Error Codes online documentation.

PSERVER-X-279: The print server encountered an error (code) while attempting to access the directory.

Source: PSERVER.NLM
Action: For information about the error code displayed, search the Error Codes online documentation.

PSERVER-X-280: The print server was unable to build a list of objects in the directory. An unexpected Directory Services error occurred while attempting to read the directory.

Source: PSERVER.NLM
Action: Run DSREPAIR.

PSERVER-X-999: The message file for this NLM cannot be found.

Source: PSERVER.NLM
Action: See message 999: The message file for this utility cannot be found..